Opened 17 years ago
Closed 17 years ago
#10981 closed defect (bug) (fixed)
Storing rewrite_rules in a transient causes issues with non-permanent object caches and plugins that add endpoints
| Reported by: | markjaquith | Owned by: | markjaquith |
|---|---|---|---|
| Priority: | high | Milestone: | 2.9 |
| Component: | Rewrite Rules | Version: | 2.9 |
| Severity: | major | Keywords: | dev-reviewed |
| Cc: | Focuses: |
Description
If a WP install is using a non-permanent object cache like Memcache, its "transient"-stored rewrite_rules entry will go away without warning and WP will regenerate it. That regeneration happens before init, where many plugins use add_rewrite_endpoint(). Thus the rules will get populated without the endpoint.
e.g. http://wordpress.org/support/topic/313946
Recommend we revert to old option-based method of rewrite_rules storage.
Attachments (2)
Change History (5)
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
switches to storing the rules in an option, like before.