We use version 5.11.0 and we're still having this issue. Is it possible to see if a solution has been introduced?


I think this is now fixed and should be part of 5.14. You can either wait for 5.14 release or apply patch from here.



Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.