View Full Version : admin/updateversion201.php
yosemite
7th of October 2006 (Sat), 12:41
in the upgrade package to 2.01 it says;
Open admin/updateversion201.php to change your EE's version number to 2.01
how do you do this? mine still says 2.0
Pekka
7th of October 2006 (Sat), 13:38
Browse to the file.
http://www.yoursite.com/yourgallery/youradmin/updateversion201.php
yosemite
7th of October 2006 (Sat), 13:43
thank you, that makes sense.
so far so good, i am at the retrieve photo sizes section
as far as the register_globals goes it still register_globals=on at my login. i have this in the root
register_globals = off
post_max_size = 20M
memory_limit = 80M
upload_max_filesize = 20M
max_execution_time = 120
expose_php=off
allow_url_fopen = off
does this need to be in the ee directory?
dzilk
8th of October 2006 (Sun), 21:24
I have the same settings in my php.ini (both in the root and the EE directories). I also am still seeing the register_globals=on and allow_url_fopen = yes when doing the install check.
.htaccess doesn't seem to work for me either.
Any ideas?
David
DavidW
9th of October 2006 (Mon), 04:27
It does depend on the server and PHP configuration. In some cases, the only way to control either of these things is in the system's default php.ini.
In the sort of Apache 1 environment on UNIX my hosting provider is using (which is typical for those still using Apache 1, as my hosting provider is, for various reasons), register_globals can be controlled in .htaccess using the line:
php_flag register_globals off
With Apache 2, this 'knob' usually doesn't work though
php_value register_globals 0
might (you may need to wrap it in an appropriate <Directory ...> </Directory> structure). In fact, that works with the Apache 1 setup I use.
Nothing can be done about allow_url_fopen - that can only be controlled in php.ini and won't be changed on the hosting cluster at my provider because it would cause too many regression issues. It's one of the old issues with security - security related updates breaking existing code. Some hosting setups allow 'local' php.ini files, but many don't.
When I get my debugging setup running on my server, it will be Apache 2.2 and the latest PHP 5 set with security to the maximum (so register_globals and allow_url_fopen both off) - that way, I can test any PHP code I'm going to use in a maximum security environment.
Different providers use different setups - this really is a question for your hosting provider. If you have a dedicated server (virtual or not) or a dedicated instance of Apache / PHP, edit your php.ini according to the PHP instructions.
Hopefully Pekka will split this thread, as this isn't an issue to do with updateversion201.php.
David
vBulletin® v3.6.12, Copyright ©2000-2012, Jelsoft Enterprises Ltd.