AEM as a Cloud Service: Author Tab displays JavaScript code instead of environment name in Sites Console
This article addresses an issue where the browser tab for the AEM Cloud Sites author environment displays JavaScript code instead of the expected environment name.
Description description
Environment
Adobe Experience Manager as a Cloud Service (all versions)
Issue/Symptoms
When accessing the Sites console in the production author environment, the browser tab displays JavaScript code (such as function(e){... MODULE_NOT_FOUND ...}) instead of the environment name. This issue is reproducible only in the production Author environment.
- The problem occurs after navigating to the Sites console in the AEM Author instance.
- The tab title shows JavaScript code rather than the expected environment indicator.
function(e){... MODULE_NOT_FOUND ...}
- The issue is observed when the ACS AEM Commons Environment Indicator or similar add-ons are installed and active.
- The behavior is triggered by an interaction between the unified AEM UI shell (
/ui#/aem/...) and the ACS AEM Commons Environment Indicator extension.
Resolution resolution
Follow these steps to resolve the issue:
-
Verify Add-on Installation
-
Check if the ACS AEM Commons Environment Indicator or similar add-ons are installed and active:
- Look for packages or bundles like
com.adobe.acs.commons.*. - Review configuration under
/apps/acs-commons/configor via OSGi for the Environment Indicator.
- Look for packages or bundles like
-
-
Upgrade AEM Release Version
- Ensure your AEM as a Cloud Service environment is running the latest available release version.
- If not, coordinate with your administrator or Adobe support to upgrade to the latest release.
-
Validate Resolution
- After the upgrade, access the Sites console in the author environment and confirm that the browser tab now displays the correct environment name.
-
Monitor for Recurrence
- If the issue recurs, document the steps and contact Adobe support with details.
Cause
The issue is caused by a compatibility conflict between the unified AEM UI shell and the ACS AEM Commons Environment Indicator extension, resulting in JavaScript code being rendered as the tab title. Upgrading to the latest AEM release resolves the compatibility issue.