Hi

We have about 7 domains and quite a large and deep menu structure. Unfortunately we've hit a blocker when trying to create menu links which link to domain specific nodes with child menu links which link to 'all affiliate' content. The problem being that the child menu links are only visible on the domain of the parent menu link.

In reference to the below, the menu links for child pages 1,2 and 3 are only visible on domain B which makes perfect sense. However, in our case both parent pages related to the 'same' node (the title is the same and the path is the same) it's just the content differs slightly per domain.

- Parent page (domain A specific nodes)
- Parent page (domain B specific nodes)
- - Child page 1 (all affiliate node)
- - Child page 2 (all affiliate node)
- - Child page 3 (all affiliate node)

Is there anyway Domain can be used to handle our use case?

Comments

agentrickard’s picture

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

I don't think so. In this case, does it even make sense to show a child of an "invisible" parent?

agentrickard’s picture

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

Actually, the problem is that the parentage varies by domain. This looks like the use-case for Domain Menu Block, however, the Menu user interface doesn't really support having the children as part of multiple menus.

I.e., your children need multiple parents, which Drupal doesn't support.

rattusrattus’s picture

rattusrattus commented

I suppose what I was hoping was, as with Internationalization, it's possible to create different 'versions' of the same node per domain that way only needing one parent

agentrickard’s picture

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

Never tried it. This sandbox project is similar. https://drupal.org/sandbox/agentrickard/1840772

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Active » Closed (works as designed)
mstrelan’s picture

mstrelan commented

@troublemaker - I'm currently developing a domain access which achieves what you want to do using entity translation to provide different versions of a page per domain. It makes complete sense to develop like this if your domains are language specific, eg you have an English site and a French site. Just set the default language of the English site to English, and the default language of the French site to French.

But I take it you're not using different languages, but then neither am I.

The locale module allows you to create additional languages, including custom languages. I felt a little dirty doing this at first, especially coming up with a "RFC 4646 compliant language identifier", until I read RFC 4646, in particular the section on "private use subtags". Essentially you can just use en-x-ANYTHING and it's perfectly valid.

So once you've got your languages all set up all you need to do is allow translation of the content type used for your landing page, and for any fields you want to translate (eg. body) and you're all set.