-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Modify warning about existing picture name #2818
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
Comments
@misaochan Just to confirm, is this user an alpha user or a beta/normal user? |
I asked him to confirm, but |
Edit: How strange, he isn't in our alpha testing group as far as I can see. I wonder why the feedback is displaying that as his version? |
Indeed he is on our beta version ie. 66e1539a1. We decided to use SHA for both alpha and normal releases. See comment.
|
Eep. Let's carry on the discussion about SHA there, I think I might not have worded that comment clearly, lol. |
It works for me. It shows a warning popup message but lets me continue. Also, i verified that the suffixes are appended as expected. |
Maybe after a user reaches a certain level, we can let him choose to not display these warnings again and again. |
It can be about missing "Use previous title and description button" too. On the other hand, the warning feels like if I proceed with the same file name, I will violate Commons. However we already add suffixes for same file names. Can we include some more detailed text to the warning about even f they proceed with same name, a suffix will be added to their filename. Besides can we add "don't display again" button to this warning? |
This poster clarified that he was actually talking about #2035 . Sorry for the false alarm! I actually don't much see the point in the warning about the same filename since suffixes are automatically appended anyway. But if we keep the warning, I agree with @neslihanturan 's suggestion:
Shall we go with that? |
I'm looking for a first repo to work on, and I'm interested in working on this. |
@jamespm4 It is yours. :) |
Hi, can I work on this? @misaochan |
@anadi198 it seems like this has been inactive for over a year, so it is now yours. Feel free to go for it. :) |
@anadi198 , I saw you are also working on another issue. If you are not working for this issue, please let us know. So that someone else can work:) |
@neslihanturan I didn't realise I got a reply on this thread, feel free to assign it to someone else. I can take this up once I'm done with the current one if no one else does. |
@anadi198 I have just merged your other PR. Please feel free to work on this now if you'd like. |
Just making sure,
needs to be changed to something like:
Also, should I save the "don't display again" boolean into saved preferences? |
Yes, that is correct. :)
I don't see why not. |
@misaochan I'm not sure if just opening a PR notifies the necessary people or not so I'm just dropping this comment to update you. |
His comment:
Did we change something that broke the automatic appending of suffixes to files of the same name? @ashishkumar468 @maskaravivek
Edit: The scope of this task has changed to:
Can we include some more detailed text to the warning about even f they proceed with same name, a suffix will be added to their filename. Besides can we add "don't display again" button to this warning?
The text was updated successfully, but these errors were encountered: