kafkas-prag.de

Try this fix:
https://www.ads-software.com/support/topic/cant-update-from-42-to-421?replies=15#post-6886150

Alright, I’m taking the plunge now and will check immediately.

Update went through as expected, this is what file.php, line 149 looks like right. So it’s finally fixed:
https://www.ads-software.com/download/release-archive/
I double-checked the .zip. The file.php in the update package is okay.

For future reference:
4.2.0 and 4.2.1 both contained a buggy file.php
4.2.2 is fixed.

Here is to hoping that they hid yet another bug in 4.2.2 which came out this morning.

Actually, I’m hesitant to update my WordPress site now.
They managed to fuck up 3 recent updates that could only be solved by digging through the support forums and would’ve left my site unupdateable if I hadn’t manually edited some obscure files.

@rypher21:
Don’t tell me
wp-admin/includes/file.php
in 4.2.2 is broken again?

How about you drop a link to your page?
If your site is stuck in maintenance mode, you can put an end to that by deleting the .maintenance file on your FTP.

Had the same problem going from 4.2 to 4.2.1
This helped:
https://www.ads-software.com/support/topic/cant-update-from-42-to-421?replies=11#post-6886150
(Backing up your database and FTP files is a good idea before any update, always)

This trick also helped with updating WordPress from 4.2.0 to 4.2.1.
Thanks a lot.

Oh, one more thing:
4.2.1 still contains this bug.
So right after the update from 4.2 to 4.2.1 you have to do the same thing again to ensure that you’ll be able to make the next update to 4.2.2

I came across a solution after searching up and down through this forum by total accident.
(Thanks btw to the moderator who deleted more than a dozen replies to my posting by people who are suffering from the very same problem).

Modify wp-admin/includes/file.php -> line 149

if ( empty( $filename ) || '.' == $filename ) {
by replacing it with:
if ( empty( $filename ) || '.' == $filename || '/' === $filename ) {

After editing my file.php, the update went through smoothly, but it goes to show how rushed 4.2.1 was.
If you wanna read up on the backgrounds, you can do so here:
https://www.ads-software.com/support/topic/unable-to-update-plugins-after-upgrade-to-42?replies=33

Okay, I did as #12 remi123 suggested and it worked.
But how come I had to add those lines while the 4.1.1 upgrade worked flawlessly for others?

I also noticed that there are a couple more lines under the official “end” in my wp-config.php:

/* That's all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
	define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');

@ron:
Link or screenshot pls.