Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
TinyMCE Config (take 2)
System
The format of my previous post got a little screwed up for reasons unknown, hopefully this one reads better....
I am having some problems with TinyMCE configuration and am hoping someone can point me in the right direction.
1) When I add the following in my DCT ..
<textarea cols="50" external-editor="tinymce" external-editor-inline="t" required="f" rows="20" wrap="off"/>
the default TinyMCE editor is displayed, so far so good.
2) When I add the config as follows ...
<textarea cols="50" external-editor="tinymce" external-editor-config="custom1" external-editor-inline="t" required="f" rows="20" wrap="off"/>
Then different toolbars are displayed as per the configuration in IWHOME\httpd\iw\tinymce\config\custom_config.js which looks as follows ..
IWTinyMCECustomConfig("custom1", "toolbarRow",
"whitespace,styleselect,fontselect,fontsizeselect,forecolor,||,bold,italic");
3) if I change the custom_config.js to add or remove a button the change is not reflected
4) Likewise, if I change the from "custom1" to "myconfig" (in both the DCT and TinyMCE config file) the TinyMCE editor appears to revert back to the default.
5) Interestingly if I then change the config ID in the DCT back to "custom1" without changing the name in the TinyMCE config file then the toolbars associated with "custom1" are displayed.
It's almost as though the TinyMCE configuration is being read from a different location than IWHOME\httpd\iw\tinymce\config\custom_config.js or the config is somehow cached .. I even resorted to an iwreset but this made no difference.
I am following the steps in the forms publisher dev guide but can't seem to figure out why TinyMCE is behaving as it is.
ps: we are using TeamSite 7.1
thanks in advance
Find more posts tagged with
Comments
Rick Poulin
All three of your problems are very simple to explain. This custom_config.js is read by your browser -- the server side is entirely unaware of it. Hence, your browser cached it and that's why you're basically not seeing that file change. Clear your browser cache (in IE, you sometimes have to go as far as opening the temp files folder and deleting this file yourself). That should do it.
Migrateduser
thanks for the quick response
yes, that was all it was ... IE browser caching strikes again