Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi Airone, I had a look at the change log for the two updates after 3.0.10.

    Version 3.0.12

    Fixed: Redirect when accessing the WordPress backend
    Added: Russian translation
    Added: Simplified chinese translation
    Fixed: German log string typo

    Version 3.0.11

    Improved: About page will only be shown after install
    Updated: AWS SDK to Version 2.3.1 (PHP 5.3.3+)
    Fixed: some notices and warnings
    Fixed: Change of BackWPup role for other users
    Added: Message for Pro version to support plugin

    There are only 3 fixed issues from above that I suspect might cause your issue….

    Fixed: Change of BackWPup role for other users
    Fixed: Redirect when accessing the WordPress backend
    Updated: AWS SDK to Version 2.3.1 (PHP 5.3.3+)

    What do you think?
    Do you have an error log of your issues?

    Kind regards

    Hi Airone and mbrsolution,

    I am not sure if we had the same issues, but as soon as I activated 3.0.12 on a local install I got a bunch of warning and notices. Hunted down the issue to line 244 of backwpup.php.

    The if statement as found in 3.0.12

    //display about page after Update
    if ( ! get_site_option( 'backwpup_about_page', FALSE )  && $_REQUEST[ 'page' ] != 'backwpupabout' )

    To fix this issue just change the if statement by adding && array_key_exists(‘page’, $_REQUEST) like so

    //display about page after Update
    if ( ! get_site_option( 'backwpup_about_page', FALSE ) && array_key_exists('page', $_REQUEST) && $_REQUEST[ 'page' ] != 'backwpupabout' )

    It looks like this if statement first showed up in 3.0.11 and the offending $_REQUEST[ ‘page’ ] was added in 3.0.12

    Hopefully the plugin author reads this and updates the plugin.

    Cheers,

    Tamara

    Hi Tamara, thank you for your fix.

    I can see why not adding your fix can cause the plugin to fail. I know many have had issues with this error popping up after upgrading to the latest version. Although it is very strange that I have had no issue myself and I am running the latest WordPress 3.6 beta 3 version.

    Kind regards

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Update to 3.0.12 crashed my sites’ is closed to new replies.