Add support for premium themes from Envato / Themeforest

[royduin]

I'd like to install some premium themes from Themeforest with Composer which isn't that easy, see my question on Stack Overflow: http://stackoverflow.com/questions/34295318/install-premium-wordpress-theme-with-composer.

But today I came across the Envato API: https://build.envato.com/api/ which provides the possibility to download purchases: https://build.envato.com/api/#market_0_Buyer_Download by item_id or purchase_code which can be obtained by https://build.envato.com/api/#market_0_Buyer_ListPurchases. The only disadvantage of this is that only the latest version can be downloaded because Envato doesn't provide the possibility to download older versions. But with for example a premium Wordpress theme the API gives the metadata of the theme as wordpress_theme_metadata which contains the version so it's possible to do some kind of check if it's still the same or a new version.

An implementation for this would be very nice! What do you think?

[vercotux]

I developed a composer plugin in order to do this with Envato (and WPMUDEV and some others), but I'm afraid to publish it in case they will try to block it.

[tamlyn]

The basic problem with this is that your purchases are private to you and therefore can't legally be held in a public repository like this. I'm guessing any implementation would need to have your API token or whatever so that it can fetch only your purchases.

[royduin]

@vercotux, can you share your code with me/us? You can find my contact information at my website listened in my Github profile.

@tamlyn, I agree but you can legally list them and if you want to use it you've to provide your password or API key. I can't see why Envato won't allow that.

[tamlyn]

Yes, listing all but only installing with the appropriate credentials sounds reasonable. It's not something I have any need for at the moment but I would happily accept any PRs that implement this.

[vercotux]

@royduin I would gladly publish it, but like I said, I am afraid some of the providers will not like that and would attempt to block it. I would only publish it under the condition that enough people agree to help maintain it if that happens.

[royduin]

@vercotux, I'm in and if we can add it to wpackagist I think @tamlyn is happy to merge it.

[vercotux]

It is designed to work without (or alongside) wpackagist though. It would have to be somewhat adapted to integrate it into wpackagist. Right now it allows me to define a repository package from Envato, for example:

{
    "type": "package",
    "package": {
        "name": "envato/revslider",
        "type": "wp-plugin",
        "version": "4.6.0",
        "dist": {
            "url": "http://codecanyon.net/user/<USERNAME>/download_purchase/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
            "type": "envato"
        }
    }
}

I'm entirely not sure how it could be built into wpackagist as I am not familiar with its inner-workings.

[emilbayes]

I don't think this belongs in wpackagist, but as a custom Composer installer plugin, just like eg. https://github.com/johnpbloch/wordpress-core-installer.

[vercotux]

Update: I've pulled my repository and will not be publishing anything. Envato are a bunch of crooks. I offered them help and they ignored me for 1 month then after countless emails and tweets basically told me to f*** off. They can go **** themselves. Don't finance this scum.

@vercotux Hey, can you share it privately?

[tyrann0us]

What you are looking for is called SatisPress. Refer to #162 (comment) for more details.

[szepeviktor]

Just started to design a Composer plugin for Envato
https://github.com/szepeviktor/composer-envato
by providing an item ID and a personal token you will be able to install a theme or plugin with Composer.

[ethanclevenger91]

I developed a service called Package Peak that allows you to authenticate against several Envato accounts with a single API token and get access to your purchases in a versioned manner.

Doing this, I learned that Envato doesn't keep old versions of plugins/themes, just the latest published version, so Package Peak has to store it.

I assume wpackagist is currently just mirroring the WP plugin repo and not actually hosting any files, which would make an Envato solution much more complicated than an passing an authenticated request along.