4.7 broke site, reverted to earlier to fix

  • Hello,
    My site https://www.sonicnuance.com broke after an auto update of WordPress from 4.6 to 4.7 (I’ve learned my lesson on auto updates). The uploads directory got wiped, plugins were removed and credit card processing stopped working. I don’t know what it was about going to 4.7 that caused the issue but my webhost (BlueHost) support said that 4.7 had “bugs”. I’m using Kallyas theme if that is of any help.

    There seems to be confusion in the theme, plugin and hosting communities on what is the status of 4.7. Can a moderator please elaborate? I will stick with 4.6 until I get consensus from webhost, themebuilder and www.ads-software.com on the status of 4.7.

    I think the moral for me is to never use auto update, and to update to the latest WordPress only AFTER my theme and plugins are verified to work with the latest wordpress.

    Thanks

    • This topic was modified 7 years, 11 months ago by sonicnuance. Reason: i put in the wrong forum
    • This topic was modified 7 years, 11 months ago by sonicnuance.
Viewing 3 replies - 1 through 3 (of 3 total)

  • Howdy @sonicnuance,

    First, ouch! That’s no fun at all.

    Second, I agree about auto-updates – they’re scary and I feel like I need more control – especially on an ecommerce site.

    I’ve updated dozens of WP sites using WooCommerce and haven’t run into ANY issues where WP 4.7 has done anything like what you described. Especially things like wiping the uploads directory. It just doesn’t have that functionality.

    I think that Bluehost rep was blowing smoke. It’s easy to blame WordPress, but it’s much more likely to be some incompatibility with the plugins or theme you use. Or, it could have been something at the host level.

    I’d recommend:

    1. thoroughly researching your critical plugins and your theme to make sure the developers all claim 4.7 compatibility and then check support forums to make sure there aren’t hordes of screaming, frustrated owners of broken sites.
    2. Consider making a clone of your site on a staging domain (staging.sonicnuance.com, for instance) and then block it from search engines and/or put in Maintenance Mode (using a plugin). Then, anytime there are larger updates to WP, plugins, or your theme, test them on your staging instance before you update Production.

      I hope that helps!

    www.ads-software.com does not ‘auto-update’ major updates such as 4.7. Minor updates such as 4.6.1, if auto update is not disabled, would auto-update. Now, when you refer to “auto-update”, did you tell WordPress to do the update, or, are you specifically noting that in your case, your site was updated to 4.7, but you took no action to have this occur?

    I have many sites all running 4.7 without issues. None were ‘auto-updated’.

    You may see several posts here over last few days of folks with issues related to updating to 4.7, but almost all, if not all, are related to old themes or plugins, or combinations of that are in use when the update runs.

    I would:

    1. Deactivate all plugins.
    2. Switch to installed default unedited theme (2016).
    3. Update to 4.7. All should be well, you have a default install now.
    4. Activate your theme. Is site OK? (test theme related items)
    5. It is? Great, you do not have a theme issue. If not OK, you have a theme issue, Consult theme developer.
    6. With a properly working theme in place, activate your plugins one at a time and test site functionality. When the site breaks you have found the bad plugin. Deactivate it and consult plugin developer.

    Also, always better to have a development site for testing purposes prior to rolling out to live site, especially anyting related to eCommerce.

    See: https://codex.www.ads-software.com/Configuring_Automatic_Background_Updates#Core_Updates

    I have a similar issue – see below:

    I added a mobile plugin and deleted, but the mobile site still looks terrible, like something might be broken. Can someone help me?

    incyclesoftware.com

    Thanks,
    Stephanie Long

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘4.7 broke site, reverted to earlier to fix’ is closed to new replies.