Domain menus module [#188812]

Hi,

I try to use drupal for hosting friend's home pages and I'm very interested by this module. Currently I still have a big issue with the beta5 version : menus are shared between each affiliates sites and pointing to "access denied" nodes when not used in the correct affiliated site.

I have created a "laurent" primary link on my "http://laurent.collectif.be" affiliated site. This link perfectly works in this affiliated site but also appears in the main site "http://collectif.be" and in other affiliated sites like "http://aude.collectif.be" where it link to an access-denied node.

What do you think about creating "Domain menus" module allowing to dedicate a specific menu to a particular affiliate site ?

Regards

Comments

Comment #1

agentrickard

he/him

English

Georgia (US)

commented 2 November 2007 at 21:55

I like the idea, but haven't given a lot of thought about how to implement it.

The core module framework (and API) should support such a module. It is also possible that the Domain Prefix module that I'm thinking about will solve this issue by creating multiple menu tables in your database.

Comment #2

skizzo commented 5 November 2007 at 16:15

You may want to check the Localizer module. I understand that it provides language specific Menus (and optionally Blocks, Nodes, and Taxonomy) based on domain prefix. Whether the prefix is "fr." rather than "laurent." it should not matter, as it is only DNS configuration. However it is a totally different approach, as you must go multi-sites. I considered Localizer for a similar user case, as I need domain-specific Forums, but after a cursory examination I thought that it would be kind of overkill. What I like in Domain Access is its administrative simplicity, although I am not sure whether there will be a performance issue in the long run, having the content of many sites all merged in a single db.

Comment #3

agentrickard

he/him

English

Georgia (US)

commented 5 November 2007 at 16:21

I'll take a look at Localizer, which might work. I think the Domain Prefix stuff (which I started yesterday) will also solve this problem.

As to load testing, here's our (informal) internal report:

We got the load tests back for Skirt. At 60 and 120 (Savannah-level traffic) concurrent users, it did OK, but started to choke bad at 180 (Topekal-level) and 240 (Jacksonville-level traffic).

We turned on page caching, and saw 100% performance increase. We can conceivably run hundreds more users, well above what any of our papers' traffic.

I thought you might like to know, since there was initial concern that the extra overhead of the node access table would be added processing per page load; but it's not even thinking about it. :)

For the nerds, this is on 2 app servers and a single database server (we'll add a master/slave database configuration in Skirt's Phase 2).

So I read this to say that Domain Access does not significantly affect Drupal performance.

Comment #4

skizzo commented 6 November 2007 at 08:26

The report excerpt is comforting... Thank you for the effort you are putting in the Domain Prefix development, if you have a perception of how long that could take please let me know. On a sidenote, I think I found a stop gap solution for domain-dependent forums: since DA supports per-domain home pages, I can produce multiple views (one per domain) filtering on terms for forums, and use those views as home pages (there is still a problem with the forum selection drop-down box in the posting form: it encompasses all forums from all domains...)