Templates are out of date. When I update LS erases any user edits.

1) Update Template.
2) Edit page that uses this Template.

"Your page has some templates that are out of date."

My page template is simple, header, footer, nav margin, and it has a 'central text area' that the user can edit. This 'central text area' is the only component the user can edit.

But when I modify the template that holds this content and then update the page based off this template the 'center text area' field component gets erased (reverted to its initial template content, i.e. blank)

Basically, if I ever update my template all my user content gets erased once they update their template.

Am I doing something wrong?

Do I have to remove the 'central text area' from my template and make it a separate template or component? (and also make sure never to update it!)

thanks,

Find more posts tagged with

Comments

wscott

Are you selecting Update or Overwrite when you update the template? If you select Update, this should not occur. UNLESS you've actually deleted/re-added the component on the template (in that case it counts as a whole new component and won't pick up the customizations to the previous component).

Shazzer

I'll expect a bashing for this one, as I know the updating of templates is *supposed* to have been fixed up in 2.2.1, but we have always had exactly the same problem with template updates. There is a simple solution though...

The component update works perfectly, but template updates ALWAYS wiped our user-entered content from components that were part of the updated template - but ONLY if you leave the default settings for updating templates intact.

Our initial solution was to remove all centre components (ie the user-entered content areas) from all templates, leaving only the header, footer, nav etc. However, we later had a requirement to allow users to add an id to the nav component, meaning that all template updates would wipe the user-entered id on every page.

The good news is that doing your updates as follows should ensure you never have the problem again:

1. Make a test component change and submit the component. When you do the get-latest on components in the TEMPLATES branch, ENSURE you select "Overwrite all, discarding changes" rather than the default of "Update all, preserving changes". (Yes, I know this totally goes against reason.)
2. Submit your updated templates and when doing the get-latest components in the content store, ENSURE you keep the default option settings intact - "Update all, preserving changes".

On our sites, this method updates all components and templates perfectly, leaving all user-entered data alone. Updating the template branch with new components with the default of "preserve changes" wipes the user-entered data every time once propagated through the content store, although I am certain this is not what it is meant to do.

If anyone can illuminate on why the solution above works but leaving the default settings on when updating templates with new components causes content xml loss, would be cool to know.