Hi.

Recently, i tried to use og on drupal 7.
I think it seems good. But also og has a limitation. because drupal core doesn't have api like group.
So, Drupal og can't set which entities are group content per group and too hard to set fields per group. (one group has bundle that have two text fields, but another group has bundle that has three integer fields.)
And many modules implement field api are must change a code to integrate with og. But many fields are not integrated.

So, drupal with og doesn't have flexibility.
If drupal core support grouping api with entity and fields, og will use it and can have flexibility.
How about yours think?

(PS. Sorry for my ugly english.)

Comments

Grayside’s picture

Grayside CreditAttribution: Grayside commented
Version: master » 7.x-2.x-dev
Status: Active » Postponed (maintainer needs more info)

While it is true that Drupal core does not particularly support concepts in grouping, OG uses many of the same architectural practices that I would expect Core to use if it did. The biggest problem OG as a contrib project faces is providing this amount of complexity without enough volunteers offering code, support, and so on.

It would be interesting to hear more architectural ideas about what Core "grouping APIs" might look like, as that could be a worthwhile consideration for future evolution of the project, with or without it moving into Core.