@@ -225,6 +225,34 @@ plugins.
225
225
Same as :ref: `setup-plugin-mvc-callDefaultActionIfActionCantBeResolved `
226
226
but this will raise a "page not found" error.
227
227
228
+ .. confval :: mvc.showPageNotFoundIfTargetNotFoundException
229
+ :name: plugin-mvc-showPageNotFoundIfTargetNotFoundException
230
+ :type: :ref: `data-type-boolean `
231
+ :Default: `false `
232
+
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
235
+ (usually an internal error message is shown).
236
+
237
+ When this configuration option is set to `1 ` (true), instead the default
238
+ "Page not Found" page will be shown instead (with a 404 HTTP header by default).
239
+
240
+ .. confval :: mvc.showPageNotFoundIfRequiredArgumentIsMissingException
241
+ :name: plugin-mvc-showPageNotFoundIfRequiredArgumentIsMissingException
242
+ :type: :ref: `data-type-boolean `
243
+ :Default: `false `
244
+
245
+ **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).
248
+
249
+ When this configuration option is set to `1 ` (true), instead the default
250
+ "Page not Found" page will be shown instead (with a 404 HTTP header by default).
251
+
252
+ Note that extension authors can also implement the Controller method
253
+ :php: `ActionController->handleArgumentMappingExceptions() ` to individually operate
254
+ on invalid arguments.
255
+
228
256
.. confval :: format
229
257
:name: plugin-format
230
258
:type: :ref: `data-type-string `
0 commit comments