Comments

flk’s picture

Status: Active » Needs review
StatusFileSize
new7.75 KB
dries’s picture

Could you go over the messages and clean up the wording a little bit? Sometimes we use 'database something' (eg. 'database port'). Other times we use just 'something' (eg. 'port').

chx’s picture

This issue is about the port notices which are rather consistent of what there are. Such a consistency patch can be rolled separately. (I am not 100% we need that, if we talk about database server do we need to stress that the username and password is for the database server? but, separate issue)

drumm’s picture

Version: x.y.z » 5.x-dev
Status: Needs review » Needs work

The added code needs to be consistent with itself. I think 'port' is good in these contexts.

tstoeckler’s picture

Title: Show possible wrong port notice for installer. » Error message in installer mentions possibly wrong username, etc. but not port
Version: 5.x-dev » 8.x-dev
Status: Needs work » Active

This is still valid. Relevant code: http://drupalcode.org/project/drupal.git/blob/HEAD:/includes/install.inc...

Tagging with usability, because of recent efforts to reduce wordiness of messages and help text. Maybe the text is good as is, in which case this is won't fix.

tstoeckler’s picture

Issue tags: +user experience

Adding tag

NROTC_Webmaster’s picture

tstoeckler,

Can you add the patch? I can't see the reference.

tstoeckler’s picture

@NROTC_Webmaster: Sorry, I don't get what you mean. Which patch?

NROTC_Webmaster’s picture

I was talking about the link in #5 but I'm guessing you were actually referring to the file in core.

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.

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.

asvira’s picture

Component: other » install system
Issue summary: View changes
Priority: Normal » Minor
Status: Active » Needs review
Related issues: +#82173: provide port number as advanced option in installer
StatusFileSize
new5.65 KB

Why don't we just mention possible wrong port number along with possible wrong host name in the same sentence? It may sound like this:

* Have you entered the correct database name?
* Have you entered the correct username and password?
* Have you entered the correct database hostname and port number?

Patch is attached (made on 8.8-dev branch).

Looking forward to your thoughts.

asvira’s picture

StatusFileSize
new5.29 KB

Submitting new patch since the previous one has failed to apply.

johnwebdev’s picture

+++ b/core/lib/Drupal/Core/Database/Driver/sqlite/Install/Tasks.php
@@ -97,7 +97,7 @@ protected function connect() {
-        $this->fail(t('Failed to connect to your database server. The server reports the following message: %error.<ul><li>Is the database server running?</li><li>Does the database exist, and have you entered the correct database name?</li><li>Have you entered the correct username and password?</li><li>Have you entered the correct database hostname?</li></ul>', ['%error' => $e->getMessage()]));
+        $this->fail(t('Failed to connect to your database server. The server reports the following message: %error.<ul><li>Is the database server running?</li><li>Does the database exist, and have you entered the correct database name?</li><li>Have you entered the correct username and password?</li><li>Have you entered the correct database hostname and port number?</li></ul>', ['%error' => $e->getMessage()]));

sqlite does not have the concept of username/password, port number and hostname. the fail messages here should mostly be about filesystem permissions and the path to the database file, I think.

asvira’s picture

StatusFileSize
new5.84 KB

I rewrote messages for sqlite. Replaced "database server and database" with "database engine and database file". If these changes need to be discussed, I will remove sqlite from this patch and create a separate issue for adjusting sqlite install messages.

Also, this issue might be resolved by resolving https://www.drupal.org/project/drupal/issues/3050161

tatarbj’s picture

Issue tags: +DrupalCampBelarus2019
gogowitsch’s picture

Version: 8.6.x-dev » 8.8.x-dev
StatusFileSize
new5.85 KB
new1.86 KB

+1 from me!

The patch in #19 looked good except for minor grammar hiccups with the SQLite message. I have added a new patch to fix these.

I changed the branch to 8.8.x, because all active development should happen there now that 8.7.x is released.

asvira’s picture

Thank you @Gogowitsch. Your adjustment is fine for me.
Looking forward for more reviewers

asvira’s picture

Status: Needs review » Reviewed & tested by the community

Seems that this is ready to go to Core maintainers.

Status: Reviewed & tested by the community » Needs work
asvira’s picture

Status: Needs work » Reviewed & tested by the community

Rerun tests

Status: Reviewed & tested by the community » Needs work
asvira’s picture

Status: Needs work » Reviewed & tested by the community

All tests passed.

  • catch committed 747bd48 on 8.8.x
    Issue #82571 by asvira, Gogowitsch, flk, tstoeckler: Error message in...
catch’s picture

Status: Reviewed & tested by the community » Fixed

13 years!

Committed 747bd48 and pushed to 8.8.x. Thanks!

Status: Fixed » Closed (fixed)

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