I'm testing the new Backdrop release against some changes in our general system setup, and right on the very first test, it's behaving very strangely. The Actions test enables a test module, actions_loop_test, that depends on code running in its hook_init implementation. But that hook never gets called. I've tried the same test in a new generic installation and it works fine. So it must be something about how our site is configured. But I can't even imagine what could have this kind of effect. It looks like the test page it's attempting to run is running in the standard site environment? In the test code, system, dblog, and actions_loop_test implement the hook, but from a debug call inside dblog_init(), when the test page runs, all the usual modules are there.
Are there config values or things in the settings.php file that might be messing with the tests, outside of what simpletest controls?
Recent comments
This is good enough, but maybe the module maintainer would like to add such a feature.
specific webform permissions
This should be allowed atleast on private files directory. Accepted your answer though.
How to upload js and gz files
This is a security precaution. It's not recommended and it's not documented in the settings.php file, but you can set allow_insecure_uploads to be TRUE if you wish to allow uploading files like...
How to upload js and gz files
You could also just add an image field to the content type but not display it and instead reference them in your markdown.
Images Disappearing from inline-images
You can create a small custom module using this hook: https://github.com/backdrop-contrib/webform/blob/136c20cb1c51cea203f3f0bc5355237c1d4dbf84/webform.api.php#L652-L678 /** * Determine...
specific webform permissions