I use Taxonomy Default to assign some default taxonomy when create a new node. However, when I tried to clone a node which should give me everything exactly to the original node. With Taxonomy default enabled, taxonomy from the original node is gone in clone node. Should this be the problem of Taxonomy default or Node clone?

Thank you,

Comments

abx’s picture

Title: Taxonomy Default apply when using with Node Clone Module » Taxonomy Default applied when using with Node Clone Module
bradweikel’s picture

Status: Active » Postponed (maintainer needs more info)

I'm on vacation and can't look at this right away, but you could help me out by following these steps and letting me know what happens.
1) Create a node that uses defaults terms
2) Disable the taxonomy defaults module
3) Clone that node

If the terms are correctly copied to the clone, then I'll know for sure that the problem is with taxonomy defaults.

abx’s picture

Thank you for your answer. The steps you told me is what I already did before I post :) Disable Taxonomy default module allow me to clone node correctly.

When leave blank setting in Taxonomy default, it can mean to set it blank or disable taxonomy default on that vocabulary. Either set it blank or disable it result the same thing for a new node. But with clone node, it's actually set it blank which is not intended behavior ?

Enjoy your vacation :)

Marvin Daugherty’s picture

Subscribe

Marvin Daugherty’s picture

I did a hack on my taxonomy-defaults.module at line 79.
I know this is bad, but it was quick.

78      // Ignore this vocabulary if it is the core forum vocabulary
79      if ($vid == $forum_vid) {
80        continue;
81      } 

becomes

78      // Ignore this vocabulary if it is the core forum vocabulary or add other ignored vocabularies
79      if ($vid == $forum_vid || $vid == 1) {
80        continue;
81      }

Seems to work and will repost if I find a problem.
Hope this helps someone.

aruuska’s picture

Here is patch if someone still has needs for it.