We're reusing the SiteSettingsForm (used at installation time to set up the destination Drupal database). In that context, localhost is the most common place to host the Drupal database, so it's collapsed under "Advanced options". Our source database is much more likely to not be localhost, so it should be exposed at the top level - we need to modify the form definition from the parent.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

cilefen’s picture

Version: » 8.x-1.x-dev
Status: Active » Needs review
FileSize
1.09 KB
88.94 KB
90.03 KB

What about the field defaults? We may want to unset some of those in another issue. For example, the default for the database name is the Drupal 8 site's database name.

Before:

After:

  • Commit 8f904f1 on 8.x-1.x authored by cilefen, committed by mikeryan:
    Issue #2281779 by cilefen: Expose hostname more prominently
    
mikeryan’s picture

Status: Needs review » Fixed

Committed, thanks!

Yes, please go ahead and open a new issue, I agree the default db name should be cleared - but not the others. It's a common use case to have the source db on the same server as the destination db (and it's my use case as I test;), so it's convenient to have the credentials pre-filled.

One thing to watch out for - test submitting the form with a typo in the credentials, when it reloads we do want the db that the user entered to still be in the form.

Status: Fixed » Closed (fixed)

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