In my case I have a lot of tag groups, and the tags do not appear to be showing up in the right group.
One instance has the word "Africa", showing up as the default group, when in fact the configuration for the field has the group name as "spLocationTags".
However, looking at a tag value in the same group that has multiple cms documents referencing it appears to be right (same group), but the cms document itself that has one tag in the wrong category has all of its tags from that group in the same, incorrect category.
Let me know what info you need to track it down specifically.
The tree is built up in 2 stages - get the tag groups, and then get the tags for the group.
The queries for this copied directly from the package are:
select [group] from cmstags GROUP BY [group] ORDER BY [group];
select id, tag FROM cmsTags where [group] = 'default' ORDER BY tag;
The second one has the group name passed in as a parameter, but for the purposes of this post I have added "default".
Are you able to run the above queries directly against the database to see the outputs and let me know if they replicate what you are seeing in the Tag Manager section - I am hoping they do :-)
Is there a way to refresh back using a query to determine which document contains the tag? I'll take a closer look at this later this afternoon.
So.. interesting; as I mentioned in my case I picked up on this issue with the tag 'africa'.
select id,tag,[group] from cmsTags where tag='africa'
Shows two tags
id tag group
1059 Africa default
809 Africa spLocationTags
which on glance seemed right, except I have never used a default tag group, other than the on in media.
This query
select *
from cmsTagRelationship
inner join cmstags on cmsTags.id=cmsTagRelationship.tagId
where tag='africa'
only returns tag id #1059, which means the [correct] tag 809 appears to be orphaned if tags are managed using their relationships; BUT what is really concerning is that the query returns the node as nodeid 9152, which is, in fact the correct document, but it is associated with the wrong tag group somehow.
Looking at the field in the CMS, and then looking at the data type, the tag group is, in fact spLocationTags.
So I guess my next question is - is there a way to rebuild the cmsTags/cmsTagRelationships and is this potentially a bug in umbraco?
Not exactly sure what you are asking sorry, but here's a sql query that returns the summary information for a tag
select id, tag, [group], propertytypeid, count(tagId) as noTaggedNodes FROM cmsTags LEFT JOIN cmsTagRelationship ON cmsTags.id = cmsTagRelationship.tagId Where cmsTags.Id = {0} GROUP BY tag, id, [group], propertytypeid;
With respect to your other queries, sorry I don't have any answers there - my main focus has been in reading existing data.
It would be interesting to see your database so I can better understand - are you able to provide a backup file that I could restore - I am using SQL 2012 at home...
Tag Manager 5.0 issue
Nope, not quite right.
In my case I have a lot of tag groups, and the tags do not appear to be showing up in the right group.
One instance has the word "Africa", showing up as the default group, when in fact the configuration for the field has the group name as "spLocationTags".
However, looking at a tag value in the same group that has multiple cms documents referencing it appears to be right (same group), but the cms document itself that has one tag in the wrong category has all of its tags from that group in the same, incorrect category.
Let me know what info you need to track it down specifically.
Hi John
A bit stumped on this one to be honest.
The tree is built up in 2 stages - get the tag groups, and then get the tags for the group.
The queries for this copied directly from the package are:
The second one has the group name passed in as a parameter, but for the purposes of this post I have added "default".
Are you able to run the above queries directly against the database to see the outputs and let me know if they replicate what you are seeing in the Tag Manager section - I am hoping they do :-)
Cheers Nigel
Is there a way to refresh back using a query to determine which document contains the tag? I'll take a closer look at this later this afternoon.
So.. interesting; as I mentioned in my case I picked up on this issue with the tag 'africa'.
select id,tag,[group] from cmsTags where tag='africa'
Shows two tags id tag group 1059 Africa default 809 Africa spLocationTags
which on glance seemed right, except I have never used a default tag group, other than the on in media.
This query select * from cmsTagRelationship inner join cmstags on cmsTags.id=cmsTagRelationship.tagId where tag='africa'
only returns tag id #1059, which means the [correct] tag 809 appears to be orphaned if tags are managed using their relationships; BUT what is really concerning is that the query returns the node as nodeid 9152, which is, in fact the correct document, but it is associated with the wrong tag group somehow.
Looking at the field in the CMS, and then looking at the data type, the tag group is, in fact spLocationTags.
So I guess my next question is - is there a way to rebuild the cmsTags/cmsTagRelationships and is this potentially a bug in umbraco?
Hi John
Not exactly sure what you are asking sorry, but here's a sql query that returns the summary information for a tag
With respect to your other queries, sorry I don't have any answers there - my main focus has been in reading existing data.
It would be interesting to see your database so I can better understand - are you able to provide a backup file that I could restore - I am using SQL 2012 at home...
Good luck with your dilemma
Nigel
Thanks. Interestingly the one with the group spLocationTags returns a proprtytypeid of null, with no tagged nodes.
I created a bug, this feels like an issue inside the CMS to me.
http://issues.umbraco.org/issue/U4-10882
is working on a reply...