Download & Extend

Rewording the "proceed with the installation" text on the installer's requirements page

Project:Drupal core
Version:8.x-dev
Component:install system
Category:task
Priority:minor
Assigned:Unassigned
Status:closed (fixed)
Issue tags:Novice, Usability

Issue Summary

I just installed the Drupal 7.x-dev tarball for the first time and I would like to share this experience in order to make the installation procedure as smooth as possible. After unpacking the tarball and navigating to my site I instantly got the installation screen. I like that. After I choose my profile I got a screen indicating some requirements problems. Now, I know how to fix these so that was not a problem, but then... If I want to see if my problems are fixed, should I refresh the screen or click "proceed with the installation"? I choose to refresh my screen but later I noticed that proceeding with the installation would do exactly the same thing. In my opinion (but I am not a native English speaker) the word "proceed" implies skipping these checks and I think the use of the word "retry" would clear things up. Besides that does "Check the error messages" mean that I have to check them or that Drupal is going to do that for me? I thought of the first option since this text was not part of the link.

In the next stage, when I mistype my database information, I get an error message. This message gives some double information (It refers to the Installation and upgrading handbook twice and suggests to contact my hosting provider twice.) Furthermore, the blue links on the orange background are unclear and the possible explanations may be itemized.

Another question I have: Can't removing the write permissions from the default folder and the settings.php file be done automatically? It can always give this notice when it doesn't succeed because of i.e. php safe mode or something.

Maybe I am nitpicking but these are just my 2cents.

AttachmentSizeStatusTest resultOperations
installation_unclear_link.png111.42 KBIgnored: Check issue status.NoneNone

Comments

#1

Seems one of my points was already addressed here:
#641008: Duplicated text in install error message

AttachmentSizeStatusTest resultOperations
installation_double_message.png68.08 KBIgnored: Check issue status.NoneNone

#2

Status:needs work» active

#3

I found my question regarding the usage of chmod by PHP answered here #418302: Copy default.settings.php to settings.php during install IFF webserver owns files (FTP on shared hosting) #90, so that only leaves the proceed vs. retry as an issue.

#4

use tag 'usability' to get ux team attention :) Thanks for this first-timer report, valuable insights. I agree the text you point out could be more specific. User interface texts are basically frozen now though :\, I think we even have an issue open somewhere about this that didn't get resolved.

#5

#6

Just a note that if there is evidence that these types of messages are causing significant confusion, I would classify that as a "bug". Though it'd be nice to get these kinds of things cleaned ASAP.

#7

Version:7.x-dev» 8.x-dev

#8

Status:active» needs review
Issue tags:+Novice

Having that you suggested "retry" and that update.php uses something like that as well

<?php
$status_report
.= 'Check the messages and <a href="' .
 
check_url(drupal_requirements_url($severity)) . '">try again</a>.';
?>
here is a patch with Check the messages and <a href="!url">try again</a>.
AttachmentSizeStatusTest resultOperations
652288-requirements-wording.patch807 bytesIdlePASSED: [[SimpleTest]]: [MySQL] 34,252 pass(es).View details

#9

Title:Improve installer usability: » Rewording the "proceed with the installation" text on the installer's requirements page

It makes a lot of sense to me to have it use the same text as update.php, and the patch looks good... Probably needs one more person to review it though.

#10

Status:needs review» reviewed & tested by the community

Yay for simpler wording!

#11

Status:reviewed & tested by the community» fixed

Yes much better :)

Committed/pushed to 8.x.

#12

Status:fixed» closed (fixed)

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

nobody click here