OG Vocab: How to use it in a space to show content?

The taxonomy terms for content are usually shown as links just below their body fields on their full node pages.

If you need to show custom taxonomy terms within some sort of View or table, then you need to customize and add those yourself. If you post more details on exactly which view you are using I can try to help more.

The taxonomy terms for content are usually shown as links just below their body fields on their full node pages.

Resurrecting this thread because I'm testing the vocabulary terms visibility in OA 2.41 and noticed that, specifically on Discussion post's content type, once the new Taxonomy was created and associated with the relevant OA Space in order to be able to add vocabulary terms to content then these terms don't appear "below the content body" as expected (as a link), denoting a possible issue/problem in the view of them.

More, the taxonomy terms visibility behaviour, changes when content type changes (in OA Sections belonging to the same taxonomy enabled OA Space):

• Calendar Section: a new Calendar Event is created, no vocabulary is shown at all so no vocabulary term can be selected, not able to test the terms visibility.
• Task Section: a new Task is created, vocabulary is shown and vocabulary term can be selected, vocabulary term is displayed "below the content body" as link.

A thing to note is that content that can be associated with taxonomy terms, despite associated terms are visible or not on the content's body, then is filtered (so it appears as a list) when link cited above is selected (links appear in the content's body under two strings "OG Vocabulary" and associated vocabulary's name)...this means that taxonomy mechanism works but its visibility (in terms of seeing "terms tagging" on content) not or, at least, not on every OA content type.

Can this be confirmed?

Step to reproduce: Create a new Vocabulary and add few terms to it directly by OA Space Configure->config->taxonomy OR associate, in the same page, with an existing non empty Vocabulary now note that on Discussion Post, among "Attachment" and "Access" you will note the Vocabulary and you have the file into which to select terms.
Publish the post and note the absence of the term/terms added. As said the same doesn't happen with a Task (it seems to work) instead Calendar event doesn't show the vocabulary at all.

Am I doing something wrong?

Thanks, Davide.

You should probably wait till 2.42 is released later today and give it another try. There have been several changes to og_vocab recently and also some fixes to taxonomy in Atrium. So this might already be fixed.

Hi Mike! OK! I'll give it a try after updating a OA 2.41 site I used for tests, thanks again.

Should be fixed now in the 2.42 release. Re-open if there is still an issue.

Hello Mike, upgraded to OA 2.42 and did few tests.

What is changed since my comment #2:

• Calendar Section: a new Calendar Event is created, now vocabulary is shown and vocabulary terms can be selected, vocabulary terms are displayed "below the content body" as a bulleted list of links (one bullet for each term involved).
• Task Section: a new Task is created, vocabulary is shown and vocabulary terms can be selected, vocabulary terms are displayed "below the content body" as a series of links in the same row (with each term link that has a grey balloon background around it) so, basically, it continues to work as expected (in term of visibility).
• Discussion Section: a new Discussion Post is created, vocabulary is shown and vocabulary terms can be selected, vocabulary terms are still not displayed "below the content body" nor as a bulleted list of links (one bullet for each term involved) neither as a series of links in the same row.
• Document Section: a new Document Page is created, vocabulary is shown and vocabulary terms can be selected, vocabulary terms are displayed "below the content body" as a series of links in the same row (as happens with Tasks).

Tested on existing (2.41) sections and also after creating new (after 2.42 upgrade) sections. So if an Event now shows vocabulary terms as expected, a Discussion Post still doesn't.

Please also notice my note about different ways vocabulary terms are displayed (personally I prefer - it's more compact and modern - the way they're displayed in a Task/Document content type than the way they appear on an Event content type).

If you need a screenshot let me know.

The Task/Document format is how they *should* be displayed on all other content types. Not sure what would be different in the theming with Events but I'll look into it as well as why they don't show on Discussions.

Here I am with few screenshots (bulleted list representation on Event versus the default way). Thanks Mike. Davide.

Edit: Also note that only in Task, vocabulary terms are preceeded by the vocabulary name which they belong to.

I've added several commits across several modules to improve the consistency of terms on content types.

1) Events were using a View for "Event detail" and adding the taxonomy terms there. I removed the terms, links, attachments from this view and put them into panelizer panes where they belong. I think this View is left over from some old code in Atrium and probably shouldn't be used for this. But left the rest of the view for now.

2) Tasks is using a Full node render in panels, which renders the og_vocab field as part of the content type display options. There probably should be a different want to handle the task rendering, with the "Status" box handled as a themed item rather than relying on the field groups. The problem is that it will only render the OG Vocab field, and not any other global taxonomy added to the node. So some day this should be refactored to use the same "Node terms" panelizer pane as the other content types. For now I have hidden the vocab name so this list of terms will match other content types.

3) Documents were actually doing it right!

4) Discussions were missing both the Node Terms and Node Links panes in the panelizer layout, so added those.

5) Finally, moved the css to control how these links look (labels with gray background) into the oa_radix theme instead of in oa_wiki.css

So, keeping this issue as Fixed. In v2.43 if there is still a problem, open a new issue for it.

Thanks Mike, really! Hope to be able to test ASAP. Davide.