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.
When activating the taxonomy defaults module (at least in conjunction with taxonomy access control, and without any configuration of the modules), I loose my taxonomy choices upon preview of the blog entry (taxonomy menu term are reset).
When I deactivate the defaults module, things work properly.
Comment | File | Size | Author |
---|---|---|---|
#6 | taxonomy_defaults_patch_1005944.txt | 1.78 KB | Alice Heaton |
Comments
Comment #1
julius95 CreditAttribution: julius95 commentedsame happens on my site.
Best wishes
Julius
Comment #2
guictx CreditAttribution: guictx commentedI'm having the same problem on 6.20 install without any extra taxonomy modules besides core.
Comment #3
bradweikel CreditAttribution: bradweikel commentedThis could be related related to the fix submitted for #647686: Hidden vocabulary values displayed on preview. I'll look into it soon, but in the meantime you might try replacing
with
(The line is actually still there, just commented out, so you could just reverse the comment).
This will reintroduce the #647686: Hidden vocabulary values displayed on preview bug, so only do it if you aren't using hidden taxonomies. Let me know if it works, though, so I know exactly where to start when I have time to work on this.
Comment #4
flatline2010 CreditAttribution: flatline2010 commentedIt seems to work ...
Comment #5
lucuhb CreditAttribution: lucuhb commentedI have the same problem here but the solution doesn't work for me : If a default item is defined for a taxonomy but a user selects another item for this taxonomy, the default item is selected instead of the user's choice on the node preview.
Comment #6
Alice Heaton CreditAttribution: Alice Heaton commentedHello,
Here is a patch that fixes the issue originally reported by @flatline2010, and does not re-introduct the bug from #647686
I don't know about the issue reported by @lucuhb - I cannot reproduce it in my test case. If it's still an issue I would recomend to create a separate ticket for it.
Let me know if it works for you.