[#47813] - [6.2] Do not crash tours when no steps
- Fixed in Code Base
- 24 May 2026
- Medium
- Build: 6.2-dev
- # 47813
- Diff
- Digital-Peak:tours
User tests: Successful: Unsuccessful:
- 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
When there are no tours, then the guided tours script crashes randomly, especially on GH actions with the error:
TypeError: Cannot read properties of undefined (reading 'length')
This run here is an example:
https://github.com/joomla/joomla-cms/actions/runs/26169001264/job/77141859241?pr=47811
Testing Instructions
- Make sure guided tours is enabled
- Browse the back end
Actual result BEFORE applying this Pull Request
Sometimes the following error is shown:
Oh no! It looks like your tour is off track. The tour exited and cannot run.
Expected result AFTER applying this Pull Request
No error.
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 | ⇒ | JavaScript |
I guess it happens only till the first tour is added, so it doesn't break in 6.1 or lower because they have them already. But did not check it.
I have tested this item ✅ successfully on 5ff1c2b
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47813.
I have tested this item ✅ successfully on 5ff1c2b
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47813.
The test you linked failed during the installation step for a different reason.
> Transition was skipped
Let's tackle that one in a different pr then.
| Labels |
Added:
bug
PR-6.2-dev
|
||
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-05-24 18:34:23 |
| Closed_By | ⇒ | MacJoom |
Thank you!
I would assume that this bug also exists for lower versions than 6.2.