Forums
(@dsmith1547)
11 years, 1 month ago
Yes, seems to be fixed now. Thanks!
11 years, 2 months ago
Hi,
I updated to version 2.0.6 and the problem is back – so I can re-implement my workaround, but the next update may of course break it again.