When the site administrator "allows" a content type for default group, it immediately becomes "allowed" inside the group to group members. Instead the default (inside groups manager contet type tab) should be such that the checkmark for the content type is not checked. THis way each manager can enable the allowed content type as they fit necessary. Suddenly making a new content type available directly to subscriber negates the purpose of the module, at least in the short team the group manager has to go and disable some checkboxes.

All I am saying is disable the checkboxes by deafult when a contet type is made available by site admin.

Comments

ajayg’s picture

ajayg commented

The help for default says " For the Default group, all ALLOWED content types will also be ACTIVATED."
What I am looking for is "all allowed content type is not ACTIVATED" by default.

If this is not possible, could you please suggest which lines of code I can patch so atleast I can try my own custom version.

I can understand why the default options was chosen. Usually you want the group members to create more content and given them that options. However I have some custom content type that I want only Group managers to create by default (unless they give this option to members).

Anonymous’s picture

Anonymous (not verified) commented

I would also like to have UNACTIVATED the default, or even better if there is an option for the site admin to check. For example in the admin/og/og_content_types/admin/0 setting have a box at the bottom saying:

Default Activation Status:
[] ACTIVATED
[x] UNACTIVATED

I played around with the module this morning, and I think this is the line of code (line 506):

            $required[$group][$type] = ACTIVATED;

Just set it to:

            $required[$group][$type] = DEACTIVATED;

*****NOTE!!!!***** I am not a programmer... I hope rconstantine or others who know code better can verify this is a valid fix and won't screw something else up. I did a brief test and it seemed to work (prevented content creation to that node).

Anonymous’s picture

Anonymous (not verified) commented

I also forgot, you need to uncheck all allowed types, then allow them again for the above fix to start working.

ajayg’s picture

ajayg commented

What proably needed a seperate checbox near each type
Allowed, Activated, Required
Since you will need atleast some type to work out of boz when a group is created.

Currently the way it is implemented in DB is there are only two records 1)Sitewide and 2)default. Only the groups which have been customized by group manager are added to this table. So if your group does not have entry, that means all of the content types are available to you. Once you disable once any item entry gets created for group in the DB and even if you enable it stays there. First I thought this was done for scalability (needing as many few records in the table) but I now I wonder if this is really the reason. Because a query is anyway required to check if the entry is there in the table or not.

Perhaps rconstantine can throw some light.

ajayg’s picture

ajayg commented

Anybody knows?

Anonymous’s picture

Anonymous (not verified) commented
Assigned: Unassigned »
Status: Active » Postponed

@Ryan.

This sounds like a great feature but will need your input before we can agree on what is best to be done .I'll postpone this feature for implementation after migration to D6

Anonymous’s picture

Anonymous (not verified) commented

Just wanted to say I'm still hoping to see this implemented, it's quite important on my site, where you need to be a group admin in order to post most of the content (an educational site where teachers create content for students). The idea of having another checkbox of Activated next to the Allowed and Required columns would be great, then I could choose by type, rather than making them either all activated or unactivated by default (as per my hack). BTW, all the other bugs I noticed in the 5.x version which made this module hard to use out of the box has disappeared, kudos!!

baff’s picture

baff commented

subscribe

jvieille’s picture

jvieille commented
Issue summary: View changes

Drupal is now 8, not yet addressed?