#40363 closed defect (bug) (fixed)
Remove `current_blog_` cache invalidation from `clean_blog_cache()`
| Reported by: | flixos90 | Owned by: | spacedmonkey |
|---|---|---|---|
| Priority: | normal | Milestone: | 5.4 |
| Component: | Networks and Sites | Version: | |
| Severity: | normal | Keywords: | good-first-bug has-patch |
| Cc: | Focuses: | multisite |
Description
clean_blog_cache() currently invalidates keys current_blog_{$blog->domain} and current_blog_{$blog->domain}_{$blog->path} of the site-options group. As far as I can see those keys are not used anywhere in Core (and have not been used for quite a while), so we should be able to remove them from that function.
Related: #40201 (more elaborate improvements of clean_blog_cache())
Attachments (1)
Change History (14)
#2
@
9 years ago
I am also confirming that these keys are not used anywhere in the core. better to remove them.
This ticket was mentioned in Slack in #core-multisite by spacedmonkey. View the logs.
9 years ago
This ticket was mentioned in Slack in #core-multisite by flixos90. View the logs.
9 years ago
#6
@
9 years ago
- Owner set to
- Status new → assigned
Assigning ownership to mark the good-first-bug as "claimed".
This ticket was mentioned in Slack in #core-multisite by flixos90. View the logs.
9 years ago
#8
@
9 years ago
@jeremyfelt @johnjamesjacoby I am not sure, but I think I remember there were some concerns about removing these?
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
I checked and these cache keys haven't been used in core for sometime. It should be safe to remove them.