nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

unable to edit in a template from DCR

SethHickel

Recently when I choose to edit a dcr it opens in a text editor instead of opening the template used to create the dcr. What could have changed? Any suggestions on how to change whatever changed back?

Thanks.

Find more posts tagged with

Comments

nipper

You lost the Extended Attributes telling TS you have a DCR.

I have a script that can fix the EAs if needed.

Andy

ISCBorisB

Recently when I choose to edit a dcr it opens in a text editor instead of opening the template used to create the dcr. What could have changed? Any suggestions on how to change whatever changed back?

Thanks.

Chances are, you've somehow lost "TeamSite/Templating/DCR/Type" Extended Attribute.

Check DCR Properties, if above is indeed the case re-set an attribute to the correct
"Category/Type" Value using for example "iwextattr" Command

nipper

If you lost one, chances are you lost others as well, so it is worth using a script that looks at all DCRs and fixing them if necessary

SethHickel

Correct - tks - seeing that now. How might that occur? It seems to be more prevelant in one branch then in another. I think that a lot of these are due to an incident where we had file corruption. I can understand those - but are there other situations that could cause this to occur? For instance - if a content provider decided to open the generated HTML to edit in DreamWeaver instead of the form would that break the connection or would it simply cause the DreamWeaver edits to be overwritten the next time the file was generated from the form?

nipper

Correct - tks - seeing that now. How might that occur? It seems to be more prevelant in one branch then in another. I think that a lot of these are due to an incident where we had file corruption. I can understand those - but are there other situations that could cause this to occur? For instance - if a content provider decided to open the generated HTML to edit in DreamWeaver instead of the form would that break the connection or would it simply cause the DreamWeaver edits to be overwritten the next time the file was generated from the form?

There was/is a setting *somewhere* that tells TS to maintain EAs on import. It used to be in the iw.cfg (TS 5.5 days) and now I think it is in the UI, though I do not remember where. If you have that set to no, then yes, edit with DW and submit will lose the EA.

The history if the file may tell you what happened

Andy

SethHickel

Thanks - much appreciated!

nipper

Thanks - much appreciated!

Search the UI customization guide: Configuring ContentCenter Extended Attribute Behavior upon Import