![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
#53322 closed defect (bug) (fixed)
There is no way to bypass loading of object cache
| Reported by: | jorbin | Owned by: | jorbin |
|---|---|---|---|
| Priority: | normal | Milestone: | 5.8 |
| Component: | Bootstrap/Load | Version: | |
| Severity: | normal | Keywords: | has-patch |
| Cc: | Focuses: |
Description
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.
5 years ago
#1
- Keywords has-patch added; needs-patch removed
#4
@
5 years ago
This is so minor that I would feel bad opening a ticket about it, but object-cache.php is misspelled in the filter docs added in [51087], and Default true. is indented by two extra spaces relative to the line above it.
Add a filter to allow disabling object cache
Trac ticket: https://core.trac.wordpress.org/ticket/53322