I believe your solution is much simpler and easy to maintain. Any chance you can set license on github if you allow other authors to use it?
Many authors use this custom version because the official version of TGMPA does not support this “plugin update” functionality… Of course we have fixed all security issue and also bulk installer issue… So, it is all green in our side… If you force us to use the official one, it is a backward for some of us… We need an explanation here…
We also have modified version of the plugin that includes plugin updates and more clear interface highlighting outdated and required plugins. I see no reason why you should limit us on classes/tools we do use as far they are patched with security fixes.
We invested lots of time to extend TGMPA class and would like to continue with it as it’s very convenient for our theme users to update plugins this way. The users get used to it’s look. If we back to official class we should rewrite documentation and educate 4000 buyers to update themes and plugin the other way. By limiting us to official TGMPA version, you risk that our theme buyers will not update plugins manually with each theme update (because it’s more complex) that brings even more security issues leaving buyers with outdated plugins. Do I need to say that TGMPA wasn’t updated/supported for a very long time until this security problem?
God inspired our team to leave the every-day jobs and go for our dreams in 2014, so we can have more satisfaction doing our job, make more money for our families and have more money to help others.
We have a multi-confessinal team living in different countries with great respect to each other. As team lead I can’t be happier!
Christ is risen.
Yes we are still looking for a right person.
Feel free to send your details!
can you please consider to add support for the anchor links (attribute name=”“) on item description pages?
We want to send the users to the chagelog and some other theme description sections without sending them out of the description page to not loose the sale.
Hey guys. I’ll be completely upfront with you, no one likes it when we have to soft disable a file. It certainly doesn’t benefit you, the buyer, or even us. And we’re very aware of the impact it has when an item needs to be taken down for repairs. The Review Team will always approach each occasion with common sense to that we can avoid or minimize the pain as much as we can.
It simply not true. Maybe YOU act like this when you do soft-disables, but for us it’s clear that a person who disabled our theme twice didn’t think that the item is in the top list for this week and the problem is ridiculously minor to “punish” my team like that. We developed the theme for 8 months and can loose all the traction in a week because of it. As a person who pay salaries to my support team and developer, I can’t rely on “common sense” here because it tell me to find a better place to sell my product.
What many authors in this thread wants is not to rely on the reviewer’s “personal sense” or their judgement, but have a common rule like: If the issues with the item isn’t a security problem then you obliged to send author a notice to fix it in 72 hours and only then disable the theme.