Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.At the moment, the terms added by OG Vocab at the content creation are not saved as normal terms handled by Core Taxonomy. Therefore, the core taxonomy (views) page can't display the tagged content. e.g. /taxonomy/term/* pages or Content: All taxonomy terms (All taxonomy terms) Views Field.
Unless what I saw above is a bug. The question is Why not reuse the core taxonomy for data CRUD?
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | Screenshot 1:14:13 10:17 AM.png | 72.17 KB | amitaibu |
Comments
Comment #1
amitaibu> At the moment, the terms added by OG Vocab at the content creation are not saved as normal terms handled by Core Taxonomy.
Yes they are, you just need to enable "Taxonomy index" on the field settings (make sure you work with an updated Entity-reference module).
btw, there's no "critical" support request ;)
Comment #2
skyredwangI didn't see the setting there, however, my setting has been enabled. So, I guess this become a bug report.
I am using Entity reference 7.x-1.0, OG Vocabulary 7.x-1.x-dev (2012-Dec-17) and Chaos tool suite (ctools) 7.x-1.2 with patch #1707810: Allow mockup field settings in ctools_field_invoke_field()
You mention that I need an aupdated Entity-reference module. Which version is that?
Comment #3
skyredwangUpgraded to OG Vocabulary 7.x-1.x-dev (2013-Jan-09), still don't see the taxonomy data available via Core Taxonomy
Comment #4
skyredwangUpgraded to Entity reference 7.x-1.0+3-dev (2013-Jan-01), run cron, clear cache, but still don't see the taxonomy data available via Core Taxonomy
Change this issue to a critical bug.
Comment #5
amitaibu@skyredwang , please try on a clean installation -- I've re-checked and it's working.
Comment #6
skyredwangUpgraded Entity reference to 7.x-1.0+4-dev (2013-Feb-01). Still don't see the tagged content under /taxonomy/term/*
Comment #7
amitaibu> please try on a clean installation
Is it on a clean installation?
Comment #8
skyredwangAfter a complete uninstall and manual clean up, then re-install, it finally worked. I guess this is no upgrade path.
Comment #10
heyyo CreditAttribution: heyyo commentedI also have the problem on an existing website. I have no important content on it, but could not recreate this website from scratch.
Could you explain me what you did @skyredwang.
I tried to remove all og_vocab fields and reinstalling og_vocab module, but still I have no data inside taxonomy_index table when a create new node with tags.
Comment #11
skyredwangI uninstalled this module first, then deleted all the related tables generated by this module (The uninstalling process should have done this instead).
Comment #12
heyyo CreditAttribution: heyyo commentedYes thanks, I finally succeeded also. I also had to remove og_vocabs variables and entry in system, and also entry in field_config and field_config_instance
Comment #14
scotwith1tI'm gonna have to chime in here and reopen as I'm having the same issue as @heyyo. After disabling, uninstalling and checking to make sure all og_vocab-related stuff was gone from the DB, reinstalling did not make the terms start being added to the taxonomy_index table. Can you explain how the module attempts to make that happen? What file, what function is it supposed to happen so i can try and debug?
Comment #15
scotwith1tNot entirely sure, but i think my issue lied with Features. All of our content types are being packaged up with features, which have the og_vocab field on them. Something about this setup makes that taxonomy-index handler not get registered with ctools. If I remove all og_vocabulary fields, disable, uninstall the module, reinstall and re-create the fields (by checking the checkbox for the desired content types on the vocab edit page), it starts working. So, best I can tell, there may be an issue with this module's og_vocabulary field being packaged up with features. On a clean install with no features in play, i couldn't get it to break at all.
Comment #16
scotwith1tSo I'm more and more convinced ours is a problem with features compatibility. Basically, when you export an instance of og_vocabulary, there is NO part of the export code that indicates there is an taxonomy_index behavior on the field instance. Any tips on how to approach this, I'd be happy to try and get this worked out, but pretty sure that this is a shortcoming of the module but not entirely certain...thanks! I can create a new issue if you think that's needed too.