[#47229] - [6.1] What's new tour for Joomla 6.1
- Fixed in Code Base
- 13 Mar 2026
- Medium
- Build: 6.1-dev
- # 47229
- Diff
- obuisard:whatsnewtour
User tests: Successful: Unsuccessful:
Pull Request resolves # .
- 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 PR will:
- add a tour that highlights new features introduced in Joomla 6.1,
- remove the autostart tour of the prior release.
Testing Instructions
Download the update package, not the full install as the tour is only available on updates!
It is possible to find the tour in the list of tours at the top of the Joomla dashboard and run it manually.
Make sure you see images when running the tour (on the first step only) and when editing the tour (System -> Manage -> Guided tours).
Actual result BEFORE applying this Pull Request
No tour highlighting new features for Joomla 6.1.
Expected result AFTER applying this Pull Request
The What’s New in Joomla 6.1! tour is available and should start automatically when in the dashboard or in the system area.
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
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | SQL Administration com_admin Postgresql Language & Strings Repository NPM Change |
| Labels |
Added:
Language Change
NPM Resource Changed
Guided Tours
PR-6.1-dev
|
||
@tecpromotion thats a techinical code level differentation. The Whats new tour is user facing and in that context they are new fields
Technically, no new custom fields have been added. This is controlled purely via the XML and the template. The wording can, of course, be further adapted.
The Guided Tour team decided on 'Three media custom field options'. It seems to be good for user and developer alike.
I have tested this item ✅ successfully on 31c33bc
I have tested this successfully. Thanks @obuisard!
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47229.
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-03-13 14:22:34 |
| Closed_By | ⇒ | tecpromotion |
@obuisard Why do yo always use the same old example for the update SQL scripts instead of using the current one from 6.0-dev? As you can see, we have better insert statements there which avoids to insert the records if they already exist, see https://github.com/joomla/joomla-cms/blob/6.0-dev/administrator/components/com_admin/sql/updates/mysql/6.0.0-2025-09-17.sql and https://github.com/joomla/joomla-cms/blob/6.0-dev/administrator/components/com_admin/sql/updates/postgresql/6.0.0-2025-09-17.sql
@tecpromotion The update SQL scripts "6.1.0-2026-02-25.sql" of this PR here have an older date in their file name than the present scripts "6.1.0-2026-03-07.sql" and "6.1.0-2026-03-10.sql" at the time of the merge. We can live with that now as all of these scripts have not been released with any pre-release yet, and we do not grant updates between nightlies.
But in general you always should make sure that when you merge a PR with update SQL scripts, the scripts have a newer schema version in their name than the highest existing one.
So here the name should have been e.g. "6.1.0-2026-03-11.sql".
not too late to change it now
I have tested this item ✅ successfully on d42382a
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47229.