When in Experience Editor making changes to some fields, such as a multilist that could control a rendering of items to show, do not reflect on the page until it is saved. This can be confusing and cumbersome for content editors.

Is there a way to force a save and refresh when editing these items in Experience Editor to make the content editing experience better?

1 Answer 1


I wrote a blog post on this a while ago: http://www.flux-digital.com/blog/refreshing-experience-page-editor-after-using-edit-frames-or-buttons/

One word of caution though, we did see some odd issues caused by this firing and causing a save on components where it wasn't needed. So I'd suggest perhaps checking your templates(s) before firing the save, something like the following (not tested):

if (item != null)
 if(item.TemplateID == MyTemplateIds.MyBannerTemplate.ID){
  item.Fields[fieldInfo.FieldID.ToString()].Value = str1;

I'll update the blog post at some point to include info on this but Let me know if you find a better way of doing this or if this works for you.

  • I like this approach. I'm wondering if there is a way to also inform the page that the save has happened so the user doesn't need to see that prompt on refresh.
    – bmyers
    Oct 5, 2016 at 1:38
  • I might be possible using the JavaScript api but I've never done it so I'm not sure to be honest. Oct 6, 2016 at 13:14

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.