Server Requirement Error

[tantrum]

Hi sorry if this a repetition of another post, but I have searched the forum high and low for an answer to this, and i'm sure its pretty simple... but... i'm tearing my hair out at the moment. I have installed osCommerce via an autoinstallation "Fantastico" area of my Bluehost hosting package. I have installed osCommerce before and customised it.. and am pretty compitant at following instructions etc... but just can't seem to crack this one! When I try and log into the admin section I get the following message.

 

"Server Requirement Error: register_globals is disabled in your PHP configuration. This can be enabled in your php.ini configuration file or in the .htaccess file in your catalog directory."

 

I have looked in the .htaccess file and the php.ini files in all directorys and ensured all the numbers are correct...

 

I also tried installing the following contribution http://www.oscommerce.com/community/contri...egister_globals

 

.... which just gave open access to my admin files... which I do not want... The admin username and password was still shown in the password protect directory section.. but just seems to bypass it.

 

Anyone that can help me?

[Webtytte]

Hi sorry if this a repetition of another post, but I have searched the forum high and low for an answer to this, and i'm sure its pretty simple... but... i'm tearing my hair out at the moment. I have installed osCommerce via an autoinstallation "Fantastico" area of my Bluehost hosting package. I have installed osCommerce before and customised it.. and am pretty compitant at following instructions etc... but just can't seem to crack this one! When I try and log into the admin section I get the following message.

 

"Server Requirement Error: register_globals is disabled in your PHP configuration. This can be enabled in your php.ini configuration file or in the .htaccess file in your catalog directory."

 

I have looked in the .htaccess file and the php.ini files in all directorys and ensured all the numbers are correct...

 

I also tried installing the following contribution http://www.oscommerce.com/community/contri...egister_globals

 

.... which just gave open access to my admin files... which I do not want... The admin username and password was still shown in the password protect directory section.. but just seems to bypass it.

 

Anyone that can help me?

 

Have you tried visiting your web host homepage and logging into the admin panel for your site? I did that and there was a setting to either set register globals to on or off..

 

Regards

Webtytte

[AlanR]

Read the contribution.txt file that's in the Register Globals Patch Contribution.

 

The code you're using for the protection is relying on POST or GET variables that are not being read now since they're globals.

 

One (simple) fix to call a function that's included in the package's functions/general.php file so they are read and defined.

 

It's link_post_variable

[tantrum]

Read the contribution.txt file that's in the Register Globals Patch Contribution.

 

The code you're using for the protection is relying on POST or GET variables that are not being read now since they're globals.

 

One (simple) fix to call a function that's included in the package's functions/general.php file so they are read and defined.

 

It's link_post_variable

 

 

Thanks thats very helpful. I didn't realise there was a second patch... i'm a bit of a php newbie anyway so all this code is frying my head really!! I think I better get myself a book! All this POST and GET and things.... i'm sure its simple enough if you understand it!

 

I'm not sure if the first patch worked... it seemed to look like it didn't require a login... but I think my browser was maybe storing the password etc.. I tried it on another pc after starting from scratch with the patch you suggested, and it works fine.. just some fine tuning on the contributions now!! Then time to start modifying :thumbsup:

 

Still have no idea if it is my bluehost hosting package... my bad coding... or stupidity... ho hum!

 

Thank goodness for forums and helpful people! :thumbsup:

[AlanR]

I'm not sure if the first patch worked... it seemed to look like it didn't require a login... but I think my browser was maybe storing the password etc..

If you need to test something that requires a password always quit your browser and restart it before you test again. A .htaccess authentication persists for example.