Make WordPress Core

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#53322 closed defect (bug) (fixed)

There is no way to bypass loading of object cache

Reported by: jorbin's profile jorbin Owned by: jorbin's profile jorbin
Milestone: 5.8 Priority: normal
Severity: normal Version:
Component: Bootstrap/Load Keywords: has-patch
Focuses: Cc:


Right now in wp_start_object_cache, the existence or non-existence of the object-cache.php dropin is the only way to signify if WordPress should load the object cache without messing around with globals in a way that is not completely reliable.

Some specific use cases:

  • If you want to be able to conditionally test uncached requests
  • If you are on a host that auto installs an object cache and you don't have access to the file system

Classifying as a bug since we have the ability to disable the advance-cache dropin and it was an oversite to only be able to disable that one.

Change History (5)

This ticket was mentioned in PR #1346 on WordPress/wordpress-develop by aaronjorbin.

3 years ago

  • Keywords has-patch added; needs-patch removed

Add a filter to allow disabling object cache

Trac ticket:

#2 @jorbin
3 years ago

  • Milestone changed from Awaiting Review to 5.8

#3 @jorbin
3 years ago

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

In 51087:

Boostrap/Load: Add filter to allow disabling of object cache

In [37626] a filter was added to allow disabling the advanced cache dropin, but no similar filter was added for the object cache dropin. This corrects that oversight.

Fixes #53322.

#4 @dlh
3 years ago

This is so minor that I would feel bad opening a ticket about it, but object-cache.php is misspelled in the first line of the filter docs added in [51087], and Default true. is indented by two extra spaces relative to the line above it.

Last edited 3 years ago by dlh (previous) (diff)
Note: See TracTickets for help on using tickets.