@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.
I'm really hoping to make this simple change on new content types: https://github.com/backdrop/backdrop-issues/issues/7080
Let's disable the "Display author and date information" by...
For our DEV meeting:
an older bug needs (and could have) a fix.
Issue #5729 - Views: Search Filter: On Empty Input "Show None" option Shows All
There are 2 pull requests, but one...
Ruby Text can be a bit of a hassle to edit...
Yes, I can imagine that. No idea, how an editor dialog (or whatever) for easier editing of those should look like - in terms of...
"why are these tags only relevant for admins?" I'm allowing the editor as well. That being said, Ruby Text can be a bit of a hassle to edit... easy to accidentally delete a tag or part of a...
Out of curiosity: why are these tags only relevant for admins?
Don't "regular" editors on that site also need them under circumstances?
Yes, the editors play nicely, no problem to...
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