Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Chip Bennett

    (@chipbennett)

    What are your settings?

    Mine just updated to 3.8.1 and broke my site.

    Here are my settings:

    Automatic Updates Enabled : No
    Everything gets grayed out till

    Disable VCS check : Checkmark
    Update Emails enabled: Yes

    Send emails for successfully updates: Check
    Send emails for failed updates: Yes
    Send emails for critically failed updates: Yes

    Plugin Author Chip Bennett

    (@chipbennett)

    @persiusx please start a separate support topic.

    Thread Starter Fizzgigg

    (@fizzgigg)

    I have the same settings as persiusx (and had before the update too), plus at the end “Send Update Debug Emails?” that is unchecked.

    Ditto what Fizzgigg wrote: same settings, same automatic update from 3.8 to 3.8.1 (but happily it didn’t break my site).

    I just want to add THANK YOU for writing this plugin. Even if it’s not working at the moment. 🙂 WP ought to have included this functionality when they introduced automatic updates.

    Thread Starter Fizzgigg

    (@fizzgigg)

    I agree with Bill Statler. Auto update was a good thought, but forcing everybody to auto update was in my opinion a strange and bad decision.
    Thank for this plugin, and I am confident we can sort this out. And later maybe even translations? 🙂

    Plugin Author Chip Bennett

    (@chipbennett)

    Thanks for your patience, all. I found the issue, and it’s an easily-fixed bug with the Plugin. This line:

    if ( ! $options['active'] ) {
        add_filter( 'auto_upgrader_disabled', '__return_true', 1 );
        return; // It's all disabled, no need to check the others.
    }

    The name of the filter is wrong. It should be auto_updater_disabled.

    If I recall correctly, many of the filter names were changed during WordPress 3.7 beta-testing prior to release. I missed this one. I apologize.

    I’ll push out a fix immediately.

    Plugin Author Chip Bennett

    (@chipbennett)

    Just pushed version 1.3.1, which addresses this issue. Thanks again for your patience!

    Plugin Author Chip Bennett

    (@chipbennett)

    @persiusx:

    I also wanted to say: minor-version updates should never “break” your site. They’re only bugfix/security releases. If your site broke somehow after a minor-version update, you should start a support topic for that site-breakage, in the appropriate forum:
    http://wordpress.org/support/forum/how-to-and-troubleshooting#postform

    Please be sure to provide all relevant details, including:

    1. WordPress version before update
    2. WordPress version after update
    3. Active Theme
    4. Active Plugins
    5. Any error messages received during/after update
    6. Exact nature of the site breakage, with proper debugging

    Thread Starter Fizzgigg

    (@fizzgigg)

    Excellent work with the update, Chip. The difference between a trustworthy developer and an untrustworthy one is not so much the ability to avoid mistakes, but the ability does deal with them as they appear. 🙂

    Plugin Author Chip Bennett

    (@chipbennett)

    Thank you for that.

    If you’re looking for a developer who always avoids mistakes, you’re looking in the wrong place. 🙂 But, I do my best to keep track of them, and correct them as soon as I can.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Updated’ is closed to new replies.