Skip to content

[6.1] Rename and improve update SQL scripts for the 6.1.0 what's new guided tour#47389

Merged
tecpromotion merged 2 commits intojoomla:6.1-devfrom
richard67:6.1-dev-guided-tours-update-sql
Mar 14, 2026
Merged

[6.1] Rename and improve update SQL scripts for the 6.1.0 what's new guided tour#47389
tecpromotion merged 2 commits intojoomla:6.1-devfrom
richard67:6.1-dev-guided-tours-update-sql

Conversation

@richard67
Copy link
Member

Pull Request for #47229 (comment) .

  • I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.

Summary of Changes

This pull request (PR) renames the update SQL script which were added with PR #47229 so that they have a newer schema version in their name than the highest schema version of currently present update SQL scripts at the time of the merge of that PR.

In addition it modifies the insert statement for the tour record so it does not produce duplicates when running multiple times, e.g. after a failed previous update attempt. The same has been made for the 6.0.0 what's new tour, see #45967 .

Finally it makes some small code style change for better readability.

Testing Instructions

Code review should be sufficient, e.g. compare with #45967 , and in addition check the new file names.

Actual result BEFORE applying this Pull Request

The update SQL script "6.1.0-2026-02-25.sql" is not executed when updating a 6.1 nightly build from before last night to the latest 6.1 nightly build using the upload & update method because the schema version in the file name of that script is older than the current database schema version.

When executing the update SQL script more than one time, you have duplicate tour and tour step records.

Expected result AFTER applying this Pull Request

The update SQL script "6.1.0-2026-03-13.sql" is executed when updating a 6.1 nightly build from before last night to the latest 6.1 nightly build using the upload & update method because the schema version in the file name of that script is newer than the current database schema version.

When executing the update SQL script more than one time, you only have duplicate tour step records (which cannot be easily avoided) but no duplicate tour record.

Link to documentations

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

@brianteeman
Copy link
Contributor

Thanks @richard67 will it also need a change in the list of removed files?

@richard67
Copy link
Member Author

Thanks @richard67 will it also need a change in the list of removed files?

@brianteeman In this case here no, as the "6.1.0-2026-02-25.sql" haven't been released yet. If they had been in beta2, it would need that.

@brianteeman
Copy link
Contributor

I have tested this item ✅ successfully on 4aa265d

tested mysql only


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

Copy link
Contributor

@tecpromotion tecpromotion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @richard67

@tecpromotion
Copy link
Contributor

Thanks @brianteeman for testing

@tecpromotion tecpromotion merged commit e823146 into joomla:6.1-dev Mar 14, 2026
51 of 52 checks passed
@tecpromotion tecpromotion added this to the Joomla! 6.1.0 milestone Mar 14, 2026
@richard67 richard67 deleted the 6.1-dev-guided-tours-update-sql branch March 14, 2026 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants