I've been following that this module was just updated to 4.7, that is great. I have a feature request which I think might work ok as part of this module, as opposed to another module. Right now, when you publish a node via admin/node, or publish multiple nodes, they're not assigned taxonomy. I understand this is different from what taxonomy_defaults does right now, but I think it might be a good addition? So, you can setup the defaults on admin/taxonomy/taxonomy_defaults, but then, allow taxonomy to be set when publishing nodes for the first time via admin/node.

Does this make sense to add to this module, or do separately?

cheers,
Ian

Comments

heine’s picture

heine commented

The current implementation sets taxonomy on initial node submission. How exactly do you envision the addition of taxonomy upon publishing? Would the admin need to select anything? In other words should a taxonomy select box be shown? How to deal with multiple node types?

Ian Ward’s picture

Ian Ward commented

Hi Heine,
Thanks for writing back. I just looked at node.module and at function node_operations which handles the queries on chaning the status of nodes on admin/node and all it does is run simple mysql UPDATE statements. I thought it ran something where more control was possible.

Based on this, what you are saying about adding an additional column to this page seems like the only way? It would have to check what node type each node is, which it does already, and then only display perhaps a dropdown of appropriate term trees? Maybe the possibility to shut this off per node type in the settings would help eliminate having the dropdown select list appearing next to node types where you simply don't need it.

Does this make sense?

cheers,
Ian

heine’s picture

heine commented
Status: Active » Closed (won't fix)

I've been thinking about this for a while, and while I agree that this is interesting functionality, I don't think this should be in taxonomy_defaults, but rather in a seperate module.