New answers tagged experience-editor
3
It's completely different in Experience Editor.
When you click on any of the versions, there is a request to
/-/speak/v1/ExperienceEditor/SelectVersion.js
It builds an url for selected version, checks if the item has presentation details and finally it calls code similar to:
var url = ExperienceEditor.Web.setQueryStringValue(ExperienceEditor....
0
First of all, you need to create and register command to create a normal URL for your current page. you need to create a class which will inherit PipelineProcessorRequest<ItemContext> and will override the ProcessRequest method. In this class, we need to write our code for getting the URL. I am writing a simple code here, but you can change it as per ...
0
The default WebEdit buttons "Move Up" and "Move Down" under /sitecore/content/Applications/WebEdit/Custom Experience Buttons are actually meant for moving the item up and down respectively. It doesn't move the field values of the same item.
So, instead of trying to explore how to move fields using those custom experience buttons (which ...
1
I don't think this is something your going to be able to achieve with custom experience buttons. Generally the order of the display of fields in a component is fairly fixed so this would be a bit of an odd approach / concept for Content Editors.
You have 3 options here I think:
Option 1 - Create a new instance of a component where the text is above the title ...
0
I found the cause of the problem.
It was caused by myself during the upgrade of glassmapper. The views are rendered by React and therefore it is needed that the models already contain the rendered fields in experience editor mode.
By installing a higher version of the glassmapper nuget package the files App_Start\GlassMapperSc.cs and App_Start\...
1
Please change requestValidationMode="4.0" to requestValidationMode="4.5" in web.config file. It was working for me.
Top 50 recent answers are included
