@rogelio - Thanks for reporting this. When you are in doubt, this is always a good place to ask your question or raise your concern.
I don't have a technical response for you, but I can make a process suggestion.
1) If you have the time and/or skills to provide more information about what is or is not happening, that would be really helpful and might help triage which module is causing the problem. Provides step by step guide to reproduce the problem is HUGELY helpful.
2) If not sure which module is causing the problem, I think it's appropriate to take your best guess and pick one or simply go ahead and open an issue in both issue queues. Be clear in your description of the issue that it involves two modules and you are not clear which is causing the problem (maybe both). If opening issues in both queues, I would add a link to the respective issue in the other queue.
If either module maintainer can verify the the problem is not with their module, they can easily close the issue and no harm is done.
As usual, you are much more likely to get results/help if you are able to provide the clearest and easiest possible step by step guide to reproduce the problem.
In a blog post titled "Github Tips and Tricks for Contrib Maintainers", I'd like to see some of the following topics:
When is the README sufficient for documentation? When should...
Posted1 day 4 hours ago by Olaf Grabienski (Olafski) on:
Have you tried uc_cart_add_item()? You need to provide the nid of the product. Then you can use backdrop_goto('cart/checkout'); to send the user to the checkout screen. uc_cart_add_item...
Posted1 week 5 days ago by Alejandro Cremaschi (argiepiano) on:
No problem, let's see how it evolves.
I'd be happy to provide a suggested version if i could.
I will keep that in mind and try learn this hook chain hopefully very soon. I will...
Posted2 weeks 9 hours ago by RS Snyder (theflightrs) on:
I could request hashing support, but that's the lazy way
🤣
I would appreciate it if you as an active maintainer would 'officially' add a hashing support...
Comments
@rogelio - Thanks for reporting this. When you are in doubt, this is always a good place to ask your question or raise your concern.
I don't have a technical response for you, but I can make a process suggestion.
1) If you have the time and/or skills to provide more information about what is or is not happening, that would be really helpful and might help triage which module is causing the problem. Provides step by step guide to reproduce the problem is HUGELY helpful.
2) If not sure which module is causing the problem, I think it's appropriate to take your best guess and pick one or simply go ahead and open an issue in both issue queues. Be clear in your description of the issue that it involves two modules and you are not clear which is causing the problem (maybe both). If opening issues in both queues, I would add a link to the respective issue in the other queue.
If either module maintainer can verify the the problem is not with their module, they can easily close the issue and no harm is done.
As usual, you are much more likely to get results/help if you are able to provide the clearest and easiest possible step by step guide to reproduce the problem.
https://github.com/backdrop-contrib/rules/issues
https://github.com/backdrop-contrib/userpoints/issues