Thanks for the response.
The error is resolved after installing your latest plugin update (11.7.9) which was released after my initial post.
You can decide whether the plugin caused the error or not. ??
Either way, I’m glad it’s fixed!
-
This reply was modified 2 years, 7 months ago by jamesdc.
