Vulnerability in EPiServer.Forms
Episerver CMS 10.9.1.0Im facing a wierd problem with the default property "Shortcut" under the "Settings" tab on all pages.When selecting "manage shortcut", previously, the options for the property "Shortcut type" would be:
Instead now i have behaviour as if the "Shortcut type" property was of type integer. I can choose any number instead of the 5 options listed above. However if i chose e.g "4" it will correctly map to the option above that would be on that index.Anyone have any idea? I read about the Shortcut property here: http://webhelp.episerver.com/latest/cms-edit/all-properties-view.htmand as far as i am concerned i have no controll over what options should be listed for the property.Thanks!
The ShortcutType is an enum (generally stored as an integer).
You can find the different enum values here: http://world.episerver.com/documentation/Class-library/?documentId=cms/10/5A6DD5DB
Normal = 0 Shortcut = 1 External = 2 Inactive = 3 FetchData = 4
So my question is Alf, why does my editor interface not show those options? On our prod server, we have 5 options which are strings such as "Shortcut to Page in Episerver CMS".Instead it lets me select an integer.
Do you mean that when you perform the following steps
That the dropdown does not show the options?
No shortcutShortcut to another content itemShortcut to page on another websiteNo shortcut, display text onlyFetch content from another content item
Yes, exactly. Sorry for not being clear. Instead of these 5 options i can set it to any integer. Setting it to 0 will "fold out" additional fields, as if i would have set it to "No shortcut".(So functionality technically works but its not very user-friendly)
Sounds like translations aren't displayed properly.
What languages are you running on your website and what languages are you using for the Episerver interface?
Running Swedish and English. Tried both english and swedish in the epi interface, same result.
We were also experiencing this issue a little while ago on a client but it's no longer occuring checking on CMS 10.10.4 which we have upgraded to.
Scott's right..this has been resolved in EPiServer.CMS.UI 10.9.6
The bug raised can be found here: http://world.episerver.com/support/Bug-list/bug/CMS-7699