After upgrading from 7.4 u90/u91 to a newer version, some Content Pages throw errors and cannot be edited
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- After upgrading from 7.4 u90/u91 to a newer version, some Content Pages throw pop-up errors: "Your request failed to complete".
- If you try to edit those pages, an empty page is shown.
- In the browser console some errors appear: "Uncaught (in promise) Error: true"
Environment
- Upgrades from 7.4 u90/u91 to a newer version
Resolution
- First of all, follow this article to print some useful logs: "Your request failed to complete" error is displayed on the user interface but there is no more information about it.
- After that, if this message is shown in the log file after that, you are likely to be affected by this issue:
[SessionErrors:66] Adding key fragmentEntryContentInvalid
- Enable traces (set level to
ALL) for com.liferay.fragment.internal.renderer.FragmentRendererControllerImpl and check the log.
- You may see something like this:
com.liferay.fragment.exception.FragmentEntryContentException: FreeMarker syntax is invalid.__
The following has evaluated to null or missing:_==> featureFlags [in template "template_id" at line 2, column 37]__----_
Tip: If the failing expression is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use [#if myOptionalVar??]when-present[#else]when-missing[/#if]. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??_----__----_FTL stack trace ("~" means nesting-related):_ -
Failed at: #if featureFlags["LPS-182728"]?? && f... [in template "template_id" at line 2, column 32]_---- [Sanitized]
- If so, check your Form Fragments. You may have duplicated some of the out-of-the-box Form Fragments in versions 7.4 u90/u91. They had some freemarker code that checked a Feature Flag. That code must be removed.
Did this article resolve your issue ?