Many Liferay portlets—such as the Blogs portlet, the Web Content portlet, the Wiki portlet, and so on—utilize CKEditor. This article discusses ways to approach and troubleshoot issues involving CKEditor within Liferay portlets.
Resolution
Before testing for the issue on Liferay's portlets to define whether the reported issue is a Liferay defect, perform tests first on CKEditor's demo site.
If the issue is reproducible there, it is most likely to be related to CKEditor itself. In this case, it is either a CKEditor configuration issue which can be fixed by proper configurations or a CKEditor defect which stands out of the Liferay support scope.
Note: CKEditor bug fixes and new features are not backported. CKEditor suggests upgrading to the latest version to avoid preventable issues.
To find detailed workarounds to CKEditor configuration issues, please refer to CKEditor's documentation.
Additional Information
- You can find all of the Liferay portlets that might be using CKEditor as their editor by referring to the "Editors" section in the portal.properties file.
- To check the detailed version of the CKEditor that has been used by the portal, please go to the portal-web\third-party directory in the source code and check the version of the related ".ZIP" file.
Related Links: