Legacy Knowledge Base
Published Sep. 10, 2025

After soy modification, the components under Control Panel are not visible

Written By

Thanga Meena

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

  • Post portal upgrades from DXP 7.0 to Liferay 7.2, under the control panel, pages like the site, user organization, etc are not visible and getting UI error as "XXXX is temporarily unavailable"

Environment

  • Source version: Liferay DXP 7.0
  • Destination version: Liferay DXP 7.2

Resolution

Please note: The following information involves customizations that are beyond the scope of Liferay Support.  Please exercise appropriate discretion in the use of this information. 

Caused by: com.liferay.portal.kernel.template.TemplateException: Unable to process template 136_BUNDLE_CONTEXT_/META-INF/resources/js/FragmentPreview.soy,136_BUNDLE_CONTEXT_/META-INF/resources/js/AceEditor.soy,
------
Caused by: com.google.template.soy.error.SoyCompilationException: errors during Soy compilation_1128_BUNDLE_CONTEXT_/META-INF/resources/ConfigTag.soy:27: error: 'br' tag is a void element and must not specify a close tag._        <br></br>_ 
        ^__1128_BUNDLE_CONTEXT_/META-INF/resources/ConfigTags/ConfigDocTags.soy:93: error: 'br' tag is a void element and must not specify a close tag._    <br></br>_          ^__1128_BUNDLE_CONTEXT_/META-INF/resources/ConfigTags/ConfigDocTags.soy:100:
error: 'br' tag is a void element and must not specify a close tag._          <br></br>_                ^__1128_BUNDLE_CONTEXT_/META-INF/resources/ConfigTags/ConfigProductTags.soy:65: error: 'br' tag is a void element and must not specify a close tag._    <br></br>_   
      ^__1128_BUNDLE_CONTEXT_/META-INF/resources/ConfigTags/ConfigProductTags.soy:71: error: 'br' tag is a void element and must not specify a close tag._          <br></br>_                ^__1128_BUNDLE_CONTEXT_/META-INF/resources/ManageProgram.soy:5:
error: Cannot mix SoyDoc params and header params in the same template.
  • The above error shows that there are some modifications in the soy related code.
  • After removing the custom modules from the portal which are related to the soy, the pages become visible under the control panel that is the issue gets fixed. 

On a side note, You can reach out to your development team or with the Global support team to get further assistance on the same as they will review your custom development codes to assist you with the right approach to achieve your business needs. 

Did this article resolve your issue ?

Legacy Knowledge Base