External Theme Updates

I think I’ve misread something then. Sorry about that. Maybe Envato just wanted the authors to use this – http://notes.envato.com/general/envato-wordpress-toolkit/

UmbrellaStudios said
@contempoinc well i think a reason could be the security of that app. they might think it is an in-secure way to re-distribute Envato property (because we are exclusive author).

The big problem with Envato & piracy is not related with the security of any system; i don’t think you should worry about that. And as said by Jonathan, the file is your property, not Envato. You are just selling here the rights to use it.

I agree with the trust points idea for immediate update approval.

kriskorn said
I think I’ve misread something then. Sorry about that. Maybe Envato just wanted the authors to use this – http://notes.envato.com/general/envato-wordpress-toolkit/

You did That’s to allow customers to update themes without having to go to the TF website, go to their account, go to their downloads and download the theme again to get an update. But the updates still need to go through reviews here on Themeforest before they’re available for the customers.

How about a simple .patch file updater?

Lets say you have some hotfixes for example. For each fix you create .patch files and release them on your supportforum. The users (validated with purchase code) download these patch files and upload them in the backend. The updater simply patches hotfixed files and skips them, if they are already patched (because of a new tf-update or manuel fix & whatnot). You can also release patch-collections each week and the users can multiupload those zipped collections. I don’t see any violations in such an approach and reverting patches is also possible.

See: http://php.net/manual/de/function.xdiff-file-patch.php

nevermind..

Well i will consider this, thanks a lot for that suggestion.

TomSiwik said
How about a simple .patch file updater?

Lets say you have some hotfixes for example. For each fix you create .patch files and release them on your supportforum. The users (validated with purchase code) download these patch files and upload them in the backend. The updater simply patches hotfixed files and skips them, if they are already patched (because of a new tf-update or manuel fix & whatnot). You can also release patch-collections each week and the users can multiupload those zipped collections. I don’t see any violations in such an approach and reverting patches is also possible.

See: http://php.net/manual/de/function.xdiff-file-patch.php

RubenBristian said
nevermind..

Well i just did a request ticket to clear this out, because the last thing i need is a trouble with TF.

pezflash said

UmbrellaStudios said
@contempoinc well i think a reason could be the security of that app. they might think it is an in-secure way to re-distribute Envato property (because we are exclusive author).

The big problem with Envato & piracy is not related with the security of any system; i don’t think you should worry about that. And as said by Jonathan, the file is your property, not Envato. You are just selling here the rights to use it.

UmbrellaStudios said
What was the point of the previous URL ?

RubenBristian said
nevermind..

I didn’t read the OP well and responded off topic

@ UmbrellaStudios — Be sure to post any info you receive here.