[Building Sakai] FW: Melete : Editor adds an extra line

[Arlow, Magdaleen]

This message (and attachments) is subject to restrictions and a disclaimer. Please refer to http://www.unisa.ac.za/disclaimer for full details.
________________________________

We sent this message to Etudes for specific Melete advice, but wanted to ask the community whether other users experienced similar problems with Melete after the 2.9 upgrades.

Thanks

Magdaleen Arlow
Deputy-Director : Academic Systems Development
ICT Department

' +27 (0) 12 429 3102
Cell + 27 (0) 82 783 9163
Email : arlowm at unisa.ac.za<mailto:arlowm at unisa.ac.za>


From: Mogaswa T
Sent: 09 December 2013 01:48 PM
To: dev at etudes.org
Subject: Melete : Editor adds an extra line

Dear All,

I am using Sakai 2.9.1, Melete 2.9.1 and the CK Editor that comes with Sakai 2.9.1.

When using the CK Editor to enter "Textual" content, after clicking Save the editor adds an extra line at the beginning of the document. In fact it adds the following html code <p><br />&nbsp;</p>.

The same html code is added every time a SAVE or DONE button is pressed. This only happens on Melete and not any other sakai tools.

I initially thought that it relates to the CK Editor options - in particular the following
breakBeforeOpen : true,
            breakAfterOpen : false,
            breakBeforeClose : false,
            breakAfterClose : true

After toggling the above CK Editor ptions, I am still having  the same problem.

Is the a place in melete that sets the behaviour of the CK Editor?

The closest I could get to a solution is this problem: http://collab.sakaiproject.org/pipermail/sakai-dev/2009-May/001330.html

"Melete uses sakai:inputRichText tag to render FCK editor while most of
the other sakai tools use sakai:richTextArea tag. When we were working
on this issue it was recommended to use sakai:inputRichText tag and the
other tag was being deprecated but it never did and is actually a better
tag."

Could the sakai:inputRichText be responsible for this odd behaviour?

Has anyone ever seen this before and what was the solution to it?

Regards

Thabo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131209/2bdaf880/attachment.html