pdillon809

@apputvikleren Yes, deactivating the plugin to be updated appears to work.

I’ll add my name to the list. Can’t update plugins with 4.2
…./wp-admin/update-core.php
…./wp-admin/plugins.php

neither method works. 2 different plugins have save problem.

Adding my credentials to wp-config.php worked for me too

Same problem here. I tried auto updating 5 different sites from 4.1 to 4.1.1 on the same machine. 4 failed and one succeeded. Never had an issue with auto upgrades on these sites before.

Two of the failed-update sites display the nag message “An automated WordPress update has failed to complete – please attempt the update again now.”, two don’t. The hidden file .maintenance is not present in the root of the nag message sites.

You’re welcome.

I believe it’s usual practice to leave debug set to “false” on production sites. “True” is usually set for development. So, you can leave it set to false without problems.

I believe you should be able to remove the error notice by changing the debug parameter in your site’s wp-config.php file.

Look for this line:
define(‘WP_DEBUG’, true);
and change it to:
define(‘WP_DEBUG’, false);

I also have the same error when I set the debug to true. It has been the case over several of the last versions of the plugin. The updates did not fix it for me.

-paul

One workaround is to check if your debug value is set to true of false in wp-config.php

Change
define(‘WP_DEBUG’, true);
to
define(‘WP_DEBUG’, false);

Any answers on this? I had to revert back to an earlier version of the plugin.

I have this problem too

Here’s the solution that worked for me.

Hope this helps.

OK, I tracked down the issue (in my case).

I disabled all plugins – wasn’t the issue. Changed from child to parent theme and sitemaps worked.

So you could switch themes to isolate the issue – if you aren’t using child themes.

Many solution suggest checking for whitespace between the php tags in your theme files. I had done this previously but (I guess) not thoroughly enough. This took some time.

Issue is resolved for me.

Any word from the developers on this?

I have the same issue and posted in a separate thread. Not had any suggestions yet.

I sent a copy. Not sure about a name but I’ll think of a couple of suggestions.

thanks

-paul

Entering wp-login.php does stop the loop and brings up the login box but isn’t helpful in our instance.

Resurrecting the old version would be much appreciated. There may be others who also are using BuddyPress in conjunction with a membership plugin – I saw numerous posts on this subject when I was developing the site. We need multiple levels of access for the WP parts of the site so a membership plugin is required. WLM recognizes bbpress forums but not BuddyPress. Other membership plugins that do recognize BuddyPress had other issues that wouldn’t work for us.

Your original plugin worked well for us and continues to do so.