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

Using form tag on VFE

aby_sam

One of our content class used for editing XHTML content, it's having a strange problem.
When content writers use form tag within the VFE, the content saves perfectly. However if the user edits the same DCR, on clicking the VFE, the VFE editor disappears from the DCR.
A second try on editing the same DCR brings back the VFE editor, however this time all contents are lost.

Everthing is working as designed the moment I remove the form tag.

Anyone can throw light to solve this issue.

TS 6.0
AIX 5.2

Find more posts tagged with

Comments

kaalraa

One of our content class used for editing XHTML content, it's having a strange problem.
When content writers use form tag within the VFE, the content saves perfectly. However if the user edits the same DCR, on clicking the VFE, the VFE editor disappears from the DCR.
A second try on editing the same DCR brings back the VFE editor, however this time all contents are lost.
Everthing is working as designed the moment I remove the form tag.
Anyone can throw light to solve this issue.
TS 6.0
AIX 5.2

Have you done any customisation on VFE?

Adam Stoller

One of our content class used for editing XHTML content, it's having a strange problem.
When content writers use form tag within the VFE, the content saves perfectly. However if the user edits the same DCR, on clicking the VFE, the VFE editor disappears from the DCR.
A second try on editing the same DCR brings back the VFE editor, however this time all contents are lost.

Everthing is working as designed the moment I remove the form tag.

Anyone can throw light to solve this issue.

TS 6.0
AIX 5.2

This is, I believe, a long-known issue / limitation of the VFE field. I believe it is covered by bug #52327:[indent]Internet Explorer does not properly render VisualFormat HTML that contains a
<form> tag.[/indent] which is listed as a "Fixed Issue" for TeamSite 6.5.0 SP1.

So unless you upgrade, do not expect to be able to embed <form> tags within your VFE fields.

gzevin

adding to fish's comment.

a work around is to place a structure in the DCT that will let you insert form tags. E.g., a replicant with an OR-container with VFE and plain textarea.

aby_sam

Thanks for your input.. The plain text area may not be a solution as far as our DCR is concerned. Most content creators make use of the VFE properties.

I found on the KB that this issue was fixed in TS 6.5 SP1. Since we have no plans to upgrade so soon, not using the form tag is the best available alternative Smiley Happy

gzevin

Thanks for your input.. The plain text area may not be a solution as far as our DCR is concerned. Most content creators make use of the VFE properties.

I found on the KB that this issue was fixed in TS 6.5 SP1. Since we have no plans to upgrade so soon, not using the form tag is the best available alternative

I am not suggesting to permanently switch to plain text area. The contributors could easily be trained to paste form HTML in a separate area, while still using VFE for the rest of the document.

It's strange how you can avoid using the form tag, if you DO need to use it, but I leave that with you Smiley Happy