Problem/Motivation
I recently did some design changes to a theme and used the same name/id in lower-case instead of upper-case for the final version.
Example theme-name while testing: NAME2
Name of the final version: name2
This caused problems in the block-configuration: e.g. excluding a block from certain pages didn't work anymore with the final theme-version. Some blocks that were saved with the old upper-case theme-name in the block-table appeared on every page even when resaved with a "blacklist" of pages (the upper-case theme-name in the theme-column was preserved). Only block-settings with the new lower-case theme name in the theme-column of the block-table were active.
Proposed resolution
I finally changed the theme-name in the theme-column of the block-table from upper-case to lower-case manually, which solved all problems.
Remaining tasks
The theme-name in the theme-column should not be case-sensitive (or the same name in a different word-case has to be recognized as a different theme). At least when a block is resaved with the new theme-name/id activated, differences in word-cases have to be detected.
User interface changes
UI-changes should not be necessary.
API changes
??
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous commented