From b3f67a16094168cc334f5da93a86f09476e01601 Mon Sep 17 00:00:00 2001 From: xXx-caillou-xXx Date: Thu, 30 Aug 2018 15:02:22 +0200 Subject: Change how we're handling invalid configurations Since our configuration format is a bit more complex than php's one, we have a `sp.allow_broken_configuration` parameter (`false` by default), that you can set to `true` if you want PHP to carry on if your Snuffleupagus' configuration contains syntax errors. You'll still get a big scary message in your logs of course. We do **not** recommend to use it of course, but sometimes it might be useful to be able to "debug in production" without breaking your website.--- src/tests/encrypt_cookies_no_env.phpt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'src/tests/encrypt_cookies_no_env.phpt') diff --git a/src/tests/encrypt_cookies_no_env.phpt b/src/tests/encrypt_cookies_no_env.phpt index c3aeaef..d9d9138 100644 --- a/src/tests/encrypt_cookies_no_env.phpt +++ b/src/tests/encrypt_cookies_no_env.phpt @@ -16,5 +16,6 @@ EOF; --FILE-- --EXPECT-- -1 +Fatal error: [snuffleupagus][config] Invalid configuration file in Unknown on line 0 + Fatal error: [snuffleupagus][config] You're trying to use the cookie encryption featureon line 2 without having set the `.cookie_env_var` option in`sp.global`: please set it first in Unknown on line 0 -- cgit v1.3