Customizing TinyMCE per branch/component?

Hi,

is it possible to customise the livesite TinyMCE per branch, component or the like?
E.g. has the content of customer-livesite-resource-config.xml a teamsite-global context?

Cheers, Ronald

Find more posts tagged with

Comments

miroperez

The tinymce customization is currently a global setting. What sorts of things would you like to customize on more atomic level?

niske

I had understood that you can create a separate config file and then somehow reference this config file in your DCT
don't know the details, sorry

RonaldV

Well excuse my french: that is somewhat of a strange question.

Teamsite (without LS) is very strong in application seperation: you can have 100 different website fed from teamsite and each of these can be configured seperately in almost every sense.

With Livesite this whole idea is lost completely: all components/templates have global availability for instance.

Now back to the tinymce config, I can easily think of a website X (livesite based) that only allows some minor tinymce features (bold, underline, italic, no more) AND a website Y (livesite based) that requires the full tinymce feature scope. And with a global tinymce config they can not share the same teamsite server anymore.

That's why.

RonaldV

DCT? That's Teamsite NOT Livesite.

Frederik

ideally, each LiveSite textarea datum should be able to use a separate TinyMCE configuration. Just like each TS forms' textarea can have a separate VisualFormat configuration.

side-note: TS forms can use separate TinyMCE configs per textarea, but still not as good as VisualFormat. The good thing of VF configuration was that they were using separate files. Each project could create its own VF conf files, and not have to mess with merging project configurations in a global config file (as with TinyMCE & FormsPublisher)

This came up before - obviously with the same conclusion ;-)
http://devnet.interwoven.com/forums_vb/showthread.php?t=20861&forumid=66&highlight=TinyMCE

kmu

One of these dicussions should be made sticky - happens to be a common question...