@@ -231,24 +231,35 @@ plugins.
231
231
:Default: `false `
232
232
233
233
**Only for Extbase plugins **. By default, when calling an extbase controller action
234
- that is not registered for an Extbase plugin, a fatal exception is thrown
234
+ that is not registered for an Extbase plugin, a fatal exception
235
+ :php: `TargetNotFoundException ` is thrown
235
236
(usually an internal error message is shown).
236
237
237
238
When this configuration option is set to `1 ` (true), instead the default
238
239
"Page not Found" page will be shown instead (with a 404 HTTP header by default).
239
240
241
+ The configuration option can be either set on the global `config.tx_extbase `
242
+ scope, or also plugin-specific via
243
+ `plugin.tx_yourextension.mvc.showPageNotFoundIfTargetNotFoundException ` /
244
+ `plugin.tx_yourextension_pluginName.mvc.showPageNotFoundIfTargetNotFoundException `.
245
+
240
246
.. confval :: mvc.showPageNotFoundIfRequiredArgumentIsMissingException
241
247
:name: plugin-mvc-showPageNotFoundIfRequiredArgumentIsMissingException
242
248
:type: :ref: `data-type-boolean `
243
249
:Default: `false `
244
250
245
251
**Only for Extbase plugins **. By default, when calling an extbase controller action
246
- with unsupported arguments a fatal exception is thrown (usually an internal error
247
- message is shown).
252
+ with missing/invalid required arguments a fatal exception :php: ` RequiredArgumentMissingException `
253
+ is thrown (usually an internal error message is shown).
248
254
249
255
When this configuration option is set to `1 ` (true), instead the default
250
256
"Page not Found" page will be shown instead (with a 404 HTTP header by default).
251
257
258
+ The configuration option can be either set on the global `config.tx_extbase `
259
+ scope, or also plugin-specific via
260
+ `plugin.tx_yourextension.mvc.showPageNotFoundIfRequiredArgumentIsMissingException ` /
261
+ `plugin.tx_yourextension_pluginName.mvc.showPageNotFoundIfRequiredArgumentIsMissingException `.
262
+
252
263
Note that extension authors can also implement the Controller method
253
264
:php: `ActionController->handleArgumentMappingExceptions() ` to individually operate
254
265
on invalid arguments.
0 commit comments