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; } } }

DCT with Multiple Visual Format Editors

boggle

Hi has anyone managed to get Visual format editors on the same DCT to work with different .xml controller files?
We are using Teamsite 6.7.2 on Windows 2003 servers with clients mixed between Windows XP and Windows 2000.

If we have identical editors then things work but is we try to use different controller files so that there we can model different editor behaviour [different stylesheet, and some fields allow

others do not, ...] then we have a problem, especially with new form creation, where only one editor field gets populated. Basically as long as you only iedit one textarea per DCT edit session you are fine (only one editor invoked): just don't try to modify both of the text areas.
if both text areas use:
it works but if you set one to
<textarea required="t" cols="66" rows="7" external-editor="visualformat" external-editor-config="/iw/config/ei-ae_internet_breadcrumbs.xml"> to have different behaviour look-out.

If all the editors per DCT have to have the exact same features it limits the usefulness. Is there a workaround for this.<textarea required="t" cols="66" rows="7" external-editor="visualformat" external-editor-config="/iw/config/ei-ae_internet_breadcrumbs.xml"> to have different behaviour look-out.

If all the editors per DCT have to have the exact same features it limits the usefulness. Is there a workaround for this.

Find more posts tagged with

Comments

boggle

Sorry about the formatting of my post. It did not look like that when I was writing it. Could still use some help

creditosBanco.rptdesign

Pawan

Hi has anyone managed to get Visual format editors on the same DCT to work with different .xml controller files?

We are using Teamsite 6.7.2 on Windows 2003 servers with clients mixed between Windows XP and Windows 2000.

If we have identical editors then things work but is we try to use different controller files so that there we can model different editor behaviour [different stylesheet, and some fields allow others do not, ...] then we have a problem, especially with new form creation, where only one editor field gets populated. Basically as long as you only iedit one textarea per DCT edit session you are fine (only one editor invoked): just don't try to modify both of the text areas.
if both text areas use:
< textarea required="t" cols="66" rows="7" external-editor="visualformat" external-editor-config="/iw/config/service_canada_internet_vfcfg.xml" >
it works but if you set one to
< textarea required="t" cols="66" rows="7" external-editor="visualformat" external-editor-config="/iw/config/ei-ae_internet_breadcrumbs.xml" >
to have different behaviour look-out.
If all the editors per DCT have to have the exact same features it limits the usefulness. Is there a workaround for this.

just fixing the post.

ISCBorisB

Sorry about the formatting of my post. It did not look like that when I was writing it. Could still use some help

You can play with external-editor-inline Attribute. Set it to false and see if it helps. Like this:
<textarea external-editor="visualformat" external-editor-inline="f" ... >

Note though that this trick changes UI slightly, Contributors have to click a button to activate VFE, etc

boggle

Thank you but not really an option at this point to take off the dct. We have users with enough problems when it opens on the page (in the same box). But if there is no other way around it but to make it pop-up I'll bring it up with the powers that be here.

If we do that though, we might just as well set up validation with W3C and use a dumb textbox for data entry.

Actually, has anyone tried just giving the user a textbox and save capability but not allowing submit until the content passes W3C xml validity and accessibility? Thereby skipping the whole issue of the editor? Of course we'll have to work in a way to preview somehow.

ISCBorisB

[...]giving the user a textbox and save capability but not allowing submit until the content passes W3C...

You can do all that and plenty more in a workflow, including Preview, Tagging, Generation, Approval, Submission, you name it.
In such case you may want to remove Save,SaveAs,Generate... buttons and perhaps use tt_data *Command* to instantiate WF on "Finish", etc