Make WordPress Core

Opened 8 years ago

Closed 7 years ago

#44199 closed defect (bug) (invalid)

Can't upgrade to WordPress 4.9.6

Reported by: alex-vojacek's profile Alex Vojacek Owned by:
Milestone: Priority: normal
Severity: critical Version: 4.9.6
Component: Upgrade/Install Keywords:
Focuses: Cc:

Description

Everything has been working just fine, updating wordpress has been a regular push a button and be done with it, up until the latest update.

My website refuses to upgrade to WordPress 4.9.6, each time I press the upgrade button, it says it's been upgraded but then it shows it is still 4.9.5

I tried it a thousand times now, even uploaded a fresh copy of wordpress 4.9.6 into the site and overwritten all files and it is still displaying WordPress 4.9.5 and the Upgrade wordpress notice is there.

It is driving me nuts, what is going on here?

Change History (4)

#1 @SergeyBiryukov
8 years ago

  • Component changed from General to Upgrade/Install

#2 @swissspidy
8 years ago

  • Keywords reporter-feedback added

Hi there and welcome to WordPress Trac!

This sounds like an OPcache issue (see #36455), which means that your server still has the old PHP files in its cache.

A quick workaround to solve this would be creating a file like opcache.php in your WordPress root folder with <?php opcache_reset(); in it. Then, open that file in the browser (e.g. https://example.com/opcache.php) and delete the file afterwards.

Alternatively, you could use a WP-CLI command like https://packagist.org/packages/wearerequired/wp-cli-clear-opcache to do the same. Provided you have WP-CLI and this WordPress plugin installed, you would run wp opcache clear on the command line.

Please try this and let us know if it works.

#3 @Alex Vojacek
8 years ago

Your idea about OPCache was right. I did a far more easy method. I just restarted php-fpm service and the upgrade was a success.

Thanks so much !

#4 @desrosj
7 years ago

  • Keywords reporter-feedback removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Since @alex-vojacek was able to resolve this issue by resetting OPcache.

Note: See TracTickets for help on using tickets.