What is interesting was that this feature was not behind a paywall as late as version 6.7. Despite users clearly having an issue with uploading a file, your organization chose instead to put the workaround behind a paywall. I get that a company needs income but that is just a reprehensible move to put a feature that solves a problem users are having with your plugin behind a paywall that was previously free.
Second, I find it interesting that your official solution to the “stuck at 100” problem focuses on max execution time and was also previously blamed on internet speed. However, downgrading to 6.7 magically solves the problem in two ways. The plug-in no longer gets stuck at 100 and you can also restore from aim folder on the server.
This would suggest the problem lies with a change in the plug-in and the solution to the problem has been put behind a paywall. That’s some crafty hustling Yani.
