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 for sharing this link. We have a feature freeze in just a few days, so now is a good time to see what is happening in the issue queue.
Seeing what issues are new
The Search module from CMS core allows to limit the Content type and is quite suitable for use, the settings are available for understanding. The form is added to the pages like other blocks /...
Generating Search Form
I played around with metatags and when i revisited those pages they now have description metatags. Not sure what the initial problems were though. Sorry for the time waste.
Meta tag description on a page created by a layout
You might want to chime in on this issue.
Meta tag description on a page created by a layout
Layout is not Content, it is not used to create pages, so I think you have chosen the wrong way. To avoid problems, just need to use every tool for its own purpose. This is not a direct answer,...
Meta tag description on a page created by a layout