[Building Sakai] Melete Problem

[Coetzee, Nico]

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

Hi Mallika

Thanks for the reply, I only saw the thread after I posted, sorry.  Do you perhaps know where to put the autoParagraph=false setting, must this be in sakai.properties or somewhere else?

Regards
Nico


From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Mallika M Thoppay
Sent: 10 December 2013 07:25 PM
To: sakai-dev at collab.sakaiproject.org; dev at etudes.org
Subject: Re: [Building Sakai] Melete Problem

Nico,

If you followed the thread that was reported for this issue, supposedly autoParagraph: false fixed it for someone. You can try that.

Thanks,
Mallika
Melete Team

On 12/9/2013 10:57 PM, Coetzee, Nico wrote:
This message (and attachments) is subject to restrictions and a disclaimer. Please refer to http://www.unisa.ac.za/disclaimer for full details.
________________________________

Dear All,

We are 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

Nico Coetzee





_______________________________________________

sakai-dev mailing list

sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>

http://collab.sakaiproject.org/mailman/listinfo/sakai-dev



TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"




--

Mallika M Thoppay

Learning Systems Developer

Etudes Inc

http://etudes.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131211/41cdcc20/attachment.html