We have migrated 6.2 to 6.4. As we all know Tag folder structure in 6.2 is etc/tags where else in 6.4 it should store in content/cq:tags. When i try to create tags in 6.4, it is not falling under content folder. Instead it is still falling under etc/tags.
Thanks in advance. kindly let us know, what we are missing here.
NOTE: using acs-commons 3.9.0 and service pack 6.4.2
Let me know in case of any additional information required.
Tag Manager API Supports either older location (/etc/tags) or newer location at a time. At the start of the component, It detects if this is an upgraded system i.e. /etc/tags exists. Then the TagManager runs in BC mode, i.e. it uses /etc/tags as base path, If not, it uses new location '/content/cq:tags'. In BC mode, TagManager (tag pickers) shows the tags from /etc/tags and not from /content/cq:tags.
To make TagManager to use new location (i.e. /content/cq:tags.) the system should not have tags under /etc/tags.
In case of upgraded instances where tags are present under old location (i.e. '/etc/tags') are supported by tagmanager API and classic/touch UI. Once references to old tag base path (i.e. '/etc/tags') are replaced by using tagId or new tag location (i.e. "/content/cq:tags"), you can move tags to the new location (i.e. '/content/cq:tags') in CRX followed by component restart.Also, may I know why are you still creating tags under /etc/ and not in /content? I would suggest you to migrate your old tags to the new location and also create new tags using the new location only.
Hi, I am facing the same issue. I have an AEM 6.5 instance. I can see tags coming from /etc/tags instead of /content/cq:tags. I rename /etc/tags to /etc/tags1 still tagging UI doesn't start picking tags from content and it shows all blank screen even though I have lot of tags under /content/cq:tags.
I need the tagging to work with /content/cq:tags because I am planning to translate the tags and only in /content/cq:tags I can add languages property because this property is not allowed on /etc/tags.
Both of your inputs helped me a lot. Found the root cause of the above issue. It is because, In some place old etc/tags path has been configured in code. I have tried starting new instance without our code and it is working as you both explained above
When you create a tag in AEM 6.4 - you see the path in which the tag is stored.
Here you see the proper path:
If you are not seeing tags stored in the path - that is specified in Tag Path when you create the tag, there is an issue with your AEM instance. As this is not a fresh AEM 6.4 instance - but rather an upgraded server - i am wondering if there is an upgrade bug responsible for this behavior.