BloggerSavvy
Member
Posted 3 years ago #
When I use the Automatic Upgrade feature in WP 2.7, I am asked to input the appropriate ftp credentials. After submitting them, there is a long wait, then the browser displays a message that says:
-------------------------------------------------------------------
"You have chosen to open update-core.php which is a PHP script from http://xxxxxxxxx.xx What should Firefox do with this file? Open with xxxx Save file"
-------------------------------------------------------------------
IE repeats the same issue. This did not occur (that I remember) prior to 2.7. I can duplicate this on different domains and different servers.
Does anyone have a fix - please?
BloggerSavvy
Member
Posted 3 years ago #
Update
Using htaccess to:
php_value max_execution_time 18000
php_value max_input_time 18000
Does not resolve the issue.
Changing php.ini to allow:
max_execution_time = 18000
max_input_time = 18000
memory_limit = 256M
Does not resolve the issue.
Using the plugin or the built-in feature from WP 2.7? It sounds like you mean the built-in, but I want to be sure :)
What browser (IE version what?)?
What host?
BloggerSavvy
Member
Posted 3 years ago #
@Ipstenu - Using the built-in feature from WP 2.7
Using both Firefox and IE (same issue with all). Host is Linux.
Your web host may not work with the 2.7 upgrader.
There's a list here: http://codex.wordpress.org/Core_Update_Host_Compatibility
Has all the ones that work, those that don't, etc.
BloggerSavvy
Member
Posted 3 years ago #
@Ipstenu - Thanks! Nice resource link! Do you know where I can find the information so that I can make a server compatible with the Core Update feature? If so, I could probably use SSH to make the necessary changes. Appreciated, thanks! :)
Sadly, I've never found the specifics for how it works. Though... Have you tried SFTP instead of FTP for the upload?
http://codex.wordpress.org/Version_2.7#WordPress_Upgrader and http://core.trac.wordpress.org/ticket/5560 may shed some light.
BloggerSavvy
Member
Posted 3 years ago #
I got a fix!
Change PHP to run as CGI - Then upgrade works.
It would be nice if WP coders looked at this issue so that those who have PHP as an Apache module (DSO), won't run into this issue.