cancel
Showing results for 
Search instead for 
Did you mean: 

WYSIWYG Issues

daxter123
Champ in-the-making
Champ in-the-making
Hi

I am facing following issues when adding/editing content through WYSIWYG editor.

1. on inserting the image the editor doesnot display image
2. on pressing enter button twice editor generates HTML like this <p> </p> which display non-displayable character after rendition
3. i have applied this configration http://wiki.moxiecode.com/index.php/TinyMCESmiley Tonguelugins/table in web-client-config-wcm.xml but seems its not working.

             <param name="table_styles">VZDN Table=vzdnTable</param>
             <param name="table_default_border">1</param>
             <param name="table_default_cellpadding">0</param>
             <param name="table_default_cellspacing">0</param>

can anybody tell me is there any issue in configuring the editor behaviour.

thanks
5 REPLIES 5

scottf
Champ on-the-rise
Champ on-the-rise
I too had the same issue as Number 1, it has been raised as a defect in JIRA.

daxter123
Champ in-the-making
Champ in-the-making
Thanks Scott,

Any idea about point 2 and 3…

Can we apply this type of configuration for TinyMCE in alfresco.

Thanks

ben
Champ in-the-making
Champ in-the-making

scottf
Champ on-the-rise
Champ on-the-rise
Thanks Scott,

Any idea about point 2 and 3…

Can we apply this type of configuration for TinyMCE in alfresco.

Thanks

Hey,
I found when adding plugins, like the table plugin, to the tinymce configuration, doing it solely through web-client-config-wcm.xml was not enough as some config items were not being picked up or initialized properly.

To fix this I now configure my tinymce editor through a combination of the xml file and also by manually editing the tinymce settings in Alfresco\tomcat\webapps\alfresco\scripts\ajax\xforms.js

Not ideal but doing it this way allows me to tweak the editor and numerous plugins in more ways than purely through the xml file.

samuel_penn
Champ in-the-making
Champ in-the-making
On point (1), which browser is that in? We get that problem in IE, though it seems to work just fine in Firefox.

Sam.