Since #320063: Assign CCK Field to subdomain won't fix :-(

Is it possible to integrate Domain Access into Display Suite.

What I'd like to do, is to create different node displays (teaser,full, etc.) for different domains.

Comments

danieldd’s picture

danieldd commented

Without having yet tested this myself have you tried domain_ctools? I understand this can be used to present different Panels pages based on domain.

I'm not familiar with Display Suite but as you may know Panels has incredibly powerful capability to provide customised node displays.

aTrotter’s picture

aTrotter commented

Well, i'm currently not so much into module programming, so I wouldn't know what to do with domain_ctools :-).

Whilst panels is a very nice module, I'm not to sure if it's suits my needs in this case. What i'd like to do is:

I've got a website which is divided in to parts: US and international. On this website many products get featured. Since the Americans are a little special with their inches and gallons and what not, a product has the following attributes:

...
Dimensions [inch]
Dimensions [cm]
etc ...

So on the international site i'd like to output the dimensions in cm, on the US site I'd like to output the dimensions in inches.

That's where Display Siute comes into play: with this module you can define which fields of a node are shown in the teaser,full node view, search results, etc. You also can create your own output styles and use them in views.

So I could create new display styles like: teaser_int, teaser_us, full_int, full_us.

If I'd use domain access to define which display types used on which domain, that'd be really nice :-).

I'm not sure which would be the best way to do this integration, so I also created a issue on the Display Suite list (#887596: Integration into Domain Access).

edit: typo

agentrickard’s picture

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

Depending on how Display Suite saves its configurations, you might be able to do this now (through the UI) with Domain Settings or Domain Prefix. I have never used the Display Suite.

Domain CTools won't really help here, since it just provides access controls per domain, not context switching (or template switching).

agentrickard’s picture

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

Looked quickly at Display Suite, and it's one of those evil modules that.

a) Doesn't use system_settings_form() but saves all its variables in the {variables} table.

b) Stores fairly complex data not in its own tables but in {variables}.

So neither Domain Settings nor Domain Prefix will help you. You need custom integration, which has to go in a separate module.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Active » Closed (won't fix)
Rory’s picture

Rory commented

@agentrickard thank you very much for your opinion on this. Display Suite in D7 looks to have come a long way but I've just encountered the D7 version. It would be great to know whether or not you think integration would be friendlier now from a purely D7 perspective.

I'm centered on using Domain Access and expanding around that. When managing the display of fields, Display Suite 7.x seems to cover a lot of ground, in terms of how content appears, but I'm anticipating that as Domain Access focuses on node access while Display Suite seems to work on different levels, it should be carefully considered against integrating the two?

Looking way back in time #887596: Integration into Domain Access the maintainer of Display Suite writes:

This might be possible if domain had context plugin.

Which if I understand correctly was a functionality of the Node displays contributions module on D6... since which several functionalities have been moved into Display Suite consolidated for D7.

Rory’s picture

Rory commented
Version: 6.x-2.5 » 7.x-3.x-dev
Status: Closed (won't fix) » Active
agentrickard’s picture

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

I'm not against integrating the two. I'm just saying: that integration requires custom code that is not going into the Domain package. Someone else will have to write it.

There was/is a Domain Context module as well.

Rory’s picture

Rory commented

Good to know. Will see what the DS folks think about Domain Context over at #1490618: Integration with Domain Access. Could be digging in the wrong direction here.

Rory’s picture

Rory commented
Status: Active » Closed (won't fix)