[Building Sakai] Problems with Kaltura CKeditor Plugin

[Beth Kirschner]

Thanks Matt -- I tried your simpler approach of adding a comma after kaltura and this worked great:
	extraPlugins: (sakai.editor.enableResourceSearch ? 'resourcesearch,' : 'kaltura,')+'', 

The only additional change I had to make was to copy the kaltura.gif file into the library:
	cp -p kaltura/fckeditor/kaltura/kaltura.gif reference/library/src/webapp/editor/ckeditor/plugins/kaltura/images

In the short term, maybe some can update the kaltura release notes with these two changes?
- Beth

On Nov 9, 2012, at 10:55 AM, Matthew Jones wrote:

> Hi Beth, the plugin configuration for 2.9 kind of changed (half changed) with neither Noah or myself having time to completely finish it (the easier configuration part - SAK-22113). I knew this was something I'd wanted to get into the release notes and forgot about. We wanted to make it so it might be possible for a user could put a json file in the ${sakai.home} to say where a optional plugin was located (and other changes to ckeditor), and what it was called without having to significantly edit the ckeditor configuration file  This resulted in a small addition to the ckeditor.launch.js file near the bottom. This would also make it easier to upgrade CKEditor by moving the plugins that were custom developed and maintained by us out of the plugins directory.
> 
> The line that's creating "kalturamovieplayer" is in
> https://source.sakaiproject.org/svn/reference/trunk/library/src/webapp/editor/ckeditor.launch.js
> 			 ckconfig.extraPlugins+="movieplayer,wordcount"; (kaltura is at the beginning in this case)
> And I guess it expects that if you have extraPlugins defined earlier that either it's empty, or it has a trailing comma (as resourceSearch does).
> 
> One fix would be to add a comma after kaltura, that would be the easy fix. The better fix would be to change the kaltura installation docs to put kaltura plugin right into the ckextraplugins directory.
> 
> https://source.sakaiproject.org/svn/reference/trunk/library/src/webapp/editor/ckextraplugins/
> 
> Then add a new line to the bottom of the file.
> 		   CKEDITOR.plugins.addExternal('kaltura',basePath+'kaltura/', 'plugin.js'); 
> 
> 
> 
> And add kaltura to the end of that ckconfig.extraPlugins+= line instead of at the top.
> This shouldn't be hard to do those configuration, but just hasn't been written yet. :( With this pattern you could even have kaltura anywhere else in the file system (like in the kaltura webapp), not in the "extraplugins" directory. Though that directory is free for all plugins!
> 
> 
> On Fri, Nov 9, 2012 at 10:27 AM, Beth Kirschner <bkirschn at umich.edu> wrote:
> I'm stumped on a problem embedding the CKEditor kaltura plugin into a Sakai 2.9 build. I've followed the great README in svn:
>         https://source.sakaiproject.org/svn//msub/unicon.net/kaltura/tags/20120701/ckeditor/README
> 
> But am getting a file not found (404) error in my browser that complains about a missing kalturamovieplayer/plugin.js file:
>         404 Not Found - http://localhost:8080/library/editor/ckeditor/plugins/kalturamovieplayer/plugin.js?t=B8DJ5M3"
> 
> I've grep'ed the source code and the deployed files in tomcat and can no reference to the kalturamovieplayer directory.
> 
> Any ideas where this reference is coming from? Any pointers from someone who has the CKeditor kaltura plugin running in Sakai 2.9?
> 
> Thanks,
> - Beth
> 
> _______________________________________________
> sakai-dev mailing list
> 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 with a subject of "unsubscribe"
>