DocumentationExperience Cloud KCS

Translation Project dashboard fails to render due to obsolete Social class import

Last update: July 27, 2026

This article explains how to resolve an issue in Adobe Experience Manager 6.5.x where the Translation Project dashboard fails to render because a JSP compilation error is triggered by an obsolete Social or Communities class import. To fix this, identify the affected JSP, create an overlay in /apps, remove the obsolete import, and deploy the overlay.

Description description

Environment

  • Adobe Experience Manager 6.5.x (on-premise or AMS deployments)

Symptoms

  • After creating a Translation Project and adding asset pages with child pages, the Translation Project dashboard does not display the expected pages, although the page count is visible.

  • The AEM error log shows a JSP compilation error similar to:

    Only a type can be imported. com.adobe.cq.social.commons.CommentSystem resolves to a package

  • The issue is typically observed in one environment (such as development) but not in others (such as staging or production).

Cause

This issue is caused by an outdated import statement for a Social/Communities class (com.adobe.cq.social.commons.CommentSystem) that no longer exists in AEM 6.5.x. The obsolete import causes JSP compilation to fail, preventing the dashboard UI from rendering.

Resolution resolution

Follow the steps below to resolve the issue:

  1. In CRXDE Lite, navigate to /libs/cq/gui/components/projects/admin/translation/pagecard/pagecard.jsp and confirm that the JSP contains an import statement for com.adobe.cq.social.commons.CommentSystem.

  2. Create an overlay in /apps.

    • In CRXDE Lite, create /apps/cq/gui/components/projects/admin/translation/pagecard/ if it does not already exist.
    • Copy pagecard.jsp from /libs/cq/gui/components/projects/admin/translation/pagecard/ to /apps/cq/gui/components/projects/admin/translation/pagecard/.
    • Set sling:resourceSuperType to cq/gui/components/projects/admin/translation/pagecard on the overlay node if it is not already present.

  3. Edit /apps/cq/gui/components/projects/admin/translation/pagecard/pagecard.jsp and remove or comment out any import statements that reference com.adobe.cq.social.commons.CommentSystem or other obsolete Social or Communities classes.

  4. Deploy the overlay through your standard deployment pipeline to keep the change consistent across environments.

  5. Access the Translation Project dashboard and confirm that pages now render correctly without JSP compilation errors.

recommendation-more-help
experience-cloud-kcs-help-kbarticles