Unable to update plugins after upgrade to 4.2

  • I upgraded to 4.2 without any issues. But then I went to try and update my plugs that said they needed updating (JetPack and Contact form). I picked the ones to update, got taken to the ftp info page (which looked very weird), I entered the info and then I get taken to the next page like normal, but all that shows is:

    “The update process is starting. This process may take a while on some hosts, so please be patient.

    Enabling Maintenance mode…”

    It never progresses beyond there and the plugins won’t update. Any ideas?

    (For what it’s worth, I was able to update the themes.)

Viewing 15 replies - 16 through 30 (of 85 total)

  • Now that 4.2.1 has been released, I’m surprised it’s not corrected. I even had to reupload the fix :/

    i have same problem i can’t update to 4.2.1

    Thread Starter miri

    (@miri)

    Now I have this same problem with trying to update to 4.2.1 on a subdomain. *sigh*

    Hi,
    in my case, i just can’t update to 4.2.1

    Blocked to “activation mode maintenance”, nothing happened.

    Working fine with the fix, applied at all, updated and applied again ??
    Thanks for the fix.
    Hope its in the 4.2.2 included :/

    @ stefan : you use the fix of Keith or Patricia ?

    Best regards

    @patricia BT thanks for the hint and direction to

    https://core.trac.www.ads-software.com/ticket/32135 the diff file shows that it’s simply modify wp-admin/includes/file.php

    replacing line 149
    if ( empty( $filename ) || ‘.’ == $filename ) {
    with
    if ( empty( $filename ) || ‘.’ == $filename || ‘/’ === $filename ) {

    which worked for me ??

    If this patch basically produces a filename of time() rather than “/.maintenance” then surely the function of the site being shown to visitors as being under maintenance won’t work ?

    I’m not sure but it would seem that WordPress would be looking for .maintenance not a variable number, and therefore visitors will continue to be able to use the site even when it should be ‘down for maintenance’ ?

    The impact may be small in most cases but I think it should be known.

    I don’t know the inner workings of WordPress well at all, I don’t even know why a tempname function need be so complex.

    Keith

    Thanks for the fix:

    replacing
    if ( empty( $filename ) || '.' == $filename ) {
    with
    if ( empty( $filename ) || '.' == $filename || '/' === $filename ) {

    worked for me also.

    Odd that this hasnt been fixed!

    I used the fix of Patricia

    I confirm it works

    Thanks

    hope the fix is included in 4.2.2 and published soon

    Fixing line 149 in wp-admin/includes/file.php does indeed do the trick. One thing to keep in mind: if you have a site on 4.2 and want to get it to 4.2.1 for the security patches, you likely need to patch that line. Then if you want to update plugins, you’ll need to patch that line again since the 4.2.1 update will overwrite file.php.

    Sure hope this is fixed in 4.2.2. It’s keeping auto-updates from applying in addition to interfering with updates of plugins, themes and core wordpress itself.

    Fixing line 149 works for me also. I hope this gets fixed very soon, its not easy to update many websites with this bug.

    Using this fix I got one of my sites to finally update from 4.2 to 4.2.1
    Thanks!

Viewing 15 replies - 16 through 30 (of 85 total)
  • The topic ‘Unable to update plugins after upgrade to 4.2’ is closed to new replies.