awesome package. I'm experiencing some problems though. I use the blog4umbraco package and they have a tagsearch that I use.
After changing the name of a tag it does not work as expected. When looking in the backend all seems good but when I do a search on the tag via the tagcloud I get no hits. I have to republish each page manually to get it to work. I have tried all diffrent publish-methods (publsih all on content, publish all on Content and deleted umbraco.config) but nothing else bur republishing by hand works.
I'm aware that this might be a problem with the search function in blog4umbraco, but I just wanted to check with you if you have any ideas?
Thanks for your kind words re the package - quite a simple thing in reality but has proven very useful.
I also use Blog4Umbraco.
In checking the App_Data/umbraco.config file, I note the tags are stored as the actual tag name within the xml so this explains the issue you describe above re the serach. The search will be referencing the config data for it's search results.
However (as you have no doubt noticed) when you view a page the listing of tags reflects the change of name that you applied within the tag manager. Republishing the page then updates the umbraco.config file, bringing your search back "into line" as such.
So you have highlighted a really nice enhancement feature for the package. Ideally I need to add a checkbox on the "edit tag" page to request all linked pages be republished. Maybe this should just happen transparently anyway.
Let me know your thoughts - would you prefer it to happen automatically, or should you choose to do it ?
thanks for the fast response! I have discussed this with our interaction designer and we think that the perfect solution would be if there culd be a ceckbox that already is checked that republishes all related pages. Then if you for some reason don't want to publish the pages you have the option not to.
So, by default republish all, but having the option not to would be great. Then it covers all scenarios :)
I have just taken a quick look at this enhancement and it is actually harder than I first thought.
The gotcha is that you need to update the tags property on the documents, however you have no real idea of what the alias of the property is.
One option would be to loop through all the properties of the document to identify the tag property and update that. However this could prove quite resource hungry depending on how many tagged nodes there are to loop through.
So I'll put the thinking cap on for a while and see what happens...
If you've any suggestions then I'd love to hear from you.
Edit tag problems
Hi,
awesome package. I'm experiencing some problems though. I use the blog4umbraco package and they have a tagsearch that I use.
After changing the name of a tag it does not work as expected. When looking in the backend all seems good but when I do a search on the tag via the tagcloud I get no hits. I have to republish each page manually to get it to work. I have tried all diffrent publish-methods (publsih all on content, publish all on Content and deleted umbraco.config) but nothing else bur republishing by hand works.
I'm aware that this might be a problem with the search function in blog4umbraco, but I just wanted to check with you if you have any ideas?
Hi Niklas
Thanks for your kind words re the package - quite a simple thing in reality but has proven very useful.
I also use Blog4Umbraco.
In checking the App_Data/umbraco.config file, I note the tags are stored as the actual tag name within the xml so this explains the issue you describe above re the serach. The search will be referencing the config data for it's search results.
However (as you have no doubt noticed) when you view a page the listing of tags reflects the change of name that you applied within the tag manager. Republishing the page then updates the umbraco.config file, bringing your search back "into line" as such.
So you have highlighted a really nice enhancement feature for the package. Ideally I need to add a checkbox on the "edit tag" page to request all linked pages be republished. Maybe this should just happen transparently anyway.
Let me know your thoughts - would you prefer it to happen automatically, or should you choose to do it ?
Cheers
Nigel
Hi Nigel,
thanks for the fast response! I have discussed this with our interaction designer and we think that the perfect solution would be if there culd be a ceckbox that already is checked that republishes all related pages. Then if you for some reason don't want to publish the pages you have the option not to.
So, by default republish all, but having the option not to would be great. Then it covers all scenarios :)
Hi Niklas
Added to my todo list.
It's not a big change so will try and get it done over the next week or two.
Feel free to send me your contact details so I can advise you when it's done - [email protected]
Cheers
Nigel
Hi Niklas
I have just taken a quick look at this enhancement and it is actually harder than I first thought.
The gotcha is that you need to update the tags property on the documents, however you have no real idea of what the alias of the property is.
One option would be to loop through all the properties of the document to identify the tag property and update that. However this could prove quite resource hungry depending on how many tagged nodes there are to loop through.
So I'll put the thinking cap on for a while and see what happens...
If you've any suggestions then I'd love to hear from you.
Cheers
Nigel
is working on a reply...