Skip to content
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

File numbering in case of different upper/lower case letters #33483

Open
wizzardking opened this issue Aug 8, 2022 · 2 comments
Open

File numbering in case of different upper/lower case letters #33483

wizzardking opened this issue Aug 8, 2022 · 2 comments
Labels
1. to develop Accepted and waiting to be taken care of 26-feedback bug feature: files

Comments

@wizzardking
Copy link

wizzardking commented Aug 8, 2022

How to use GitHub

  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

If a file is sent in Talk where the filename already exists, a "(1)" is appended to the filename.
But this logic requires that the upper and lower case is identical.

So it is possible that in the Talk folder there is a file "1.jpg" as well as a "1.JPG".

With Linux based systems this is no problem. On Windows systems, however, I have to regularly clean up the Talk folder for all users so that the NextCloud desktop client no longer issues error messages because of this.

It would therefore be useful if it would take into account the WIndows machines here and also add a (1) to the file name if the files differ in case.

Steps to reproduce

  1. Send a File with filename "1.jpg"
  2. Send another File with filename "1.JPG"
  3. Wait until the Windows desktop client tries to synchronize the Talk folder - which will throw an error message.

Expected behaviour

The second sent file should be saved in Talk folder as "1 (1).JPG", because it already has a file with identical filename (for windows systems)

Actual behaviour

The second sent file will be saved as "1.JPG", because it theoreticaly has an other filename as the first file - but it will result in a sync error on Windows Desktop Clients.

Talk app

Talk app version: 14.0.3

Custom Signaling server configured: no

Custom TURN server configured: no

Custom STUN server configured: no

Browser

Microphone available: yes

Camera available: yes

Operating system: Windows

Browser name: Chrome

Browser version: 103

Server configuration

Operating system: Ubuntu

Web server: Nginx

Database: MySQL

PHP version: 8.1

Nextcloud Version: 24.0.3

List of activated apps:

@wizzardking wizzardking added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels Aug 8, 2022
@nickvergessen nickvergessen added 1. to develop Accepted and waiting to be taken care of feature: upload & shares & voice 📤🎙️ and removed 0. Needs triage Pending check for reproducibility or if it fits our roadmap labels Aug 8, 2022
@nickvergessen
Copy link
Member

While this is fully correct and I understand the trouble, it's outside of the scope of Nextcloud Talk.
The files app itself allows creating such files next to each other without adding the (1) or showing a conflict or anything.

@szaimen
Copy link
Contributor

szaimen commented Jan 23, 2023

Hi, please update to 24.0.9 or better 25.0.3 and report back if it fixes the issue. Thank you!

My goal is to add a label like e.g. 25-feedback to this ticket of an up-to-date major Nextcloud version where the bug could be reproduced. However this is not going to work without your help. So thanks for all your effort!

If you don't manage to reproduce the issue in time and the issue gets closed but you can reproduce the issue afterwards, feel free to create a new bug report with up-to-date information by following this link: https://github.com/nextcloud/server/issues/new?assignees=&labels=bug%2C0.+Needs+triage&template=BUG_REPORT.yml&title=%5BBug%5D%3A+

@szaimen szaimen added needs info 0. Needs triage Pending check for reproducibility or if it fits our roadmap and removed 1. to develop Accepted and waiting to be taken care of labels Jan 23, 2023
@nickvergessen nickvergessen added 1. to develop Accepted and waiting to be taken care of 26-feedback and removed needs info 0. Needs triage Pending check for reproducibility or if it fits our roadmap labels Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop Accepted and waiting to be taken care of 26-feedback bug feature: files
Projects
None yet
Development

No branches or pull requests

3 participants