Thanks @LaMi it was only unclear as the workaround is not possible in production environments
and there was not mentioned that it will also be included in 2.0 as the fix was already made in March.
Thanks @LaMi it was only unclear as the workaround is not possible in production environments
and there was not mentioned that it will also be included in 2.0 as the fix was already made in March.