Closed strongpauly closed 2 years ago
Hi, this particular error has been fixed in release 3.6.1, however, note that the module has not yet been ported to v10. so you are likely to come across other problems if you continue using it.
v10 support is being slowly introduced
I can confirmed this has been fixed in 3.6.1. I'm currently only using the module in my v10 test environment, will raise any further bugs I find, but so far it looks good for my use cases. Thanks!