Hi,
I just wanted to ask if the following use case can be realized with da:
- I want to have the following hierarchy:
sports.com (root) ->tennis.sports.com -->clubX.tennis.sports.com -->clubY.tennis.sports.com ->football.sports.com -->.... - I want to give users on clubX.tennis.sports.com the possibility publish their content on
- Own domain
- Parent domain (tennis.sports.com)
- root (for all)
- As a user I can only view content flagged with the domain_ids I am assigned as domain_editor
- Sports.com and tennis.sports.com are Meta Portals who should all display all "open" content of the sub istes
- football.sports.com must not display content of any tennis site - there shall at least be no option for the user
And now my questions:
- Can this be done with existing domain and other contribs?
- Can the relations between domains (|-root -1---*->children -1---n->children) be archived?
- Is domain access the right thing for this scenario (or should I use og,...)
- Is is possible to write a module? I have developed quite a lot of modules for work and would start one, but are there hurdles that would make something like it merely impossible?
I made two screens how the result could look like.
Greetings for Germany
| Comment | File | Size | Author |
|---|---|---|---|
| How admins/roleX should see publish options | 7.56 KB | Ghostthinker | |
| How users should see publish options | 17.55 KB | Ghostthinker |
Comments
Comment #1
agentrickardIt is definitely possible.
I think nonsie has been working on something like this, which should be a separate module using the API.
Title change, since "relationships" is a Views term with its own issue.
Comment #2
nonsieKen's right, we use a custom module named Domain Relationships on some of our Domain Access powered sites. At the moment all that it does is create parent-child relationships between domains (take a look at http://www.thebeehive.org/domains for example) and does not provide publishing option overrides which could be added in. It does however alter domain listings to show the hierarchy of the domains.
I've been cleaning up the code and it should be on http://drupal.org/project/domain_relationships by the end of this week.
Comment #3
Ghostthinker commentedThanks alot. Contact me if you need any testing/development work.
Comment #4
agentrickardGo ahead and close this issue when there is a release.
Comment #5
druojajay commentedHallelujah. Subscribe.
Comment #6
voxpelli commentedNo release yet as I can see - would very much like to build upon it for a current project of mine. Commenting here to show my support and to subscribe to updates on the status.
Comment #7
agentrickardPost an issue in the other module's queue instead, please. In fact, I'm going to move this out of my queue.
Comment #8
Ghostthinker commentedI got the source from nonsie for reviewing it. But atm I'm facing other problems in my company so I had no time. The module is in a very early stage, so I guess it would be helpfull if everybody who is interested posts some ideas what exactly this module should cover. By the way - I will review/patch it by the end of this week.
Comment #9
agentrickardIf you need any kind of form builder functions in the main module, let me know.
Comment #10
druojajay commentedMy use case:
We have domains for each city. But there's no easy way to auto-group the content from a cluster of cities into a regional site, other than periodically bulk updating the nodes.
It would be useful, but not necessary, to add a bi-directional component. A sort of "publish to all affiliates" for a subset of the domains.
dru
Comment #11
voxpelli commentedMy use case:
I've a couple of newspapers, on their own domains, group under some major newspapers which are supposed to group together the news from their sub-newspapers.
I would need to make this grouping of newspapers to be able to find all of the news from the current domain-group and show them on the major newspaper.
Any one having an ETA of when the current code may go public? If it's not soon enough then I might have to hack together a solution for my project instead.
Comment #12
Ghostthinker commented@druojajay Great idea, but please post this as a feature request here http://drupal.org/project/domain_relationships
Comment #13
druojajay commented@SteveOn Sorry, I took your previous invitation to post things "here" to mean "this thread".
Reposted as feature request: http://drupal.org/node/565336
Comment #14
nonsie@voxpelli - we've been using the current dev release code since Dec, 08. I'm only calling it dev since I don't know anyone else using it on a live site.
Comment #15
nonsieMarking it as duplicate of #565336: Bi-directional hierarchies (and other use cases?)