AEM Tagging - Not pulling results with TagManager.find | Community
Skip to main content
b7wilso
b7wilso
Level 3
March 7, 2016

AEM Tagging - Not pulling results with TagManager.find

  • March 7, 2016
  • 1 reply
  • 6713 views

Sorry, I really hope that this is not too basic of a question.  That said, please forgive the basic-ness of the question as this is really my first foray into tagging.  My local environment is a Windows environment running AEM 6.1, but I don't think I have gotten around to installing SP1 there yet.  Alternatively, my Dev environment is on Linux, AEM 6.1 and we do have SP1 installed on there.

So I have a component built on tagging that works just fine in my local environment (both Author and Publisher) but when I promoted it to our Dev environment it is not pulling the results with TagManager.find in Publisher only (but it does work in Author).  When I first tested on Publish in my local environment it didn't work there either at first, until I found https://docs.adobe.com/docs/en/aem/6-1/develop/tags/framework.html and added cq:Taggable to the Page Component, at which point it worked fine.  Based on the displays I have setup in the code, TagManager.find is returning null (and not throwing any sort of error).  I am doing a ResourceResolver.adaptTo to create the TagManager.  Please see attached screen shots.

Thanks in advance for your help!

Brad W

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

edubey
edubey
Level 10
March 8, 2016

Have you replicated tags which are created in Dev author to Dev publish?

b7wilso
b7wilsoAuthor
Level 3
March 8, 2016

Good thought, but it auto-promoted just that tag when I promoted either page or the tagged component.

b7wilso
b7wilsoAuthor
Level 3
March 8, 2016

JK - Based on my initial read of your provided link I am pretty sure we haven't done this.  I will give it a try and come back and let you know.  Thanks!


Bad news, in this case it does not seem to have helped.  Based on the screen shot provided from our Operations dept it does appear that the tag is readable by all in that publish environment now (admittedly it was not before). 

Terms & ConditionsAccessibility statement

Loading footer...