When fields in content types are grouped using grouping feature introduced in 7.2/7.3, and one such group has rx_DynamicDropDownSingle control, the entire content type editor becomes non-editable. Neither unassociated group nor other group tabs are accessible in the content editor. Onclick to expand the group node wouldn't respond. Please find attached screeenshot.
To reproduce
- Install psodynamicdropdown solution in 7.3 instance : https://github.com/percussion/PSODynamicDropdown/archive/master.zip
- Add rx_DynamicDropDownSingle control in a field group of any content type
- Try to create new item of this type in content explorer
- Notice that group nodes are not accessible.
- Now remove the rx_DynamicDropDownSingle control from the group and would notice that the content editor loads all fields without any issue when new item is created.
Customers analysis for this issue:
"Looking at the javascript used by Dynamic Dropdown, the word "group" is used in variable and function names, so I'm wondering if this might be causing the conflict."
When fields in content types are grouped using grouping feature introduced in 7.2/7.3, and one such group has rx_DynamicDropDownSingle control, the entire content type editor becomes non-editable. Neither unassociated group nor other group tabs are accessible in the content editor. Onclick to expand the group node wouldn't respond. Please find attached screeenshot.
To reproduce
Customers analysis for this issue:
"Looking at the javascript used by Dynamic Dropdown, the word "group" is used in variable and function names, so I'm wondering if this might be causing the conflict."