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.

1 files changed, 1 insertions, 15 deletions

diff --git a/src/tests/upload_validation_no_exec.phpt b/src/tests/upload_validation_no_exec.phpt
index ca52017..a6cde10 100644
--- a/src/tests/upload_validation_no_exec.phpt
+++ b/src/tests/upload_validation_no_exec.phpt
@@ -14,20 +14,6 @@ Content-Disposition: form-data; name="test"; filename="test.php"
 var_dump($_FILES);
 ?>
 --EXPECTF--
-array(1) {
-  ["test"]=>
-  array(5) {
-    ["name"]=>
-    string(8) "test.php"
-    ["type"]=>
-    string(0) ""
-    ["tmp_name"]=>
-    string(0) ""
-    ["error"]=>
-    int(3)
-    ["size"]=>
-    int(0)
-  }
-}
+Fatal error: [snuffleupagus][config] Invalid configuration file in Unknown on line 0
 
 Fatal error: [snuffleupagus][config] The `script` (tests/data/upload_no_exec.sh) isn't executable on line 1 in Unknown on line 0