[Tickets #14112] Re: tags not being cleaned from rampage tables when tagged object is deleted

noreply at bugs.horde.org noreply at bugs.horde.org
Wed Sep 16 15:49:37 UTC 2015


Ticket URL: https://bugs.horde.org/ticket/14112
  Ticket             | 14112
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | tags not being cleaned from rampage tables when tagged
                     | object is deleted
  Queue              | Horde Framework Packages
  Type               | Bug
-State              | Unconfirmed
+State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Rubinsky

Michael Rubinsky <mrubinsk at horde.org> (2015-09-16 15:49) wrote:

> Versions:
> Horde 5.2.2
> Turba H5 (4.2.2)
> Kronolith H5 (4.2.2)
> Mnemo H5 (4.2.1)
> rampage_* tables not updated when a tagged object is deleted:
> rampage_objects still keeps the deleted object reference

This was originally due to the fact that Content/Rampage is not only  
concerned with tags. The idea was this was to be used to map any  
related content together. This still may happen, but it's not  
currently implemented.  In other words, we can't just delete the  
object reference when the tag count goes to zero, but only when the  
object is explicitly deleted. I'll add code to do this, but need to  
think about where it will go, since it doesn't really belong in a  
Tagger class.

> rampage_tag_stats still keeps the usage count including the deleted object

This was true for all applications except for Kronolith, which  
actually did it correctly but there was an error in Content_Tagger  
that would essentially increment the count anytime tags were edited  
and still contained some of the same tags. So, e.g., adding a new tag  
after the object already contained tags would increment the count for  
ALL tags, not just the added one. This has been fixed in Git.

More information about the bugs mailing list