In 'populartags' code selects TAGs using the 'ident' field that is a sequential code generated each time we 'add' or 'edit' a Blog post. However editing an old blog post it generates a new 'ident' without changing its position in the cue for the MySql? query that uses the record ID, and consequently brings it that TAG to the latest blogs.
This allows an user to manipulate the TAG cloud pointing to his/her personal blogs. (We had that case - people are creative)
Changing the field 'ident' to 'ref' and using the clause MAX() in the MySQL query as well as the constraint tagtype='weblog' made an effective solution.
Patch attached
