1. David Decker

    The post ( http://jetpack.me/2014/04/10/jetpack-security-update/ ) says clearly that this update was rolled out via “core auto update functionality” – where possible. So it updated automatically in the background, just like for core with 3.8.2!

    I just got this confirmed via Twitter conversation with other WP developers.


    Only little “issue”: the info about that was maybe a bit late, updates were already rolling out and sites were automatically updated before webmasters/ maintainers got know what was going on.

    However, in the end, it’s great to see, another security issue got fixed very fast!

    I, personally, love the auto background updates. I had no problems since 3.7 — on a bout 100 installs. So props to @Nacin & the whole team for all this work!!!


    • Ryan Hellyer

      That seems correct. The auto-updates should be able to roll out faster than anyone can find/read a blog post on the topic.

      I’ve been using auto-updates on plugins and themes since before it was in core, via that plugin (which I can’t remember the name of right now). It’s awesome and allows me to be super lazy when it comes to updates :)



    SOOOOOOOOOOOOOOOOOOOOOOOOOOOO many times when I do a jetpack update. the .maintenance file DOES NOT get deleted.

    This is specially annoying when you have 8 of your own sites, plus A LOT of corporate/client sites.

    PLEASE fix that?

    solution I do: login via ftp and delete .maintenance file.


  3. Matt

    What is the issue if the file stays there?


  4. vesati

    The issue is that users will only see a text referring to maintenance, so users have no access to actual site content as long as .maintenance file exists. I do the same as Miroslav…


    • Samuel "Otto" Wood

      The way WordPress actually handles that .maintenance file should prevent that from being an actual issue for very long.

      What WordPress does is to put PHP code into that file. It writes it to contain a single variable, named $upgrading, and it sets that variable to a time value of when the file was created.

      Later, when WordPress checks for the existence of the file, it actually includes the file, thus loading that variable. It then checks to see if the time in the $upgrading variable is more than 10 minutes old. If it is older than 10 minutes, then it ignores the file and continues on as per normal.

      So even if the file is left behind for whatever reason, it doesn’t stop the site from displaying for more than 10 minutes, max.


  5. blacksteps

    Hello…I am not a superpro like most of the people who post here, Call me a newb..Anyway, is this a WordPress update or a Jetpack update? The only update button I see is for WP and that is telling me a bout new themes..When I look at Jetpack, I see all kinds of cool things, but no Update button. Can someone hold my hand and help me across the street? THANKS!


  6. blacksteps

    Just found the answer here… http://jetpack.me/2014/04/10/jetpack-security-update/ Down in the forum…Next time can I suggest someone do a simple graphic, maybe a screencapture?…From that forum, others have had the same issues.This is so urgent and so important that the solution should be as plain as day…..THANKS


Comments are closed.

%d bloggers like this: