Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: Frontend Editors not loading on any content editing screens
Hello, we recently migrated Liferay from on prem hosting to AWS, and in addition upgraded from 7.0 to 7.1
In all of our AWS environments, Visual editors do not load when trying to edit content. This applies to all content - blogs, web content, message boards, wiki, etc.
On our developers' local environments, visual editors load just fine. This is only impacting our AWS environments, including production.
In our portal-ext.properties file we have never had any default properties for web editors.
We tried adding these lines to our dev environment and this did not resolve the issue.
We confirmed that the Frontend Editor services are running. We tried restarting ckeditor and it does not throw any errors or warnings in the logs.
There are no javascript errors in the browser console.
I created a test page using the liferay classic out of the box theme and the visual editors do not load in that either.
I have a ticket open with Liferay but was hoping we might get some suggestions here as well. We're a bit at a loss about what to try next.
In all of our AWS environments, Visual editors do not load when trying to edit content. This applies to all content - blogs, web content, message boards, wiki, etc.
On our developers' local environments, visual editors load just fine. This is only impacting our AWS environments, including production.
In our portal-ext.properties file we have never had any default properties for web editors.
We tried adding these lines to our dev environment and this did not resolve the issue.
editor.wysiwyg.default=ckeditor
editor.wysiwyg.portal-impl.portlet.ddm.text_html.ftl=ckeditor
editor.wysiwyg.portal-web.docroot.html.portlet.announcements.edit_entry.jsp=ckeditor
editor.wysiwyg.portal-web.docroot.html.portlet.blogs.edit_entry.jsp=ckeditor
editor.wysiwyg.portal-web.docroot.html.portlet.mail.edit.jsp=ckeditor
editor.wysiwyg.portal-web.docroot.html.portlet.mail.edit_message.jsp=ckeditor
editor.wysiwyg.portal-web.docroot.html.portlet.message_boards.edit_message.bb_code.jsp=ckeditor_bbcode
editor.wysiwyg.portal-web.docroot.html.portlet.message_boards.edit_message.html.jsp=ckeditor
editor.wysiwyg.portal-web.docroot.html.taglib.ui.discussion.jsp=ckeditor
editor.wysiwyg.portal-web.docroot.html.taglib.ui.email_notification_settings.jsp=ckeditor
We confirmed that the Frontend Editor services are running. We tried restarting ckeditor and it does not throw any errors or warnings in the logs.
There are no javascript errors in the browser console.
I created a test page using the liferay classic out of the box theme and the visual editors do not load in that either.
I have a ticket open with Liferay but was hoping we might get some suggestions here as well. We're a bit at a loss about what to try next.
[code]Currently installed patches: dxp-11-7110, hotfix-2057-7110
I attached a screenshot of what the form looks like with the visual editor not loading.
Attachments:
Hi buddy, why don't give other editor a try. As may be the issue is solely with the editor (present one) you are using.
Regards,L.Smith
Regards,L.Smith
Hi,
We faced the exact same issue on AWS.
The issue is that Amazon CloudFront filter out some HTTP headers including the User-Agent and replace it with "amazon cloudfront".
Liferay checks that the user browser is compatible with WYSIWYG editors using this User-Agent.
The solution is to let the User-Agent HTTP header go through Amazon CloudFront and you'll be ok!
We faced the exact same issue on AWS.
The issue is that Amazon CloudFront filter out some HTTP headers including the User-Agent and replace it with "amazon cloudfront".
Liferay checks that the user browser is compatible with WYSIWYG editors using this User-Agent.
The solution is to let the User-Agent HTTP header go through Amazon CloudFront and you'll be ok!
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™