Make WordPress Core

Opened 17 years ago

Closed 16 years ago

#5570 closed defect (bug) (fixed)

Remove default persistent object cache

Reported by: ryan's profile ryan Owned by:
Milestone: 2.5 Priority: normal
Severity: normal Version: 2.5
Component: General Keywords: cache
Focuses: Cc:

Description

The persistent object cache is not enabled by default and is not actively maintained. Let's remove it. It can be resurrected as a third-party cache backend. The in-memory caching parts of cache.php should be retained.

Attachments (1)

no_persistent_cache.diff (9.9 KB) - added by ryan 17 years ago.

Download all attachments as: .zip

Change History (7)

#1 @westi
17 years ago

+1

I am quite happy to take this on as a plugin as well.

#2 @ryan
17 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [6539]) Remove persistent object cache. fixes #5570

#3 @ryan
17 years ago

(In [6540]) Fix cache close. see #5570

#4 @bitethemailman
16 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened
  • Version changed from 2.5 to 2.3.2

includes/function.php still makes serialization calls, throwing a PHP memory error when it runs out of space.

#5 @DD32
16 years ago

includes/function.php still makes serialization calls, throwing a PHP memory error when it runs out of space.

That'd be due to options being set/updated, they *have* to be serialised if they're not a simple string. So by the sounds of it, Something is storing rather large options which overflows the memory limits?

#6 @DD32
16 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed
  • Version changed from 2.3.2 to 2.5

reseting to 2.5 version. Infact, It'd be better to seek help in the support forums, or open a ticket which refers to your problem specifically. This ticket was for the removal of the cache, which doesnt affect you. (Assuming you're running an uptodate version of WordPress)

Note: See TracTickets for help on using tickets.