Steps to reproduce the issue

Tags

Found in testing 6.0-dev #44669, reproduced in 5.3.1, setup new system and:

• Create one tag
• Check database table __history and see item_id entry com_tags.tag.id
• Trash and delete the tag
• The database table __history entry for com_tags.tag.id is still existing

Content Categories

Found in testing 6.0-dev #44670, reproduced in 5.3.1, setup new system and:

• Create one content category
• Check database table __history and see item_id entry com_content.category.id
• Trash and delete the category
• The database table __history entry for com_content.category.id is still existing

Expected result

Related contenthistory entries are deleted together with the tag and the content category.

Actual result

Related contenthistory entries are are still existing after deleting a tag or a content category.

System information (as much as possible)

When testing #44669 for 6.0-dev, it was found that deleting tags with API or deleting tags with the administrator backend has this issue. Reproduced in 5.3.1 in deleting a tag with the administrator backend.

When testing #44670 for 6.0-dev, it was found that deleting content categories with API or deleting content categories with the administrator backend has this issue. Reproduced in 5.3.1 in deleting a content category with the administrator backend.

Additional comments

• Article's contenthistory entries are deleted together with the article if the article is deleted with administrator backend.
• This may be of low priority as it is only a matter of a missing clean-up.