It’s just a HTML page with links to different demo sites.
I think the current “Churches” sub-sections should be renamed “Religion” or “Faith” as the word “Churches” implies Christianity. When it comes down to it a template or theme for a Christian church can be used for any other religion once the imagery has been changed to suit. The features are going to be the same or similar.
Removing the badges won’t make much of difference in terms of privacy as you can still see the number of sales of every item in an authors portfolio. It wouldn’t take much effort to work out their approximate earnings from those figures.
In regards to legal issues I think it’s simple. Don’t break the law and pay the taxes you owe.
I see no problem with making it optional but I don’t think it is going to solve the problems the OP raises.
Creattive saidThat’s the problem. There is no way to contact a buyer who has left a review so it’s just assumed that if someone is willing to leave a review they wouldn’t have a problem with the author putting it on the item description page. I haven’t heard of any incidents where it was a problem.
to ask for permission you would have to be able to contact the person who left the review, but this is not possible, so how do the “big Guys” do it?
Search for Open House Theme Options on CodeCanyon. It’s what I will be using from now on.
If it was left as a comment on the item’s comment page then it is already publicly viewable so I see no reason why you could not display it on the item page itself. However, as reviews are not currently public you should probably ask permission first. I don’t think many people would have a problem with you using their positive testimonial as their review shows that they like your work. It’s just common courtesy as its not something they agreed to at the time of writing the review.
Although I do believe Maarcin’s point could be easily argued it was not my argument. I was simply clarifying it for, WPWiseOwl, as you misunderstood it. And in my post I did not mean “the same” in the literal sense. I meant “the same” by Envato’s own definition of what constitutes an individual item on the marketplace.
The change in rule blurs lines that up until now were very clearly defined.
WPWiseOwl saidThe point maarcin was making is that if you can upload two separate versions of the same file here on the marketplace, as far as Envato is concerned, they are independent items (otherwise why sell them as separate items). Therefore an author could sell one version here and another version somewhere else because they are not the same.
Um, no. Since Envato doesn’t offer the ability to change the exclusivity status of each item, you’re either “exclusive” with Envato or you’re not. Exclusivity applies your entire account rather any individual item. If you have multiple accounts though that’s a different story, I suppose.
So the argument is either: a.) They are not the same. Authors can sell different version of the same theme here and elsewhere.
b.) They are the same and there should only be one “version” of an item with everything included.
Allowing this is a bad idea and your justification for it is weak.
For example, if a buyer is looking for a standard WordPress theme, why should they be forced to purchase a more expensive version (which is only more expensive because it is built with advanced features the buyer doesn’t want or need).By “more expensive version” we’re talking about $10 to $15. Buyers are hardly going to have to take out a mortgage to afford it. Whether they choose to use the extra features or not they are still getting great value for money. Anyone who has been on the marketplace for a few years knows that extra features in a theme help sales rather than hinder it, just look at the top selling themes for concrete proof.
Conversely, an author that has built a tremendously advanced theme may lose sales from buyers seeking a simpler version in a lower price bracket.
All this will achieve is flooding the marketplace with 3 variations of each “multi-purpose” theme and some confused buyers not knowing the difference between 1 version and the next.