Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

What if Liferay 7.0 Page Templates are not visible after upgrade?

Written By

Sebastian Madaras

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

  • The Page Templates from Liferay 7.0 are no longer visible for the certain users after the Liferay upgrade.

Environment

  • Liferay DXP 7.1
  • Liferay DXP 7.2
  • Liferay DXP 7.3
  • Liferay DXP 7.4

Resolution

  • LPS-136413 and LPS-137014 are the solutions that improved the case. These fixes make sure that the behavior cannot be replicated from scratch.
  •  If your user isn't able to see the Page Templates after the upgrade. By creating a new role with the permissions under "LAYOUT PAGE TEMPLATE ENTRY" + "LAYOUT PAGE TEMPLATES" and by granting the user with the role, he will be able to see the Page Templates under each Sites global scope.
  • The main reason that these Page Templates are not visible, is because the resource-permissions differ for the entities between the Liferay versions. Using the attached groovy-scripts and by executing it in Control Panel --> Configuration --> Server Administration --> Scripts the missing resource-permissions will be created.Important: The script should be used only if a sample of database was saved. This is highly relevant, as the script does make changes to the database and in case of any problem the customer should be able to rollback to a working state.

Additional Information

  • If the above points cannot improve the current behavior, please feel free to create a new ticket for the Customer Support team. 

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?