Hello I'm new here, nice to meet you!
I come with problems: I'm using a new server's php and I don't have rights to change php.ini or anything else, so I don't know if this can be solved.

I tried to write a simple HTML form to submit search-engine data to the php page, and tested for its presence via the $_POST array entry. This didn't work and I was confused so tried it on my friend's php installation, which I know it works on. And it did, so I searched online for a similar problem and found a thread on this site talking about $HTTP_POST_VARS, which I've never used.

I'm going to go look up the difference between $POST and the other one now, but does someone off the top of their head know why $HTTP_POST_VARS worked on the new server but $POST didn't? It seems like they would need the same sorts of parameters enabled, no?

    Might want to check the version of PHP that is installed on the server, because it may just be that it's old. $HTTP_POST_VARS is deprecated in favor of $_POST...at least most times... o_O

      Yes! Thanks it looks like I did that just as you wrote back and sure enough, it's 4.0.4 and this is before the $_BLAH variables came into effect. I should get used to learning about obstacles like this since not everyone is going to already have exactly what my familiar server has...

        with things like that its better to just tell people your scripts requires php version 4.x.x instead of trying to program using $HTTP_POST_VARS. this helps keep people updating their php installs so they always have the latest fixes and it makes your life easier. thats what a majority of large scripts do anyway.

          Yeah I know, that is generally much better but in this case I have to be the one to conform because not only can I not change anything but the server belongs to a large group of sites and would be slow to change, so I guess the best I could do is basically write the people nicely suggesting it...
          the first thing I wanted to change about php on the server was enable XSLT support. At least the $_POST error has a simple fallback plan, unlike this ;]

            Write a Reply...