At least in the next major release, the domain-specific admin paths should better reflect the domain they refer to, including the machine-name of the domain instead of the numeric ID.
'admin/structure/domain/view/1/config' is far less informative than 'admin/structure/domain/view/mydomain_org/config'.

Apart from that, the current paths seem unnecessarily long and a bit confusing.
Why is it 'admin/structure/domain/view/1' (for editing!) and 'admin/structure/domain/view/1/config', when the more straightforward and consistent way would be 'admin/structure/domain/1/edit' resp. 'admin/structure/domain/1/config'.

Taken together, I'd propose to use 'admin/structure/domain/mydomain_org/edit' resp. 'admin/structure/domain/mydomain_org/config' as admin paths.

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

The 'view' is to avoid potential conflicts with other admin paths used by the module. Imagine changing to machine_names and giving a domain the machine name of "roles". Hilarity ensues.

Agree on the machine_names, though. Patch welcome.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Active » Postponed
bluegeek9’s picture

bluegeek9 commented
Issue summary: View changes
Status: Postponed » Closed (outdated)

Drupal 7 in End of Life and no longer supported. We encourage you to upgrade to a supported version of Drupal. For more information, see https://www.drupal.org/upgrade.

//www.flaticon.com/free-icons/thank-you Thank you for your contribution! Your continued support of this project makes other volunteer contributions more sustainable.
There are multiple ways to show appreciation for the work contributed to this project, including:
  • Triaging issues and adding more context to existing issues.
  • Writing documentation or patches for this project.