It was confusing at first to see the Group type select list when I create and edit nodes. Then I enabled the Fields UI and realized that when I make a content type an OG group type, this adds an instance of the field og_group under the Manage fields tab.

If I understand the direction OG is headed in D7, I think it would be more intuitive if OG would just be added to a content type under the Manage fields tab, rather than also having OG settings under the Edit tab.

Alternately, if OG settings are going to remain under the Edit tab, I suggest giving administrators the ability to hide the Group type select list on the node/add and node/%/edit pages. It seems weird say 'this is a group type' when I create a content type, and then have people override this setting node-by-node.

Just a thought.

Comments

amitaibu’s picture

amitaibu
Primary language Hebrew
Location Israel
commented
Status: Active » Closed (works as designed)

> Group type select list when I create and edit nodes

My plan is to have a setting implementation to hide this field, and set it to enabled by default. The reason to have this field, is that it allows more flexibility. For example you can set one user to be a group (by role for example), but another keep as a "regular" user.

amitaibu’s picture

amitaibu
Primary language Hebrew
Location Israel
commented

> OG would just be added to a content type under the Manage fields tab, rather than also having OG settings under the Edit tab.

The way you actually set it as a group/ group post type is by adding the og fields. Node is a specific case where you have settings for that as-well.