Akinraze

lost

solution found here: http://friendsofed.infopop.net/2/OpenTopic...165&m=324102421

after what dmarchman said about this being a well know problem, i was so ticked i could have spit bullets, so I headed on over to macromedias site and after several pages of searching I ran accross this article/tutorial http://www.macromedia.com/devnet/mx/dreamw...h_users_08.html Copy paste from the bottom of the page: Note: PHP users with PHP 4.2 and higher will be disappointed to learn that instead of being redirected to the originally requested page after log-on, the application sends them to the home page. The reason for this is that the server behavior that is supposed to cause the redirection to the originally requested page relies on a configuration setting, register_globals, that must be on for redirection. Since PHP 4.2, the default setting for register_globals is off. You can go into your php.ini file and change it to on and the site will work as expected. However, it was turned off for a reason—this setting creates a potential security hole in PHP. Thus, before you decide to go into php.ini and change the setting, I recommend that you research the issue on the web. in my case, this IS the issue, I am sure the ISp that houses my site won't concider changing this setting so I didn't change it on mine to verify (but probably should just for sake of knowing for sure). I installed 5.0.4 on my system for production and went into the my php.ini and sure enough: register_globals = Off, s i think I can pretty much say that this IS the problem, I think I will focus on studying the tutorials here on the site to get mine working now. goodluck!

lost

What was the script you turned to? I am having the same problems now.

Would there be any possibility to make a script that would call the access level if it was automatically generated, then grant access per that level? I am looking to completely automate the site, no intervention after site completion other than maintainance. See, I would have went this route with Dreamweavers built in restrictions, but I would have to enter in a level for every member, then set the access for every page the member may access, and if the site ends up getting thousands of members, this would end up becoming a full time job if i went this way. What I am trying to say is, I wouldn't want to set the ability in every members hands to edit every other members submissions based on a two level access restriction. Thanks

Hello all, 1st time poster here and newbie all around. I am in the midst of making a dynamic php site for World of Warcraft, i have most of the forms to enter data into the database made and am starting to think about the security for the members data. I want to be able to let a member come back to the site to check more checkboxes when they need to, but only let the meber who submitted that form be able to edit it. The site is up for testing at www.google.com security to access submission pages is not setup yet, as I was waiting to do the above mentioned method, so if you notice there are not sufficient mesures in place, thats why. If you go there to test, after registering, do not try submitting to Leatherworking or Tailoring, those 2 are not uploaded yet. To view the data after submitting, go to the home button (top left) then select View database, then the profession you submitted to. all that should be enought for you to get an idea of how I want and need the secuirty features setup. So if anyone could point me the right direction, i would be greatful, as i don't "think" that the default restrictions in DW:MX 2k4 is enough to do this...?!?! Thanks Akinraze