Problem/Motivation

domain_path can only create domain-specific aliases for nodes. This leaves out lots of things like views and panels.

Of particular interest is this module's ability to have a single path (like /news) refer to different pages on each domain. This is possible currently with nodes, but not with views.

Proposed resolution

Remove the dependence on entity_type and entity_id, and instead refer to the source / alias sets directly in the same way as core paths.

Remaining tasks

patch needed.

User interface changes

The additions to the node edit form would remain. We would ideally have additional domain-specific settings on admin/config/search/path/edit/%, with something like
function domain_path_form_path_admin_form_alter(&$form, &$form_state) {

API changes

A big change internally, but since domain_path doesn't offer an API to other modules the impact would be slight.

CommentFileSizeAuthor
#2 1294186.patch3.92 KBgrendzy
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

agentrickard’s picture

Possibly.

Say more....

grendzy’s picture

FileSize
3.92 KB

I was thinking that the columns entity_type and entity_id could be removed entirely. It would function only on source / alias sets, like core paths. (The patch that follows is meant to be illustrative, I'm sure it won't actually run). Issue summary forthcoming...

grendzy’s picture

Issue summary: View changes

summary

agentrickard’s picture

I can see the benefit. I was coming at it from a different angle. I think a patch in this direction is probably welcome.

We would then also need a UI for adding domain-specific paths to other pages.

This should, in some ways, interact with the Domain URL module to provide a consistent UI. http://drupal.org/project/domain_url.

agentrickard’s picture

Issue summary: View changes

clarify UI change