Skip to content

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

Closed
misaochan opened this issue Mar 30, 2019 · 19 comments · Fixed by #4045
Closed

Modify warning about existing picture name #2818

misaochan opened this issue Mar 30, 2019 · 19 comments · Fixed by #4045

Comments

@misaochan
Copy link
Member

misaochan commented Mar 30, 2019

His comment:

It isn't possible to use one name for a series of pictures. In the older version it was possible. Now I have to copy and paste the name and add manually a different number. That's horrible.

At the moment all of my uploads fail and I don't know why.

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?

@maskaravivek
Copy link
Member

@misaochan Just to confirm, is this user an alpha user or a beta/normal user?

@misaochan
Copy link
Member Author

I asked him to confirm, but 2.10.2~66e1539a1 indicates that he is on alpha.

@misaochan
Copy link
Member Author

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?

@maskaravivek
Copy link
Member

Indeed he is on our beta version ie. 66e1539a1.

We decided to use SHA for both alpha and normal releases. See comment.

Given that the version number does not actually HAVE to be incremental, and AFAIK does not even need to be all numbers (the build.gradle equivalent is actually a "version name"), why not use the SHA for both?

#2127 (comment)

@misaochan
Copy link
Member Author

misaochan commented Mar 30, 2019

Eep. Let's carry on the discussion about SHA there, I think I might not have worded that comment clearly, lol.

@maskaravivek
Copy link
Member

It isn't possible to use one name for a series of pictures

It works for me. It shows a warning popup message but lets me continue.

Also, i verified that the suffixes are appended as expected.

@maskaravivek
Copy link
Member

Maybe after a user reaches a certain level, we can let him choose to not display these warnings again and again.

@neslihanturan
Copy link
Collaborator

It isn't possible to use one name for a series of pictures. In the older version it was possible. Now I have to copy and paste the name and add manually a different number. That's horrible.

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?

@misaochan
Copy link
Member Author

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:

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?

Shall we go with that?

@misaochan misaochan changed the title User on 2.10.2~66e1539a1 unable to use same name for multiple pictures Modify warning about existing picture name Apr 3, 2019
@jamespm4
Copy link

I'm looking for a first repo to work on, and I'm interested in working on this.

@misaochan
Copy link
Member Author

@jamespm4 It is yours. :)

@anadi198
Copy link
Contributor

anadi198 commented Oct 13, 2020

Hi, can I work on this? @misaochan

@misaochan
Copy link
Member Author

@anadi198 it seems like this has been inactive for over a year, so it is now yours. Feel free to go for it. :)

@neslihanturan
Copy link
Collaborator

@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:)

@anadi198
Copy link
Contributor

@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.

@misaochan
Copy link
Member Author

@anadi198 I have just merged your other PR. Please feel free to work on this now if you'd like.

@anadi198
Copy link
Contributor

Just making sure,

A file with the file name %1$s exists. Are you sure you want to proceed? (strings/upload_title_duplicate)

needs to be changed to something like:

A file with the file name %1$s exists. Are you sure you want to proceed?\n\nNote: A suitable suffix will be added to the file name automatically.

Also, should I save the "don't display again" boolean into saved preferences?

@misaochan
Copy link
Member Author

misaochan commented Nov 23, 2020

Yes, that is correct. :)

Also, should I save the "don't display again" boolean into saved preferences?

I don't see why not.

@anadi198
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants