My favorite is Mike McAlister, by far.
Interesting and good to know. I’m not surprised that no one knows this, so I’m glad it’s finally all getting cleared up.
Maybe that’s why no one buys the Extended License! No one knows what it is or how they can/should use it. Buyers are familiar with the Developer license from every other theme shop, and it would integrate well into ThemeForest.
Well done! Glad to see the licenses getting cleaned up.
I agree with DesignerThemes about the price of the Extended License. No one buys the Extended License for $2000+ when they know they can get away with a Single License and just use the product as many times as they’d like. We’ve all seen this happen to our items. The massive price difference is encouraging the Single License, even when the buyer should be acquiring an Extended License.
However, if that price was a little more realistic (along the lines of industry standard ‘developer licenses’), I think we would all see an increase in responsible purchases of the Extended License. It would instantly create a much more dynamic pricing option for buyers to consider.
Maybe something like this is being rolled out with the item-specific licenses?
This has come up a few times actually. But I think the idea is that they are hoping to keep your money in your account in hopes that you’ll spend it on the marketplaces. This doesn’t really make sense for authors, but I could see why they would do it for buyers who deposit money. Without an automatic withdraw, money stays in the ecosystem.
I’ve forgotten to withdraw earnings a few times myself. Both times really put me in a spot, because like Chris, I rely solely on my theme sale earnings. My fault, I suppose, but it really shouldn’t be locked up for another month by default. That money is serious business for some people who rely on it. There should at least be a way to work with people who forget to do it.
@Brandon, it definitely should be part of the codex, but even if/when it does get added, that doesn’t ensure people are going to adhere to it. There are plenty of rules that are in place now that aren’t upheld by authors. But I agree it would be a good start.
It perplexes me how much resistance there is in this thread about using best practices. It’s such a simple concept.
Here you have Justin Tadlock, Carl Hancock and Pippin Williamson, all of which are very successful and respected members of the WordPress community, giving free advice on how to make your themes, plugins and businesses better, yet authors are arguing with them as if they have the superior insight.
Let’s be clear, it is a MIRACLE that most of the theme “developers” here on ThemeForest do as well as they do. It’s not because they are gifted designers, thoughtful developers, or seasoned businessmen that their themes do as well as they do. Granted there are some, but it’s no secret that the majority of themes fill the bottom-of-the-barrel niche, and they do it very well. Naturally, these authors are going to get defensive when their practices are (rightfully) criticized. Unfortunately, for every one of these authors who is willing to sell subpar code, there is an unsuspecting buyer willing to snatch it up. And so the vicious cycle begins.
Rule #1, leave your user’s content alone. Shortcodes, custom post types, and anything that interferes with a WordPress user taking their content with them when they switch themes (which they always do) belongs in a plugin. It’s that simple. It doesn’t have to be noted in a codex page to become part of your workflow. It’s common sense and more importantly it’s your responsibility to uphold the standards that the WordPress community puts in place, not just the standards you get away with here on ThemeForest. It’s better for the community, it’s better for your customers and it’s better for business.
Hello friends, I was wondering if support or staff could clarify some of the details about the new rules regarding including icon fonts with themes. The only reference I can find is here: http://themeforest.net/forums/thread/using-custom-fonts-on-themeforest-items/69689?page=1#611634
The post by Jarel touches on it, but doesn’t say exactly what the reasoning is. Of course, I can understand Envato wants to protect themselves from copyright issues. I’ve seen users with fonts that clearly should not be included with a theme. But why disallow icon fonts entirely, even with proper licenses? Should that not be left up to the author to regulate, just like with copyrighted images?
Especially with 100% commercial friendly licenses available for many of these icon fonts, it seems regressive for theme development. Especially when plenty of current marketplace themes utilize copyrighted or limited-use PNG icon sets, with seemingly no repercussion.
The alternative of having a buyer install the font themselves is very unrealistic. Many theme buyers can barely install the theme itself, even with docs and an install video, let alone go out and find and install a font properly.
Anyway, a little insight here would be great!
Oh, what’s that? Looks like my name on one of those Envato Moleskines!
@jonathan Ah, I see what you’re saying. When I initially read the post my wires were crossed and I thought I read it was for Nettuts.
I’m all for sharing my thoughts and experiences on the marketplaces, but I don’t necessarily like the idea of someone having to pay to hear them.
Either way, I’m not afraid of some fresh competition. Bring it on newbies!