CF 11 update 11 & FCK Editor

Here is a current solution:

https://tracker.adobe.com/#/view/CF-4198259

I am not so sure about <script type="text/javascript" src="/CFIDE/scripts/ajax/ckeditor/ckeditor.js"></script>.

How was it generated?

Whoever or whatever generated it must have made a mistake. That is because, after you install update 11, the only file in the cfeditor directory is /CFIDE/scripts/ajax/ckeditor/adapters/jquery.js

If, as you say, the Javascript code should be

<script type="text/javascript" src="/CFIDE/scripts/ajax/fckeditor/fckeditor.js"></script>

then you could do an extended search across your whole site, and replace /ckeditor/ckeditor.js with /fckeditor/fckeditor.js

As Charlie says, Coldfusion updates generally ensure backward compatibility. In fact, I can confirm that, after update 11, /CFIDE/scripts/ajax/fckeditor/fckeditor.js still exists.

In any case, I have assumed there was some manual intervention in the generation of the script. If the Javascript was generated automatically by ColdFusion, then you should file a bug report.

Aaron, a few thoughts:

• That's interesting to hear, because while it's true that CF2016 update 2 indicates that FCKEditor was deprecated in favor of CKeditor (ColdFusion 2016 and ColdFusion Builder 2016 Update 2 are available for early access » Adobe ColdFusion Blog ), you say you are running on CF11, I'm not aware of them having rolled that back to 11 (but someone else may know otherwise)
• Even then, they say it's *deprecated*, not obsoleted, which should mean that the old way should work. Perhaps they misstated, though, and it really is being obsoleted. I don't know.
• You say that you updated CF11 to the latest (which would be update 11). What did you come from (what was the update level before 11)? That would tell us if you only did update 11 or perhaps others in the same go (as they are cumulative). This may help to know, if anyone confirms that some CF11 update did also affect fckeditor
• Finally, it may be none of the above, but could be instead simply that there was an error in your applying of the update. While it should go smoothly, it sometimes has one or more errors. The way to know is to look at the update log (and not the one mentioned by the update process, which instead is a list of files UPDATED by the update). Rather than explain the ins and outs of how to check things, I did a blog post. Check it out: How to solve common problems with applying ColdFusion updates (in 10 and above) - Charlie Arehart's ColdFusion Troublesh…

And let us know if any of that is helpful or you solve things some other way.