Hi. I have the same issue. I have had to roll back to 2.2.4 in order to resolve it.
Thread Starter
alwhit
(@alwhit)
I have managed to resolve this by rolling back to a previous version of the plugin… can you let me know when this issue is fixed though so I can update (I saw the issue reported in the simpler version of the plugin)