Catch all errors thrown when generating shortcode replacements

Catch all errors thrown when generating shortcode replacements (#17)

When a controller that is used to generate shortcode replacements throws an Exception, this exeception will currently fall-through.

I think this kind of errors should be contained, and we should try to display the shortcode as unchanged as possible, as if we had not attempted to resolve it in the first place (of course, logging the problem).

Co-authored-by: Fabian Schmick <fs@webfactory.de>

Avoid passing the current request into controllers resolving shortcodes

See #15 – this never worked for ESI-based shortcodes, at least not with Symfony ^4.0.

For inline-based shortcodes you need to review your substitution-generating controllers and check whether they depend on the request Request attribute.

Additionally, the default logging level and channel have been changed, see #5.

Fix Logging

Only log the url if a request exists

Fix regressions and missing dependencies introduced in v1.4.0

Oh my! Had we run the tests automatically, we'd have catched this earlier.

First release

Now supporting shortcodes in shortcodes.