Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
Dropbox is Changing the file name to UPPERCASE letters
Sometimes filenames in my Dropbox folder(s) are changed to UPPERCASE letters. Seemingly random, but probably isn't :) I can see from the version history that the file has been renamed (changing f...
Weird thing, but I will have to stick to the workaround then. Thanks!
Hi all,
I just had yet another file case changed by Dropbox, however this time I'm absolutely sure it was changed by Dropbox, because the file is part of a script, and is referenced by a piece of code with its original name.
I filed a ticket under Ticket #9720408
The chat assistance was not helpful, this is all really scary and I'd like to get a feedback from you guys other than "Dropbox won't do that".
I'm absolutely positive that it happened, and if you cannot demonstrate why and how it will quickly be fixed, I'll have to let go of your - otherwise very helpful - service.
- Daphne
Dropbox Community Moderator
Hey there ben p.11,
Just to note, I've merged your post here as it seems your issue is similar to the one discussed here.
To start off, could you please just let me know what OS systems you're using when accessing your Dropbox files via the desktop app? Also, if you check the version history of the file and are able to locate where the rename took place, can you see which device this change was made from?
Let me know what you find and we'll go from there - thanks!
I'm using Dropbox for linux under ubuntu 18.04 as per your instructions here : https://www.dropbox.com/fr/install-linux
The version history is worthless, not mentioning the current state of the file.
My problem is NOT SOLVED. I think moving my post to a solved topic is not good practice.
- Daphne
Hey ben p.11,
I understand that for you this isn't solved, however this helps us to keep all relevant information in one place.
I located your open ticket with our Support team and passed along your comments here, and I'd advise to continue working on this with our specialist as you'd need to discuss account specific info for further investigation.
Unfortunately, as this is a public forum I wouldn't be able to look into this with you in nearly as much detail as I don't have access to the necessary info, and we wouldn't be able to discuss sensitive info here.
Sorry that I can't be of much more help here, but please don't hesitate to get back to the specialist with any further info or questions you have as they are better suited to assisting you with getting to the bottom of this.
Thanks!
I'll just add what we found on this issue yesterday on our Windows sytem (what's shown on dropbox.com agrees with what's local):
A number of dirs and even some files changed case on a mass scale, and quickly, definitely by DB itself.
For example:
Rssc Invoices --> RSSC Invoices
Bylaws_Final_Unsigned.docx --> Bylaws_Final_UNsigned.docx
After much discussion, we determined what DB did: out of the blue reverted months-old changes that we made to the case of some dirs and files.
At different times early in the year, we corrected/changed the case of some dirs and files, two of which are shown above. In those cases, we changed "RSSC" to "Rssc" and "UNsigned" to "Unsigned." Just to pick those two examples out of the many involved. Dropbox then yesterday decided to undo those almost-forgotten changes througout our file structure.
Hopefully this bug can be found. And let's pray that DB never undoes renames where more than the case changes.
- Jane
Dropbox Staff
There are only two devices joined (I checked in the Security section), and they're both synced 24x7, so that wasn't it.
Directories don't have history, but I spot-checked some files that we know changed, and only old events are listed, nothing for the given day and the actions in question.
- Jane
Wasn't this already investigated via prior cases with others? Looking at those might show what the problem was and why it wasn't resolved. That would seem much easier than trying to go through the whole thing again each time with support.
- Jane
I didn't follow that answer for OP and didn't see it as a solution at all. The conclusion ("
It would basically be me saying: DB must have done it, and you saying "Impossible."
Getting back to your temp/TEMP example, while I understand what you're saying about the impossibility of files by those names existing in the same dir in Windows, that's beside the point. We're merely talking about a file changing from one thing to another thing as humans see it. So, temp->TEMP or whatever, which is perfectly legal and supported by everything, DB included. We're not talking about temp and TEMP coexisting, and we understand that at a non-human level there is no difference. Keep in mind also that what I saw, at least, was DB reverting old changes that we made, not just up and deciding to do this to random dirs/files.
Looking at Ben's case would make sense, since it already exists.
- Jane
