Follow up from #1809352-139: Write tour.module and add it to core. @Dries said:

I was confused about not seeing the tour icon after applying the patch. I actually had to look at the code to figure out how it worked, and I had to look at the YAML files to figure out where a tour icon would appear. I wonder if it would be better to always show the help/tour-icon, even if no help is available. If no help is available, the (1) icon could have a different color and (2) say "No help is available for this page" when clicked. I think it would help with the discovery and learnability of this feature. For what it is worth, I had the same issues with the 'Edit' toggle for in-place editing. I personally prefer to have permanent icons (both for help mode and edit mode) that are explicit about the features not being available on specific pages, than having them disappear/appear randomly. Not sure if most people feel that way though; my opinion may not be representative for the larger audience.

Comments

Bojhan’s picture

Bojhan commented
Title: Evaluate UX and decide on whether Help and Edit toolbar icons should be visible on pages they don't apply to » Evaluate auto-magic showing of Tour and Edit buttons only on pages where they apply

For tour it doesn't have to be an issue, if we find a way to get Tour to start from help or through a DSM?

nick_schuch’s picture

nick_schuch commented
Component: other » tour.module
leehunter’s picture

leehunter commented
Issue tags: +docs infrastructure
clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
commented

I found it hard to note there is a tour available. Once it's clear there is a tour icon it would be nice to have a visual queue for it's status ie changing it's color.

Some tours have wildcards like on view/*/edit so these are not able to start through help.

ifrik’s picture

ifrik
she/her
commented

I'm not sure whether this is the right issue to post this - please point me to the appropriate one if necessary.

I was trying to find the existing tour for Views in the latest D8 dev version, and could not find it. This might have to do with a change in the path.

If I go directly to /admin/structure/views/view/frontpage/edit the tour module icon shows up and the tour works.

However, if I follow the icon link "edit view" from the frontpage, the path is /admin/structure/views/view/frontpage/edit/page_1?destination=node - and no tour module icon shows up.
And following Structure > Views > Edit , the path is /admin/structure/views/view/frontpage - no tour module icon.
In both cases, changing the path to end with /edit makes the tour module icon appear and work.

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
commented

@ifrik see #2027469: View UI Tour is not working and had a sandbox update. esp. #7 there are more paths to a view tour.

I'm working on #2028535: Provide a TourTestBase class for use by core and contrib modules were we could discuss the path discovery between the module routing and the paths mentioned in a tour.

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
commented
Issue summary: View changes

Updated issue summary.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

pixelmord’s picture

pixelmord commented
Category: Task » Bug report
Issue summary: View changes

Right now the experience is bad, because users either overlook the button in the toolbar when you are on pages that have a tour that is related to them or you do not see the button at all because you are on one of the hundred other pages.
There's a tour overview is in the help page that will only be available if the help module is installed and the listed tours are not linked.

I consider this a usability BUG because there is no use of the module and the provided tours if nobody can find them.

A solution could be to:

  • Always show the tour button and either start a tour from there on a page that has one or show an overview
  • Always show the tour popover for a page until the user dismisses that dialog and we can be safe that he has seen that
  • The dismissal of the tour start dialog should also highlight the fact that you can always get back to taking a tour by clicking the button in the toolbar.
Bojhan’s picture

Bojhan commented
Version: 8.2.x-dev » 8.3.x-dev
Issue tags: -docs infrastructure

Solving this will be quite some work, agree that some overview and constant showing of the button is needed.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

realityloop’s picture

realityloop commented
Related issues: +#2844897: Opening of page with tour listed in help section should automatically start tour

Added related issue

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

catch’s picture

catch
he/him
Primary language English
commented
Title: Evaluate auto-magic showing of Tour and Edit buttons only on pages where they apply » Show (disabled) Tour and Edit buttons on pages with no tour/edit available
Issue tags: +Needs issue summary update, +Bug Smash Initiative

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Status: Active » Postponed

This extension is being deprecated, see #3336033: [Meta] Tasks to deprecate Tour module. It will be removed from core and moved to a contrib project, #3376099: [11.x] [Meta] Tasks to remove Tour.

This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.

quietone’s picture

quietone commented
Project: Drupal core » Tour
Version: 11.x-dev » 1.0.x-dev
Component: tour.module » Code
Status: Postponed » Active
smustgrave’s picture

smustgrave commented
Version: 1.0.x-dev » 2.0.x-dev

  • smustgrave committed d0cccf06 on 2.0.x 
    Issue #1920462 by clemens.tolboom, quietone, Bojhan, nick_schuch,...
smustgrave’s picture

smustgrave commented
Status: Active » Fixed

So to keep it simple for 2.0.x the Tour button will always appear.

If the current route has no Tour it will appear with different text, color, and be disabled.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.