Closed (fixed)
Project:
Contextual View Modes
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Feb 2013 at 21:19 UTC
Updated:
7 Oct 2013 at 11:21 UTC
If you have a content type that has a space or underscore in the name then the default view mode for that type does not save correctly.
For example, I have a type called "Section landing" with a machine named call "section_landing". I can enable/disable contextual view modes for that type, but I cannot save a view mode to use.
Looking in the database you can see the setting got saved in this manner:
s:7:"section";a:1:{s:14:"landing_mobile";s:14:"mobile_display";}
Possibly related to something mentioned in a comment under #1887908: Error when trying to set global settings
Comments
Comment #1
beatnikdude commentedI just verified this issue in 7.x-1.x-dev on a clean install.
Comment #2
victoriachan commentedHi,
I have this same problem too. I tried with a content types blog and news_item.
And when I checked the cvm_global_content_type_modes variable that gets saved, it says:
Comment #3
victoriachan commentedHi,
I've discovered that this has been fixed in the 1.x-dev version. As mentioned in #1887908, a bandaid solution has been applied to us triple underscore as delimiter instead of single underscore.
Will mark this issue as fixed.
Thanks,
Victoria