If a Site Navigation portlet is configured to use a custom Application Display Template (ADT) and the site's public pages are exported to a LAR, then the Site Navigation portlet will fail to find the ADT after import.
The ADT is successfully imported into the new environment, and since the configuration for the portlet can still be accessed, it can simply be selected again to fix the portlet, but it cannot be found until this is done.
Steps to reproduce:
- Set up two Liferay instances
- On one instance, create a new site with a new public page
- On the new page, enter the Site Navigation portlet's Configuration menu, then click "Manage Display Templates for <Site Name>"
- Add a new Application Display Template (enter in some sample text for the script so it can be identified when displayed)
- Select the new ADT under "Display Template" in the Site Navigation's configuration, then click "Save" and close the popup
- Export the site's public pages to a LAR
- On the other Liferay instance, create a new site, and import the LAR to public pages
Expected result: the import is successful and the Site Navigation portlet displays the correct ADT properly
Actual result: the import is successful, but the Site Navigation portlet's display is broken (the portlet itself is invisible unless the mouse hovers over where it should be), and in the configuration menu, a default ADT appears to be selected.
Reproduced in ee-7.0.x: da88760b99a41cfa12faa4f4aea88e1649850475