Quote:
Originally Posted by rattlsnak
Well, that would work if all the data was going to represented the same way, but it isnt. Like one guys wants pictures of his roof, one guys wants inspection dates, one guys wants etc,. so basically all the pages they want would be different, so I would need to have each user be directed to a certain page. (like user 1 would only have access to pages - user1.html, user1a.html, user2 would only have access to pages- user2.html, user2a.html, and so on)
That make sense?
|
are the pages for the users static pages or are they generated dynamically? I'm sort of getting the impression they are static.
If static, get the login name fron a db table of valid usernames and file names, check if valid, write a cookie of the username, and grab the associated static file name and redirect to that... write out a list of his other available pages for navigation as returned from the user table. run a check on that users page against the username cookie value to kick out if someone types in that url directly.
other option would be to use an 'include' of the users static page from a file location beneath the root level or something like that, but you have to deal with the navigation somehow.
interwebs coding is srs bsns