WordPress.org

Ready to get started?Download WordPress

Forums

Do background updates (3.7) not work on Multisite? (10 posts)

  1. goodevilgenius
    Member
    Posted 8 months ago #

    Just upgraded to 3.7. Was excited to hear about the "Background updates" feature. However, after the upgrade, I was greeted with the message:

    "This site is not able to apply these updates automatically. But we’ll email user@domain.tld when there is a new security release."

    Is this because I use multisite? Or is there likely some other cause?

  2. beggers
    Member
    Posted 8 months ago #

    I don't use multisite and I got the message, too.

  3. chrisbfinternet
    Member
    Posted 8 months ago #

    Snap. Not a multisite issue, all my sites are affected, I guess the security on my server prevents auto updates?

    Google brings me to this page first so I will investigate and post back.

  4. Hansaplastique
    Member
    Posted 8 months ago #

    Same here, also with a Multisite ... :(
    Did anyone find any "reasons" we should look for to enable this feature, and maybe a better question: do we want this feature? (I always verify if an update breaks things or not before updating my production server)

  5. Hansaplastique
    Member
    Posted 8 months ago #

    We all might want to check this link for more details ... :-)

  6. "This site is not able to apply these updates automatically. But we’ll email user@domain.tld when there is a new security release."

    That is NOT a multisite error. It means the way WP is set up on the server doesn't work with auto updates, so let's look at how it IS set up.

    1) Can you use one-click upgrades without entering any etxra data? That is, do you just click the button and go?

    2) Do you have disallow_file_mods or anything similar set in your wp-config.php?

    3) Do you ever have to enter a username and password for FTP to upgrade?

  7. goodevilgenius
    Member
    Posted 8 months ago #

    1) Can you use one-click upgrades without entering any etxra data? That is, do you just click the button and go?

    Yes

    2) Do you have disallow_file_mods or anything similar set in your wp-config.php?

    No

    3) Do you ever have to enter a username and password for FTP to upgrade?

    No

    Seems that it should work just fine.

  8. beggers
    Member
    Posted 8 months ago #

    Ipstenu, are you specifically stating that this is why some of us are getting the message, or are you just guessing? Because if this is true, the install should tell us or give the option to make the necessary changes. After all, this was its big selling point.

  9. chrisbfinternet
    Member
    Posted 8 months ago #

    http://make.wordpress.org/core/2013/09/24/automatic-core-updates/:

    If the install uses FTP for updates (and prompts for credentials), automatic updates are disabled
    If the install is running as a SVN or GIT checkout, automatic updates are disabled

    I've only ever seen WP use FTP for updates and prompt for credentials. Doesn't this mean that 99% of WordPress installation can't use the automatic update feature?

    How else can WP be installed, other than via FTP or SVN? (Or more to the point, how can I make use of the auto-update feature?)

  10. mfalkvidd
    Member
    Posted 8 months ago #

    So that's why. Couldn't figure out why my sites weren't able to auto-update. Thanks a lot chrisbfinternet!

    I use git to be able to easily revert plugin updates (well not database changes, but the code at least) and theme updates. It also makes it easy to see what has changed from one version to another (git diff).

    It would be great if this did not prevent me from using auto-update.

Reply

You must log in to post.

About this Topic