There is a link to close the message in the box on the right.
Thread Starter
Li-An
(@li-an)
I know but each time I go to the page, there is the message… EACH TIME.
That message is annoying and as such is, arguably, against #5 of the plugin guidelines.
@philipjohn Do you see the same behavior as Li-An does?
You’re right, it would be a violation of the plugin guidelines, but that message is supposed to disappear forever after it has appeared once. No need to click anywhere, it appears once, you navigate somewhere else, and it’s gone.
It should remain gone, because the option backwpup_about_page gets the value 1 once the redirect has taken place. That option value should not be touched during an update, so the page should not appear again.
The fact that it re-appears in Li-Ans installation is an erroneous behavior, maybe even a bug we’re going to try to fix here as quickly as possible. The re-appearance of that page is in no way intended by the plugin authors.
Update: I’m seeing in the forums Li-An is not the only one. We’re on it, please stay tuned.
Same here. Looks like the plugin is not saving the dismiss decision.
I can confirm the bug is present no matter the version and PHP platform used. It’s a bug IN the plugin.
If you want this gone now, before we fix it, this is the place where it happens: http://plugins.trac.wordpress.org/browser/backwpup/trunk/inc/class-admin.php#L102
if ( ! defined( 'DOING_AJAX' ) && ! get_site_option( 'backwpup_about_page', FALSE ) && ! isset( $_GET['activate-multi'] ) ) {
update_site_option( 'backwpup_about_page', TRUE );
wp_redirect( network_admin_url( 'admin.php' ) . '?page=backwpupabout' );
exit();
}
It’s a super-quick hack, but you could just out-comment or delete the whole if statement.
Thread Starter
Li-An
(@li-an)
OK, I will wait for the update.
Caspar: I’ll wait for the official fix to avoid getting nuts modifying a dozen sites. If it will be fixed this week I can live with it 🙂
Thanks. I’m trying to get a hold of a developer right now, so yes, it is going to be fixed this week.
We did fix that on the 3.1.1 and will include it in the next bugfix release. Please re-install version 3.1.1 to get this problem fixed.
3.1.1 is the official last update from wp repo, and the bug is happenning yet, nor this appears fixed in the changelog. Did you mean 3.1.2?
@marcelo Pedra
No, you have to download the 3.1.1 version again. There is no 3.1.2, the fix is just backported to the 3.1.1 and 3.1 branch.
