Flagging files

On file pages there is a “Report” button to flag files suspected of breaching copyright, but - - especially in the light of the newly raised quality bar - - is there a formal way to flag files that appear to have fallen through the reviewer’s cracks? Files with obvious bugs that should never have passed review?

-1 that would be used way too much… for example ‘bugs’ that appear when editing the FLA but most of the time is caused by user error. Also I think authors would target their competitors too make sure there file gets pulled down temporarily for bugs they might pick up. I see this often on files where someone says “awesome template but uhm there is a small glitch here” now with your idea they could flag it and take it down – would be more of a sabotage feature in this competitive marketplace minor bugs are usually fixed by the author with an update – if there is something very wrong with the file buyers usually report to FD support and you’ll probably hear about it.

I would personally love that feature, but I think DS is right, it would get abused too much Every buyer that doesn’t know how to edit XML and thinks it’s your fault would be flagging files. Some buyers can be pricks and take their own problems out on authors.

Imagine a button saying “Report a bug in this file” and then think how many times a buyer starts off saying “there’s a small issue with this file, I changed this but it doesn’t work now..blah blah” they probably going to report it as a bug if you don’t respond quickly enough. And then who decides if it’s a bug or caused by user error – your file could even be taken down unnecessarily and then you have to figure out how they broke it and then explain that it’s not a bug but they did this incorrectly – then your file goes back on and you lost a whole bunch of sales – no thanks

I hear what you are both saying but I did not mean for a “flagging” to take down a file (or even be visible to the public)... just to bring it up for a “second opinion” if a bug is so glaring that it should not have been missed by reviewers in the first place : more an indictment on the reviewer than the author

If a bug is that noticeable the file simply won’t get any sales. DS is right, I think there’s enough trigger happy individuals around here already. Besides it happens so rarely I don’t see any need for it.

Imagine a button saying “Report a bug in this file” and then think how many times a buyer starts off saying “there’s a small issue with this file, I changed this but it doesn’t work now..blah blah” they probably going to report it as a bug if you don’t respond quickly enough. And then who decides if it’s a bug or caused by user error – your file could even be taken down unnecessarily and then you have to figure out how they broke it and then explain that it’s not a bug but they did this incorrectly – then your file goes back on and you lost a whole bunch of sales – no thanks

Absolutely – I just meant to initiate a second look at a glaring bug in the preview .. nothing to do with user modifications or editing. It is pretty obvious what I meant; reviewers don’t edit files when testing them.