User tests: Successful: Unsuccessful:
Pull Request resolves #48207
This PR refactors com_tags to use the same parent-scoped alias architecture as com_content and com_categories. The alias uniqueness check in TagTable::store() is now scoped to parent_id so that aliases are unique among siblings but can be reused under different parents. Additionally, TagModel::save() has been updated with the standard "empty alias handling" logic to auto generate aliases from the title and automatically increment them if a sibling duplicate exists, triggering the standard UI warning banner instead of a hard validation error.
Step 3: Succeeds, alias is child.
Step 4: Fails with error: "Save failed with the following error: Another Tag has the same alias."
Step 5: Fails with error: "Save failed with the following error: Another Tag has the same alias." (Globally scoped error, despite different parent).
Step 3: Succeeds, alias is child.
Step 4: Succeeds, but shows a warning: "Alias already existed so a number was added at the end. You can re-edit the tag to customise the alias." The saved alias is auto-incremented to child-2.
Step 5: Succeeds without warnings, alias is child. (Because it is under a different parent).
Please select:
Documentation link for guide.joomla.org:
No documentation changes for guide.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
| Category | ⇒ | com_tags Administration Language & Strings |
I have tested this item ✅ successfully on e1942cc
I have tested this item ✅ successfully on e1942cc
I have tested this item ✅ successfully on e1942cc
I have tested this item ✅ successfully on e1942cc
RTC
RTC
RTC
| Status | Pending | ⇒ | Ready to Commit |
RTC
RTC
| Labels |
Added:
RTC
Language Change
PR-5.4-dev
|
||
✅ Final test before merge with JBT
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-08-28 12:28:18 |
| Closed_By | ⇒ | muhme | |
| Labels |
Added:
bug
|
||
Thank you very much @hiteshm0 for your contribution. Thank you @richard67 for your support. Thanks to @krishnagandhicode and @brianteeman for testing.
This PR resolves #48207