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
I know it's a long and difficult job to make Backdrop known and for people to realize the power (and simplicity) of the product. And I think you do a great job. What I like about Backdrop...
My work and a big thanks to all of you
Looks good. Tres bien! It is definitely worth releasing that. We often have people looking for good simple themes and that is quite a thing of beauty whilst being simple. You're right...
My work and a big thanks to all of you
Thank you for your message. You are right. The more modules and themes there are, the more attractive Backdrop will be. It's not the number of users that poses a problem for me, it's...
My work and a big thanks to all of you
Just had a look at IIV and I could definitely see myself using this, especially the IIV Dark colour scheme.
My work and a big thanks to all of you
We don't expect modules to be perfect on first release. Sometimes it is good to get people using them. You can do releases with a beta label if you like (might need some help), but please don't...
My work and a big thanks to all of you