Skip to content

[6.0] [Guided Tours] Remove What's New tours on update from Joomla 5 #45875

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 9 commits into
base: 6.0-dev
Choose a base branch
from

Conversation

obuisard
Copy link
Contributor

@obuisard obuisard commented Aug 10, 2025

Follow up of PR#45512.

Summary of Changes

On update from Joomla 5, the Joomla 6 instance should be cleaned of all What's New tours meant for Joomla 5.
If this is approved, the language files and images should not be excluded from deletion on update any longer (see #45850).

Testing Instructions

Update to Joomla 6 from Joomla 5.4.
Go to System -> Manage -> Guided Tours

Actual result BEFORE applying this Pull Request

What's New tours for Joomla 5.2, 5.3 and 5.4 should be present.

Expected result AFTER applying this Pull Request

What's New tours for Joomla 5.2, 5.3 and 5.4 should be removed.

Link to documentations

Please select:

  • Documentation link for docs.joomla.org:

  • No documentation changes for docs.joomla.org needed

  • Pull Request link for manual.joomla.org:

  • No documentation changes for manual.joomla.org needed

@richard67
Copy link
Member

I have tested this item 🔴 unsuccessfully on 7b27377

Using PostgreSQL names quotes in scripts for MySQL and MariaDB causes SQL errors and the update breaks.


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

@exlemor
Copy link

exlemor commented Aug 10, 2025

I have tried testing this PR, and received an orange warning at the top of website after update:

JInstaller: :Install: Error SQL You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '"#guidedtour_steps" WHERE "tour_id" IN (SELECT "id" FROM "#guidedtours" ...' at line 1

YET, the What's New tours for Joomla 5.2, 5.3 and 5.4 are gone from the System --> Manage --> Guided Tours list ?!
(Checking the database, it looks like they are gone as well:

ScreenFloat Shot of Safari at Aug 10, 2025 at 5_18_56 PM

Due to the warning/error, I can't make it a successful test :/

@richard67
Copy link
Member

@exlemor Have you read my review comment? It clearly tells that this PR is broken and leads to SQL errors when updating.

@exlemor
Copy link

exlemor commented Aug 10, 2025

@exlemor Have you read my review comment? It clearly tells that this PR is broken and leads to SQL errors when updating.

(now that you pointed it out yes lol - I had the page open which didn't include your comment when I was testing it, I guess I should have reloaded the page and then I would have noticed your comment before testing ;) ) (thanks)

Replaced "
Replaced LIKE
@exlemor
Copy link

exlemor commented Aug 10, 2025

I have tested this item ✅ successfully on 76b094e

I was able to successfully test this after latest fixes - thanks @obuisard, @richard67 for the recommendations.


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

@richard67
Copy link
Member

@obuisard I've allowed myself to rename the update SQL scripts so they are newer than the recently merged ones from other PRs and not collide with your other PR.

@richard67
Copy link
Member

@exlemor 's test is still valid because when he had tested, the other PRs with newer update SQL scripts were not merged yet, and so it worked. But now it would not work anymore, that's why I've renamed the scripts.

@rbuelund
Copy link

I have tested this item ✅ successfully on eb0f0ad


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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants