@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.
Thanks. It still took a lot of trial and error for all the settings within the settings, but I eventually got it to display based on these instructions.
Another easy way to do this is to use the module Corresponding Entity References (cer). You would need to add an entity reference field in the authors content type pointing at the book, then set...
Posted5 hours 14 min ago by Alejandro Cremaschi (argiepiano) on:
I also found the contextual filter area in the view for this block. But that’s where it stops.
I'll try my best - views based on entity reference can be a challenge....
Create a block with a contextual filter on the "author" node ID, and based on that relationship get the book node IDs.
Thanks! I think I get the general idea.
I set up...
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