Group admin + group redactor + group subscriber

og_user_roles is a hack and is not supported here.

Hi Moshe,
I am messaging you because of Organic Groups problem I am having. I posted this question before but nobody seems to be responding. Maybe the question is too easy or too hard:)

I have problem in my group front page. It shows only 10 posts even it is set to show 50. Does anyone know how to change or fix this. This is set up page for view " og_ghp_ron"..... and it has following......

Name: Defaults
Title: None
Change settings for this styleStyle: Unformatted
Change settings for this styleRow style: Node
Use AJAX: No
Use pager: Yes
Items per page: 50
More link: No
Distinct: No
Access: Unrestricted
Header: None
Footer: None
Empty text: None
Theme: Information

I am assuming this is where I change number of posts per page.I changed number of posts to 50 but nothing happens. I know this is the right view because when I go to any group front page I can see 3 tabs there (edit,clone,export) end when I click on edit it leads me to that view settings.
I dont know what else to try. Please if you have any ideas,suggestions anything at all it would be greatly appreciated.

Thank you so much

og_user_roles is a hack and is not supported here.

That it is not supported here is certainly the moderator's prerogative. However, that it is a hack is the moderator's opinion. The og_user_roles module has been in place, used by Drupal users and constantly improved over the past two years. I suggest that interested persons look at the module project page: http://www.drupal.org/project/og_user_roles and the issue queue: http://drupal.org/project/issues/og_user_roles?status=All to make up your own mind.

Just to set the record straight, basic OGUR functionality (group roles) is fully supported within Drupal 6.x. The key "hack" was incorporated into Drupal core here: http://drupal.org/node/176342

The OGUR extended component, Taxonomy Access Control/OG Integration, is not recommended, but provided and supported as it does resolve an important access issue for lots of people.

As the OGUR contributor, I apologize for the heartburn the OG contributor receives as a result of persons posting their OGUR related questions in his issue queue. I will look at my own documentation and see what I can do to get people to not do that.

Because, I believe that cooperation is much more productive than name-calling.

I think this should be clarified by the OG_user_roles team first. Moving it to that queue. If that module is involved, it is not fair to bug Moshe about this until that team has verified and pointed out how this is not an og_user_roles issue. If knowledge related to og_user_roles is needed to resolve this, it belongs in that queue.

In the original question, I think he wants to know why a user elevated to OG group admin status can edit groups. I answered this before here: http://drupal.org/node/313323

From his attached image: http://drupal.org/files/issues/cap.gif I ascertained that he assigns his "group redactor" role to users who are elevated to group admin.

What the user doesn't understand is that when you elevate someone to group admin status, he automatically has the ability to edit the group node. I seem to recall an OG issue where the idea was bounced around about making the group admin status a permission instead of being hard coded. I don't know where that went.

In all fairness to me, the only thing this has to do with og user roles is that the user uses an ogur feature to automatically assign the "group redactor" role to users who are elevated to admin status.

The solution: "group redactors" can not also be group admins.

Explanation provided, closing.