Comments on: Domain Access update http://ken.therickards.com/2007/11/25/domain-access-update/ Ken Rickard's notes about what he's doing Mon, 06 Oct 2008 13:56:30 +0000 http://wordpress.org/?v=2.0.10 by: Ken Rickard http://ken.therickards.com/2007/11/25/domain-access-update/#comment-31479 Sun, 30 Dec 2007 15:07:43 +0000 http://ken.therickards.com/2007/11/25/domain-access-update/#comment-31479 This is not the best forum for this discussion. Please open an issue for both topics. http://drupal.org/node/add/project-issue/99990 Unsure about TAC, see http://groups.drupal.org/node/7725 for some background. But it should work. Open an issue and we can report some tests. This is not the best forum for this discussion. Please open an issue for both topics.

http://drupal.org/node/add/project-issue/99990

Unsure about TAC, see http://groups.drupal.org/node/7725 for some background. But it should work. Open an issue and we can report some tests.

]]> by: Chandan Haldar http://ken.therickards.com/2007/11/25/domain-access-update/#comment-31473 Sun, 30 Dec 2007 14:29:05 +0000 http://ken.therickards.com/2007/11/25/domain-access-update/#comment-31473 In my usage scenario, there is a small number of common generic roles across the whole affiliate domains ecosystem, and a very large number of domains, all sharing the same database. Selected parts of a domain's user/grants/node admin functions need to be delegated to a domain admin (specific to a domain). A authenticated user has access to a node as per the role/grants allotted by the domain admin of the container domain of the node. For example, a domain admin might choose to grant an "author" role for his domain to an authenticated user (which allows that user to create various nodes in that domain) and also withdraw that grant at any time independently of how other domain admins treat that user for their domains. Thanks a lot for the suggestion. I'll read about the domaingrants hook. I'm not a very experienced drupalite, so I may be slow on things, thanks for your help again. Another question: is it known if domain_access and the taxonomy access control module work together in peace using the multiple node access patch? In my usage scenario, there is a small number of common generic roles across the whole affiliate domains ecosystem, and a very large number of domains, all sharing the same database. Selected parts of a domain’s user/grants/node admin functions need to be delegated to a domain admin (specific to a domain). A authenticated user has access to a node as per the role/grants allotted by the domain admin of the container domain of the node. For example, a domain admin might choose to grant an “author” role for his domain to an authenticated user (which allows that user to create various nodes in that domain) and also withdraw that grant at any time independently of how other domain admins treat that user for their domains.

Thanks a lot for the suggestion. I’ll read about the domaingrants hook. I’m not a very experienced drupalite, so I may be slow on things, thanks for your help again.

Another question: is it known if domain_access and the taxonomy access control module work together in peace using the multiple node access patch?

]]> by: Ken Rickard http://ken.therickards.com/2007/11/25/domain-access-update/#comment-31433 Sat, 29 Dec 2007 22:27:28 +0000 http://ken.therickards.com/2007/11/25/domain-access-update/#comment-31433 You could, by writing a module that uses the API, but I am not sure that changing roles per domain is a good idea. The "best" way to solve this is by using the provided hook_domaingrants() to change the default permissions granted to a user. See the provided Domain Strict module for an example of how this is done. The "edit domain nodes" permissions is designed to replace the "administer nodes" permission for most users. See the documentation. You could, by writing a module that uses the API, but I am not sure that changing roles per domain is a good idea.

The “best” way to solve this is by using the provided hook_domaingrants() to change the default permissions granted to a user. See the provided Domain Strict module for an example of how this is done.

The “edit domain nodes” permissions is designed to replace the “administer nodes” permission for most users. See the documentation.

]]> by: Chandan Haldar http://ken.therickards.com/2007/11/25/domain-access-update/#comment-31284 Fri, 28 Dec 2007 07:31:02 +0000 http://ken.therickards.com/2007/11/25/domain-access-update/#comment-31284 Domain Access is cool. One question. Is there a concept of domain-specific roles for users? User should have the default "authenticated user" role in every affiliate domain and a few other specific roles in particular affiliate domains. When the user visits a node belonging to a domain, her access is automatically determined by the role she has in the container domain the node belongs to. Is there a way to get this effect with DA? Domain Access is cool. One question.

Is there a concept of domain-specific roles for users? User should have the default “authenticated user” role in every affiliate domain and a few other specific roles in particular affiliate domains. When the user visits a node belonging to a domain, her access is automatically determined by the role she has in the container domain the node belongs to. Is there a way to get this effect with DA?

]]> by: Ken Rickard http://ken.therickards.com/2007/11/25/domain-access-update/#comment-29451 Wed, 05 Dec 2007 01:21:38 +0000 http://ken.therickards.com/2007/11/25/domain-access-update/#comment-29451 Rog- I'd like to understand more about what you're trying to do. Rog-

I’d like to understand more about what you’re trying to do.

]]> by: Rog http://ken.therickards.com/2007/11/25/domain-access-update/#comment-29369 Mon, 03 Dec 2007 14:34:24 +0000 http://ken.therickards.com/2007/11/25/domain-access-update/#comment-29369 I just have to say thank you for your work on Domain Access thus far. My own multisite-project may be outside of what you might consider the scope of Domain Access' Affiliate focus, but with where Drupal seems to be headed, your module(s) may very well end up as the only reasonable multisite method. Even new to Drupal as I am, I can see the trend to move everything into nodes. And therein lies the problem with the "standard" multisite method of separating tables via prefixes to sub-sites, because each node type doesn't have its own table. I'm looking forward to seeing how Domain Access evolves. I just have to say thank you for your work on Domain Access thus far.

My own multisite-project may be outside of what you might consider the scope of Domain Access’ Affiliate focus, but with where Drupal seems to be headed, your module(s) may very well end up as the only reasonable multisite method.

Even new to Drupal as I am, I can see the trend to move everything into nodes. And therein lies the problem with the “standard” multisite method of separating tables via prefixes to sub-sites, because each node type doesn’t have its own table.

I’m looking forward to seeing how Domain Access evolves.

]]> by: grndlvl http://ken.therickards.com/2007/11/25/domain-access-update/#comment-29124 Wed, 28 Nov 2007 22:06:02 +0000 http://ken.therickards.com/2007/11/25/domain-access-update/#comment-29124 Check it out in action at http://activote.com currently a live beta. Send me any feed back. Check it out in action at http://activote.com currently a live beta. Send me any feed back.

]]>