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
Trying to push it to upstream 🤞 https://github.com/drush-ops/drush/pull/6621
Using Drush 8 with php 8
Wow, thank you!
Using Drush 8 with php 8
Hi folks, I went ahead and ported all drush 8.x stuff to PHP 8.3 and completely ripped out the legacy Symfony 2 internals. You can check out the exact details of what was done in the PR...
Using Drush 8 with php 8
The inability to check for and install updates makes website development and maintenance extremely difficult. Managing over ten websites across two different hosting providers—one of which is...
Unable to run update - fails with Connection timed out
Thanks for the response, Herb! Since I posted that I did some more testing and have posted this issue https://github.com/backdrop-contrib/tfa_basic/issues/33 In fact, if both email...
TFA - how to setup fallback options 'per user'