Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Tagfield in Content Fragment not displaying values from standard tags selection

Avatar

Level 2

I created a content fragment model with a tagfield selector, and whenever I select a tag and save it will save to JCR but when I click back to author it, the tags are not selected and I click into the tag selector it has 0 tags selected  

 

Working normally:

goonmaniangooner_0-1659031383059.png

goonmaniangooner_1-1659031451942.png

goonmaniangooner_2-1659031477156.png

 

After editing and clicking back into content fragment: 

goonmaniangooner_3-1659031525511.png

goonmaniangooner_0-1659032762713.png

 

 

 

 

28.07.2022 11:08:35.853 *WARN* [[0:0:0:0:0:0:0:1] [1659031715681] GET /editor.html/content/dam/cob-corp-acquisition/content-fragments/test-1 HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex This index is deprecated: /oak:index/lucene; it is used for query Filter(query=select [jcr:path], [jcr:score], * from [nt:base] as a where contains(*, '"/content/dam/cob-corp-acquisition/content-fragments/test-1"') /* xpath: //*[jcr:contains(., '"/content/dam/cob-corp-acquisition/content-fragments/test-1"')] */ fullText="/content/dam/cob-corp-acquisition/content-fragments/test-1", path=*). Please change the query or the index definitions.

 

 

 

the error.log only displays this notable warning when I save/open the content fragment

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @goonmanian-gooner,

It looks that you've added free text instead of tags. This can be observed in the repository, tags have always following structure namespace:tagID.

Nevertheless, the issue you have described is an AEM bug - a bug in the product. This has been fixed by Adobe - fix is available starting from SP9 for AEM 6.5. This can be confirmed looking into AEM 6.5.9 release notes:

Summarizing, to fix this issue you have to upgrade your AEM instance to version AEM 6.5.9 or higher. Please also be aware that in AEM 6.5.10 significant change regarding Content Fragments has been introduced, so if you'll decide to upgrade to AEM 6.5.10+ you may need to recreate your CF models and CF.

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

Hi @goonmanian-gooner,

It looks that you've added free text instead of tags. This can be observed in the repository, tags have always following structure namespace:tagID.

Nevertheless, the issue you have described is an AEM bug - a bug in the product. This has been fixed by Adobe - fix is available starting from SP9 for AEM 6.5. This can be confirmed looking into AEM 6.5.9 release notes:

Summarizing, to fix this issue you have to upgrade your AEM instance to version AEM 6.5.9 or higher. Please also be aware that in AEM 6.5.10 significant change regarding Content Fragments has been introduced, so if you'll decide to upgrade to AEM 6.5.10+ you may need to recreate your CF models and CF.

Avatar

Level 2

Hello @lukasz-m, I believe this is a different issue, the tags in the JCR are labelled as cq:Tag within the

/etc/tags/default

goonmaniangooner_1-1659453795931.png

However if I were to delete the tag, and recreate it, it then saves correctly. I do not know if this is another bug?

This is what the Content Fragment looks like in the JCR

goonmaniangooner_0-1659454159142.png

Tagpicker is the tagfield datatype, and all the values within are the ones I picked, and cq:tags are the only that reappear/save when clicking back into the cfm.

goonmaniangooner_1-1659454269613.png

 

Avatar

Level 2

It seems the tagID being in CAPS caused the issue as the ones with lowercase tagIDs save correctly.

goonmaniangooner_0-1659460193548.png