There is an undocumented "trick" to using this tool, and it's caused hours and hours of people troubleshooting in vain why their subscription imports are not working correctly.
The trick is: do not use the official tagged releases. They are way out of date and do not work correctly with modern versions of WooCommerce/Subscriptions. People need to download the latest version of master branch and use that.
The existence of tagged releases implies that people should use the latest tagged release and that master branch is a development branch. On at least 3 separate occasions I have had to explain to people that they should not use the latest tagged release after they've spent hours debugging and re-running subscription imports.
I think the plugin needs either official documentation saying "Use the latest version of master branch" or up-to-date tagged releases. Thanks!
There is an undocumented "trick" to using this tool, and it's caused hours and hours of people troubleshooting in vain why their subscription imports are not working correctly.
The trick is: do not use the official tagged releases. They are way out of date and do not work correctly with modern versions of WooCommerce/Subscriptions. People need to download the latest version of master branch and use that.
The existence of tagged releases implies that people should use the latest tagged release and that master branch is a development branch. On at least 3 separate occasions I have had to explain to people that they should not use the latest tagged release after they've spent hours debugging and re-running subscription imports.
I think the plugin needs either official documentation saying "Use the latest version of master branch" or up-to-date tagged releases. Thanks!