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
Thanks, the /tmp folder was the problem. I moved it elsewhere and then the updated worked. Thanks again!
Update 1.35.1 appears to install but hasn't
Probably not the reason, but worth to do a quick check: Sometimes the update cache interferes, so if something's odd with updates - some module (or core) claims to have updated, but then...
Update 1.35.1 appears to install but hasn't
Nope, not touched any permissions!
Update 1.35.1 appears to install but hasn't
Did it on my end on some sites without problem. I don't know why this update would be different for you. Perhaps some file permission changes?
Update 1.35.1 appears to install but hasn't
The issue with checking for updates in the BackdropCMS dashboard makes website development and maintenance more difficult. I manage more than ten websites hosted by two different providers, one...
Unable to run update - fails with Connection timed out