I've been using CloudBerry Explorer infrequently for a while, as a long-term archive of large files. Today I went to do that again, and noticed something that I don't remember from before.
In the left-hand pane I have a folder on the local machine; on the right, a folder in a Glacier. I drag a file from the left to the right, and get a warning:
File thefile.ext already exists. Would you like to overwrite it?
The thing is, the file does NOT exist in the Glacier yet. If I click "Yes" to overwrite it, the copy happens as expected. Bug? Or am I not understanding something?
Ah. Maybe the message should suggest that this might be the case, since it was, well, wrong? I'm still confused that it made the claim, since it had NEVER been true, so why would it even suspect it? Better would be something along the lines of "Inventory out of date--CloudBerry Explorer cannot determine whether file already exists; click 'Get Inventory' to be sure".
Hmm, there's nothing in the Help about Get Inventory. Seems wrongish?
Ah. Maybe the message should suggest that this might be the case, since it was, well, wrong? I'm still confused that it made the claim, since it had NEVER been true, so why would it even suspect it? Better would be something along the lines of "Inventory out of date--CloudBerry Explorer cannot determine whether file already exists; click 'Get Inventory' to be sure".
Hmm, there's nothing in the Help about Get Inventory. Seems wrongish?
Ouch, clicked "Get Inventory" and it says "Preparing inventory" and "approx. 5 hours left". OTOH it also says "100%" so I'm confused.
It's not really clear why you receive this error message, so the best way would be to update to the latest version, reproducing the issue and sending the logs to our support team in case it persists after refreshing inventory via tools > diagnostic menu. You can refer to this forum thread in the issue description when sending diagnostic archive.
Thanks for the update! Do you happen to know when the next update will be? Like is it days or weeks away? I'm just wondering if I should work around it for now or wait until it's fixed. Thanks again.
I will be able to share this info tomorrow, check this page from time to time regarding the update. I also have to note that i can only share approximate ETA as it all requires development and testing and the time-frame could shift drastically.