Hello,
In my case, when specific role user creates new node, it creates new domain for it (created using Rules with the new module I develop domain_rules, and similar to domain_user module).
This new node on the new subdomain should be available to anonymous users, but since it is not part of the "admin/build/domain/roles", it does not happen.
I wouldn't want to need to add each subdomain to the role.
Is there a way nowadays to do this ?
I think we might want to add this feature as an additional option in the "Role settings behavior".
Another solution is to enhance the domain_rules I am working on, and add the ability to set the default roles for new domains as an action.
Comments are welcome.
Regards,
Shushu
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | domain-by-role.png | 35.51 KB | agentrickard |
| #7 | 782838-domain-roles-to-all.patch | 4.54 KB | agentrickard |
| #6 | domain-roles-to-all-782838-6.patch | 2.48 KB | David Stosik |
| #4 | domain-roles-to-all-782838-4.patch | 4.24 KB | David Stosik |
Comments
Comment #1
agentrickardThe 6.x branch is closed to new features. All the main module does is set a 'domain_roles' variable as a serialized array, so you should be able to edit that value in your action.
Comment #2
agentrickardComment #3
agentrickardComment #4
David Stosik commentedIs this issue equivalent to << Add "All domains" checkboxes line in Domain roles form >> ?
If so, could you please have a look to the attached patch ?
Regards,
David
Comment #5
agentrickardQuick look is good. This could (of course) use a test....
Comment #6
David Stosik commentedThis patch applies to last 3.x-dev version.
Comment #7
agentrickardSweet. I cleaned up the form a bit (putting 'All domains' at the top; cleaning up the theme function.) Then I added a very basic test (more are welcome).
Committing.
Marking needs work for Documentation and a Test.
Comment #8
agentrickardTagging for documentation.
Comment #9
agentrickardComment #10
dqdI'll close this issue due to inactivity for 13 years and upcoming EOL of Drupal 7 in January 2025. While the project's version for Drupal 7 will surely keep providing support for security issues and website breaking bug fixes for Drupal 7, we should try to minimize the open issues for Drupal 7 in the queue as much as possible. A big thanks around for the report and all the efforts in here.