• Let’s see, within the space of a week, we updated to 4.1.2, followed by 4.2, and now 4.2.1. I know you guys do great work for peanuts (literally), but has something happened to the vetting processes with respect to release candidate approvals?

    …and again a word of caution to the wise: don’t be too quick to click on the core update button when you get that scary looking notification. Before doing so, check with your theme and plugin devs, and make sure that what you’re using is compatible with the latest release of the core before updating the core. If that’s not the case, at the very least wait until needed theme and/or plugin updates are available, before performing a core update. AND before doing ANY updating, ALWAYS make backups of your site files and database.

    Cheers,

    Jan C.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter janco

    (@janco)

    ooops, probably should have also mentioned that if you’d like to turn off those nefarious autoupdates to help prevent chaos, you can add the following line of code to the wp-config file toward the bottom:

    define( ‘WP_AUTO_UPDATE_CORE’, false );

    If you add it under define(‘WP_DEBUG’, false); you’ll be good to go. Just remember that if you do add it, you’ll have to perform updates manually, which isn’t necessarily a bad thing if you know what I mean.

    Cheers,

    Jan C.

    There’s always a good reason for updates. 😉

    http://codex.ww.wp.xz.cn/Version_4.2.1

    As far as I’m concerned, updating my site to stop a potential threat like the one that’s detailed on that page sounds like a good thing. I also do understand the idea that not every site will work happily with a new update, it is relatively rare that something does go wrong. So far I haven’t had an issue with any of the sites that we’re running for our clients, so I’d be one to say that there’s no issues with it, that I have seen at least.

    Thread Starter janco

    (@janco)

    Understood about the security related updates, a very valid point. Just seemed like a lot of updates are happening in a relatively short period of time, especially the jump from 4.1.2 to 4.2. ‘Course, could just be a fluke this time around.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Slow down with the updates…’ is closed to new replies.