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

TinyMCE fields and HTML Tags

dlsoderberg

TeamSite 6.7.1 SP1 P2 on Linux

We have some templates that require a TinyMCE field for a page or body title. The config has been stripped down to contain only the Italics and Character map buttons for these fields. (probably irrelevant, but thought I would throw it in) Is there a way from a TinyMCE configuration standpoint to keep it from adding the [html]

[/html] tags? I've started on a workaround using Form API to strip out tags, but wanted to see if I was just missing something in the configuration. Just moving towards TinyMCE for everything and used to VFE, so if this is a simple answer, please be gentle.

Find more posts tagged with

Comments

Faizi

TeamSite 6.7.1 SP1 P2 on Linux

We have some templates that require a TinyMCE field for a page or body title. The config has been stripped down to contain only the Italics and Character map buttons for these fields. (probably irrelevant, but thought I would throw it in) Is there a way from a TinyMCE configuration standpoint to keep it from adding the [html][/html] tags? I've started on a workaround using Form API to strip out tags, but wanted to see if I was just missing something in the configuration. Just moving towards TinyMCE for everything and used to VFE, so if this is a simple answer, please be gentle.

Hi,

Have you gone through TimyMCE docs?
Check the TimyMCE docs at this location \\iw-home\httpd\iw\tinymce\docs

Hope this helps.

Thanks,

Firenze

It is a tinyMCE "feature".

You can go into the tinymce configuration files and remove some of their "helpful" html cleaning functionality, but I have been reluctant to to this due to concerns about getting this configuration out of sync with whatever Interwoven ships next.

There is probably a slick way to include an override to the tinymce methods with your javascript methods. I haven't had the time to dig in too deep.

In most cases in my DCTs the tinymce fields are in replicants, so we have trained users to move the text into a html free editor like notepad, delete the replicant and paste it in to remove the leading "p" tag.