But this never taken care in the past when it reflected on item ratings and comments. It is easy to have policies/guidelines in written form. But do you really think authors will afraid about this change if the written policies were functional in the past? (speaking only about support and its connection with ratings especially about new items)
Agreed. And that’s why this project is about more than just written policy. As mentioned in the blog post:
We’ve got lots of work to do under the hood as we adjust the T&Cs, item management processes, author settings, item pages, ratings, download pages, purchase confirmation API and much more.
Hello and welcome to the site I don’t work on the Review team, so I can’t really speak about what can or cannot be excepted, but I know what has helped me is to ask myself “Is this photo something that people will ever need or want to purchase?” The most successful stock photography authors are always asking themselves this and then taking photos that reflect that.
You’ll also want to consider “Is this photo already available on the site or have similar style photos already reached a high saturation?” While a photo may be technically well done, if there are already 1000 similar photos on the site, there’s a much smaller chance of getting the item accepted. Hope that helps
Heya guys. Just to be clear, no one is asking you to offer customization or “teach the customer to code” As Collis mentioned in the blog post:
We’re working on a clear way to define support work. Our current working definition is that support includes:
But does NOT include:
- Responding to questions or problems regarding the item and its features
- Fixing bugs and reported issues
- Where relevant, providing updates to ensure compatibility with major new software versions (e.g. of WordPress)
- Customization, configuration or installation
- Support for 3rd party software and plugins, except as advertised by the author
To put it in plain English, support is making sure the item works for the buyer in the way that it was advertised and answering questions around that, but it doesn’t include actually configuring the item. Our research indicates this is a fairly consistent view from authors too.
Are some buyers still going to ask for the “kitchen sink” when they buy a theme? Some may, no different than they do now. But we’re going to be very clear with what is and is not considered support. So in summary, no you will not be required to teach a buyer how to code
While it would be awesome to have everything on the site available in different languages, it’s probably not feasible at this time and it’s not one of our major focuses for this year. We have run some testing on Tuts+ on translating some tutorials into different languages, but it will take a lot more work and thought
Hello From what I’ve heard, there could be plenty of reasons emails may not be getting through, from spam to blacklisting and domain issues. Whenever you notice mails are not being delivered, please open a Support ticket and give them all the details. This will be the only way we can properly look into the issue for you. Posting on the forums will often get overlooked and it’s not the place to go for troubleshooting, so we ask you to always open a Support ticket. Thanks!
Any content on the item pages or item demo pages must follow our community content policy:
You must not discuss or link to offensive topics, such as pornography, violent themes, sexism, racism or other discriminatory subjects.
as well as our Terms of Service:
36. Content removal: We can look at or remove any of your content for any reason at our discretion. Reasons might include quality assurance, if we receive a valid copyright take-down notice, if we think that the use of your content is unauthorised, misleading, incorrect, offensive, or in breach of anyone else’s rights, or if we think that your use of Envato Market and any content might result in liability to us or anyone else.
Any offensive material should be reported to our Support team. Thanks!