Hello Neil. It seems that the first fix(1.6) broke the extension, but the second fix(1.7) has solved this issue. Thank you very much for your feedback.