[Portfolio] Question about editor in forms for OSP
hbzhang at vt.edu
Thu Jul 29 12:30:02 PDT 2010
In the PortfolioAdmin site, under the system directory, there is a file
In line 38, you can find this:
src="/library/editor/FCKeditor/fckeditor.js"> // empty block </script>
If you use either customized render or the default render formCreate.xslt,
you need to make sure it calls the fckeditor.js under the
The fckeditor.js under that path should be the one for your 22.214.171.124 FCK
editor. Any other path may not point to the Sakai instance FCK editor js.
I am not exactly sure this can help. It is just I had similar experiences
before, I found this is a small trick for me to resolve the problem I had.
From: portfolio-bounces at collab.sakaiproject.org
[mailto:portfolio-bounces at collab.sakaiproject.org] On Behalf Of Brian Dashew
Sent: Thursday, July 29, 2010 2:35 PM
Subject: [Portfolio] Question about editor in forms for OSP
As we were investigating a problem some users were experiencing getting
content into a form containing an FCK Editor field, we discovered that our
instance of OSP was for some reason using an old version of the editor
(2.4.1, while the rest of our instance of Sakai is running 126.96.36.199). We
aren't sure if that's an institutional oversight or an intentional feature
of the tool. Is there a reason we would not want to include an updated
version of the editor in our forms for OSP? And does anybody have
documentation for how to change this old version out for the version running
in other tools?
Instructional Designer, Academic Technology & eLearning
Poughkeepsie, NY 12601
Email: Brian.Dashew at marist.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the portfolio