WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #31378, comment 10


Ignore:
Timestamp:
02/21/2015 09:41:07 PM (6 years ago)
Author:
andrebron
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #31378, comment 10

    initial v1  
    88
    99apt-get install php5-mysqlnd
    10 
    11 Replying to [comment:9 andrebron]:
    12 > Interesting situation for me...  Dev site updated fine, but production site does not.  They are on 2 different servers running same OS, permissions and such.  Disabled firewalls...
    13 >
    14 > Tried adding/removing  (FS_METHOD).  No go for me.
    15 >
    16 > Manually updating WordPress Core files does not work either.  Very strange.
    17 >
    18 > After manually updating all core files (except wp-content), Admin Dashboard still not updating.  Some db update issue perhaps?
    19 >
    20 > Updating to Core 4.1.1 tries the update, then no errors are shown, then refreshes back to the updates screen without having completed the update to Core 4.1.1.
    21 >
    22 > @dd32 What Core file has `$_POST['version']` set to pass to the FTP credentials screen?
    23 >
    24 > Replying to [comment:5 dd32]:
    25 > > A bug is present in 4.1 which has resulted in `$_POST['version']` not being passed through the FTP credentials screen, and as a result, it fails to find a update package to use, and returns early with a blank screen..
    26 > >
    27 > > I've just deployed a change to api.wordpress.org which should work around this, with the downside that the Update screen will display a duplicate update offering on the update screen.
    28 > >
    29 > > If you're still running 4.1, and affected by this, please try updating again from '''Dashboard -> Updates'''?