#15048 closed defect (bug) (fixed)
long theme name length causes menu bug
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | 3.1 | Priority: | normal |
Severity: | normal | Version: | 3.0.1 |
Component: | Menus | Keywords: | has-patch |
Focuses: | Cc: |
Description
Was working on a theme where the theme name was "TTI Center for International Intelligent Transportation Research" (long, I know) when I stumbled upon a strange issue: the menu options under Theme Locations would not save.
I was able to duplicate the problem with Twenty Ten. If the theme is renamed to something longer, such as Twenty Ten Nine Eight Seven Six Five Four Three Two, the menu locations will not save or come up.
Attachments (2)
Change History (9)
#2
@
13 years ago
Yeah it's not really a big deal, it just took me a whole day of smashing my head against the wall to figure out why my menus wouldn't save. I just wish I would of known there was a name limit :P
Yesterday I dug through wp.org and found 3 threads - all unsolved - with people describing this exact issue, even though most likely rare.
I realize having a name that long (like described above) is pretty stupid but in my case it just happened to be the client name.
I like nacin's suggestion, +1
#4
@
13 years ago
To avoid options table write storms and mass cache invalidation on busy multisite sites, option updates need to be limited to admin page loads.
It would need to be longer than about 60 characters.
Theme mods (which include headers, backgrounds, and theme locations) are stored by theme name rather than by slug. I really want to change that and all of the other times we pass theme name around in the themes functions.
What we could do is start storing it as the slug, then check the name second (and shift it to the slug after). That should handle any compat issues with people using get_theme_mod.