When users navigate to the modules install page (and possibly elsewhere), they click links that take off of their local Drupal installation (where we tell them "You can find modules and themes on drupal.org").

Solution discussed in usability wrap-up session:

Open drupal.org in a new window.

Comments

pjcdawkins’s picture

Open drupal.org in a new window.

Another more ambitious (although possibly not very beneficial) option would be to integrate drupal.org in Drupal, so it's more like Wordpress's built-in plugin search. Then "You can find modules and themes on drupal.org" would be completely unnecessary.

dcmistry’s picture

That would be awesome, if that happens. But seems like too ambitious :)

Bojhan’s picture

Regarding the ambitious part, we tackle that in other issues. This issue is truely navigating to Drupal.org and not finding the way back. This can occur in many places, especially in help we link to handbooks.

anarcat’s picture

@Bojhan - in which issue do we tackle the "search on Drupal.org" problem exactly? I couldn't find anything specific about this.

Dave Reid’s picture

Usability testers don't know the basics of using a web browser and using back buttons? Or is there more to this? BTW it's frowned upon to automatically open new tabs for users.

Gábor Hojtsy’s picture

To the "integrate drupal.org into Drupal" suggestion there is in fact a google summer of code project working on that: Module/Theme Browser in Core

gdemet’s picture

I think users might not have been able to tell that they were leaving their CMS admin and going to an external site.

One possibility might be a little pop-up that briefly appears saying something to the effect of, "You are now leaving your site's administration area and going to an external site (drupal.org). Please use your browser's back button if you'd like to return".

Note that I'm not convinced that would be a good idea, as it might just end up confusing folks more, but it's one way to offer a little more messaging to the user.

Bojhan’s picture

@DaveReid Actually, after browsing for 2/3 minutes - it takes a hell lot of "browser back button" pushing to get back. But yhea, I am also unsure how fixable this is other than opening a new window.

rolfmeijer’s picture

Maybe users are not (all) able to use their back-button, but is opening a new window a better solution? I’ve always been under the impression it is not (see for instance http://www.useit.com/alertbox/9605.html issue 9).

grendzy’s picture

Are we sure this isn't an artifact of the test environment? I'd like to think we can count on a user to remember the URL of their own website. But I can understand how a made-up test URL could be forgotten.

rolfmeijer: I was about to post the same link. Opening new windows is hostile to users.

Anonymous’s picture

Does anyone know whether the opening new window thing being hostile to users still holds? I know it was true 15 years ago, but with the tabs and everything in modern browsers, it might have changed? I haven't seen any more recent studies.

tamanna-freelancer’s picture

having a javascript pop up appear saying "are you sure you wnat to leave the site" the user will know he is leaving the site.

dcmistry’s picture

From relatively recent post: http://www.smashingmagazine.com/2008/07/01/should-links-open-in-new-wind...
"Bottom line:
It is important that users are placed in control of the user interface they are using. Since users expect the link to be opened in the same window, set your links to open in the same window. Don't force a new window upon users unless there's a very good reason to do so. For the latter purpose, consider opening links in new windows if the link provides assistance or help, if it may interrupt an ongoing process or it leads to a non-html-document. "

There are always exceptions to the rule. This looks like an exception. Having D.O. open in the same window does *interrupt* the ongoing process of installing/browsing a module.

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.

RoloDMonkey’s picture

Issue summary: View changes

I would like to throw my support behind the idea of having this link open in a new tab. I think this is a very good case for an exception to the old UI rules, and users are much more used to this kind of behavior in 2016.

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.

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

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should 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.

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

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should 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.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should 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.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should 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.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.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: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should 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: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

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

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should 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.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should 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: 9.5.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. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.