Hi,
Currently JHelperTags not considering about purely UCM data when deleting last tag. It's just remove entry from #_ucm_content table when saving after removing last tag.
This fix checks the whether $table type is JTableCorecontent and if so, not remove #_ucm_content entry.
I wonder why deleteTagData ever should delete the UCM part.
But then the whole UCM thing is flawed and should seriously be rethinked and not be used by other extensions.
Hi,
Currently ucm only work for tagged items. When a user add tag to an item, then it get inserted in to #_ucm_content. So when user remove last tag, the record at #_ucm_content also need to remove.
Currently there's no component which purely using #_ucm_content table. We can eliminate this if condition once all components start to use UCM.
Yep, currently only tags uses the ucm tables. But given it's UCM you don't know if any other extension uses it as you said. That's why I think it should only delete the tags part of it, and not the UCM part.
But it shows one of the flaws of the implementation.
We can eliminate this if condition once all components start to use UCM.
I don't think that ever happens. At least not with the current implementation.
Hi,
I think this PR tries to give the solution according current situation. And this will help extension developers to see how UCM should properly work.
As far as I know, this is not the way UCM was originally planned. Somehow it was restricted to tagged items and as a result of that, this kind of undesired things imposed.
I believe this will help to remove an undesired situation from extension developers who like UCM.
I wonder why
deleteTagData
ever should delete the UCM part.But then the whole UCM thing is flawed and should seriously be rethinked and not be used by other extensions.