I guess it means this bug have been fixed since 7.1.1 but I don't have
any idea what it was and how to workaround it.
Ideally the best would be to upgrade.
On Tue, Dec 13, 2016 at 1:47 PM, Enste, Patrick <patrick.enste(a)atos.net> wrote:
Unfortunately I cannot reproduce it on 7.4.5.
Anything else I could do?
Kind regards,
Patrick
--
Thomas Mortagne