Myself and others at Trellon have been working on a spaces_domain module. This module will allow each domain or sub-domain of a site to be a separate space.

I could be wrong, but it appears that the spaces module forces a space to have a PURL path prefix. We would like to use the PURL domain and subdomain modifiers rather than the path modifiers. Perhaps you could provide some guidance on how this could be best accomplished. Does our module need to have its own implementation of hook_purl_provider() instead of relying on spaces_purl_provider()?

Comments

yhahn’s picture

yhahn commented

You should look at this related issue: http://drupal.org/node/549982

However, there is nothing in spaces that dictates what PURL method to use -- you can configure PURL to use a different method.

1. Go to admin/settings/purl/types and enable the subdomain method.
2. Then go to admin/settings/purl and switch the modifier type for the space type you are using to subdomain.

That's all you should have to do -- FYI in the past we have used spaces_og in conjunction with PURL subdomain modifiers which means each group space gets its own subdomain. To mean the idea of a "spaces_subdomain" is something of an abuse of the concept as subdomain is simply part of the URL address of a space, not the actual structure in Drupal which groups/organizes content together. You should ideally build your space types around IA concepts and then use PURL to determine what URL part leads you to that space.

jmiccolis’s picture

jmiccolis commented
Status: Active » Fixed

Setting this to fixed - it's entirely possible to use spaces with domains as yhahn describes above.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.