Comments

fadgadget’s picture

mmmm im really struggling here. I see that we can create OG Vocab views but im really not being able to even show a term name never mind relate it to the group or group node.

Does anyone have any pointers for me?

Thanks

fadgadget’s picture

sod it i give up. I will uninstall the module and return to it one day if there is an easy solution. Ive really too much to do. My members, who have all left due to me arsing about, will just have to wait for OG Vocabs. I'm not saying all this bitterly ive just had enough head banging against the wall for one day.

If anyone has any thoughts or even better a Views 3 export view that i could use then i wouldbe forever gratefull.

thanks

fadgadget’s picture

Is the "group categories block" still part of this? I dont seem to have one. Thanks

fadgadget’s picture

Tried a Term View with Contextual filters Taxonomy vocabulary: Vocabulary ID - Providing default value "Current OG Group from context" but that doesnt seem to be working for me either. I feel that i am getting close.

I was supposed to go to a family dinner tonight but this has stopped me from doing so. If anyone reads this and can help then pleeeeeease help me. im almost in tears here. thanks

fadgadget’s picture

well i find it very strange that i dont seem to have a group catergories block and noo one else seems to have mentioned its possible exclusion from the D7 version of the module. This makes me think that i really just dont have a group catergories block.

Im sure if it was ommited from D7 someone would have mentioned it and there would be talk about how Views has replaced it. There is none of this so i can only presume there is some kind of bug with my set up.

Does anyone have a group catergories block?

thanks

fadgadget’s picture

im in bed in the huff now but for the record

Chaos tools
7.x-1.3

Organic groups
7.x-2.1

Organic groups vocabularies
7.x-1.1+0-dev

fadgadget’s picture

ok ive done a fresh instal on another domain and i can safetly say that there is no longer a group catergories block. It must all be Views driven now.

Im ok with Views and thought i could accomplish it ok but its really got me scratching my head i must admit. I see you can make an OG vocab view but even when i add every field thats available to me there isnt one that shows the term. Maybe im thinking too hard here. Maybe its just like regular taxonomy. That said OG Vocab views are putting me off a bit. Let me g try and make another view (and waste another night of my life)

fadgadget’s picture

Actually why doesnt the documentation mention any of this? Im not pointing fingers etc as i know folks are just doing us favours by releasing modules. I do think that the docs should mention something on how to set up a view or even just give us pointers that thats what we should be doing.

I still dont know if creating a View is the way to go. I suppose the module does what it says in giving us a vocab per group. How we care to display the vocab really is up to us and how we use Drupal.

bah :(

fadgadget’s picture

When i create an OG Vocab View i dont even have relationships to add. When i add a contextual filter i dont have anything to filter on via the group. I presume if i add the OG Context module it could help but ive tried that and i still fail. I cant even display a term never mind have it relating to a group. arrrrghhh im decending into madness. I dont know what life was like before i started with this. this is gonna tip me over the edge. Maybe i should give up on websites. 7 years f my life has been wasted with it and for what? heres plenty of other websites out there for folks. Maybe i could just have a simple blog. A simple blog with OG Vocab arrggghhh

fadgadget’s picture

I should draw your attention to this post that i made in the forum
http://drupal.org/node/1964940

I wasnt being annoyed with folks as mentioned as i do fully understand that folks only help when they can and for free etc. I was exasperated on this issue but it was meant to be tongue in cheek. I wanted you all to know how much i was failing. Granted i do get a little exasperated with Drupal at times as i am quite intense. I dont want anyone to think as Worldfallz did that i was demanding anything from anyone i was just being a little hopefull.

Worldfallz did mention this though relating to this issue-

That said however, I set up a test site and I took a look at the module and you're definitely not missing anything. The d7 version doesn't provide a block which leads me to believe it can be done with views. I spent some time trying to figure it out, but couldn't.

Ive got to confess that ive had to go a simpler route with things now but im sure that any help will help someone else in future. Heh i'll even write up a wiki page on it if its resolved as im a good guy that will help where he can. Its hard to help folks mind when you know nothing. Now if you was to ask me about this weekends Scottish football coupon then...

amitaibu’s picture

Component: Documentation » Code
Category: support » feature

I should draw your attention to this post that i made in the forum
http://drupal.org/node/1964940

Thanks!

What you wanted indeed still doesn't exist in 7.x, so setting as feature request (however not working on this in the coming future, as I don't need it myself, so patches are welcome...)

fadgadget’s picture

Thanks Amitaibu. I appeciate the reply. I thought i was going mad the last few days. I actually watched one of your presentations at drupalcon looking for clues on this the other night and vowed to get my hair cut like yours. I appreciate all that you offfer to us drupal users and im sorry if i did appear a bit 'huffy'.

roysegall’s picture

I'm adding the that worked for me. The views will be based on a OG vocabulary and you will need to add relation ships:
1. OG Vocabulary: OG vocabulary - this will display only terms from vocabulary that defined as OG vocabulary.
2. OG Vocabulary: OG vocabulary relation - this will display the terms from the group your watching her content.

If there are users that relate to more then on groups(i.e the admin site) you should turn on the OG context module. Displaying the terms beside your group content could be via the block system or with the module panels.

roysegall’s picture

Status: Active » Needs review
roysegall’s picture

I'm attaching a patch with an exported view block that will display the terms of the group.

fadgadget’s picture

A brilliant Roy. I was going down a differant road since but i think i do want OG Vocab more than i want my new road. Forgive my ignorance but is that patch creating a new file rather than a patch of an old one?

Ill give it a try and see....

fadgadget’s picture

a wait a sec it could be more than one file needed to be created.....

og_vocab_relation_views_handler_relationship.inc
og_vocab.views.inc
og_vocab.views_default.inc

and then a patch on og_vocab.info

I bet if i knew how to use GIT then it would do it all automatically for me. Ive tried a few times and failed with GIT. Ive just learnt how to patch. Ill go ahead and create these files but ive a feeling me removing all the + signs from the text is gonna screw me over. still thats my fault and problem due to my lack of knowledge.

amitaibu’s picture

> bet if i knew how to use GIT then it would do it all automatically for me.

Try http://drupal.org/project/drush_iq

fadgadget’s picture

Thanks Amitaibu i will look into that after this. I think ive done 'the hard part' so far.

k so i created the files mentioned above and i patched the og_vocab info and module files. I was very suprised that the module resinstalled with no errors. shocked in fact and thats nothign against you Roy more to do with me creating all this manually.

My only concern could be the mention of a og_vocab.test file in the info. I havent created one and i dont see one. If it goes wrong for me i will look at that more.

Created a og vocab fine and dandy as before. Now im a little stuck where to go but ill keep on. I dont see any views created but maybe i wasnt supposed to. Lets check blocks.....(i really need to delete some of these one day)..... nope. I will read up again and look at Views then.

fadgadget’s picture

StatusFileSize
new63.74 KB

mmmm creating the View has been harder than i had anticipated. A view of OG Vocab type gives me a 'There are no relationships available to add.' message when i try to add a relationship. await a sec Roy said that he had a exported view. Maybe i should be importing it from there durrr....

k so i definatly dont have a view called 'Group Terms' but i think thats because i didnt do it the git way.

Relationship handler og_vocab.vid is not available.
Relationship handler og_vocab.id is not available.
Unable to import view.

mmm why havent i got a relationship? It must be do with something i never done earlier poss. ah wait a sec i have my new files with .txt at the end. that has to be it.

nope still the same. The files are referanced correctly in the info file and they have the right paths etc.

Ill have to leave it for now as im up to my neck in it with other drupal things. My family dont even know what i look like. My members have all left. 7 years of drupal stumbling and i still love it lol

I dont know if this is acceptable but here is my module with the changes Roy offered me. Maybe someone can see whats glaringly wrong with it. Again thanks very much for the solution Roy.

amitaibu’s picture

@fadgadget, you are adding a lot of noise to the issue. If you want this issue to be committed, comments should be shorter and relevant...

fadgadget’s picture

Sorry Amitaibu its just how i work. I have to type things as i think or else i cant type. thats why im quite good at running forums and the like as i talk a lot. I will heed your words though and remember them for future referance. I was just having a chat. soz :(

Renee S’s picture

Thanks, @RoySegall, this worked for me.

fadgadget’s picture

StatusFileSize
new60.72 KB

I had actually gone down another route after my problems with this but now ive scrapped my new route and i was hoping to use og vocab again. Im on the dev version and all seems to work well enough thanks Roy. Well to the point of actually creating the views for myself.

I have managed to make a Term View with the attached settings which works as hoped on group and post nodes but im having difficulty making it appear on Group taxonomy page listings.

Ill go look at it more and probably mess this issue up more and i apologise for that in advance.

fadgadget’s picture

Looking at #15 Roy seems to have went down the route of creating an OG Vocab view (as apposed to a term view) From what i can gather from the text within his view is that he is adding relationships.

/* Relationship: OG Vocabulary: OG vocabulary */
+ $handler->display->display_options['relationships']['vid']['id'] = 'vid';
+ $handler->display->display_options['relationships']['vid']['table'] = 'og_vocab';
+ $handler->display->display_options['relationships']['vid']['field'] = 'vid';

I dont seem to have any relationships. So its back to a normal term view for me. I'd love is someone just said 'no need to worry anymore Ross here's a woring View export for you this will sort you out and free up the day for you' but ive a feeling thats not going to happen lol Lets try a term view again.....

New view with just the 'Content referencing Taxonomy term from og_vocabulary' relationship. Block on all pages and seems to work as hoped even on taxonomy pages. Actually no i tell a lie the block appears on ALL pages even ones outwith the group. Lets see some filters....

CONTEXTUAL FILTERS
Taxonomy vocabulary: Vocabulary ID

This seems to hide the block on all pages. Not the desired effect. Mmmmm what to do next? Ive gave up trying to get it to appear on the node as i achieved that. If i have to make a view for tax term pages and one for node pages then thats not a problem. So its back to

CONTEXTUAL FILTERS
Taxonomy vocabulary: Vocabulary ID (if no default value then taxonomy term ID from url)

Specify validation criteria: tax term

nah just doesnt want to work. I think im gonna have to admit defeat i think.

CONTEXTUAL FILTERS
(Content referencing Taxonomy term from og_vocabulary) Content: OG vocabulary

Looks as if it could have worked. Provide default value : current OG group doesnt work or taxonomy term fails for me also having nothing in the options shows all terms across all og vocabs in a block on the node and also on the term page (which is promising possibly) changing anything though makes the block dissapear

bah now on the nodes all i get is all terms for all og vocabs so my original thoughts on it working for nodes isnt true.

k lets look at my relationship. There is only one that it can be

Entity Reference: Referencing entity
A bridge to the Content entity that is referencing Taxonomy term via og_vocabulary

A clue in that is the 'a bridge to the Content entity' so lets add that again, require it. bah im getting either nothing at all or all og vocab terms. I think im going to have to give up.

$view->name = 'ogtermview';
$view->description = '';
$view->tag = 'default';
$view->base_table = 'taxonomy_term_data';
$view->human_name = 'ogtermview';
$view->core = 7;
$view->api_version = '3.0';
$view->disabled = FALSE; /* Edit this to true to make a default view disabled initially */

/* Display: Master */
$handler = $view->new_display('default', 'Master', 'default');
$handler->display->display_options['title'] = 'ogtermview';
$handler->display->display_options['use_more_always'] = FALSE;
$handler->display->display_options['access']['type'] = 'perm';
$handler->display->display_options['cache']['type'] = 'none';
$handler->display->display_options['query']['type'] = 'views_query';
$handler->display->display_options['exposed_form']['type'] = 'basic';
$handler->display->display_options['pager']['type'] = 'some';
$handler->display->display_options['pager']['options']['items_per_page'] = '5';
$handler->display->display_options['style_plugin'] = 'default';
$handler->display->display_options['row_plugin'] = 'fields';
/* Relationship: Entity Reference: Referencing entity */
$handler->display->display_options['relationships']['reverse_og_vocabulary_node']['id'] = 'reverse_og_vocabulary_node';
$handler->display->display_options['relationships']['reverse_og_vocabulary_node']['table'] = 'taxonomy_term_data';
$handler->display->display_options['relationships']['reverse_og_vocabulary_node']['field'] = 'reverse_og_vocabulary_node';
$handler->display->display_options['relationships']['reverse_og_vocabulary_node']['required'] = TRUE;
/* Field: Taxonomy term: Name */
$handler->display->display_options['fields']['name']['id'] = 'name';
$handler->display->display_options['fields']['name']['table'] = 'taxonomy_term_data';
$handler->display->display_options['fields']['name']['field'] = 'name';
$handler->display->display_options['fields']['name']['label'] = '';
$handler->display->display_options['fields']['name']['alter']['word_boundary'] = FALSE;
$handler->display->display_options['fields']['name']['alter']['ellipsis'] = FALSE;
$handler->display->display_options['fields']['name']['link_to_taxonomy'] = TRUE;
/* Contextual filter: Content: OG vocabulary (og_vocabulary) */
$handler->display->display_options['arguments']['og_vocabulary_target_id']['id'] = 'og_vocabulary_target_id';
$handler->display->display_options['arguments']['og_vocabulary_target_id']['table'] = 'field_data_og_vocabulary';
$handler->display->display_options['arguments']['og_vocabulary_target_id']['field'] = 'og_vocabulary_target_id';
$handler->display->display_options['arguments']['og_vocabulary_target_id']['relationship'] = 'reverse_og_vocabulary_node';
$handler->display->display_options['arguments']['og_vocabulary_target_id']['default_action'] = 'default';
$handler->display->display_options['arguments']['og_vocabulary_target_id']['default_argument_type'] = 'og_context';
$handler->display->display_options['arguments']['og_vocabulary_target_id']['summary']['number_of_records'] = '0';
$handler->display->display_options['arguments']['og_vocabulary_target_id']['summary']['format'] = 'default_summary';
$handler->display->display_options['arguments']['og_vocabulary_target_id']['summary_options']['items_per_page'] = '25';
$handler->display->display_options['arguments']['og_vocabulary_target_id']['specify_validation'] = TRUE;
$handler->display->display_options['arguments']['og_vocabulary_target_id']['validate']['type'] = 'og';

/* Display: Block */
$handler = $view->new_display('block', 'Block', 'block');

fadgadget’s picture

if i try to create a View of OG Vocab table i get no relationships of note as per attached.

Just incase ive confused anyone about my intentions i was just hoping to show an og vocab block of a groups terms in the group home page, on nodes and also on the tax term page for the og group terms only.

Ive a feeling that its only me that is unable to do so as im sure everyone else will be runnign about with a nice block on all these pages.

Again thanks in advance for any help anyone could offer me.

fadgadget’s picture

StatusFileSize
new47.95 KB

ooops here we go

fadgadget’s picture

nooooooooooooooooooo im tempted to use OG Vocab in a project im doing (same old site just done differant). Ive installed the new latest dev version and was hoping to see a few Views in there to help me. I also see a lot of interesting og vocab relationships. I cant bear to try try and work it all out again (not thati ever did manage to work it out)

Could anyone assist me please? I'd love a View with a page and a block all working great. Is that too much to ask? Suppose :( Any help would be appreciated as i really aint getting any younger and im near finished this project thats taken me 7 years. Thanks in advance.

Renee S’s picture

Hi fadgadget, I appreciate that you'd really like this functionality, but continuing to post the same request for help multiple times is not going to get the result you desire. This is open source -- everybody here is a volunteer and has as many commitments, and active projects, as you do. If you can't solve the problem yourself, I suggest hiring a developer, or offering a bounty, to solve your problem.

fadgadget’s picture

Sorry Renee i was just hoping to get what everyone else seems to have. Im not tooooo drupal unaware and can solve most things eventually but OG vocab and me have just never got on. I was just lookign for a bit of help thats all. You will note that my last reuest for help was 2 months go and since then the OG Vocab module has had quite a bit of updates. I dont think me asking how to achieve basic functionality is too much of a request. If someone in the know could tell me then it will help me and others and we can close this issue and move on.

fadgadget’s picture

Status: Needs review » Closed (won't fix)

To take this further and to further not endear myself to the rest of the community i suppose it all boils down to a couple of things. The docs shows us how to set up OG Vocab field in the content type. Fine great easy. Nothing is mentioned about what you have to do next to actually use the module in a basic way. As far as i can see then that there is no way to actually use the module even in a basic way.

People might know how but are just not for sharing or b) you cannot do as i had hoped with views.

I live on £50pw so obviously hiring a developer or even offering a bounty is beyond my means.

Im in a huff now so ill just close the issue and ill leave your issue queue in peace.

Renee S’s picture

Status: Closed (won't fix) » Needs review

Re-opening, as RoySegall's patch worked for me and was at "needs review."

skyredwang’s picture

Status: Needs review » Reviewed & tested by the community

#15 patch is good, please commit

kari.kaariainen’s picture

Status: Reviewed & tested by the community » Needs work

#15 patch, the view works great, but the terms don't need labels and they should be links linking to the term page. Also cache needs clearing after installing the module, and finally the block needs to be configured to only show on the group page.

heyyo’s picture

I tried a different approach because the patch in #15 was really slow almost 1s to retrieve only 2 terms.

I'm listing all vocabs from given Group ID(s), so my View is directly reading the table OG_vocab_relation.

Contextual filters
OG Vocabulary per Group: Group ID (with default value retrieved from OG_context)

Relationships

  • Then I'm using a relationship from Vocab ID to Vocab ID on table Taxonomy_term_data to access Terms.
    OG Vocabulary per Group: OG vocabulary Term
  • And from this Term I add an optional relation ship to nodes with those terms
    (Term) Entity Reference: Referencing entity
    To be able to count those nodes with aggregation

And optionally I also used Tagadelic with View_tagadelic to have different CSS class per utilization of terms.

And to retrieve only terms with Nodes using them I had a filter on count(NID)

To access OG_Vocab_realtion table and to have Contextual filter and relation to term, I had to modify og_vocab.views.inc

/**
 * Implements hook_views_data().
 */
function og_vocab_views_data() {
  $data['og_vocab_relation']['table']['group']  = t('OG Vocabulary per Group');

  $data['og_vocab_relation']['table']['base'] = array(
    'title' => t('OG vocabulary'),
    'help' => t('OG vocabulary relation base table.'),
  );

  $data['og_vocab_relation']['vid'] = array(
    'title' => t('OG Vocabulary'),
    'help' => t('Term from a OG vocabulary.'),
    'relationship' => array(
      'handler' => 'views_handler_relationship',
      'base' => 'taxonomy_term_data',
      'base field' => 'vid',
      'title' => t('OG vocabulary Term'),
      'label' => t('Vocabulary'),
    ),
  );
  $data['og_vocab_relation']['gid'] = array(
    'title' => t('Group ID'),
    'help' => t('Filter per Group ID.'),
    'argument' => array(
      'handler' => 'views_handler_argument_string',
    ),
  );

  return $data;
}

My Views:

$view = new view();
$view->name = 'terms';
$view->description = '';
$view->tag = '';
$view->base_table = 'og_vocab_relation';
$view->human_name = 'Terms per OG Group';
$view->core = 7;
$view->api_version = '3.0';
$view->disabled = FALSE; /* Edit this to true to make a default view disabled initially */

/* Display: Master */
$handler = $view->new_display('default', 'Master', 'default');
$handler->display->display_options['use_more_always'] = FALSE;
$handler->display->display_options['group_by'] = TRUE;
$handler->display->display_options['access']['type'] = 'none';
$handler->display->display_options['cache']['type'] = 'none';
$handler->display->display_options['query']['type'] = 'views_query';
$handler->display->display_options['exposed_form']['type'] = 'basic';
$handler->display->display_options['pager']['type'] = 'full';
$handler->display->display_options['style_plugin'] = 'tagadelic';
$handler->display->display_options['style_options']['default_row_class'] = FALSE;
$handler->display->display_options['style_options']['row_class_special'] = FALSE;
$handler->display->display_options['style_options']['count_field'] = 'name';
$handler->display->display_options['row_plugin'] = 'fields';
$handler->display->display_options['row_options']['inline'] = array(
  'name' => 'name',
);
/* Relationship: OG Vocabulary per Group: OG vocabulary Term */
$handler->display->display_options['relationships']['vid']['id'] = 'vid';
$handler->display->display_options['relationships']['vid']['table'] = 'og_vocab_relation';
$handler->display->display_options['relationships']['vid']['field'] = 'vid';
$handler->display->display_options['relationships']['vid']['label'] = 'Term';
/* Relationship: Entity Reference: Referencing entity */
$handler->display->display_options['relationships']['reverse_og_vocabulary_node']['id'] = 'reverse_og_vocabulary_node';
$handler->display->display_options['relationships']['reverse_og_vocabulary_node']['table'] = 'taxonomy_term_data';
$handler->display->display_options['relationships']['reverse_og_vocabulary_node']['field'] = 'reverse_og_vocabulary_node';
$handler->display->display_options['relationships']['reverse_og_vocabulary_node']['relationship'] = 'vid';
/* Field: Taxonomy term: Name */
$handler->display->display_options['fields']['name']['id'] = 'name';
$handler->display->display_options['fields']['name']['table'] = 'taxonomy_term_data';
$handler->display->display_options['fields']['name']['field'] = 'name';
$handler->display->display_options['fields']['name']['relationship'] = 'vid';
$handler->display->display_options['fields']['name']['label'] = '';
$handler->display->display_options['fields']['name']['element_label_colon'] = FALSE;
$handler->display->display_options['fields']['name']['link_to_taxonomy'] = TRUE;
/* Field: COUNT(Content: Nid) */
$handler->display->display_options['fields']['nid']['id'] = 'nid';
$handler->display->display_options['fields']['nid']['table'] = 'node';
$handler->display->display_options['fields']['nid']['field'] = 'nid';
$handler->display->display_options['fields']['nid']['relationship'] = 'reverse_og_vocabulary_node';
$handler->display->display_options['fields']['nid']['group_type'] = 'count';
$handler->display->display_options['fields']['nid']['label'] = '';
$handler->display->display_options['fields']['nid']['exclude'] = TRUE;
$handler->display->display_options['fields']['nid']['element_label_colon'] = FALSE;
/* Contextual filter: OG Vocabulary per Group: Group ID */
$handler->display->display_options['arguments']['gid']['id'] = 'gid';
$handler->display->display_options['arguments']['gid']['table'] = 'og_vocab_relation';
$handler->display->display_options['arguments']['gid']['field'] = 'gid';
$handler->display->display_options['arguments']['gid']['default_action'] = 'default';
$handler->display->display_options['arguments']['gid']['default_argument_type'] = 'og_context';
$handler->display->display_options['arguments']['gid']['summary']['number_of_records'] = '0';
$handler->display->display_options['arguments']['gid']['summary']['format'] = 'default_summary';
$handler->display->display_options['arguments']['gid']['summary_options']['items_per_page'] = '25';
$handler->display->display_options['arguments']['gid']['limit'] = '0';
/* Filter criterion: COUNT(Content: Nid) */
$handler->display->display_options['filters']['nid']['id'] = 'nid';
$handler->display->display_options['filters']['nid']['table'] = 'node';
$handler->display->display_options['filters']['nid']['field'] = 'nid';
$handler->display->display_options['filters']['nid']['relationship'] = 'reverse_og_vocabulary_node';
$handler->display->display_options['filters']['nid']['group_type'] = 'count';
$handler->display->display_options['filters']['nid']['operator'] = '>';
$handler->display->display_options['filters']['nid']['value']['value'] = '0';

/* Display: Content pane */
$handler = $view->new_display('panel_pane', 'Content pane', 'panel_pane_1');
$handler->display->display_options['pane_category']['name'] = '';
$handler->display->display_options['pane_category']['weight'] = '0';
$translatables['terms'] = array(
  t('Master'),
  t('more'),
  t('Apply'),
  t('Reset'),
  t('Sort by'),
  t('Asc'),
  t('Desc'),
  t('Items per page'),
  t('- All -'),
  t('Offset'),
  t('« first'),
  t('‹ previous'),
  t('next ›'),
  t('last »'),
  t('Term'),
  t('Content referencing Taxonomy term from og_vocabulary'),
  t('All'),
  t('Content pane'),
);

Comments are welcome

fadgadget’s picture

Issue summary: View changes

i finally learnt how to use drush. Managed to apply the patch in \15 fine. Netbeans told e thre where serveral errors in it and now when i try and enable the patched dev module i get a white screen of death. I havent beeen taking my depresants so i give up eary this time.

I onnna have a play about with the reg version and see if it stiill just doesnt make sense to me :(

fadgadget’s picture

k i just used the regular 7.12 version and things installed smoothly etc. I think i now back to where his this thread started BUT with a years more drupal knowledge about me. i read up the thread and try to achieve-

  1. Show the groups tax terms in the sidebar on the og node
  2. Show the groups tax terms whilst viewing group contnent/li>
  3. and for my final trick i will also attempt to show the group's tax term whilst viewing the groups tax term page

:hope

fadgadget’s picture

I suppose i would need to think 'how would i show tax terms along side each of the above outwith the OG Vocab module' and see whats happens from there.

  1. Show the groups tax terms in the sidebar on the og node -I need a Group Terms view Block No a terms view block. realting to the term (entity) s in some kind of conceptul filter r relationship. .
  2. Show the groups tax terms in the sidebar on the og node - same view as before but differant content type in view and the probable rrealtion ship required (awww)
  3. Show the groups tax terms whilst viewing Groups Vocab term page - errrr i dunnnooo ill li think of that later.-
  4. and for my final trick i will also attempt to show the group's tax term whilst viewing the groups tax term page - sort later
fadgadget’s picture

in 'add relationship' suprised

OG vocab: Vote results
Aggregate results of votes cast on OG vocab.
OG vocab: Votes
Votes cast by users on OG vocab.

Og Vocab cant have turned itself into a rating mdule to compete with Fivestar is it? No rthis must mean domething else. Im in an OG Vocab style view but ive a feeling a normal term view ight be the one that works.

Heh lets just unleash this OG Voc Views block on the site snd see if anything happens There would be no point to all this thread though if it did happen and nothing is gonna happen is it? ....... no relations no contexual filters , default fields lets do it babby..........mmmm not bad we got something......

vocabtest
Og vocab ID: 1

right lets see Contextual Filters....mmmmmm juicey....errrrrr....ummmm errrr Bundle or Entity? 'Og vocab ID' could be the boy then we can pull the terms from the Og vocab ID possibly....

'Current OG Group from context' filter. leave everything else as it is.........the bock has now gone. That might not be all bad mind. (errr what you talking about reg of course its bad) errrrrrr where there is a will.

on Group Content there is a nice perfect field there to play with. By using that 'lets put the field in a block module' lets see how this loooks.....ah hah its the field that i made via the very initial demo of this. 'og_group_voscab'. this is our lady.

ah wait a sec thats just displaying the term on the node in the sidebar for me now. Not th desired behaviour but 'no bad' if its the best i can get

Trying to add a relationship again to the OG Vocab view block and it really does look like something to do with a voting system than a tagging module.

Lets go try a tax term view instead.....

fadgadget’s picture

right got a default term view on all pages of my site. Its showing all terms which isnt the hard bit is it? lets get some relating or filtering going on whilst missing putting the rubbish out for the bin men for the 3rd week runing. so the Taxonomy vocabulary: Vocabulary ID (taxterm id from url) could be a likely way to go....load filter from term page, leave everything else and.....

welll stilll just showing all the terms on every page. Filtering me thinks.

Relationships
Entity Reference: Referencing entity

just shows me both of my groups tax terms in a list together Its even starting to 'double them up' drupal views style.

Lets make this arse required (soz) ....... nope stilll shows all my terms but interestlngy enough only terms in vocabs ade by OG Vocab. Lets read up some more. The threads too hard to read with al the shit on it lol (wasnt me your honour).....

Right this shows promise for a taxonomy page -

CONTEXTUAL FILTERS
Taxonomy term: Term ID

just the same term. no siblings or parents etc. infact its just all the terms from OG Vob that i need. Ill rack on but any pointers appreciated.

thanks

fadgadget’s picture

i just about to give up for the day but i think i getting on the right track.

Entity Reference: Referencing entity
A bridge to the Content entity that is referencing Taxonomy term via og_group_voscab

lets me have a new Contextual Filter-

Content: OG vocabulary (og_group_voscab)
Appears in: node:article.

but makes the block disaappear on all pages. Lets try this contextual filters instead-

OG membership: Group ID
Og membership "gid" property.

OMG this seems to have worked/ well for displaying the OG Vocb list on Group hoe and on nodes within.

Contextual filters
(Content referencing Taxonomy term from og_group_voscab) OG membership: Group ID
open

Add

Relationships
Entity Reference: Referencing entity

While im here ill add some other posssibilities for getting htem on the ter page themeselves. Still no show.

Taxonomy vocabulary: Machine name
Filter the results of "Taxonomy: Term" to a particular vocabulary.

Taxonomy term: Term ID
The tid of a taxonomy term.

Taxonomy vocabulary: Vocabulary ID
The taxonomy vocabulary ID

fadgadget’s picture

mmmmmmm i cant get rid of 'doubles' appearing in the view eveen With Distinct and Super distinct tuned on. thats not gonna help. phew i was editting the wrong view. Right thats the views for the Group Node Home Page and Group Content Pages done (i think) illl attach it as ive copied a block to start and get the same on taxonomy pages.........

actualy here's the view here
http://jsfiddle.net/BhW84/

I keep messing it up by creating another block. Maybe taxonomy_term_data view is not what i eed here....

fadgadget’s picture

bah this is nearly a year ive been at this and i still cant achieve what i was after. ive been running around in circles. Ive since got rid of panels and i even spent a few weeks looking at Wordpress multi user to achieve it but......it's not drupal so i gave up

ach well here we go again. My family have disowned me and my friends no longer call me. Lets read up and try again :(

amitaibu’s picture

@fadgadget,
Dude is that feature really that important to you?! :)

fadgadget’s picture

It is Amitaibu. I just want a blog on my website (and other blogs) each with their own vocabs. Ive tried it without og vocab and it just doesnt do the job. I just want to make my blog have its terms on sidebar and then allow navigation via them terms within the og vocab content. It was all so easyway back when the og vocab block existed but now having to use Og Vocab views and relationships it all seems to to escape my knowledge. 8 or 9 years ive been using Drupal (funny enough the same time as since i 'went with a woman') make of that what you will :(

I tred wordpress multiuser there for a few days but 'it just wasnt drupal' so i gave up on it. Im actually tempted just to make my website a single user blog and let me OWN ALL THE TERMS but that was never the plan. I want a busy website with people doing other things whilst i hide in the corner with my own wee blog.

Im having a rare day off all things drupal today as my life is a mess and i need to give it some attention. I WILL be back tomorrow though and im gonna finally get this working. everything seems to be working ok bar the displaying of tags on the group homepage, the group tax page and the group article page. Actually that means ive got nothing really working at all have i?

How do other people navigate their og group using og vocab? Feell free to add any Views that you maybe using.

thanks

fadgadget’s picture

I hope no one minds but ive started a page here HERE to show how to create a block view that will allow people to navigate their og group via og taxonomy. I think i half sorted it out above.

If ive done 'wrong then feel free to delete.

niallmurphy-ie’s picture

Patches 13 / 15 don't seem to be creating a view or block for me.. The files have been created but nothing visible happening.

janlindso’s picture

Came here for the same reason as @fadgadget, and what a mess this thread is. So much information, so little solution. Anyway, I'm really glad you issued this problem, and I'm fully agree with you on this. I really think that this is a flaw in this module, as a block view is necessary for full functionality. I tried to create a forum thread for this problem as well, but like you, without any luck. https://www.drupal.org/node/2451089

MrSchoolcraft’s picture

I've been fighting with this same setup and having some issues.
However I've found a good happy solution.
I applied the patch in #15 to get the hooks into views.
However, that view definitely was not using contextual filters.
Upon further reading, the solution in #35 worked perfectly. It is just a slight modification and a better fleshed out view (although I had to remove the panels and tagadelic references) and now my contextual Terms per Group (based on node context, or User member context) works perfectly. If anyone has any questions or would like to discuss further, please contact me. I may try to roll #35 into an updated patch based on #15 to submit.

scotwith1t’s picture

+1 for the combination of #15 and the changes in #35 to make the view a view of terms and not vocabularies. this got us started, much obliged! :)

Yorgg’s picture

Issue summary: View changes
StatusFileSize
new5.7 KB

This one is based on #15 and heyyo's modification og_vocab.views.inc.
This is my first patch, I will run the tests.