Closed (fixed)
Project:
Revisioning
Version:
7.x-1.0
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Reporter:
Created:
1 Jul 2011 at 18:29 UTC
Updated:
20 Jul 2011 at 11:21 UTC
After upgrading to 1.0, new nodes with revisions will not have its taxonomy terms added to the taxonomy_index table. They will not show up in views filtered by term because of this.
Perhaps related to #962664: Taxonomy Index for unpublished entities?
This project adresses that issue: http://drupal.org/project/taxonomy_entity_index
(I have not tried it yet)
It worked before so what happened?
Comments
Comment #1
Andreas Radloff commentedI might add that this applies to revisions that are "current, published", and that instead of all tags I get the same tag repeated three times in the revision list at node/x/revisions/list
Comment #2
rdeboerHi Andreas,
Thanks for reporting this issue.
I can reproduce it on D7.2 and D7.4. Happens to a View with Taxonomy terms, but not for the "free-style" tags.
From #1:
"...instead of all tags I get the same tag repeated three times in the revision list at node/x/revisions/list..."
Yep -- used to be the case. This has already been fixed and checked into the master branch. If you are familiar with Git you can check it out. If not, you'll have to wait until I release 7.x-1.1. For some reason this project refuses to generate dev-releases on its project page -- I have logged an issue, but haven't had a reply.
As far as the remainder of your report, I'll look into it. Thanks for the link to this new project too. Will investigate.
Rik
Comment #3
esculcar commentedsubscribing
Comment #4
rdeboerFixed and committed to the repository, Git master branch. Will be available in next release.
BTW, this fix also works around a bug in D7's core Taxonomy module: #962664: Taxonomy Index for unpublished entities.
Bonus! Two fixes for the price of one!
Comment #5
Andreas Radloff commentedExcellent, thanks for solving it so fast! Seems to be working for me.
Great module, keep it up! :)
Comment #6
rdeboer@Andreas
Thanks for your support and to-the-point feedback that made it easier to fix the issue!