I wonder if you’d consider making the “Won a Competition” badge incremental like the referral and collector badges? I imagine there are a few authors who have won Most Wanted competitions multiple times and that would be a cool thing to collect.
if a buyer is being unreasonable or demanding, then we don’t have to support them
I don’t see any reason why you would have to support a buyer who is asking for anything beyond what support is defined as. If they’re being unreasonable or demanding, then you can simply explain that what they’re asking for is beyond the scope of the support you’re able to provide.
I haven’t read anything in the announcement that says that customization requests are required.
And if they want more than what’s defined as basic support, then charge them extra for the service. Boom. Cash money, honey.
What if I sell fully compatible WordPress plugin which was made according to all WP Best Practices, doesn’t have any errors, warnings and even notifications from Plugin Check and WP_DEBUG mode. At the same time buyer uses theme which is not WP compatible. He activates my plugin. It doesn’t work. Who is guilty?
The root problem here is that you’re viewing your customer as “guilty” when in fact, they’re simply needing some guidance and education. In this situation the solution isn’t to blame them or take offense to their inquiry. If you’ve determined that it’s another plugin that’s causing the issue, explain that to them. You’re not being asked to fix someone else’s bugs. Taking 30 seconds to educate the buyer and explain the cause of the issue will go a long way for your business.
Here’s the thing that I don’t get with all this outrage:
Support is defined as fixing bugs, responding to questions or problems, and ensuring compatibility.
Those that are against making support mandatory, are you saying that you don’t want to do all those things for your items? You don’t want to make a solid product? That you don’t want buyers to trust you and want to buy your products because they believe that you’ll stand by it?
In my opinion, this is a win-win for all authors and will generate greater buyer trust which ultimately brings us more sales and moola.
It’s manually typed.
If you’re asking which program we use to code it, then I’m using Sublime Text 2. The Zen Coding (Emmitt) extension helps make it easier to write repeating elements.
Once an item is on the marketplace for a month, data will populate there which tells you an average of how many times that item is selling each month along with monthly earnings.
The tags in the stylesheet are identical to Twenty Twelve version: 1.3 which further suggests that it’s a custom theme.https://core.trac.wordpress.org/attachment/ticket/21442/21442.4.patch http://wordpress.org/themes/twentytwelve
While I do believe there’s quite a few kinks to work out here, I think that some are being a little dramatic.
We’re talking about fixing bugs and ensuring compatibility with the software the item is supposed to be functional to begin with (eg. WordPress).
There’s no reason for an author not to be doing this already. What author would release malfunctioning files? Nobody intentionally, I hope. So when we get a message from a buyer letting us know there’s a problem, we fix it and move on.
The announcement clearly outlines exactly what support entails. If you’re dumb enough to do customizations for your buyers without charging them an upgraded support fee, that’s you’re fault and you’re only hurting your business and fellow authors.
For Envato to say that fixing bugs and ensuring compatibility is mandatory now is really just putting down onto paper a rule that’s largely been in effect already. Because if your item was found to have bugs or wasn’t compatible any longer, it would be soft disabled anyway.
So we’re essentially taking a house rule and making it official.
But the kicker is that we have the opportunity to increase our revenue which, I don’t know about you but, I could always use another revenue stream.