Hi!
Thank you for your module. It is really very useful, especially for delivery methods customization.
The only thing that is not clear: why a warning message is displayed when conditions with vocabularies that aren't in the commerce product used?
I use taxonomy vocabularies (product type and subtype) only with the product view (content types/product display) and do not use any taxonomy in the product variations types...
I think, it would be great that module could be used not only with product variations vocabularies, but also with product view vocabularies.
I tested version 7.x-1.x-dev and everything works as expected (problems described here https://drupal.org/node/2155995 does not appear and rule works properly), but a warning message spoils my expectations.
Thank you!
Comments
Comment #1
pun_pun commentedComment #2
redsd commentedHi Pun pun,
I'll look into it. I don't know if commerce gives me enough room to also check the node that is linked to the commerce product.
If I indeed can load the node I can check the nodes taxonomy aswell if there is a match with the condition(s) you created.
I like the idea and will look into it.
The error is to warn users, because they added a vocab that is not used in commerce product, the outcome of the shipping rule(s) can be different from what they expect it to be.
Comment #3
pun_pun commentedRedsd,
thank you for your quick answer.
I asked for this functionality because I use different types of products but do not use different types of certain product. And this approach supposes to use taxonomy vocabularies with the product view.
By the way, I've got the warning message but rule seems to triggered properly.
Thanks for the help!
Comment #4
redsd commentedHi Pun pun,
I updated the developer version, it now supports node taxonomy aswell.
Let me know how it works!
Kind regards,
Eric
Comment #5
pun_pun commentedEric,
It works as I wish. :) There was no warning message.
Thank you very much for this feature.
Ilya
Comment #6
redsd commentedGood to hear, I checked the version to make sure everything works as it should.
I released the new version as 2.0 since it could upgrade from 1.x.
Comment #7
redsd commented