The only official response from Envato was “we’ll consider this in the future” by Stephen. Quite frankly, i don’t why we’re forced to use TGMPA.
StephenCronin saidI’m not suggesting authors who are using TGMPA class to immediately switch to a different solution but, after the add_query_args sh**storm is gone, they should be free to
We’re a little stretched right now (responding to the add_query_arg vulnerability issue), so we need to ask people to stick with their current solutions for the moment – but it’s something we can consider in future
For instance, we are in the process of releasing a new theme (not before may) and would like to use the proposed solution.
As the TGMPA author said himself, most hooks were not available when the the project started in 2011 but they are now and since WordPress already includes plugins/themes install/update features, why not just taking advantage of them ?
A solution which reduces custom code while allowing buyers to use the same wp native interface they’re used to for wp.org plugins at the same time should be favoured by Envato rather than forbidden.
edit: for those who asked, i included the js code in the github repo.
A while ago there was a discussion here about theme bundled plugins, i kinda felt like using your class would be the only permitted way to handle them but couldn’t get an official answer.
To hook into the wp upgrade system is an alternate approach (much simpler imho) and author on TF should be allowed to take advantage of it. That’s the only reason of this thread.