tinymce configure cleanup

Is it possible to configure how tinymce cleans up its content? For example, tinymce is stripping out the querystring from links but I don't want it to do that.

The docs relating standalone tinymce indicates that it is possible but nothing in httpd/iw/tinymce/config indicates that this can be done.

Find more posts tagged with

Comments

Adam Stoller

Is it possible to configure how tinymce cleans up its content? For example, tinymce is stripping out the querystring from links but I don't want it to do that.

The docs relating standalone tinymce indicates that it is possible but nothing in httpd/iw/tinymce/config indicates that this can be done.

This may seem a strange question - but where is the documentation for TinyMCE that gets shipped with FormsPublisher?

I see a one page entry in the Supplemental guide and a caveat listed in the Release Notes - but nothing like the VFE manual.

There's a note saying that you can only use the version that is shipped with TeamSite - but I see no mention of the version number - so even if I go to the web site I won't necessarily know which documentation to look at / download.

I just checked the support site (where they still seem to fail to put the latest documentation under the Documentation section so you have to go through the Product section to get to it - sigh) and I don't see any TinyMCE documentation there either - did I miss it?

On a related note - is TinyMCE fully server-based - or is there a client installation as well (like with VFE)?

nipper

On a related note - is TinyMCE fully server-based - or is there a client installation as well (like with VFE)?

AFAIK, TinyMCE is fully server based. Greg Zevin did an integration between TS 5.5 and TinyMCE and there was no local component. It does not appear to have changed in that respect since then

Andy

yanSi

There is no client component to install for tinymce. Tinymce is located on the server at httpd/iw/tinymce.

The tiny mce docs are located under httpd/iw/tinymce/docs. They're not docs provided by interwoven, they're povided by the makers of tinymce for those who want to integrate tinymce into their own products. Most of the configuration settings mentioned in these docs are not relevant to us developers since interwoven already took care of the intergration between tinymce and FormsPublisher. The only configurable settings of tinymce within FormsPublisher are exposed at httpd/iw/tinymce/config I think.

jbum

Can you please post an example of the URL issue you're having? I'd like to see if it's a problem with inserting the link or the cleanup that happens during save.

Yes, most of the documentation provided by the supplier discusses the integration APIs. Most of the commonly used functionality has been integrated into TeamSite.

Are there any specific configuration/initialization items you'd like to see not currently in the product today?

yanSi

URLs such as this: www.abc.com/abc.aspx?variable=big will have everything after abc.aspx stripped out.

There are certain class id and html attribtes that tinymce strips out too. For example, the bgcolor attribute of tables are stripped out and class IDs on lists are stripped out.

There's one very important error that I have found in tinymce last week. My datacapture has two tinymce editors. I find that if I add images in both editors and then preview/generate the page, some images will have the width and height set to zero!!!

jbum

URLs such as this: www.abc.com/abc.aspx?variable=big will have everything after abc.aspx stripped out.

There are certain class id and html attribtes that tinymce strips out too. For example, the bgcolor attribute of tables are stripped out and class IDs on lists are stripped out.

There's one very important error that I have found in tinymce last week. My datacapture has two tinymce editors. I find that if I add images in both editors and then preview/generate the page, some images will have the width and height set to zero!!!

I've filed a bug for the URL issue. Bug 69662.

kmu

I cannot create relative anchor links (e.g. #top) using TinyMCE.

Adam Stoller

This is perhaps a more general question than what started this thread, but it seems related, so I figured I'd add it here instead of starting a new thread.

(TS 6.7.1 on W2K SP4 )

How do you customize / configure TinyMCE ?

I found

iwhome/httpd/iw/tinymce/config/custom_config.js

- but it doesn't look like anything is reading it because I changed the settings for the first toolbar and see no change when I edit a DCR that uses TinyMCE.

The documentation I've seen all indicates that you have to set

external-editor="tinymce" external-editor-inline="f"

, which I've done.

I've seen one or two posts that make mention of the

external-editor-config

but the documentation only refers to that for VFE not for TinyMCE ... - However, I tried setting it to

"/iw/tinymce/config/custom_config.js"

and it still didn't seem to have any effect.

I've also tried running iwreset -ui just in case - but that didn't seem to have any effect either.

I'm reasonably sure (a.k.a.: hoping) that there's a way to do some "simple" customizations of the TinyMCE window (like removing items from the toolbar for which we don't want users to have access) - but I don't seem to see it as yet and am hoping that someone here may have figured it out or can point me to the proper place in the proper documentation to find it.

Thanks

Adam Stoller

This is perhaps a more general question than what started this thread, but it seems related, so I figured I'd add it here instead of starting a new thread.

(TS 6.7.1 on W2K SP4 )

How do you customize / configure TinyMCE ?

I found
iwhome/httpd/iw/tinymce/config/custom_config.js
- but it doesn't look like anything is reading it because I changed the settings for the first toolbar and see no change when I edit a DCR that uses TinyMCE.

The documentation I've seen all indicates that you have to set
external-editor="tinymce" external-editor-inline="f"
, which I've done.

I've seen one or two posts that make mention of the
external-editor-config
but the documentation only refers to that for VFE not for TinyMCE ... - However, I tried setting it to
"/iw/tinymce/config/custom_config.js"
and it still didn't seem to have any effect.

I've also tried running iwreset -ui just in case - but that didn't seem to have any effect either.

I'm reasonably sure (a.k.a.: hoping) that there's a way to do some "simple" customizations of the TinyMCE window (like removing items from the toolbar for which we don't want users to have access) - but I don't seem to see it as yet and am hoping that someone here may have figured it out or can point me to the proper place in the proper documentation to find it.

Thanks

A quick chat with IWOV Support - pointed me to this Support KB - which does a very good job of answering this specific question.

Phanie

Hi all, I ran into this issue last week and figured out tht the customization of TinyMCE is to be mentioned in this way ... [html] [/html] where "custom1" is my custom code present in custom_config.js After mentioning this we need to refresh the browser window to see the changes. It works. HTH Phanie

Phanie

Hi all,

I ran into this issue last week and figured out tht the customization of TinyMCE is to be mentioned in this way ..

[textarea external-editor="tinymce" external-editor-inline="t" external-editor-config="custom1" required="t" /]

where "custom1" is my customized code for TinyMCE in custom_config.js
We need to refer to our custom1 in external-editor-config attribute.

After saving the changes just refresh the browser page and it would work.
I too reached support but was not helpful so had to figure it out.

HTH
Phanie

scandorph

@yanSi: The URL params getting stripped is a bug.
@kmu: That too is a bug and fixed in SP1.

kshitiz

I've filed a bug for the URL issue. Bug 69662.

Has there been any patch for this bug???

Migrateduser

Has there been any patch for this bug???

attached is my tiny_mce_src.js file that support patched to fixed the Query String being stripped from the URL's.. they told me to just replace the file (but upgrades/patches will overwrite it, so be aware)..

also, since I was editing the SRC file, you will see this one has a new variable at the top (this is my customization, not IWOV's) called "custom_valid_elements".. to stop all the stripping of HTML tags my users wanted (since in 6.7.1 there you cant turn off clean HTML and they still wanted to limit to valid tags)

and I commented out and replaced this line:



 //this.defParam("valid_elements", "+a[name|href|target|title|class],strong/b[class],em/i[class],strike[class],u[class],+p[dir|class|align],ol,ul,li,br,img[class|src|border=0|alt|title|hspace|vspace|width|height|align],sub,sup,blockquote[dir|style],table[border=0|cellspacing|cellpadding|width|height|class|align],tr[class|rowspan|width|height|align|valign],td[dir|class|colspan|rowspan|width|height|align|valign],div[dir|class|align],span[class|align],pre[class|align],address[class|align],h1[dir|class|align],h2[dir|class|align],h3[dir|class|align],h4[dir|class|align],h5[dir|class|align],h6[dir|class|align],hr");

 this.defParam("valid_elements",custom_valid_elements);

looks like the real change is in TinyMCE.prototype.getMCERealSrc function below, where they added the follwing 2 lines:


--------NEW ADDITION----
if(tmpURLTokens['query'])
   url += "?"+tmpURLTokens['query'];
-------END NEW ADDITION---- 


TinyMCE.prototype.getMCERealsrc=function(url) {
    var tmpURLTokens = tinyMCE.parseURL(url);
    var tmpBaseURLTokens = tinyMCE.parseURL(this.settings['base_href']);
    if (tmpURLTokens['host'] && tmpURLTokens['host'] == tmpBaseURLTokens['host']) {
        url = tmpURLTokens['path'];
  if(tmpURLTokens['query'])
   url += "?"+tmpURLTokens['query'];
    }

    return url;
};

kshitiz

Thanks!! That worked.

test_parameters.rptdesign

catorarn

I have customized the Interwoven SitePublisher TinyMCE Rich Text Format editor to disable automatic cleanup.

Customisation steps are a change in this file: C:\interwoven\iw-home\httpd\webapps\content_center\livesite\javascript\tiny_mce/tiny_mce.obf

The change is to set the property:

this._def("cleanup",false);

The business reason for this is that the web development team want to be able to copy full HTML including css and javascript into a Textarea component.

tanguyr

Hello,

Regarding changing the list of valid elements: i have found a different way to do this without changing the core tinymce js file. You can override this param ("valid_elements") in the custom_config.js file as follows:

IWTinyMCECustomConfig("[your_config_name]", "valid_elements","[your_list_of_valid_elements]");

i think this is better than changing the tinymce js file because it won't (shouldn't?) get overwritten when you patch or upgrade.

Even better, you can use something like:

IWTinyMCECustomConfig("[your_config_name]", "extended_valid_elements","[your_list_of_valid_elements]");

this list is appended to the valid_elements defined in the tinymce js file, so you can just put in what you're missing.

Regards,
/t

Edit:
IWTinyMCECustomConfig("[your_config_name]", "cleanup","false");

turns off cleanup completely

scandorph

Has there been any patch for this bug???

Yes the official patch should be in 671sp1 p1 or p2.

scandorph

Hello,

Regarding changing the list of valid elements: i have found a different way to do this without changing the core tinymce js file. You can override this param ("valid_elements") in the custom_config.js file as follows:

IWTinyMCECustomConfig("[your_config_name]", "valid_elements","[your_list_of_valid_elements]");

i think this is better than changing the tinymce js file because it won't (shouldn't?) get overwritten when you patch or upgrade.

Even better, you can use something like:

IWTinyMCECustomConfig("[your_config_name]", "extended_valid_elements","[your_list_of_valid_elements]");

this list is appended to the valid_elements defined in the tinymce js file, so you can just put in what you're missing.

Regards,
/t

Edit:
IWTinyMCECustomConfig("[your_config_name]", "cleanup","false");

turns off cleanup completely

That's right. Also, you'll have to mention the particular config id in the external-editor-config attribute of the textarea element in your DCT. This is a supported way of making the changes available in 6.7.1 sp1+.

Migrateduser

Hello,

Regarding changing the list of valid elements: i have found a different way to do this without changing the core tinymce js file. You can override this param ("valid_elements") in the custom_config.js file as follows:

IWTinyMCECustomConfig("[your_config_name]", "valid_elements","[your_list_of_valid_elements]");

i think this is better than changing the tinymce js file because it won't (shouldn't?) get overwritten when you patch or upgrade.

Even better, you can use something like:

IWTinyMCECustomConfig("[your_config_name]", "extended_valid_elements","[your_list_of_valid_elements]");

this list is appended to the valid_elements defined in the tinymce js file, so you can just put in what you're missing.

Regards,
/t

Edit:
IWTinyMCECustomConfig("[your_config_name]", "cleanup","false");

turns off cleanup completely

that is only available as of 6.7.1 SP1, not 6.7.1 (without SP1)

tanguyr

that is only available as of 6.7.1 SP1, not 6.7.1 (without SP1)

Thanks for the clarification - this thing has so many options i can't keep clear in my head what was added when.

If i understand correctly, this is also only true for the TinyMCE used with FormsPublisher, not the one used with Livesite/Sitepublisher. It's a pity that there isn't *one* way to customize and configure TinyMCE, no matter "where" it is being used.

Regs,
/t

Migrateduser

Has anyone had any luck adding a style as a extended_valid_element? I have the javascript piece working so it doesnt get stripped out. I have added the style in the same way, but when you click the update button, it takes all the code out of
[html]< style>Whatever[/html]and leaves
[html]< style />[/html]Thanks.

TommyWillB

where is the documentation for TinyMCE that gets shipped with FormsPublisher?

They have some info in the TeamSite 6.7.1 SP1 Forms Developer's guide, but there is no such guide for the non SP1 version of 6.7.1.

The 6.7.0 version of the guide only talks about the older Ektron VisualEditor.

So all of us with 6.7.1 have no clue which things work only in SP1.

:-/