Open rbottema opened 2 years ago
After some experimenting, with the following SQL queries we seem to have gotten the tags working. Is this something that should be executed by the package itself?
-- Delete all new tags for a clean sheet
DELETE
FROM [tblBigTable]
WHERE StoreName = 'Geta.Optimizely.Tags.Core.Tag'
-- Update all old tags to match new format
-- column mapping taken by comparing [tblBigTableStoreConfig]
UPDATE [tblBigTable]
SET StoreName = 'Geta.Optimizely.Tags.Core.Tag',
ItemType = 'Geta.Optimizely.Tags.Core.Tag, Geta.Optimizely.Tags, Version=2.0.3.0, Culture=neutral, PublicKeyToken=null',
String02 = String04,
String03 = String02,
String04 = String03
WHERE StoreName = 'Geta.Tags.Models.Tag'
Thanks for the SQL queries, they helped. I did not apply the 'column mapping' you did, only StoreName and ItemType.
We are in the process of upgrading our solution from CMS 11 to CMS 12 and in the process replaced the Geta.Tags package with the Geta.Optimizely.Tags package. However, after upgrading the CMS shows no tags in the overview and no results are returned when querying for tags.
When I look at the tblBigTable in the database I do still see the tags with StoreName
Geta.Tags.Models.Tag
. Could the change of namespaces to add the.Optimizely.
be the cause that no results are returned? If so, is the fix to change the StoreName and ItemType columns to the new namespaces?