portal entry

select a category, or use search below
(searches all categories and all time range)

CF 2018 ckeditor 4 erases or disallows styles

| View in Portal
October 30, 2018 06:54:16 PM GMT
<p>We recently transferred an application from a server with CF11 with FCKeditor 2.6.4 to CF 2018 with CKeditor 4. Everything seems to be perfect except for one thing. When we load content in CKeditor it erases certain styles such as table cell borders. And if I try to reenter the deleted styles in the source, as soon as a swith back to the wysiwyg view, styles are erased. Very annoying. Is there a filter activated somewhere that filters certain styles? […]</p>
<p>The post <a rel="nofollow" href="https://coldfusion.adobe.com/2018/10/cf-2018-ckeditor-4-erases-or-disallows-styles/">CF 2018 ckeditor 4 erases or disallows styles</a> appeared first on <a rel="nofollow" href="https://coldfusion.adobe.com">ColdFusion</a>.</p>
Labels: ColdFusion, Question, Troubleshooting, question, troubleshooting


Have you viewed the page with your browser's developer tool enabled, watching its network tab, to see if some files used in the rendering of the page are failing?
Comment by Charlie Arehart
1326 | October 31, 2018 01:29:02 PM GMT
Thanks for your reply. All files required for the editor are transferred except one (tableCell.js) which could explain why table cell properties are not available. I have to investigate. As for the styles being deleted, it appears that the Advanced Content Filter introduced in 4.1 could be the source of my problem. Probably certain Disallowed Rules are implemented by default. I was able to solve my problem by adding in the config.js file the folowing line of code: config.allowedContent = true;
1331 | October 31, 2018 04:59:06 PM GMT
Cool. Thanks for the update and additional info.
Comment by Charlie Arehart
1333 | October 31, 2018 06:44:48 PM GMT
Ran into a similar issue with my CF 2018 fully patched (Update 7) server. (On my dev Mac & prod Windows server). Google Dev tools showed failure to load: /cf_scripts/scripts/ajax/ckeditor/skins/moono/editor.css?t=I63C The quick fix was to back up the 'moono' folder, duplicate and rename the 'moono-lisa' to 'moono'.  I'm surprised this wasn't picked up adobe yet, it's 2020.
3638 | February 04, 2020 04:10:12 AM GMT
Hi, Yaron (and very long time, no talk). About this, did it happen upon doing an update *OF* cf2018? From what update? Or was it a move *TO* CF2018, like Francois had reported? And either way, is it the same kind of specific action as he reported here, that leads to the error you see? Or is it a request for *any* page using cftextarea? Or is it perhaps your *own* use of ckeditor? If so, what version? I'm trying to help narrow down why  Adobe might not have" picked up on this" before now, as you said.
Comment by Charlie Arehart
3640 | February 04, 2020 05:21:27 AM GMT
Comment by Charlie Arehart
3641 | February 07, 2020 01:34:57 AM GMT
CF 2018 is shipping that way.  The original moono folder has only a single file in it.  His solution works perfectly, all the needed files are in the moono-lisa folder. Dave
Comment by dtb26
4707 | March 27, 2020 01:38:42 PM GMT
For what it's worth, this is still happening. For me the editor doesn't show up at all because the .css file isn't in the moono folder. Downloaded a fresh version of 2018. Installed patches, 4,8,10. The editor is looking in the wrong folder. Renaming works. What also works is setting the property of the cftextarea: skin="moono-lisa". That way we don't have to change the folders on all our environments. Seems that at some point the default changed to just 'moono' but the moono folder is mostly empty.
Comment by joeyg60012433
4797 | July 16, 2020 06:24:44 PM GMT
Sounds like something that would be great for someone to file as a bug report, at tracker.adobe.com, and then share that link here so that others interested in the concern can add their votes.
Comment by Charlie Arehart
4798 | July 16, 2020 06:47:57 PM GMT
<p>I can do that. Also turns out 2016 has moono as the default, so the default hasn’t changed. The moono-lisa skin also exists on 2016. So in 2018 the plugin is missing whatever is in the moono folder.</p><p><a href="https://tracker.adobe.com/#/view/CF-4209353" rel="nofollow">Bug report: https://tracker.adobe.com/#/view/CF-4209353</a></p>
Comment by joeyg60012433
4800 | July 16, 2020 07:00:54 PM GMT
<p>Great. Thanks, Joey, not only for the bug report but the extra detail. With that, I was able to confirm the problem more easily, and I have added a vote. Hope others will, and that Adobe will resolve it.</p><p>Sad to think that somehow this wouldn’t have gotten caught in some sort of UI testing when Adobe builds CF.</p><p>I would also be curious to know when it started. As I look at my install of CF2018 on Windows, I don’t see the moono files having been backed up in any of the updates applied. That doesn’t MEAN they weren’t removed by an update, though it SHOULD confirm that.</p><p>Perhaps more interesting, I can confirm that in the Docker images for CF 2018, even back to the very first release, the moono folder DOES have the files in there, which may suggest that this is a Windows-only problem. I don't have ready access to my machine with a Linux install of CF to check.</p><p>(And for those not familiar with Docker or the Adobe CF Docker images, they are in fact Linux-based, even if you run them via Docker Desktop on Windows.) For any who may want to see it themselves, you can see it readily with this single line, which will start a container, show the contents of the folder, and terminate (and remove) the container:</p><p>docker run –rm -e acceptEULA=YES eaps-docker-coldfusion.bintray.io/cf/coldfusion:2018.0.0 ls ../wwwroot/cf_scripts/scripts/ajax/ckeditor/skins/moono</p><p>Of course, if you have never pulled down that the image with that 2018.0.0 tag, then you will have to wait the download (of several hundreds megs–whose size is due to be reduced significantly in CF2020).</p>
Comment by Charlie Arehart
4801 | July 17, 2020 04:51:34 PM GMT