WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 5 years ago

#14526 closed defect (bug) (invalid)

If object cache is enabled then plugin list does not get updated after a plugin is deleted

Reported by: ruslany Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.0.1
Component: Plugins Keywords: has-patch reporter-feedback
Focuses: Cc:

Description

I am using the object-cache.php file for WinCache(from here: http://ruslany.net/2010/03/make-wordpress-faster-on-iis-with-wincache-1-1/), but I beleive the same problem also repro's with object-cache.php for APC (from here: http://txfx.net/files/wordpress/apc-object-cache.phps).

If I enable the object cache and then try to delete any plugin, the plugin files get deleted from the file system, but the plugin list on the plugin page is never updated and it keeps showing the deleted plugin as if it is still installed.

This happens because the list of plugins gets added to the object cache but is never updated afterwards.

I am attaching a patch with a possible way to fix this, but I would be interested in the comments from WordPress cache developers who may have a better way of solving this.

Attachments (1)

object-cache-patch.patch (448 bytes) - added by ruslany 5 years ago.
A possible way of fixing the plugin cache updates

Download all attachments as: .zip

Change History (4)

@ruslany5 years ago

A possible way of fixing the plugin cache updates

comment:1 @peaceablewhale5 years ago

  • Component changed from General to Plugins
  • Keywords has-patch added; object cache removed

comment:2 @nacin5 years ago

  • Keywords reporter-feedback added

The plugins group is non-persistent, though. Problem with the plugin?

comment:3 @dd325 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

The plugins group is non-persistent, the caching backend should not be storing non-persistent groups past the current pageload (ie. in memory only, not in long-term cache).

Closing as invalid as your caching backend is out of date.

Note: See TracTickets for help on using tickets.