Discussions » Greasy Fork Feedback
When someone publishes a copy of my user script, I can't update it, which is unreasonable.
There should be a "Save anyway" checkbox that will allow you to do the update. It would also have allowed the other user to save the code.
I will review the logic because if the first instance of that exact code was on your account, then it shouldn't warn you about it.
After reviewing the code, I've decided the behaviour should be that you are warned about an existing script with the same code, but only if the current script does not have the same code. This would prevent the warning in your case, as you had previously posted that code to your script and were doing a non-code update.
If you have another script with the same code, the warning will remain, as we don't want reposts even by the same author.
If someone else posted a script with the same code, then either you're copying their code and so the warning is warranted, or somehow they got your code before you posted it, in which case "Save anyway" is still an option, and you will not receive further warnings about that exact code.
I've deployed the changes to make it act like this.
Okay, after a simple test (modified the script introduction information), I didn't receive a warning. I am satisfied with the functional changes to the website!
My script:
https://greasyfork.org/scripts/412245
A copy of my script posted by someone else:
https://greasyfork.org/scripts/514032
Since I set up webhooks, I had no problem updating the script content, but when I updated the script introduction, I received a prompt:
Why is it that the other party can upload a copy of my script without receiving any warning (this behavior is prohibited by the website rules), but I receive this warning when I update the script?
The function of checking the copy of the script did not properly block the other party, but blocked the update of the actual author of the script.
I know I can fix the problem by reporting the copy of the script, but it will take time and I can't continue to update until the admin handles it.
This has happened at least three times, and in order to avoid being bothered by this issue in the future, I have chosen to report this issue this time.
After communicating with the previous script copy publisher, it was found that this situation was most likely a misunderstanding, and the copy publisher may not have realized that the problem would cause trouble to the script author. They seemed to treat the "import script" function as a function similar to a private repository, which seemed to bypass the site's copy check (if any).
@JasonBarnabe