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.

CommentFileSizeAuthor
#6 taxonomy_defaults_patch_1005944.txt1.78 KBAlice Heaton

Comments

julius95’s picture

julius95 commented

same happens on my site.

Best wishes
Julius

guictx’s picture

guictx commented

I'm having the same problem on 6.20 install without any extra taxonomy modules besides core.

bradweikel’s picture

bradweikel commented

This 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

if (isset($form['type']) && $form['type']['#value'] .'_node_form' == $form_id) {

with

if (isset($form['type']) && $form['type']['#value'] .'_node_form' == $form_id && !isset($form_state['node_preview'])) {

(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.

flatline2010’s picture

flatline2010 commented

It seems to work ...

lucuhb’s picture

lucuhb commented

I 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.

Alice Heaton’s picture

Alice Heaton commented
Status: Active » Needs review
StatusFileSize
new taxonomy_defaults_patch_1005944.txt1.78 KB

Hello,

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.