I'm working on a project and trying to decide if I should use OG or Taxonomy Access. I like OG because the project inolves a nonprofit with several chapters. Each chapter would be it's own group with a chapter overview page open to the public, then some protected information only available to staff and volunteers. Also, the national HQ will use the site to share info. with the various chapters.


My problem with using OG is that it seems easier to theme an overview page for each chapter based on taxonomy using a bit of php and having some blocks that only appear to users with a proper role within that. Also, I want admins to be able to post with mailhandler, and volunteers to post to forums with mailhandler and listhandler. If done with taxonomy access I can have certain forums only open to certain roles and users can email in the forumn content directly to protected taxonomy terms. If done with OG they would have to mail it in, then login, edit and check the box to be OG only. Any suggestions in all this? Could this be managed better with OG in anyone's opinion? Thanks.

Comments

moshe weitzman’s picture

each group can specify its own theme. no code needed ... as for block visibility, you can now type in any code you want including role stuff so i think OG will be fine if you have some development ability.

i suspect mailhandler command can check tghe 'public' box and select an audience for you if you want that. you might need a lot of mailboxes though - one for each group. you will specify og_public: 1 or og_groups: [9] (where 9 is a nid). i have not tried so i don't know where the pitfalls might be. it is designed to all work together.

moshe weitzman’s picture

Status: Active » Fixed
Anonymous’s picture

Eagle-i’s picture

Status: Fixed » Active

I have taxonomy_access and og installed in a test site, to see how it behaves together.

Steps to test it:

1. I set the tax_access permissions for a certain category on non-readable for unregistered readers.
2. Then posted a blog under the category not visible for unregistered readers; when creating it I left the setting PUBLIC (og) on to see what happens

Result:
a non-registered member can read the blog.

Does that mean that og overrides the taxonomy_access?

I would like to see og publish it "public" as for registered members but not part of a group, but allow taxonomy access hide it from the public eye.
How does this all work?

moshe weitzman’s picture

Status: Active » Closed (works as designed)

as stated in the readme, you cannot use both modules simultaneously. it would take a long long time to explain node access system. you have to experiment with the code to understand it.

Eagle-i’s picture

Thanks for speedy feedback Moshe.

I did some reading on another article about node_access in the making, which is supposed to make the modules tax_access and og_module work together:

http://drupal.org/node/24868

Is that something worthwhile? It still looks a bit buggy to me though.

By the way, I installed the latest og and still get the following error, which i have no idea what to do about:

You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '(n.nid), n.title, COUNT(c.nid) AS comment_count, MAX(c.timestam query: SELECT c.DISTINCT(n.nid), n.title, COUNT(c.nid) AS comment_count, MAX(c.timestamp) AS the_time FROM comments c INNER JOIN node_access na ON na.nid = n.nid JOIN node n ON n.nid = c.nid WHERE (na.grant_view = 1 AND CONCAT(na.realm, na.gid) IN ('all0','og_uid0','og_group0','term_access1')) AND c.status = 0 GROUP BY c.nid ORDER BY the_time DESC LIMIT 10 in /home/ministry/public_html/contact/includes/database.mysql.inc on line 66

Is this a critical bug?
Or does it mean it doesn't save info?
Help !