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 in 7.3.1

ranjeeth

Hi
we have migrated form 6.7.1 to 7.3(RHEL).In the Templating we used to use VFE editor but since its no longer supported we have to use the TinYMCE.but strangely i see that tiny mice is appending the

tags for the text area like
[HTML]Your fast lane to market and power system data now includes report downloads[/HTML]
with
[html]<p>Your fast lane to market and power system data now includes report downloads </p>[/html]
I tried to change the the values in httpd/iw/tinymce/jscripts/tiny_mce/tiny_mce_src.js as
forced_root_block : ' ',
force_p_newlines : 0,
i have cleared the cache and tried but its still adding those

tags **** the page.
Any help would be appreciated.

Find more posts tagged with

Comments

Rick Poulin

There are so many things wrong with that post..

<paragraph> is not a valid HTML tag. You're going to get even more complications with that down the line.
Changing tiny_mce_src.js directly is very much not supported. You should be changing custom_config.js for FormsPub, or customer-teamsite-resource-config.xml for SitePub. RTM.
It's Javascript, not C. You want forced_root_block=null and force_p_newlines=false
Something else is putting those font tags in there. You're probably pasting from elsewhere. Consider changing valid_elements and/or extended_valid_elements and/or invalid_elements to change the cleanup subroutine suit your needs

ranjeeth

paragraph tag is an xml element from my DCR
I did try chnging them there but no luck

my post was not properly formatted.Igonre the font tags. The point is,its wrapping text with in the paragraph tag in my DCR with the html p tags which is **** the styling.

Rick Poulin

And my point was, you're trying to use an HTML editor to edit markup that is not valid HTML. Sooner or later, that's going to cause you more grief.. but for now, you might get away with (as mentioned) forced_root_block=null and force_p_newlines=false, PLUS registering "paragraph" as a tag that shouldn't be removed, via extended_valid_elements.

Adam Stoller

[...], PLUS registering "paragraph" as a tag that shouldn't be removed, via extended_valid_elements.

I'm not sure, but I think that 'paragraph' was a DCT item element for the textarea in which the WYSIWYG editor was inserted - and thus not actually within the HTML code being viewed / edited.

Rick Poulin

I'm not sure, but I think that 'paragraph' was a DCT item element for the textarea in which the WYSIWYG editor was inserted - and thus not actually within the HTML code being viewed / edited.

Oh.. could be. Ranjeeth, when you changed editor types, did you do anything other than changing the value of the external-editor attribute on the <textarea> node?

ranjeeth

Rpoulin
Apart from external-editor attribute on the node i added the external-editor-config because i have to basically remove some options rather than the Default.Thats all is what I have changed node i added the external-editor-config because i have to basically remove some options rather than the Default.Thats all is what I have changed

ranjeeth

Oh.. could be. Ranjeeth, when you changed editor types, did you do anything other than changing the value of the external-editor attribute on the <textarea> node?

Apart from external-editor attribute on the text area node node i added the external-editor-config because i have to basically remove some options instead of the the default one.That's all is what I have changed