Postponed (maintainer needs more info)
Project:
Taxonomy Defaults
Version:
6.x-2.1
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
11 Mar 2011 at 10:27 UTC
Updated:
30 Apr 2013 at 11:35 UTC
Jump to comment: Most recent file
Comments
Comment #1
abx commentedComment #2
bradweikel commentedI'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.
Comment #3
abx commentedThank 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 :)
Comment #4
Marvin Daugherty commentedSubscribe
Comment #5
Marvin Daugherty commentedI did a hack on my taxonomy-defaults.module at line 79.
I know this is bad, but it was quick.
becomes
Seems to work and will repost if I find a problem.
Hope this helps someone.
Comment #6
aruuska commentedHere is patch if someone still has needs for it.