[wp-trac] [WordPress Trac] #26676: When upgrading code, object (or DB?) cache holds on to old versions

[WordPress Trac]

#26676: When upgrading code, object (or DB?) cache holds on to old versions
--------------------------+-----------------------------
 Reporter:  Ipstenu       |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  3.5.2
 Severity:  normal        |   Keywords:
--------------------------+-----------------------------
 This is NOT a 3.8 bug, as I've seen it before, but now it's a little more
 prevalent. In seaching for enough forum posts, I tracked it all the way
 back to 3.5...

 '''Scenario:''' You have object caching (APC, memecached, whatever) and
 when you upgrade via the UI, all the files get correctly downloaded
 -however- WP gets 'stuck' on a wrong screen. For example, one user was
 stuck on 'Your DB upgrade is complete' while another kept being told that
 3.8 was ready to be installed, even though he'd already done it. In all
 cases, the files were verifiably WP 3.8, and it was just the cache being
 'greedy' on the UI.

 In all cases, flushing the server-side cache resolved the issues.

 '''Caching Plugins:''' Of course this only happened with a site using a
 caching plugin, but it was not the same one. Batcache and Memcached Redux
 were the two I spotted.

 '''Links:'''
 * http://wordpress.stackexchange.com/questions/126796/wordpress-3-8-keeps-
 asking-me-to-upgrade-to-3-8
 * http://wordpress.org/support/topic/keeps-asking-me-to-upgrade-to-371
 * http://wordpress.org/support/topic/database-update-required-infinite-
 loop
 * http://wordpress.org/support/topic/admin-not-recognizing-38-update
 * http://wordpress.org/support/topic/running-wordpress-35-and-it-wont-
 update?replies=2

--
Ticket URL: <http://core.trac.wordpress.org/ticket/26676>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software