Legacy Knowledge Base
Published Jul. 2, 2025

Content is not visible after an upgrade

Written By

István Gergely-Tárnoki

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • After our migration (upgrading to a newer version of Liferay) we cannot see our pages / web contents / templates
  • When we create a new one, we see it gets created in the database but we don't see it on the UI

Environment

  • Liferay Portal 6.2+
  • Liferay DXP 7.0+

Resolution

  • As a rule of thumb, if some parts of your portal are not visible, for example you cannot find your previously created web content articles, run a reindex for the affected content, it usually resolves the missed post-upgrade indexation issues
  • There is also a portal property index.on.startup=false set out-of-the-box on DXP, therefore data is not reindexed on startup at all, also including the very first startup:
    # Set this to true if you want to index your entire library of files on
    # startup. This property is available so that automated test environments
    # index on startup. Do not set this to true on production systems or else
    # your index will be indexed on every startup.
    #
    # Env: LIFERAY_INDEX_PERIOD_ON_PERIOD_STARTUP
    #
    index.on.startup=false
  • Although, if the property is set with value true, all the contents are indexed and visible right at the initial startup.
  • However, please note the followings from the description of the property:

Do not set this to true on production systems or else your index will be indexed on every startup.

Please apply this setting with caution.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base