- Added permissions.
- User can now edit her terms.
- You can assign\ remove a vocabualry from a group right inside the admin/taxonomy page.
- CRUD api, in preparation for Rules integration..
- Vocab overview is now a form, allowing easier form_alter().
- Breadcrumb and redirection is a little nicer.
- Clean-up comments, move functions to include files.

- TODO, and we'll be happy for some help on that is make the terms block dependent on Views.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

amitaibu’s picture

FileSize
12.79 KB

And a minor fix to a an un-handled redirect.

amitaibu’s picture

Status: Active » Needs review
FileSize
13.07 KB

And here's an automatic workflow using the Rules module:
1) Use the attached module
2) Patch OG, to allow creating a group node ('Add group settings' action). #338919: Rules action - Add group node settings to content
3) Patch rules to allow taxonomy vocab actions. 'Add a new vocabulary' when a new group is created. #350831: Add taxonomy vocab actions
4) Assign vocabulary to the new created group.

In other words, every created group automatically gets its own vocab.

amitaibu’s picture

FileSize
13.11 KB

hmm, why can't i get it right on the first time ;)

moshe weitzman’s picture

Status: Needs review » Reviewed & tested by the community

After a quick read of og_vocab.module:

  1. if (arg(0) == 'node' && is_numeric(arg(1)) && arg(2) == 'og') {. Can we avoid arg()? Same for $form['#redirect'] = 'node/'. arg(1) .'/og/vocab';
  2. Just below that, try something like array_diff($form['content_types']['nodes']['#options'], $skip)
  3. typo: vocabulry
  4. Implementation of hook_term().. I think you mean hook_taxonomy
  5. Feel free to expand the README with more ideas for the admin about how to use this, and any new info thats helpful.

I added Amitaibu as a committer. He is welcome to commit this after acting on this review.

amitaibu’s picture

Status: Reviewed & tested by the community » Fixed

Committed to 6.x-1.x-dev
http://drupal.org/cvs?commit=160722

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.