TYPO3.Neos

Hey there.

If a plugin throws an exception, now backend interaction handles such as "add new content element after" or "delete" are available.

A simple example: Create a plugin having a default action with a required property.
Real world example: orderController::checkoutAction($order)

Having a plugin with a required property makes sense if you want to allow editors to add regular content above and below such a plugin.

Avoiding required properties in those actions destroys validation, so this is not a sollution.

I can think about three sollutions:

1. Use default property when being in backend editing mode. This could be configured throug TypoScript or plugin configuration and obviousely only works for plugins that don't trigger persistence::write() operations.
2. Make plugins skippable through TypoScript when being in backend editing mode.
3. Catch all kind of exceptions like it's currently done, but don't skip interaction handler wrapping.

I would vote for both sullutions, 1 and 2. And number 2 should be default for all plugins with required arguments. I'm sure there are several plugin situations that don't have required properties but fail to render propertly, too. So it's not only a problem for required arguments.

Regards,
Stephan.