@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.
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again.
Then...
Posted5 days 17 hours ago by Francis Greaves (themetman) on:
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Posted1 week 4 days ago by Francis Greaves (themetman) on:
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