-
-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Disallow the submission of duplicate scenes and duplicate pending scenes. #282
Comments
Yeah, this ought to be a priority now that the gates have been opened, the search is not picking up some results which doesnt help either so having this step to warn people about the scene possibly already existing, is a necessary step |
Bounty added for $10. |
Nice, you added the bounty or someone else did and you're posting it here? :) |
kronkels did. |
I believe this has been implemented already, and it will check existing/pending submissions that have the same title or phash. |
Resolved by #502 |
@InfiniteStash let me know what you want to do with this bounty. |
Is your feature request related to a problem?
In the current version, it is possible to submit scenes that have the same title, performers and description as existing scenes in stashbox. It is also possible to submit duplicates of pending scenes. Indeed, someone submitted the same scene as I had submitted a couple of hours before the other person. Ironically, my submission was down voted, because the later submission was accepted first, which led me to be wrongly accused of submitting a duplicate.
Describe the solution you'd like
On the first page of the scene submission wizard, return an error stating that there already exists a scene by the same name. The same should be true for submitting a duplicate draft, perhaps provide a link to the pending submission, so that you can vote it in.
Describe alternatives you've considered
The alternative is to let everyone check their submissions manually which is prone to human error.
The text was updated successfully, but these errors were encountered: