Similar to #40022
If you try to limit the tours to specific components you get a problem as they are not context aware
For example I create the following tours for content
If I assign them just to articles component then I see all three when I am in the article manager
But if I then chose the category tour and on completion check the available tours there are none.
And if I try to be clever and assign the categories tour to also appear in the category component then we see the other category tours for the other components
Labels |
Added:
No Code Attached Yet
|
Labels |
Added:
a11y
|
Labels |
Removed:
a11y
|
Labels |
Added:
bug
|
It seems to me this is how it is intended to work.
More likely it is a real world scenario that was not considered during development
I would say this is related to issue #40025 - there should be an option to add a view/layout value to a tour in addition to a component. If we did this then the strictly context specific tour could be offered.
The good news is that if the tour URL matches the current URL then the page isn't reloaded when the tour start so you would not loose your current work.
It could be that we'd need to check POST variables in addition the GET values in the URL when deciding if to reload the page. OR we simply pass and argument to the tour initiation script to tell if not to reload the page.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-11-21 18:07:10 |
Closed_By | ⇒ | brianteeman |
It seems to me this is how it is intended to work.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/40023.