CMS Blog
Teamsite's TinyMCE considered harmful
Since the 6.7.1 Service pack 1 Teamsite is blessed with a second rich text editor for use in content entry screens. At first glance this editor, named TinyMCE, offers a big gain over the previous option for this, the Visual Formatter Active-X component, since TinyMCE is a html&javascript only implementation. And this removes the need for a client installation (not very feasible today when most workstations are locked down from admin-privileges) and better performance. Furthermore, TinyMCE is a well known, open source/standards and highly customizable editor. Sounds really good, doesn't it?
Well, actually no. Interwoven has chosen to wrap the original TinyMCE object into a custom implementation that really hides all but the basic configuration options. So yes, you can (re)organize the standard toolbar-b***ons and you can define a list of text- and table-styles. Well and that's all.
Some examples of what I really miss for configuration (and that is offered in the standard TinyMCE) is:
- turn html cleaning on/off
- configure which elements/attributes are cleaned
- extra cleaning when pasting from ms-word
- which style-sheet is used in the editor (note: because of this you are forced to share 1 stylesheet across all branches that share the same server, very disappointing)
Apart from the above remarks the TinyMCE version that comes with Teamsite is old (1.4.5) while 3.2.2 is current today.
Let's hope that Interwoven will soon upgrade to a more recent version AND open all of the standard available options to us.
BTW, below is a little but nasty workaround that will NOT be overwritten when you upgrade you Teamsite install:
1. move your <iw-home>httpd/iw/tinymce to <iw-home>httpd/iw/tinymce2
2. locate the 'alias'-section in <iw-home>/iw-webd/conf/iwwebd.conf.template and add these lines BEFORE the alias for /iw/:
Alias /iw/tinymce/ "__IW_TS_HOME__/httpd/iw/tinymce2/"
Alias /iw/tinymce "__IW_TS_HOME__/httpd/iw/tinymce2"
3. run 'iwreset -ui'
4. now you are free to modify the <iw-home>/httpd/iw/tinymce2/config/custom_config.js to change the default settings
What is new in Teamsite 6.7.2?
If you want to know more about the new Teamsite 6.7.2 version I would recommend the devnet-webcast at: Devnet webcasts (free membership) but in short here is a quick (but disappointing) list:
1. Vista support (what now already?)
2. Teamsite and Livesite are now included in 1 install (which makes it a 1.3GB (!!) download).
3. Templating forms: one can now 'search and replace' in a dcr-form.
4. Livesite now offers 'fixed layouts', meaning that a developer can now better control in what layout area a component can be placed by teh end-user. In my opinion, this is a major 'must have' but I'm unsure if the current implementation really covers all (complex) business-requirements that one can think of in this area.
5. Livesite has better/more support for content targeting based on all sorts of profiles.
This Teamsite release shows the strategic move from Interwoven from a cms vendor to marketing tools vendor. Something that pleases Gartner analysts and that might not be a bad idea if one would have a mature finished cms tool set. :-) That's why I'm quite disappointed with this release.
Why should we deploy from Teamsite editions?
I've seen many Teamsite implementations that deploy from the Staging area. This is not optimal and let me explain today why I think so.
Teamsite has excellent version management capabilities that will give you an historic archive over your website, if you chose to use it by creating editions before you actual deploy them. By passing this feature will leave you with a teamsite implementation that misses out on one of the most powerfull features. Apart from this rather theoratical reason there are also some more pratical reasons:
1. you will loose the option to rollback your website to a previous edition
2. the staging area is not garantueed to be stable during the lifespan of the deployment, which can give unexpected results
3. you will not be able to compare editions to know what has changed in between two deploys
4. you will not comply anymore with tracebility requirements (like f.i. the Sarbanes-Oxley laws)



