I tried your patch and it solves the problem here perfectly. Thanks! This fix should definitely go (at least) into 3.14, perhaps even be listed as an official patch against 3.14.12.5.
I tried your patch and it solves the problem here perfectly. Thanks! This fix should definitely go (at least) into 3.14, perhaps even be listed as an official patch against 3.14.12.5.