You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After removing a geta tag on a news story and then run the geta tags maintenance job. The GetContentReferencesByTags still returns the news story with the tag that was removed.
Any thoughts?
The text was updated successfully, but these errors were encountered:
We had this issue as well in our project that was migrated from CMS 11 (see also #15). We found out that some tags were duplicated, and these would have inconsistent behavior but usually result in deletions not being processed. Running the maintenance job would sometimes fix it, but not always (due to #27).
What I believe happened for us is that tags without group would have no group key in earlier versions, but would get a language group key in later versions. Whenever content with that tag was saved for the first time, it would be duplicated. The end result was that every tag without a group key would show up twice for us: one without group key, and one with the group key 'nl' (our site has one language, which is the 'nl' language).
The fix for us was to remove all the duplicates without the group key. If you have a few it is feasible to do this manually through the interface. We in the end solved it with a SQL query:
DELETE
FROM tblBigTable
WHERE StoreName = 'Geta.Optimizely.Tags.Core.Tag'
AND String02 = ''
AND String03 IN (SELECT String03
FROM tblBigTable
WHERE StoreName = 'Geta.Optimizely.Tags.Core.Tag'
AND String02 = 'nl')
Note that String02 is the group key, and String03 is the tag name, so in our case we are deleting tags with an empty group key, that also have a version with the group key 'nl'. YMMV.
I'm not sure if I have the root cause correct or if it applies to your situation, but hope it helps!
After removing a geta tag on a news story and then run the geta tags maintenance job. The GetContentReferencesByTags still returns the news story with the tag that was removed.
Any thoughts?
The text was updated successfully, but these errors were encountered: