#34182 closed defect (bug) (fixed)
'allowedthemes' network option never gets primed when themes are deleted
Reported by: | DrewAPicture | Owned by: | jeremyfelt |
---|---|---|---|
Milestone: | 4.6 | Priority: | normal |
Severity: | normal | Version: | 3.0 |
Component: | Themes | Keywords: | has-patch |
Focuses: | multisite | Cc: |
Description (last modified by )
It appears that the 'allowedthemes' network option is channeling Rick Astley in that it never gives up or lets down, or runs around and deserts the themes it stores.
In my testing, it would seem that all themes ever installed are stored in perpetuity. It's possible this behavior has been around since WP_Theme
was written in 3.4.
For example: I ran across this bug when testing something unrelated, and noticed that 'allowedthemes' contained 303 total keys (I have ~10 themes on my test build currently).
Attachments (1)
Change History (9)
#4
@
9 years ago
Once #30594 is in, we'll have WP_Network::network_disable_theme()
available to us. 34182.diff implements this in delete_theme()
.
Unit tests on this might be tough. We don't have anything covering delete_themes()
at the moment.
#5
@
9 years ago
- Keywords has-patch added; needs-patch needs-unit-tests removed
- Milestone changed from Future Release to 4.6
- Owner set to jeremyfelt
- Status changed from new to accepted
Needs a patch first, this one's been around for a while anyway.