Updating from 4.1 to 4.1.1 fails after submitting FTP credentials - returns blank page

[remi123]

​https://wordpress.org/support/topic/wordpress-upgrade-from-41-to-411-blank-screen?replies=25#post-6588690

Quote:

The screen turns blank after submitting the FTP credentials. (​screenshot)

WP_DEBUG shows nothing and the solution ​mentioned above (FS_METHOD) returns "Could not create directory. Installation Failed". (​screenshot - Dutch message)

Switching to the default language (en_US) also results in "Could not create directory. Installation Failed".

Sidenote; updating manually works fine (so far) but that's not a solution.

Current workaround (no permanent solution) to successfully run the update:
​https://wordpress.org/support/topic/cant-upgrade-vom-41-to-411?replies=10#post-6589194

Quote:

Add (and edit) these lines to your wp-config.php:

define( 'FTP_USER', 'ftpusername' );
define( 'FTP_PASS', 'ftppassword' );
define( 'FTP_HOST', 'ftp.hostname.net:21' );

Add them just before /* That's all, stop editing! Happy blogging. */

Delete those 3 lines out of your wp-config.php once the update is finished.

[remi123]

Blank page after submitting the FTP credentials to run the 4.1.1 update

[remi123]

"Could not create directory. Installation Failed" message after adding "define('FS_METHOD', 'direct');" to wp-config and run the 4.1.1 update

[remi123]

The second attachment may be ignored.
It is the result of a ​suggested (temporary) solution. It's not the cause of the 'blank page'.

[Censorshipiswrong]

Replying to DrewAPicture:

and the work around here is not working at all. I am on Hosting Matters.

[lesbell]

Hi,

I had this problem today on one website today (Apache Web Server)

Changing wp-config.php as set out above worked for me (after I remembered to change the details to mine!)

Les Bell

[dd32]

A bug is present in 4.1 which has resulted in $_POST['version'] not being passed through the FTP credentials screen, and as a result, it fails to find a update package to use, and returns early with a blank screen..

I've just deployed a change to api.wordpress.org which should work around this, with the downside that the Update screen will display a duplicate update offering on the update screen.

If you're still running 4.1, and affected by this, please try updating again from Dashboard -> Updates?

[mcpace]

That worked for my two multi sites that were getting blanks. Thanks!

Replying to dd32:

A bug is present in 4.1 which has resulted in $_POST['version'] not being passed through the FTP credentials screen, and as a result, it fails to find a update package to use, and returns early with a blank screen..

I've just deployed a change to api.wordpress.org which should work around this, with the downside that the Update screen will display a duplicate update offering on the update screen.

If you're still running 4.1, and affected by this, please try updating again from Dashboard -> Updates?

[nacin]

Thanks for testing, remi123. While @dd32 made an API change to mitigate this issue, we still need to fix WordPress itself.

[longjorn]

It's working for me now by using the first of the two update entries.
Tested on two different servers.
Thank you!

[andrebron]

Interesting situation for me... Dev site updated fine, but production site does not. They are on 2 different servers running same OS, permissions and such. Disabled firewalls...

Tried adding/removing (FS_METHOD). No go for me.

Manually updating WordPress Core files does not work either. Very strange.

After manually updating all core files (except wp-content), Admin Dashboard still not updating. Some db update issue perhaps?

Updating to Core 4.1.1 tries the update, then no errors are shown, then refreshes back to the updates screen without having completed the update to Core 4.1.1.

@dd32 What Core file has $_POST['version'] set to pass to the FTP credentials screen?

Replying to dd32:

A bug is present in 4.1 which has resulted in $_POST['version'] not being passed through the FTP credentials screen, and as a result, it fails to find a update package to use, and returns early with a blank screen..

I've just deployed a change to api.wordpress.org which should work around this, with the downside that the Update screen will display a duplicate update offering on the update screen.

If you're still running 4.1, and affected by this, please try updating again from Dashboard -> Updates?

[andrebron]

Side note, perhaps not related to this bug, but very interesting... Seemed to be a server side issue for me with php5-fpm on Debian 7. Probably after a php-fpm update...

Reloading php-fpm daemon resulted in the Core 4.1.1 update being applied and the following error showing up on the updates screen below Admin dashboard top menus bar:

Warning: mysql_connect(): Headers and client library minor version mismatch. Headers:xxxxx Library:xxxxx in /var/www/spectrohost/web/wp-includes/wp-db.php on line 1416

This warning can be resolved by installing and using php5-mysqlnd:

apt-get install php5-mysqlnd

[dd32]

In 31527:

Upgrades: Specifically pass the 'version' and 'locale' POST vars through the Core Update FTP credentials form.
This bug was introduced with [30384] / #30245
Fixes #31378 for trunk.

[dd32]

In 31528:

Upgrades: Specifically pass the 'version' and 'locale' POST vars through the Core Update FTP credentials form.
This bug was introduced with [30384] / #30245.
Merges [31527] to the 4.1 branch.
Fixes #31378.