Default Tag Root Configuration

[JohnPurchaseSB]

I'm working on an AEM 6.5 server that was migrated from an earlier version. Some of the steps were not strictly followed, however - I don't know the full story but I'm guessing there were actual regression problems or just no practical way to test. One example of this is when I go to Tools > General > Tagging, the root path is not what I would expect. Note the URL has a suffix pointing at the pre-migration path  -  /libs/cq/tagging/gui/content/tags.html/etc/tags.

Where is this root path set?  I'd assume that the deployment is setting this, but I can't find anything that looks like it is overriding the v6.5 default of /content/cq:tags.

[konstantyn_diachenko · Accepted solution]

Hi @JohnPurchaseSB ,

In AEM 6.5, the default root path for tags is /content/cq:tags, and this behavior is controlled primarily by the Tag Manager and the tagging configuration in AEM. If your environment is still pointing to the older /etc/tags path, this is likely due to remnants of the migration not being fully completed or a configuration override.

Here are some steps to investigate and resolve this issue:

1. All Tags must be migrated to /content/cq:tags.
   1. Copy all Tags from the Previous Location to the New Location.
   2. Remove all Tags from the Previous Location.
   3. Via the AEM Web Console, restart the Day Communique 5 Tagging OSGi bundle at https://serveraddress:serverport/system/console/bundles/com.day.cq.cq-tagging for AEM to recognize the New Location contains content and should be used.
      Notes: Restarting the Day Communique Tagging OSGi bundle will only register the New Location as the tag root if the Previous Location is empty. 
      References to the Previous Location will continue to work after migrating to New Location for all functionality that uses AEM's TagManager API for tag resolution.
      

      Any custom code that explicitly references the path /etc/tags must be updated to /content/cq:tags, or preferably rewritten to use the TagManager Java API, in tandem with this migration.
      Documentation: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/rest... 

2. Check the Tag Manager Configuration
   1. Navigate to the configuration console /system/console/configMgr.
   2. Look for the Tag Manager Implementation (com.day.cq.tagging.impl.JcrTagManagerFactory) configuration.
   3. Ensure the legacySupport.enabled.name is disabled.
3. Test the Resolution
   1. After verifying and correcting the above configurations:
   2. Restart AEM to ensure all configurations are applied.
   3. Test the behavior in the Tagging console to confirm it now resolves to /content/cq:tags.

Best regards,

Kostiantyn Diachenko.