Closed (fixed)
Project:
Domain
Version:
5.x-1.0beta7
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
26 Nov 2007 at 18:48 UTC
Updated:
27 Nov 2007 at 00:33 UTC
Jump to comment: Most recent file
This is not really a feature request but it is the closest category. We developed a module that creates a menu settings page for each domain. This allows you to assign primary, secondary and node authoring menus per domain. If anyone is interested we would clean it up and contribute it. It is actually a very simple module. Or would you want to wait and put this functionality in a larger domain_menu module?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | domain_menu.tar_.gz | 2.63 KB | canen |
Comments
Comment #1
agentrickardWhy don't you clean it up and post it here. There may be some call for a Domain Menu module, as I suspect that Domain Prefix is a bit scary to some people.
Comment #2
canen commentedHere you go.
Comment #3
agentrickardI think that our team wrote something similar for Skirt, but I haven't looked at that code, since Skirt's navigation is Flash based.
Comment #4
agentrickardI like it. It is quick and simple. Needs a little bit of documentation.
I'd be very happy for you to clean this up and release it separately. I have plenty of code to maintain already.
And one style note: no ending
?>wanted on your files. See the coding standards page for explanation.Comment #5
canen commentedI'll see what I can do here. I suck at maintaining projects though :)
Oversight.
Comment #6
agentrickardWell if you really don't want to maintain it, write up some good documentation and I can add it to the main tarball.
Let me be sure I understand correctly.
-- Under admin/build/menu you create separate menus for each site.
-- This form lets you assign those menus as the primary and secondary links for each subdomain.
The only issue I see is that some users would prefer a more robust menu solution -- but I think Domain Prefix covers that case.
Comment #7
canen commentedNo. That is not it. I can't stand the Drupal release management process and I dislike CVS. I don't mind maintaining it. I'll create some docs and add a project after work.
Yeah. The workflow is about correct.
Comment #8
mrichar1 commentedThe basic work flow is as follows:
1) Create separate menus for each site under admin/build/menu. (if you prefer, you can use the prefix module and separate them, but I find that less manageable) e.g.
Mercedes Navigation
- Primary Navigation
- Home
- About
- Secondary Navigation
- Service & Repairs
- Parts
Audi Navigation
- Primary Navigation
- Home
- About
- Secondary Navigation
- Service & Repairs
- Parts
VW Navigation
- Primary Navigation
- Home
- About
- Secondary Navigation
- Service & Repairs
- Parts
2) Assign the relevant menus on a per domain basis. e.g Set the Primary Navigation sub-menu that is within the VW Navigation root menu to be the "Menu containing primary links".
3) Restrict parent items to a specific menu on a per domain basis. This means that when you are adding/editing a page on the VW site you only see the following menu:
VW Navigation
- Primary Navigation
- Home
- About
- Secondary Navigation
- Service & Repairs
- Parts
The config page differs from the corresponding page in the main drupal system in one important way; the list of menu options available shows every available menu item, not just the root menus. This provides greater flexibility by allowing you to assign the primary and secondary links designations to menus that are not "root menus". Not only does this prevent you from having to create separate root menus, but it is also a convenient work around for this bug
Comment #9
canen commentedProject created and can be found here. I used the above comment as the start for the documentation. Improvements and suggestions welcome. Marking issue as fixed.
Comment #10
agentrickardAdding a link to the project page. Very exciting. Thanks.