Today we resized a database in Azure to a higher tier and noticed that following a server restart all of our content moved back to the 'default' tag group from our 'custom' group.
Umbraco had created 'default' tags for everything in the cmsTags table and re-assigned all the nodes to the default tag in cmsTagRelationship.
Strangely the tags were showing in the CMS but not in the frontend where we were using GetContentByTag method to access them.
A full republish and cache clear did not resolve it, the only thing within the editor that would fix it on a per-node basis was adding or removing a dummy tab in the list and publishing.
When I manually re-assigned all the tags back to the custom group via SQL in the database (locally after cloning the layout) everything was working properly.
Could anyone help explain this and how we can avoid it in future?
Umbraco 7.3 Re-assigned tag groups
Hi all,
Today we resized a database in Azure to a higher tier and noticed that following a server restart all of our content moved back to the 'default' tag group from our 'custom' group.
Umbraco had created 'default' tags for everything in the cmsTags table and re-assigned all the nodes to the default tag in cmsTagRelationship.
Strangely the tags were showing in the CMS but not in the frontend where we were using GetContentByTag method to access them.
A full republish and cache clear did not resolve it, the only thing within the editor that would fix it on a per-node basis was adding or removing a dummy tab in the list and publishing.
When I manually re-assigned all the tags back to the custom group via SQL in the database (locally after cloning the layout) everything was working properly.
Could anyone help explain this and how we can avoid it in future?
is working on a reply...