revaxarts saidI can understand the choice for plugins because currently there’s no other way to give buyers auto updates.
Also the lack of support of WP plugins demands for a custom solution. I can also limit the amount of domains the plugin is used (regular license) which isn’t possible with the “native” method.
It would be much simpler if envato would just do for plugins what they did for themes. This would allow buyers to just configure their api key once per installation and being able to update all items purchased from TF/CC at once in the same way as they do for theme/plugins installed from wp.org
About the domain check, that’s really another subject.
revaxarts saidyou have to explain them how to obtain the purchase code as well and the value is different for each purchase. On the other hand, the api key only has to be generated once and then it works for any theme.
This method requires the username and the users API key (which has to be generated – which has to be explained). David’s method only requires only the purchase code.
I also assume the purchase verify is done on the update server or else it would be possible to bypass the check and obtain a download link without a purchase code. Even by caching the result, there’s still the possibility to hit the api limit.
I push updates out to wp themes/plugins, updates are hosted on my server though, because there is no way to automatically get the latest download file from envato easily.
any reason why you do this for wp themes also ? envato api provides ‘wp-list-themes’, ‘wp-download’ so there’s no need to host the files somewhere else.
No luck for wp plugins though.
There could be no side deal with Envato because you’re the copyright holder and regular license is the only one you’re obliged to accept as an author here.
Imho, they’re just talking crap.
zendesk ? not free but $20 per year isn’t really that much. You can use a gmail filter to forward support mails to your zendesk account which will take care of the autoresponder stuff.
The reality is that, as author here, you cannot ignore the fact majority of buyers are far more concerned about the page look rather than how it performs.
While mixing complex js components in the same page could potentially lead to bad performances on older hardware or mobile, you still provide the option to do that because most buyers simply don’t care about it.
It depends on how you split your js code, for instance we have a class based, modular js/css framework made by a lot of small files. We can reuse code by including the relevant class rather than copy/paste block all around, if we fix a bug in a file, then it’s fixed for all our items, it uses native wp script dependencies system and so on.
The only disadvantage is that themes/templates end up including 40+ js / 15+ css files so we also provide single minified css/js option.
More than once, plugins like W3 Total Cache and their minifying features broke our code. We do provide options in all our themes to use uncompressed sources or single minified js/css, lately we also included lazy-loading.
We only use forum. Buyers asking for support via profile form / item comments / twitter get autoresponder/canned response:
Only official support channel is forum [link]
If you invest time and resources in a dedicated forum, you must also redirect all the questions there and avoid any other channel or else it’s useless.
Ours is public (read only), this way most buyers can search and find existing answers without being forced to register.