Problem/Motivation

Since Domain config and Domain Config UI is included in the Domain module, there is probably no reason why this module still exists.

Proposed resolution

Add an upgrade path and convert the saved config by this module to domain specific config files.

Remaining tasks

Add upgrade path.

CommentFileSizeAuthor
#2 3224436-2.patch24.01 KBjeroent
Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

JeroenT created an issue. See original summary.

jeroent’s picture

Status: Active » Needs review
StatusFileSize
new24.01 KB

Status: Needs review » Needs work

The last submitted patch, 2: 3224436-2.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

jeroent’s picture

Status: Needs work » Needs review
guardiola86’s picture

I've tried your patch @JeroenT but it fails to apply it.

jackg102’s picture

Coming in a few years after the fact, but wanted to share how our project did it simply. We had a project that used this module. It was seemingly straight forward to "hand migrate" the configuration settings to Domain Config, using the Domain Config UI. We had about 6 domains for reference. If anyone else is looking for an upgrade path, I might recommend that.

  • Copy and paste the Domain Site Settings configuration from domain_site_settings.domainconfigsettings.yml into a notes application for reference
  • Uninstall Domain Site Settings module
  • Install the Domain Config UI module (Domain Config was already installed)
  • Go to /admin/config/system/site-information
  • Select the domain that you want to configure
  • Go back to your configuration settings that you pasted into your notes
  • Fill out the requisite values for the site name, front page, 404 page etc
  • Save!
  • Repeat those configuration steps in the Site Information page for each domain until you are done.
  • That should be it from what I can tell.

There are a few other steps about removing the module from composer that are part of the normal Drupal workflow, but wanted to share how we upgraded from this module to Domain Config without a need for automation.

tim-diels’s picture

Assigned: Unassigned » tim-diels
Status: Needs review » Needs work

The patch is indeed not working. But you actually just need this install file that does the work. I'll provide a new patch file so users can actually use it.

tim-diels’s picture

Assigned: tim-diels » Unassigned
Status: Needs work » Needs review

There you go. Hiding the patch file as its not applying.