Opened 14 years ago
Closed 14 years ago
#22550 closed defect (bug) (invalid)
Unable to Post in Debug Mode Unless Super Cache is Deleted
| Reported by: | miqrogroove | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Cache API | Version: | 3.4.2 |
| Severity: | major | Keywords: | |
| Cc: | Focuses: |
Description
There might be a legitimate bug in the core cache architecture. Some flaw in the Super Cache phase 2 file is causing a WSOD even when the plugin is deactivated.
Is there a way to enforce the removal of the cache hooks with deactivation? Or is this strictly a non core issue?
Change History (6)
#2
@
14 years ago
- Keywords reporter-feedback added; dev-feedback removed
It's a regression only if it works fine in WP 3.4.2.
#5
@
14 years ago
- Summary Unable to Post in RC1 Unless Super Cache is Deleted → Unable to Post in Debug Mode Unless Super Cache is Deleted
#6
@
14 years ago
- Milestone Awaiting Review
- Resolution → invalid
- Status new → closed
Is there a way to enforce the removal of the cache hooks with deactivation?
Yes, we have register_deactivation_hook(), which SuperCache could use to remove it's special files from wp-content.
Feel free to re-open if it turns out it's a Core bug.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Steps to reproduce: