My first step is to figure out a way to open up user_access so other modules can add roles as they deem necessary. Here is the request for assistance I posted to the Drupal Development list which describes what I'm trying to do. Any asisstance will be highly appreciated and help move this project forward:
I am proposing a new project: OG User Roles. I have written to this list before and what I discovered was that I really needed to formulate a proposal for some sort of user_access hook that would include permissions granted from other modules to the final list of permissions for a user during a particular process.
That, essentially, is the modification to user_access that I have created so that my module would work. Briefly, my OG User Roles module is designed to assign role(s) to a user restricted to the OG group he is in. Details on it are here: http://drupal.org/node/87679.
What I have found is that my modified user_access (and therefore my proposed hook) works for node listing/view/updating/deleting, but NOT creating. I am able to create nodes with the modified user_access only if I call the node_add() function directly. Not a real good solution.
So, I'm back here to ask:
What else, besides user_access, does the default node/add mechanism call for permissions checks?
Here's the scenario: I've given a user in a group a role which allows him to create a document. When his group menu comes up, he sees a "create" link to the document he's been given access to create (that means my modified user_access is working). However, when he clicks on the "create document" link, he gets "Access Denied" message.
I wrote some debug code that writes out to a file the variable values from my modified user_access function when the user clicks on the "create document" link. What I noted is that the corect permissions and group context are always returned. What happens when it fails, i.e., user receives "Access Denied", is that the function loses the arg (arg(0), arg(1), arg(2)) values. They just disappear. This never happens on successful submissions.
As you can probably see, I can't very well propose a hook if my simulated hook is not working correctly. Can someone give me some clue as to where I need to look in the node/add process to figure out why I'm losing the arg values and getting the denied error when user_access is bringing back the correct permissions?
Thanks so much.
Comments
No Need for the Hook
After submitting the hook proposal, someone suggested perhaps using hook_user("load") to add og user roles to $user->roles. I tried it. It worked. But there was still one problem: I still got "Access denied" when trying to create new nodes under og user roles. I tried suggestion after suggestion, but to no avail. There is some weird access issue in Drupal that no one seems to understand.
Nevertheless, it looks like I've finally cracked this nut. I'll post notice when I've incorporated this modification into the distribution I've made available.
I had to do an end-around to do it, but I've finally come up with an implementation that doesn't require modifying other modules.
From the very beginning, the only circumstance in which my og user roles module failed was in node creation, specifically node/add/type?gids[]=gid. To solve this problem, I simply created code that would check the user access and call node_add directly:
<?phpfunction og_user_roles_addform() {
global $user;
$gids = $_GET['gids'];
$typeFound = 'no';
if ($gids) {
$group_node = node_load($gids[0]);
og_set_group_context($group_node);
}
$type = $_GET['type'];
if ($type) { <> if ($type == 'forum') {
if (user_access('create forum topics')) {
$typeFound = 'yes';
$output = node_add('forum');
}
}
etc...
}
return $output;
}
?>
This worked, but required that the user a) create a node, b) put this code in the node, c) rename the node to "addform", d) edit the og module to call "addform" instead of "node/add".
A lot to ask of a user, which is why I tried so mightily to figure out what the access problem was.
Someone on the development list once suggested using "hook_init". In seaching the Drupal site for ideas, I saw that someone had used hook_init to redirect url requests. So it hit me: Why not redirect node/add/type?gids[]=gid requests directly to my addform? But, instead of creating a separate node for addform, make it part of my module.
So, by using hook_menu to create the callback for "node/addform":
<?php$access = $user->uid; // login is required
$items[] = array('path' => 'node/addform', 'type' => MENU_CALLBACK, 'callback' => 'og_user_roles_addform', 'access' => $access, 'title' => t('Create content'));
?>
and, creating a re-direct in hook_init:
<?php
// Looking for this format: http://www.mysite.com/node/add/link?gids[]=29
function og_user_roles_init ()
{
if (arg(0) == 'node' && arg(1) == 'add' && isset($_REQUEST['gids'])) {
$gids = $_GET['gids'];
$gid = intval(current($_REQUEST['gids']));
$type = arg(2);
$path = 'node/addform';
$query = 'type=' . $type . '&gids[]=' . $gid;
drupal_goto($path, $query);
}
}
?>
I was finally able to get "node/add" working for og user roles without patching any core modules (user.module OR node.module).
If anyone is still reading this, I have one small development question:
Since my addform code is now basically replacing node_access in this circumstance, how do I check the "create" permission on any content type (not just "node" content type) for any module without having to know them all in advance?
Thanks for all the help. Again, I'll post notice of the update once completed.
Latest OG User Roles Distribution Posted
The latest OG User Roles distribution is now available here: http://ftp.scbbs.com/pub/drupal/og_user_roles/
Version: 5.x-2.x-dev
Please test out and let me know if you find any problems.
Thanks!
just want to double check
Hey somebodysysop,
Don't know if you remember me, but I had bugged you a while back about learning how to use OG & TAC together. I had been following your posts, and done all the step #1 (pre- stuff)f when you were doing the instructions in atwo or three step process installment. At a certain point, I backed everything out as I was waiting for your final instructions.
I have since noticed your og_user_roles module, and am thinking I might go with JUST THAT, and not even try to incorporate the TAC. I just wanted to double check I understand what it will give me, before I install it. My understanding is that;
1) the roles are specific to each group. So I can make a person have a permission in group1 that he will not have in group2 (unless assigned by the admin of that group).
2) that I can enable two roles (or just one if I take advantage of MEMBER as one), and make it so new subscribers to a group can only view things (MEMBER)... and then the group ADMIN(s) can up that person to a second role of "EDITOR" which will give them the additional permissions of a new role (EDITOR role be able to ADD to the group and even EDIT other peoples wiki pages within that group).
3) that i can give ADMINS the ability to manage their own groups by allowing them to change role within the group of the people they wish.
If this is a correct understanding... I am forging ahead... can you confirm this?
Because... I think it will allow me to accomplish me overall goal. He is my over all goal.
I am going to make WIKI pages only editable inside groups when they have EDITOR role in that group. And then I can also allow those people to post those group wiki post to PUBLIC as well as the group. This will mean that I can have group EDITOR people edit a document collaboratively... but if they make it PUBLIC no one outside the group can edit it (cause ALL wiki pages will only get edit permission within a specific group). And this will allow me to have the EDITORS in group one... display their wiki page publically and people with EDITOR capability in group 2 will not be able to changed it when they are viewing a public wiki... because I will only assign the EDITOR role inside a specific group.
Can you tell me also it the overall goal can be accomplished with the og_user_role use as outlined about, or if I am missing something in my understanding?
Cheers! Ricco
Yes. OG User Roles will allow you to do exactly that...
Yes, I remember you.
What you describe is exactyly what OG User Roles was designed to do. You only need the og_user_roles module to accomplish this (not the TAC/OG patches).
The TAC/OG architecture I put together was designed to allow me to fine tune permissions and what users could view, update, create and list. But, just putting content in a group that all group members can see it, but only group members with certain roles can create/update/delete, is a job that og_user_roles should be able to accomplish on its own.
Check it out. If you have any problems, let me know.
Thanks!
report on my install experience & a Question
Hey Folks,
I have installed og_user_roles, and it is working for me. I have one or two questions, but I think they are settings questions, not functionality issues. I encourage people to forge ahead. In the instructions it notifies you that you may have to build a table by hand... but installing the module created the table for me fine. I am testing out now.. but it is really slick... exactly what I was looking for.
QUESTION FOR SOMEBODYSYSOP;
It seems that the group ADMIN setting now is overridden by the og_user_roles? I can set someone to a ADMIN but it does not seem to give them any functionality by default (which I sort of expected), but I cannot for the life of me figure out how to have the group founder, give another person the ability to have the "Configure member roles" tab, and allow them to assign roles to others within the group.
I am working with 3 roles.
1) member... the role everyone gets when the register (they can make blogs)
2) contributor... assigned only in a group, giving that person the ability to (create and edit wikis inside the group)
3) GMan... my idea of the group manager, that the founder can assign to accept subscribers, and in the best of all possible worlds assign other people to be GMen.
I (founder) can currently give people contributor roles, and they get the added ability I expect.
But... What settings on; /admin/user/access do I have to give the GMAN role so that they can then assign roles to others?
Also... how does the group ADMIN setting play into it? I have tried to give a person ADMIN, and then make them a GMan (but I can't fugure out what /admin/user/access are critical. I don't want GMan to be able to edit the group node itself... just be able to up member requests to contributors, and perhaps assign other members to GMen also?
I have tried playing with;
administer nodes
administer access control
administer users
avoiding - administer organic groups
but nothing is seeming to work.
I am really sorry to ask you what is probably a issues I should be able to figure out, but any advice you can give would be helpful.
ADVICE FOR OTHERS;
1) I had some trouble until I uninstalled and offloaded these modules;
usernode
nodefamily
2) don't forget to install the mimemail module, or you will crash when you try to use the checkbox to had admins alerted when new users join the group.
get the module here; http://drupal.org/project/mimemail
3) don't forget to go to "1 subscribers" after you make the group, and give yourself the role that you need.
4) I also noticed that I was having trouble with a navigation sidebar for creating content when you create a group. All the content types I had assigned for a role were not showing up. Just the blog and the forum, and some other non-content type options. I found the work around was to immediately make a blog page in the group... and once you save the blog page... all the other content types are available to you, and will be available to others that you assign additional roles privileges to.
Overall, I ran into no "scarey" or "pull your hair out" problems in the install, and I recommend using this option to add some really really great functionality to your site.
Cheers! Ricco
Thanks. This is the sort of feedback I've been hoping for.
Thanks, Ricco, for your efforts on this. I'm trying to address your issues as best I can.
With respect to the mimemail issue, I've made a note in the README.txt file.
No idea, at this point, why there would be a problem with usernode and nodefamily. I'm using both in one installation. Will keep an eye out for that one.
Not sure about item #4. Sounds like there needs to be some sort of initialization? Hopefully someone else will try and report on what happens there.
With respect to Group Admin role being overridden by og user roles, that's something I need to look into. It shouldn't happen. Can you give me a little more feedback on this issue? What happens if you uninstall og user roles? Does user assigned group admin now have correct privileges?
To help in your situation, I've created a "configure member roles" permission. Whatever role you assign this permission to will be able to assign group roles. So, the group admin by default will not be able to "configure member roles" until his role is given that permission.
Thanks for your help!
more info ... regarding question
Hey Somebodysysop,
Ok... so the username I use on my site "Ricco" :) has a role (unique) I created called 'superuser' not #1 user, but it effectively has every permission available.
What I did to test out my problem was to assign the GMan role, every permission that my Ricco user has as superuser (figuring if it worked I would just back out permissions until I was able to remove all excess ones, after I get it to work).
I am able to assign another user the GMan role... and they get the "Configure member roles" tab, (I also make them an ADMIN), but when i have that user click the "Configure member roles" I get a 404... access denied. So it seems I am at a dead end with my knowledge, and ability to think of another approach at the moment.
I did notice you mentioned in the page thread that you seemed to experience that at one point, and made a node and polulated it, etc... 'remember the... a user would never do that comment?', but it seems like you also said that you build a workaround into the 5.x distribution you mention later, which is the one I am using. Can you think of anything else for me to try? It seems I am soooooo.... close.
Cheers! Ricco
I have resolved that issue...
Again, I have specifically created a "configure member roles" permission, so you don't have to go through all those hoops to give a user that privilege.
However, I am still bothered by the group admin issue. I noticed in one of my test environments that even with og_user_roles uninstalled, a user who I made "admin" in a group still did not get the "Add subscribers" tab.
What has been your experience here?
I will upload the updated module shortly.
New 5.x-2.x-dev distribution available for download
New 5.x-2.x-dev distribution uploaded here: http://ftp.scbbs.com/pub/drupal/og_user_roles/
This has some security modifications as well as: A "configure member roles" permission has been created. So, this permission must be given to any role allowed to use og user roles to give group members group roles. Before this change, you only had to be the group administrator to be able to assign group roles.
Thanks!
right back at ya!
Hey somebodysysop,
that note about the, usernode & nodefamily was more a a hint in case someone ran into problems. When I first installed og_users_roles and has some minor problems. I tried to clear out any of the node type modules that I did not think I was using in any way. Over the few months i have worked with drupal I have sometimes installed a module for one reason, only to realize I was not using it a few days later. My mentioning removing those modes was simply a "it worked for me" soft of hit in case anyone else didn't thin they needed them. Sometimes, I give a bit more than the critical info in my posts, figuring, I might as well try to do a more state of consiousness sort of post in case one of my random thoughts may be of hep to others.
As far as the sidebar create content thing, it goes away as soon as you make any post. So it is hardly an issue for me, or I think anyone that uses the application on my side. I will keep an eye and give more info as I create more groups.
I read in both posts your note about creating a permission for "configure member roles" and to be honest I am not sure I understand. But it sounds like what you are saying is that you are making a new version for me (and others) to download so I will look to see if it makes sense when I see it. I sounds like a new line item on the /admin/user/access page. But I am not sure how it will link to the particular permissions that are possible to build, since they seem almost unlimited... in fact your third email just arrived. so I will finish here, so that get the excitement of knowing that there are people waiting with baited breath for your code... even as you develop it. And what you have got so far is so rockin, that I am guessing the next round will take care of that one "permission denied" problem I am having.
I tested uninstalling the or_user_roles module, and YES, even once uninstalled... giving someone ADMIN permission seems to no longer give that ADMIN the ability to do anything. ADMINs now just see the permission, and connot adjust them.
going for the new mode now... thanks so much. I am Ricco on freenode.net & dal.net pretty much 24/7 if you need to pop me, and I am webulite on skype. Feel free.
You are the best. I bet your lighting a fire under the Drupal development dudes. Especially when a few more people install this mod, and realize how it makes OG truely sing!
Cheers! Ricco
PS... you should rename this page og_user_roles it will make it much easier for people to find.
Yes. I added a new "line item" to access control
I added a new permission in access control (/admin/user/access) called "configure member roles". The person who will assign group member roles must have this permission.
The good thing is that you can create a role called "group admin", and give it all the permissions you want (including "configure member roles"). User og user roles to use it as a group role so that group admin in one group won't be able to mess with content or users in another.
Let me know how it turns out.
If anyone else has any suggestions about why the group admin setting doesn't take, please let me know.
Thanks.
YOU ROCK! but you might have an initialization issue
hey there...
BTW, I WAS using your roles checkboxes to assign on the "Assignable roles:" area of the "Organic groups user roles" page. I think you might have felt i was overlooking that. I was not
It is now working! I do have something I did not has before. On the "/admin/user/access" page... there a new section that I could swear were not there before. And THEY seem to make it work :)
og_user_roles module
configure member roles .... checkboxes
One possible final question/problem. There is some very bad wording on the "Organic groups user roles" page that says...
Default Non-Group Role for new users.
Set default global (site-wide) role for new signups?
Do you wish to automatically assign all new users to a specific role that is NOT group specific upon signup?
Selectable roles:
To me a that section is talking about new registered users? But I am wondering if you mean new users to a GROUP... and here is my current problem
If that is the setting the default role a person get's when they enter a group, perhaps:
"Default role for initial group founder & subsequent subscribers"
btw... more words are always better ;)
PROBLEM/ISSUE ??? You must have thought of this. Currently if I make a group with a regular MEMBER, they get assigned the "contributor" role (so they cannot see the "Configure member roles" tab... so it sort of immediatly locks you out. I have to log in with my superuser... edit the test user to give him a GMan role, and then WHAM... the tab shows up and I can begin to manage the group
BUT... here is an issue that I cannot see even if that above area is the default role for the founder and subsequent subscribers.
If I make a group. I need to be given GMan status or I cannot start managing the group (since the ("Configure member roles" will not show up)... BUT... if that is the default... as soon as the second person subscribes they ALSO get GMan status. There is a catch 22 there. you want the 'founder' to be assigned the HIGHEST role level to begin managing the group... but want new subscribers to get the lower level of the special roles within group.
Think about that, and tell me if that section I mention above is the default role of a new subscriber/founder in the group? or if it really is as it says the "Default Non-Group Role for new users"
In any event... that is truly the final details. Although I might have found a group "initialization" issue that is gonna be a real bitch.
OTHER THAN THAT.... LOOKS LIKE YOU ARE IN BUSINESS.
BTW... upon creating these two or three groups I just made... the "create content" sidebar is showing the proper items that it should, and it changes as i change a use from "contributor" to "GMan". NICE!
I will simply adjust that area above to use the check box, and set it to GMan and see what happens.
Cheers! Ricco
The oddly worded section is for new registrants to the SITE
I needed a way to put new users who register to my site into a default site-wide (not OG specific) role. This is what the Default Non-Group Role for new users check box is for.
I'm not sure I understand what you mean about giving default users the "configure member roles" permission. In my mind, if you are going to let a member in the group assign group roles, then you need at least 3 basic roles:
Member (see, but not contribute)
Contributor (see and contribute)
Admin (administer the group, has the "configure member roles" permission)
followup
I tried that "oddly worded" area on the "Organic groups user roles" page, starting with "Default Non-Group Role for new users." to be checked, and set to GMan on the picklist... then I created a new group with a regular member user... The new group is created, but the role inside the group for the "founder" is MEMBER... neither "contributor" or "GMan". you might have a problem there... Unless I am missing were that default is set. It would seem you would want the founder to simply get the highest role level you check on the "assigned roles" area... and then perhaps have a picklist from the available roles also obviously from 'assigned roles" are that subscribers will get.
BTW.. most recently all my testing was with moderated groups if that gives you any info. In the first round... pre the new module upgrade I had been testing with OPEN groups.
Am I missing how and/where to set the role of the founder? If not... all groups creations can immediately lock out there founders. I am not criticizing. It could be simply that the role set I am using "member, contributor, GMan" and their permissions are different than the roles that you have been developing and testing with.
Cheers! Ricco
Again, not sure what your issue is here...
Your issue seems to be with roles. You do NOT give all roles the "configure member roles" permission. That should be pretty obvious, but again, I may not be understanding what you mean.
If you have 3 roles:
Founder (GMan?) (view/list create/update delete group admin)
Contributor (view/list create/update)
Member (view/list only)
Then, it's the Founder who gets the "configure member roles" permission.
There is no DEFAULT group role set. The setting you tried sets a sitewide default role, not a group default role. Group roles must assigned manually using the "configure member roles" tab.
Hopefully this will help.
the vision thing
Here is my "big picture". And why I am looking for a "Group Founder Default Role" attribute to your og_user_roles modules.
Let's say you have a basic role when someone registers to the site overall, not the a group. MEMBER, and a member can make blogs.
I thought on the page; "/admin/og/og_user_roles" in "Assignable roles:" you check all the roles you want your admins to be able to assign. But the issue I have is that I have people that are only MEMBERS with only blog capabilities starting groups. And when they do... they still only have MEMBER (blog only) permission, and therefore will never even see the "Configure member roles" tab on the subscribers list page.
For example. Let's say you have a community oriented site. that is supposed to "run itself", ie, the sys admin does not deal with registration, roles, etc... day to day. A visitor comes to the site, and registers. He is now a member and can make blogs & can make groups & can make events. So now he makes a group. I have it set up so the "Assignable roles:" for groups are "contributor" (can make and edit wikis) and (GMan) can do that, AND can make another person that follows him into a group also a GMan. And my idea was that all that follow the fonder into a group would only have MEMBER role when they enter, and the founder would be responsible for giving them more than view permission as he saw fit.
So, now the member makes a group.. and he is still only a member, so he and the group are sort of stuck. What I was thinking was that when a MEMBER made a GROUP (founds a group) he would become a GMan in that group, or even better be assigned a totally separate role that could be specified as default that would give him abilities to to more than even the GMen that he will create. (Sort of like on IRC when someone enters an empty channel and becomes an OP... and then can control all others that come in behind him). And subsequent people could enter simply as members and view only his group. then at his desire he could adjust their role in the group to either contributor or Gman. And the founder would have started a little mini environment that he is the most powerful in, and can assign helpers and such. Without the need for the site sys admin to ever get involved.
Visitors would be able to come to the site, and create and maintain groups for themselves. And the system administrator would never have to do anything but back up and take care of problems.
IF... you create one addition to your system that allowed on the "/admin/og/og_user_roles" page, in addition to 'assignable roles" a 2nd attribute area designated "founder role" that would be assigned to anyone that states a channel (who in my case is only a member) And automatically assigned anyone that starts a group that role. I could give that role "wiki, create and edit, forum creation, poll, etc... a variety of permissions to anyone that started a group, and the environment would, in effect, be self sustaining. Truely an "organic group" or community of groups.
Just some real world info. I see this application all the time. I am building this site for a non-profit that supports sustainable developement. this is not their primary site, but they see the site as a 'community building project". They plan on simply advertizing this site as a place that activists, environmentalists, other non-profits, citizens, or anyone can go to... join.. make groups, try to attract others, and hope they eventually work together in some miraculas fashion. It's almost like a mySpace or any other those community site ideas.
I thought I would just give you an over view of my particular project at this time. It is very different than a corporate or company based site where the sys admin is often in control of starting the groups, and over seeing them.
And with everything you have put together, it seems that if you could add, or show me how to add, one more attribute/field/permission level on the "Organic groups user roles" page that would allow me to specific a "Founder role" that anyone visitor that registers, and becomes a MEMBER (remember can create only blogs, events, and groups) and decides to start their own 'stamp collecting group" or "local raise money for Bob who's house burned down group", or a almost infinite variety of unrelated groups that could form on my single site... I would probably be done. ;)
Thanks so much for all you have done already. Give my suggestion some thought. I think that that one added addition, would allow you to effectively have a totally packaged application that many people could benefit from. It is almost like a web based IRC world. with groups instead of channels.
Cheers! Ricco
OK, Default Founder role assignment
I've modified og user roles to assign a default "founder" role group role to users who create groups.
In other words, it will assign a role (that you select in og user roles settings) to a user when that user creates a group. The role will be assigned to that user only in the group he just created.
So, if you set "Founder" as the default founder role, and give it the "configure member roles" permission, then when a MEMBER creates a new group, that MEMBER will be given "Founder" role in that new group, and allowed to "configure member roles" only for that group.
What roles the MEMBER/Founder can assign within the group will depend upon what roles you select as assignable in og user roles setttings.
I've also tried to re-word the README.txt file so that the Default Non-Group Role wording isn't quite so "funky".
Finally, I've also come up with the fix for assigned "group admin" users (users who do not create groups, but are given the "group admin" designation in OG) not being able to see the "Add subscribers" tab. It is described in the README.txt:
"Group Admin" for the group, we have noticed that the "Add subscribers" tab
does not appear for this user when "og user roles" is installed.
The fix for this is to:
a. Create a "GroupAdmin" role in "access control", and give this role the
"edit group content" permission.
b. Go into "configure member roles" for the group, and give the Group Admin
user the "GroupAdmin" role in this group.
This should settle all the issues for now. A new distribution with these changes is now available here:
http://ftp.scbbs.com/pub/drupal/og_user_roles/
lol... talk about timing
Hey somebodysysop,
Talk about timing. posted in the exact same minute.
It looks like your new version attempts to take care of the admin permissioning question I had. I will download the new version and test.
WOW... you made a FOUNDER role... how cool. Will also check it out
Cheers! Ricco
Only outstamnding question
Hey somebodysysop,
I rethought how I could use the existing module without the adjustment I outlined above. And I have a solution for me. I will simply have to have a site admin approve and create anew groups for now. So that request is only outstanding if you think it would improve your module.
There is one bug I think I have found.
I can make a person a group ADMIN and then, and if the group is moderated, they do receive the email for a new subscription request. but when they try to APPROVE the subscription, they get the access denied message.
I have tried playing around with the various permissions on the access control page (admin/user/access) but I cannot find any permission setting to give the person I have made an ADMIN that will allow them to approve the subscription. Right now it seems only the group manager can do that. The ADMIN does show the request on the group list page, and does have a hyperlink on "approve" which implies that he should be able to do that.
Cheers! Ricco
What is the url that the group admin follows a link to
I just broke my OG module by downloading and installing the latest 5.x-3.0 so I'm unable to test this.
What I need to know is what is the url that the group admin tries to link to in order to approve the subscription. In other words, at what url does the group admin get the "Access denied"? Once I know the url, I can fix it rather quickly.
Thanks!
subscription request URL format
Hey there,
The URL for me looks like this;
http://webulite.com/og/approve/320/13
The Admin CAN approve the subscription by using the web page (go to the subscription link, etc...) It is just the instant approval link via the email subscription request that still gives permission denies. (BTW... i had not checked that since I did my last test. I had tested the approval via the site itself. Nice catch!)
Lol... funny to see you already got a "way to go" from someone else. This module is gonna be REAL popular.
Cheers! Ricco
Give me a sample of the approval link
Send me a sample of the approval link url. I may need to add that to the list of urls that return og user roles.
And, thanks for the compliments. Just want to make the module work as advertised, and your feedback helps tremendously in that process.
Apparently I don't know what you mean by the approval link
Hey there,
I am sorry, I am not sure what you mean by an example of the approval link. The link I sent above is the link that appears in the email the ADMIN receives, and the one they are supposed to follow to approve the subscription.
Cheers! Ricco
Thanks what I meant.
Thanks. That's what I wanted -- the link that was sent in the e-mail. If that's it, then the problem is resolved.
un-F-ing believable EVERYTHING WORKS
Hey somebodysysop,
Just downloaded and test the most recent version. Everything works!
1) The Admins can now approve subscription requests.
2) The new FOUNDER's role works as expected.
Life as we know it is now unbelievable and perfect. You are truly the KING. The master of modules.
I just purchased the book Pro Drupal Development, and will now begin reading. You are my hero, and one day I hope to be just like you. Thanks so much for this module, and all the adjustments you have made. Now I can put my development on hold for a bit, and read this book and actually begin to learn how to approach some of this stuff myself. Again, you are true the KING!
Cheers! Ricco
Amazingly..
.. fast progress with this module! Great timing, too, from my point of view :)
The fully any-user created (and controlled) groups is also exactly what I need for my site, to make the communities really work dynamicly. I actually thought it was already included in earlier versions, but I hadn't tested it properly yet because as I got problems with my testserver at the moment.
Anyway, I'm really glad about the progress of this particular module :)
Got my own project for OG User Roles
Finally got my own project for OG User Roles:
http://drupal.org/project/og_user_roles
All future distributions can be downloaded from here.
Thanks to all of you who stuck with it and helped out with comments and suggestions.
og_user_roles with the whole OG/TAC combo
Hey somebodysysop,
I just wanted to double check. I got a few posts about the OG/TAC thing. If you remember I started with interest in the OG/TAC combo, but then backed off to just working with your new of_user_roles. I have installed and have been running that, and love it. Yet I have started to see notes about the OG/TAC, and it seems that you may have moved on and fixed the minor problems you were fixing in it, the last time I was pursuing that.
I Wanted you to clear up something. Does this mean that you have moved on and got the TAC working within the over all? (including the new og_user_roles). If this is the case, I will try following the instructions. But if trying to implement the OG/TAC combo, will in any way make my og_user_roles go haywire I will avoid it. I currently don;t use taxonomy at all, but now that og_user_roles is working so fine... I was thinking starting to try to add some taxonomy stuff to my site. If TAC is now working with OG, I will look not only at taxonomy, but at TAC. It truely seems it would add some really cool functionality.
Can you let me know if one that has og_user_roles working, can now try adding the OG/TAC thing you have been working on, without causing problems in the now working og_user_roles?
Cheers! Ricco
Yes, OG/TAC Combo and og_user_roles updated to work togther
First off, the TAC/OG combo is totally experimental. I have it working in my environment, but it requires the 3 patches to core/contribution modules. My goal remains to figure out how to get the functionality without patching core modules.
Yes, the recent updates to TAC/OG were made so that it works with OG User Roles. In fact, you now must have OG User Roles in order to use TAC/OG.
TAC/OG should NOT be installed on a live production server. It should only be used, at this time, on your test server. As I said, it is working fine in my environment, but that environment is controlled. I don't have any idea how it will react in environments which are using other Access Control modules.
It does require that you use Taxonomy Access Control and OG, needless to say. There is also a small patch to the core "node.module".
So, at this point, I still wish to move forward in consolidating the patches into a separate module, and then testing the whole shebang against other Access Control systems to see how, eventually, we can get them all working together.
That's where I am now.
Thanks for the support!
-SomebodySysop
experiment
Hi there. My name is Ricco, and I have been experimenting with some of the wiki features embedded in the groups.drupal.org subdomain. This entry is a test to see that you can I guess what is called "freelink", but I think of as "mediawiki" format link to a page I created in the drupal wiki group.
It is unclear to me if anyone can edit the wikipages that get created or only the author. There is also only a subset of the wiki formatting that seems to be available here, and searching to find prior created pages, I have not yet figured out.
But the [[Ricco]] page (notice only the first occurance seems to freelink) will take you to a page where I do show people how to add code to their themes node modules that will allow them to make colorized links for broken and non-broken links.
I have installed the OG user roles module, and have gotten it to work with the TAC module. It does take some tweaking, but I would be happy to help anyone that is trying to do that, get that done.
If anyone else is interested in this kind of experimentation, trying to utilize the mediawiki format to start a wiki in the drupal world, feel free to contact me, and perhaps we can try various types of testing.
Not sure What you Mean?
Could you explain a little what you mean by this? Thanks!