User tests: Successful: Unsuccessful:
Pull Request for Issue # .
#46734
#Summary of Changes
This Pull Request addressing Issue #46734 fixes the persistence of tags when saving content items. It ensures that the
Taggable
behavior correctly identifies and enables the
TagsHelper
during the model save process, aligning the behavior with other core components like com_contact and com_newsfeeds.
Specifically, the fix ensures that when the
Taggable
plugin handles the
onTableObjectCreate
or
onTableBeforeStore
events, it correctly initializes the
TagsHelper
even if the table class does not explicitly initialize it in its constructor, preventing tag data loss.
#Testing Instructions
Prerequisite: Ensure you have a clean Joomla 6.0.2 installation with sample data.
Reproduction (Before Fix):
Go to Content -> Articles -> New Article.
Enter a Title.
In the Tags field, type a new tag (e.g., "TestTag") and press Enter.
Click Save.
Observe: The page reloads, but the Tag field might be empty or the tag not saved.
Verification (After Fix):
Apply the patch.
Go to Content -> Articles -> New Article.
Enter a Title.
In the Tags field, type a new tag (e.g., "TestTagFixed") and press Enter.
Click Save.
Observe: The "TestTagFixed" is correctly saved and displayed in the Tags field field.
Check the database #__contentitem_tag_map table to confirm the mapping exists.
Regression Testing:
Go to Components -> Contacts.
Open an existing contact or create a new one.
Add or remove tags.
Save.
Confirm: Changes to tags in Contacts are still saved correctly (ensuring no negative impact on other components using the same
Taggable
mechanism).
#Actual result BEFORE applying this Pull Request
Tags added during Article creation or editing are not saved to the database. The association between the content item and the tag is lost upon save.
#Expected result AFTER applying this Pull Request
Tags are correctly saved and persisted when creating or editing Articles. The functionality works consistently across all components (com_content, com_contact, com_newsfeeds) that utilize the
Taggable
system.
| Status | New | ⇒ | Pending |
| Category | ⇒ | Repository Administration com_admin SQL |
this pr has been made with joomla 6 but you have submitted the pr against joomla 5.4 which is why there are 300+changed files
I changed the base branch. Now the delta looks a lot better.
| Title |
|
||||||
| Category | Repository Administration com_admin SQL | ⇒ | Libraries Front End Plugins |
I find it very hard to believe that there is a real problem here - tags is a heavily used component and I would expect to hear about lots of reports of tags not working. plus on the original issue multiple people reported that tags was working perfectly. so the only valid way to test this is to replicate the bug in the first place
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-01-31 11:57:23 |
| Closed_By | ⇒ | kkbiswal | |
| Labels |
Added:
PR-6.0-dev
PR-5.4-dev
|
||
I have tested this item 🔴 unsuccessfully on 70997a3
After applying the patch, I am facing the following issue:
The file marked for modification does not exist: .devcontainer/Dockerfile.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46795.