Re: question on <?php and $HTTP_POST_VARS (possibly unrelated)

On Friday 23 May 2003 00:11, Jason Jacobs wrote: > I took a site I built on another server and only ever used <? to designate > my php and never ever used $HTTP_POST_VARS (or GET), nor did I refer to > session variables as anything but $sessionvar. All these are the old (not recommended) way of doing things. They are all still useable if you set php.ini accordingly. > In fact, a package I > downloaded had all passed variables referred to with $HTTP_GET_VARS['foo'] > and it didn't work. I had to take that out and refer to it only as $foo. Can you reproduce this in a small self-contained example? > On this new server, my code broke. The guy who set up the server said the > <? needed to be changed to <?php, so he grep-ed it and changed those. Then > I found that variables weren't being passed to other pages, but they did > once I added $HTTP_GET_VARS. > > I thought this was a configuration thing in Apache, or PHP at least. I > also thought <?php was the "old" way and you didn't need that anymore. Both <?php & <? are valid and can be set in php.ini > Is it possible to easily allow this server to accept "naked" > variables and <? only? Thanks for your help. Read php.ini. Many of these changes were made to make things more secure. You had best read the changelog, history, release notes to find out why things are the way they are now. All these have been covered in the archives, the manual and probably numerous online articles as well. -- Jason Wong -> Gremlins Associates -> www.gremlins.biz Open Source Software Systems Integrators * Web Design & Hosting * Internet & Intranet Applications Development * ------------------------------------------ Search the list archives before you post http://marc.theaimsgroup.com/?l=php-general ------------------------------------------ /* All the evidence concerning the universe has not yet been collected, so there's still hope. */