@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 seemed to need to put the css in two locations - my local.css file in my sub-theme and in the ckeditor5.css in the ckeditor5 module's css sub-directory.
The latter will be...
took me a while to work out where the relevant css was put, but once I had tthis in play the solution works. I seemed to need to put the css in two locations - my local.css file in my sub-theme...
Thank you argiepiano, it works exactly as you said, the only thing is i dont have the "classify option" under file-types but I wrote it and I was able to access it and its done, now users can...
This is probably because your files are classified as octet-stream, since the mimetype for APK files is unknown to Backdrop. When this happens, Backdrop doesn't assign a file type to the managed file...
Posted2 days 3 hours ago by Alejandro Cremaschi (argiepiano) on:
For the record I cut and pasted the missing blogs. This was so long ago and the experience that I've gained made me realize the difference between content and configuration. It is likely that...
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