Hi @jimhubbard,
I’m assuming you are referring to those who experienced issues with the recent 3.6.5 update, but please do let me know if you are concerned about some other issue.
We have striven to assist those who have posted in the support forum, as you can see from the recent topics there, who experienced issues with 3.6.5. It’s much trickier to do the same when support requests are instead posted as reviews, and so I hadn’t gone through and addressed those people in the same way.
As to why there is no mention in the changelog: the issue was not due to a bug, but due to an issue in deployment, and as such no change was made to the plugin – 3.6.5 was simply reissued as 3.6.5.1. Unfortunately, this means that the issue wasn’t present during our testing and code review process, given that it was only introduced when releasing the plugin. We are currently putting in place safeguards and streamlined processes to ensure that these sort of mistakes cannot happen with future plugin releases.
