RTC PR-6.0-dev Pending

User tests: Successful: Unsuccessful:

avatar rdeutz
rdeutz
26 Sep 2025

Summary of Changes

The compare view of the versions shows for categories not the id, it shows the name. This is possible because we have a lookup table definition. This PR add the definition for tags so that we can show tag names instead of tag ids.

Testing Instructions

This is not easy to test fully:

  1. You have to make an update from 5.4.x or 6.0.0-rc1 or any 6.0.0-beta and MUST use either the custom update URL or the patched update package created by Drone for this PR.
    You can find both here: https://artifacts.joomla.org/drone/joomla/joomla-cms/6.0-dev/46174/downloads/88500/

XOR

  1. Grap the sql from that file, replace the prefix and let it run on your database (using the tool you like)

However you did it, after it you must create some versions of (articles, contact, something that has tags and versioning)

  • Go then to the compare view and check if the tags are listed as tag names or ids

Actual result BEFORE applying this Pull Request

5F4F9100-D618-4C7C-BFBA-928223AFDF7E

Expected result AFTER applying this Pull Request

D0B910E7-0FC5-464F-AA5F-B1B7DBF1544B

avatar rdeutz rdeutz - open - 26 Sep 2025
avatar rdeutz rdeutz - change - 26 Sep 2025
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 26 Sep 2025
Category SQL Administration com_admin Postgresql
avatar rdeutz rdeutz - change - 26 Sep 2025
The description was changed
avatar rdeutz rdeutz - edited - 26 Sep 2025
avatar richard67 richard67 - change - 26 Sep 2025
Title
[6.0] Add tag lookup table information to make it possble to shao the tag name instead the tag id
[6.0] Add tag lookup table information to make it possble to show the tag name instead the tag id
avatar richard67 richard67 - edited - 26 Sep 2025
avatar richard67 richard67 - change - 26 Sep 2025
Title
[6.0] Add tag lookup table information to make it possble to show the tag name instead the tag id
[6.0] Add tag lookup table information to make it possble to show the tag name instead of the tag id
avatar richard67 richard67 - edited - 26 Sep 2025
avatar richard67 richard67 - change - 26 Sep 2025
Labels Added: PR-6.0-dev
avatar laoneo
laoneo - comment - 27 Sep 2025

Does this also work for 3rd party extensions?

avatar richard67
richard67 - comment - 29 Sep 2025

It seems the information added here with an update SQL is also missing for new installations in files installation/sql/<db type>/supports.sql, or am I missing something?

avatar richard67
richard67 - comment - 5 Oct 2025

@rdeutz I've made a PR for your branch with my suggested changes. See rdeutz#21 .

avatar joomla-cms-bot joomla-cms-bot - change - 7 Oct 2025
Category SQL Administration com_admin Postgresql SQL Administration com_admin Postgresql Installation
avatar rdeutz
rdeutz - comment - 7 Oct 2025

Does this also work for 3rd party extensions?

@laoneo what do you mean with "this" in this case?

avatar richard67 richard67 - change - 7 Oct 2025
The description was changed
avatar richard67 richard67 - edited - 7 Oct 2025
avatar richard67 richard67 - test_item - 7 Oct 2025 - Tested successfully
avatar richard67
richard67 - comment - 7 Oct 2025

I have tested this item ✅ successfully on 00a02f2

I've tested updating from 5.4-dev to the custom update URL of this PR with MySQL and PostgreSQL, and I've also tested new installation with both database types.

The PR does what it shall do.

On PostgreSQL there is an issue with a wrong unique index for which I will make soon a PR.

But that's not related to this PR or the changes in 6.0-dev in general.

Hint for other testers:

If you check the content_history_options values on the #__content_types before and after an update to this PR, you will see that there are more differences than just the new element being added to the displayLookup array.

The ordering of the properties of the objects in that array will change, especially on MySQL or MariaDB, and also the odering of other properties in the content_history_options, and the double backslashes in the formFile property will be changed to single backslashes.

The reason for that is the json normalisation which is made by the json functions used in the update SQL script.

This makes the comparison harder, but the changes are ok. The order of properties in json objects doesn't matter, and the double backslashes in strings which refer to paths are also not really needed.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46174.
avatar richard67
richard67 - comment - 7 Oct 2025

@brianteeman Could you test this one here?

avatar brianteeman
brianteeman - comment - 7 Oct 2025

If you delete a tag in the tags component then its not recreated when you restore a previous version of the article that has that tag but I suppose thats to be expected

avatar brianteeman brianteeman - test_item - 7 Oct 2025 - Tested successfully
avatar brianteeman
brianteeman - comment - 7 Oct 2025

I have tested this item ✅ successfully on 00a02f2


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46174.

avatar richard67
richard67 - comment - 7 Oct 2025

If you delete a tag in the tags component then its not recreated when you restore a previous version of the article that has that tag but I suppose thats to be expected

@brianteeman Good find, and I would also assume it is expected.

avatar richard67 richard67 - change - 7 Oct 2025
Status Pending Ready to Commit
avatar richard67
richard67 - comment - 7 Oct 2025

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46174.

avatar Bodge-IT Bodge-IT - change - 11 Oct 2025
Labels Added: RTC
avatar Bodge-IT Bodge-IT - change - 11 Oct 2025
Status Ready to Commit Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2025-10-11 13:01:38
Closed_By Bodge-IT
avatar Bodge-IT Bodge-IT - close - 11 Oct 2025
avatar Bodge-IT Bodge-IT - merge - 11 Oct 2025
avatar Bodge-IT
Bodge-IT - comment - 11 Oct 2025

Thank you for you time on this @rdeutz and thanks to @brianteeman and @richard67 for tests

Add a Comment

Login with GitHub to post a comment