• Resolved James Ironside

    (@james-ironside)


    My website updated to the beta updates for automatic, however it’s on a live production site and was not something I chose to do. One day, it was on 3.9.1 the next it was on Beta 4.

    I don’t have the beta tester plugin installed that seems to be talked about frequently, and rolling back seems beyond what I’m capable of doing.

    How do I get back to the latest stable version. At the moment, I am wary of updating any plugins as they may not be compatible with the beta version which is sadly live.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator James Huff

    (@macmanx)

    First, do you have the following in your wp-config.php file?

    add_filter( 'allow_dev_auto_core_updates', '__return_true' );

    If so, remove that, and you’ll no longer be updated to any development builds.

    Now, I typically don’t recommend downgrading, you might run into unforeseen issues that no one has tested for. WordPress 4.0 is on its first release candidate, so if the version you are on includes “RC,” you should be relatively safe. “Release candidate” means that the developers think it’s ready for prime time, but want to get one more round of testing in just to be safe.

    You’re probably ok to stick with 4.0 RC until 4.0 final lands in a week or so, and 4.0 really hasn’t introduced anything that would break many plugins or themes. Plus, if a plugin or theme is broken for you right now under 4.0 RC, you should contact the plugin or theme’s developer, as it will likely be broken in 4.0 final too.

    If you really need to downgrade, which again I stress may be more dangerous than remaining on 4.0 RC, download WordPress and delete then replace your copies of everything except the wp-config.php file and the /wp-content/ directory with fresh copies from the download. This will effectively replace all of your core files without damaging your content and settings. Some uploaders tend to be unreliable when overwriting files, so don’t forget to delete the original files before replacing them.

    Thread Starter James Ironside

    (@james-ironside)

    I have looked and I do not have that filter in my wp-config.php file.

    Based on what you are saying James, I’m not keen to try and roll back. Any other suggestions?

    Thanks

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Rolling back is actually probably safe in this case. He says it “may be more dangerous than remaining on 4.0 RC” and that’s true, but 4.0 is coming out tomorrow probably so there’s not much of a need to.

    I’d go ahead and roll back, personally, and have done it for a few people recently ??

    My website updated to the beta updates for automatic, however it’s on a live production site and was not something I chose to do. One day, it was on 3.9.1 the next it was on Beta 4.

    The only reason that happens is if you were at some point on the beta releases or an RC. When 4.0 comes out, I would suggest deleting the WP files as James describes and reinstalling that way.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Updated to Nightly Build Beta Updates Error’ is closed to new replies.