With TAC integration enabled, term selection when creating a node disappears

Not ignoring this. Just haven't had a chance to try and re-produce it. Will do it this weekend. Thanks.

OK, my friend, here are the results of my testing:

Modules I have installed:

OG 5.x-3.x-dev (this is the version that does NOT have the previous "Groups" menu link bug)
OG Forum 5.x-2.x-dev (this was already installed)
OG User Roles 5.x-2.3 patched for 2.4 (weighted as #3)
TAC 5.x-1.x-dev (weighted as #2)
Patched node.module with the same patch you did.

I created a vocabulary "Test Vocabulary" and associated it with the "Story" content type. I gave the authenticated user the "create story" and "edit own story" permissons.

I then un-installed OG User Roles and and un-patched node.module. Tested to see if "Test Vocabulary" category appeared when the authenticated clicks on "create story" links from main and group menus. It does.

I then installed OG User Roles with TAC/OG disabled and tried same test. Worked.

I then patched the node.module and repeated test. Worked.

I then turned on OG User Roles TAC/OG. Repeated test. "Test Vocabulary" does NOT appear on story form when I click on main menu "Create content" link. However, it DOES appear on story form when I click on "create story" link from group.

What this means is that with TAC/OG integration, Taxonomy must be related to a group.

In my blurb, "How to Make OG and TAC Work Together: Step 2", http://groups.drupal.org/node/3700, which I encourage all users who wish to implement the TAC/OG Integration, I write:

To recap, I needed OG (Organic Groups) and TAC (Taxonomy Access Control) to work together. In the default Drupal access control setup, if you have a node that is in a group and has a particular taxonomy, any user can see the node if he EITHER belongs to the group OR has access to the taxonomy term. What I wanted was a mechanism that only allowed access to the node if the user BOTH belongs to the group AND has access to the taxonomy term.

The point being that TAC/OG Integration is designed for users who want to use BOTH TAC and OG together. If you implement TAC/OG and are unable to create pages that have sitewide Taxonomy unaffiated with a group, I'm basically cool with that because that's NOT why I created this integration in the first place.

I'm not going to go so far and say this is a "design" feature, because ideally you should be able to create Taxonomy outside of a group context. But, I'm willing to accept your inability to do so as a price for gaining the functionaility the integration provides.

So, unless your taxonomy does not show up within the group context as well, I do not consider this an issue that requires fixing.

No problem. This is an issue that needed clarification anyway. Thanks and you're welcome!