Hello,
I submitted a new module called domain_rules, which gives the strength of domain creation/deletion/etc. to the administrator using Rules.
I had to make it happen since existing modules such as domain_user didn't do exactly what I wanted. My goal was that when a certain user role create a certain content, I grab a CCK field out of it, create an alias to it, a new subdomain, set its theme (which, by design, shows the new created node as the front page), and set access to given users (in my case, anonymous).
When this node is being deleted, the domain is deleted with it...
I wish "domain access" would have been set as "domain as a node", and I guess it might happen in the future, but meanwhile, using those new abilities and some Rules, it is already here...
All combined to the new module. Hopefully everything works as it should.
See more details in my CVS application - http://drupal.org/node/774400#comment-2922914
Comments are welcome,
Regards,
Shushu
Comments
I wish "domain access" would
Frankly, that strikes me as a manifestation of the classic "make everything a node" disease. I can see the direction you're going, but I don't think most DA-powered sites would necessarily benefit from such an approach.
That being said, I welcome all attempts at making Drupal's fifth-wheel Rules system more useful, so good work.
The Boise Drupal Guy!
I think you see it the wrong way
Making thing a node is not a goal by itself, it is a tool to make Drupal stronger
What I need is:
- Ability to create/modify/delete (CRUD?) domains easilty and via Rules.
- Ability to have an owner to domain.
- Ability to search/view domains in different ways (Views intergration)
- etc.
It all can be done in different ways (as we see nowadays, with different modules such as my own, and all of the domain_* modules).
But if domain was a node - voila - it all exist + anything I can already do with nodes...
You are correct that most of the DA sites won't benefit from such an approach, but I am certain they won't loose anything from it.
Regards,
Shushu
You are correct that most of
Well, I can foresee a possible security issue where people who have the "administer nodes" permission now also have permission to edit domains on the site. You should be able to work around that fairly simply with your module, though. Just something to watch out for.
Anyway, have you also considered Organic Groups? I haven't really used it from an administration standpoint, to tell the truth, but from what I understand, it can do many of the things you need with regard to granting users the ability to create subsites themselves and be the owner of them. They're still not listable by Views as easily as nodes, but seeing as how Views' job is to "make lists of everything," I bet an enterprising coder could develop a module which lets Views display, sort and filter Organic Groups (or DA subsites).
The Boise Drupal Guy!
Alternative to Organic Groups
With the risk of getting too far from the main thread, I would still like to take the opportunity to say a word about Organic Groups.
IMHO: Organic Groups has created too much of its own universe, which makes it difficult to use it properly with Views and other essential Drupal modules. Instead of spending time on making special solutions to make OG work with Views, I suggest spending it on finding alternative solutions to OG. (Here's my take on how this can be made.)
I'm sure there are cases where OG is the right choice, but I'm also pretty sure that most OG installations use only a fraction of the function that OG offers but still has to pay the full price.
OG for Drupal 7 will be a more or less complete rework of the module(s), so it will probably be a completely different matter.
Cheers!
//Johan Falk, NodeOne, Sweden
Cool!
Hey, cool!
I didn't get all the details, but it seems very powerful. Looking forward to learning more about it!
//Johan Falk, NodeOne, Sweden