Your Development & Design Resource
FCKeditor and the Domino URL Command
01/23/2007 08:39 AM by Chris Toohey
Spent the majority of my night last night (after reeling from the Jack-has-a-son-by-Nathan-Petrelli's-wife, and the return of the Bluetooth-man as Cain to Bauer's Able) getting FCKeditor to work with a Domino-based CMS solution that I've been working on. The great news - it's working! The not-so-great-but-expected (I'm in a hyphen mood this morning) news: you need to modify it to work with Domino!
var sLink = this.BasePath + 'editor/' + sFile + '?InstanceName=' + this.InstanceName ;This tries to launch a URL Command of InstanceName - which we know that Domino will die a horrible death around, as it's not a recognized command. The solution is to give Domino a URL Command that it will recognize that won't impact your functionality while implementing this across various design element types (unlike, say ?OpenForm as this will break on File Resources, Pages and other non-Form design elements)
var sLink = this.BasePath + 'editor/' + sFile + '?Open&InstanceName=' + this.InstanceName ;Yep - it's simple and it gets the job done! As you can see here, we've used the ?Open Domino URL Command... and that's all you need! Your simple editor should now be working perfectly!
In the next few days, I'll put up a FCKeditor/Domino hybrid database that will allow the Image and File resource links within the full-on FCKeditor to grab items from a Domino database store instead of (what it's currently expecting/utilizing) a server file directory. Until then, here's a zip file containing the modified fckeditor.js that you can use to replace the build-in one and allow Domino to utilize this great tool!