Sorry but I think you either haven’t read that posts completely or are just tyring to justify what you wrote. If you check the thread there, you’ll see many authors stating that it sometimes gets disabled for ordinary css issues, I’m not talking about critical bugs here, if it’s indeed a critical bug which may do a big harm – be my guest, I’ll only be thankful for disabling it right away, to stop any further harm. Another thing is if a good selling item gets disabled for some minor bug and the author loses lots of money. So, what about this? I don’t see the answer anywhere mentioned in your post.
I do agree with Travis regarding that issue, and I do agree the system does need improvements for minor bug solving, but at the same time, I’m not trying to anger you, seriously, I see your problem, but you have to remember your an author here, and having items with bugs, on sale will only cause you more harm than good in the end!
I understand that small bugs can be annoying to get disabled for, but at the same time, you must also understand this fact. A buyer paid full value for an item that has a bug. Okay, it’s a little bit extreme to disable that item if it’s a simple and I say this again SIMPLE, CSS bug, but in cases where the design of the item may broken or may suffer, disabling will get the authors attention and he will fix it asap. Remember, you’re selling a product that is broken, a small bug or not, it’s still broken and needs to be fixed. How that is handled depending on the seriousness of the issue, I do agree with you and with Travis upon!
But this is something that should be communicated by staff if it’s a serious issue. You are clearly ticked off as it gleams from what you wrote. This thread is asking for more criticism and you will see that nothing positive will come of it. Do you think many people will come say “sorry” for expressing their feelings that they felt when they were rejected? Just create a policy so you can quickly remove the threads if it’s that big of an issue.
Mate, this is my opinion as an author, it’s not an opinion of Envato or of Staff. It’s not official. It says right there in the second post on the page, and now right at the top of my initial post!
I’m just trying to get authors to stop bashing reviewers. That’s all!
Ok but again, it’s about HOW the process is being done. Getting item disabled without any prior notice of notification, without giving author a chance to fix it is WRONG. And even Travis (Kingdog) agreed on that thread that this process indeed needs improvements. Now do you think you are doing a favor to him or anyone by writing such things? You probably forget that being a moderator brings great deal of responsibility as well.
If a moderator opens a thread and points out on such important issues for many people it might seem like an official response to our queries. and THAT is utterly direspectful to LOTS of authors here who raise their valid concerns and get answer from Envato staff representative that who agrees that process is not setup good and is indeed harmful as its current state. And you just open this thread and tell us “Go to hell, whatever Envato and reviewers do is perfect and wonderful, if you don’t like it it’s your fault”. Don’t you see the problem here? If you don’t, it’s perhaps worth to consider that sometimes better not to say anything at all then say something this unfair and irresponsible. Sorry ifthis sounds harsh, I don’t mean to offend you but I’m as pissed off from your thread as I’m sure many authors here will be.
First off, I mentioned clearly that this thread is my opinion as an author, not as a moderator. If you read that, fine, if not, I wrote it again. I’ve edited the main thread, added a BIG prior notice as well right at the beginning to mention that this has nothing to do with my role as a moderator.
Secondly. Let’s say you have an AMAZING selling item with a bug in it, a critical / non critical one, right? You make 1000 sales a day. You get prior notice that that item is broken, it may take you 10 minutes, it may take you 10 days to fix it, correct?
I’m not trying to piss you off, seriously I see your problem, but you have to remember your an author here, and having items that are broken on sale will only cause you more harm than good in the end!
What happens to the buyers that purchase that item in that time? In 10 days you’d accumulate 10.000 broken sales. I’m pretty sure you’ll get much more 1 star ratings and a very very bad reputation as an author than just having it disabled so you can fix it! See my point?
A rant thread was written to bash other rant threads. Nothing good will come of this to be honest and should be removed. Just sayin
Mate, did you read the thread? It’s not a rant! It’s pure fact about how the marketplaces work and have worked for years, explained in plain, simple English for everyone to understand.
@Paylord, reviewers are not teachers. You learn for yourself what the quality of the internet is nowadays, if you bring something different to the tablet that is visually appealing and has proper inner techniques it will get approved. Otherwise, you will get rejected. It’s not the reviewers job to guide you to being approved. Reviewers review. They say yes or no. They provide feedback only in cases where you mistake is blunt straight. In cases like typography for example, a reviewer cannot give you advice. You can style that in a billion different ways. A reviewer MUST stay impartial. He cannot insert his design styles into yours. If for example, you have a slider overlapping menu, most of the times they point that out. If your item is 100% a total failure, you get the default rejection message. If your item has so many bugs in it needs a full revamp, you get the default rejection message.
Again, reviewers, review. That’s their job. They are not teachers, and they are not responsible the quality of your item! They only check the quality of your item, the rest is up to you.
Regarding the part of letting buyers decide what they want, a buyer can decide what he wants with great ease! It’s called a freelance project or EnvatoStudio or a custom project. You can have anything you want custom built! Simple! Meanwhile, this being a stock marketplace, that principle does not apply. Custom work / getting exactly what you want, does not cost 58$ with multi purpose features. It costs $25.000 + with 5 revisions… There is a fine difference between stock, and custom work.
Honestly who cares if new or old authors open up rant threads, you don’t have to read them. Dunno how you find the time to write novels like this lol
I understand your point as well, but you see, this trend is like a wave, every drop makes it bigger, and a lot of authors are starting threads like these, authors I looked at before and admired their effort to improve. Now all you see on the forums is “Envato doesn’t want my file” ...
It’s a matter of taking responsibility for your own file, improving it until the end of time if needed, and getting it approved in the end. I have time for novels like this because I don’t usually rant on the forums, so I keep accumulating time!
You have either missed the other thread points (opened by Ait) brought by lots of authors who are not the first year here working Full time on themeforest and provide perfectly valid reasoning on why disabling items the way it is is totally harmful to us and our business or .. I don’t know why you have even written this… I can value your input as one of themeforest users here but as a moderator… really, you better just didn’t write this…
Actually, I did write that, and I can say it again if needed. I didn’t point any fingers, just so you know, I was not referring to the thread opened by Ait. The fact of the matter is VERY simple. It’s not the reviewers fault or Envato’s fault for that matter if your item has a bug and gets disabled. It’s as logic as it gets. Bug = fails to meet standards = faulty product = disabled. Fair and simple. It’s the cold heated truth, and I ca guarantee you that a buyer that purchase a broken file is better off not purchasing it at all. If an item has a bug it needs to be fixed or disabled. Simple.
@organicbee, that may be true, but the reason of validation is simple. Browsers read code, valid or invalid, yet, we have Mr IE that reads only the most special kinds of “validations”. Further more, the W3 Validator helps authors who need it, learn the basics of coding. I mean, seriously, I’ve seen rejected themes that used paragraph tags for buttons, come on! The validator has it’s reasons. Although sometimes it can be skipped, some basic structures must be followed, and I fully agree on using it to a certain point.
But, let’s get passed the validator. The discussion is not about that! As I said above
This thread wasn’t meant for you or for @organicbee, it was meant for the new trend of threads that started where reviewers get bashed just because. Look at the forums. Reviewers get bashed and get called all sorts of names, and when you look at the product of the person bashing it speaks for itself… this thread was addressed to those authors who constantly second guess the review staff and the review process without looking at their files first.
Enabled saidI’d hate to break it to you but while the reviewers do a great job they’re extremely inconsistent for basic things. Look at a few of the top theme demos that have hundreds of “real” validation errors yet they’re not rejected? Yet I see threads on the forums all the time about people getting rejected because of small things…. So yeah “truth”
jonathan01 saidWhat bothers me and why I opened this thread, is that reviewers get bashed all the times for doing their jobs, and to be quite honest, that’s unfair towards them. The marketplaces have produced some amazing items and authors over the past years, and it proved once and again that it’s a system that works.
I’m off to get some popcorn before this thread kicks off…..brb
Seriously? Validation errors? That’s all? Some validation errors are legit and can’t be fixed, an instant example are the splash screen icons and homepage icons for mobile devices that go in the meta tag. Those fail validation, but work. Without those, no splash, so, those, believe me, won’t get you rejected. On the other hand, seeing templates that use a class with no href, I mean, please…
I’m not talking about validation errors. As you put it, I hate to break it to you, but please read my thread again if didn’t understand it!
The process wouldn’t receive these threads all the time if Envato and the process was more transparent and consistent. For the record I have great respect for the reviewers.
Mate, you’re a level 10 author. This thread wasn’t meant for you or for @organicbee, it was meant for the new trend of threads that started where reviewers get bashed just because. Look at the forums. Reviewers get bashed and get called all sorts of names, and when you look at the product of the person bashing it speaks for itself… this thread was addressed to those authors who constantly second guess the review staff and the review process without looking at their files first.
I’m off to get some popcorn before this thread kicks off…..brb
Go right ahead, there’s nothing to “kick off” about this thread. What I posted here is the truth, and only the truth. It’s a matter of accepting that rants about a product that’s been rejected doesn’t help, and is a total loss of time, time better spent improving that product.
What bothers me and why I opened this thread, is that reviewers get bashed all the times for doing their jobs, and to be quite honest, that’s unfair towards them. The marketplaces have produced some amazing items and authors over the past years, and it proved once and again that it’s a system that works.
And, as a small bump to this, what I’ve posted above is my opinion as an author who’s been around the marketplaces for quite some time now. It’s not intended to offend anyone, it’s just meant to explain that everyone can have their item approved, as long as their item meets the standards. There’s no reason to bash reviewers and the review process for an item that simply didn’t cut it!