Not sure if this has already been mentioned, i think the problem was caused by the Google’s Mid April’s algorithm update. Since only a part of Envato marketplaces are responsive, perhaps the SERP’s were affected and resulting in lower traffic? Just saying, this might seem just a coincidence.
Anyways, sudden drop for me too, since mid May.
^ I use the direct buy link on my UCM website too. (details about it are in this forum thread here)
You can post add to cart and it works just fine now too – example: http://dtbaker.net/files/envato/buy-now.php (check source code)
Looks like it logs you out though, but you can log back in and it remembers your cart. So all good.I’m going to adjust my “buy now” links to the “add to cart” as it gives a little bit of a better experience. Then track conversions and see if it takes a hit.
Wow Dave, you rock!! Thank you so much for sharing!!
All in all, great improvement, thanks to the whole team!
I just seen a few days back, that WpBakery team have pulled together a way to link their item directly to checkout mode, for example http://codecanyon.net/item/visual-composer-page-builder-for-wordpress/242431?license=regular&open_purchase_for_item_id=242431&purchasable=source which will open the item page and redirect to checkout – awesome!!
Everything’s all good when we’re login, however if logged out, the checkout link is “lost” and no matter if i do or i don’t have an account, i won’t be redirected to checkout.
Usually that’s fine, the system is getting always improved, however this “tool” is great for us to link from our personal websites. For example i link like “$45 – Buy from Themeforest” and the button’s action is really obvious to take the buyer to a checkout step. I’d hate my potential client (whom he decided to buy my item, from my personal website in which i’m investing into), to get lost into the massive marketplace for such reason. Hope this makes sense!
Not every author has to deal with security patches and new WP releases, meaning that a lot of buyers can safely purchase an item without the ‘fear’ of not getting a security update for free. But again, the question that was asked back then was a suggestive question like this:
“Would you buy an item if you had to pay for security updates as well?” Of course, 99% will answer this with no.
Creating a paid support pack ‘solution’ simply isn’t necessary for a lot of items. Besides that, with the paid support packs, an author still can ignore those security updates as well if the item doesn’t sell anymore.But again, not every author has to deal with these security patches in the first place.
Exactly! The security patches reason, is actually an exception from the rule. I mean why should it influence things so much? There’s like hundreds of thousands of licenses sold and the security patches issues are a just a very tiny problem (at least of what i’m aware of) which can be solved by just making that updated file public or post the code into a gist or pastie. It’s just copy/paste a chunk of code or replace a file.
Buyers are fearful of having to pay for a basic updates/security patches in the future and some have said they would not buy that item if they had to, meaning the author may not get the sale in the first place.
I find this a perfect valid reason, but i think same goes for support packs aswell.
While the support topic always got offtopic, I’ll also +1 annual (or 6 months) license renewal because it really is the best choice as far as i can think of. It’s awesome to see changes, new platform features that are released by Envato, so for this support concern, i’ll most likely comply too.
I’d like to raise a doubt though: What will happen when there’ll be 1 million items, i mean there’s really very, very low chances that our items will appear on search results and to get some exposure. I deleted at least half of my portfolio because i wasn’t motivated at all to update them, it simply wasn’t worth the effort. (i could’ve kept them because they were still getting a few sales, but i didn’t want to affect my reputation as an author). Right now we’re motivated to release new items instead of updating old items which could lead to market flood.
No matter what, i’ll always support my items, the only thing i’d monetize though, is a priority queue support. These new support changes doesn’t really affect my business because i’ll keep doing what i did before and will do in the future too, but now “paid better”. In the end i will probably don’t even notice any changes at all.
In the end, there’s a few hundred people at Envato, i’m sure they know perfectly what they’re doing, so i personally will be confident.
Great to see things are moving forward, support is a controversial matter but it needs to be dealt with.
I do have a question though. Will Envato help authors with a toolkit API implementation for popular platforms (Wordpress BBpress, Zendesk/Freshdesk/Yeti/Helpscout etc.)? Or promote on CodeCanyon a section/category for Envato API implementations for Authors needs (we’re quite a few tens of thousands here). I’d be glad to pay for updated toolkits for support verification needs, that could be easily implemented. I’d hate to get too busy tweaking my own system.
Really sorry if this has already been asked and replied.
You should actually try seeing from a different angle – admire their works and see them as your role model. Look what they’re doing i mean it’s surreal, fantastic work.
From what i noticed Envato’s ecosystem is like a natural selection. Do something great and it will be noticed. If we keep following trends and do the same thing but with different fonts, images and colors, it will be just a tiny drop from an ocean.
I have all my respect for these guys, they’re increasing the quality bar for ThemeForest.
EDIT: I too had 2 of my items featured and been featured as an author too but i know i did something great and i’m really proud of them.
Here is a video tutorial on how to translate the theme, using PO Edit http://support.hogash.com/documentation/how-to-translate-with-po-edit/
Thank you very much!
Since the whole support is buyer-oriented, in these cases i make an exception and do it over the comments directly. It’s not worth to get this mad for these situations that happen quite rarely.