Re: TinyMCE vs W3C standards. Tables not working at all in tinyMCE.

On 7/5/2010 8:49 AM, Sachin wrote:
> Hi All
>
> I am using Lenya 2.0.3 and tinyMCE editor to edit my pages. However 
> tinyMCE editor is showing all the attributes that are depricated 
> according to w3c recommendations for xhtml.
> So whenever I try to save my page with having some deprecated 
> attribute, all the changes which I have made to the page get lost.
>
> Is there any way I can correct this? I tried integrating tinyMCE 
> version 3 but it did not worked with lenya 2.0 for me.
>
> Tables is tinyMCE are not working at all. The error in the logs is:
>
> 2010-07-05 19:05:47,953 [SocketListener0-4] ERROR lenya.publication - 
> usecase.validationError, attribute "align" not allowed at this point; 
> ignored, -1, -1
> 2010-07-05 19:05:47,954 [SocketListener0-4] ERROR lenya.publication - 
> usecase.validationError, attribute "border" not allowed at this point; 
> ignored, -1, -1
> 2010-07-05 19:05:47,954 [SocketListener0-4] ERROR lenya.publication - 
> usecase.validationError, attribute "cellpadding" not allowed at this 
> point; ignored, -1, -1
> 2010-07-05 19:05:47,954 [SocketListener0-4] ERROR lenya.publication - 
> usecase.validationError, attribute "cellspacing" not allowed at this 
> point; ignored, -1, -1
> 2010-07-05 19:05:47,954 [SocketListener0-4] ERROR lenya.publication - 
> usecase.validationError, attribute "dir" not allowed at this point; 
> ignored, -1, -1
> 2010-07-05 19:05:47,954 [SocketListener0-4] ERROR lenya.publication - 
> usecase.validationError, attribute "height" not allowed at this point; 
> ignored, -1, -1
> 2010-07-05 19:05:47,954 [SocketListener0-4] ERROR lenya.publication - 
> usecase.validationError, attribute "width" not allowed at this point; 
> ignored, -1, -1
> 2010-07-05 19:05:47,954 [SocketListener0-4] ERROR lenya.publication - 
> usecase.validationError, unknown element "tbody" from namespace 
> "http://www.w3.org/1999/xhtml", -1, -1
> 2010-07-05 19:05:47,954 [SocketListener0-4] ERROR lenya.publication - 
> usecase.validationError, unfinished element, -1, -1
>
> Please suggest.
>
> Regards
> Sachin

You could add the attributes to the schema, which would get rid of your 
validation problem. I can't remember if it uses a cleaner or not. You 
could take some of the cleaning XSLT items from the FCK module if it 
does use a cleaner. If it doesn't you could copy the FCK cleaning code 
to make it clean up the source.

Richard