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 Alejandro. That was the clues I needed.
Ubercart - Programmatically add product to cart and straight to Checkout
Have you tried uc_cart_add_item()? You need to provide the nid of the product. Then you can use backdrop_goto('cart/checkout'); to send the user to the checkout screen. uc_cart_add_item...
Ubercart - Programmatically add product to cart and straight to Checkout
No problem, let's see how it evolves. I'd be happy to provide a suggested version if i could. I will keep that in mind and try learn this hook chain hopefully very soon. I will...
File hashing uploads made through TinyMCE
I could request hashing support, but that's the lazy way 🤣 I would appreciate it if you as an active maintainer would 'officially' add a hashing support...
File hashing uploads made through TinyMCE
Hi, i understand the updating obstacle - not worth mentioning - hence it is a wacky (but working) patch until i know what to do. :-) One of my biggest wishes is to understand the hook...
File hashing uploads made through TinyMCE