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

VFS. Display local file name clash error when syncing in VFS mode. #3239

Merged
merged 1 commit into from
May 5, 2021

Conversation

allexzander
Copy link
Contributor

@allexzander allexzander commented Apr 30, 2021

Signed-off-by: allexzander blackslayer4@gmail.com

This fixes #3198

@@ -434,6 +438,11 @@ void PropagateDownloadFile::startAfterIsEncryptedIsChecked()
_item->_type = ItemTypeFile;
}
if (_item->_type == ItemTypeVirtualFile) {
if (propagator()->localFileNameClash(_item->_file)) {
done(SyncFileItem::NormalError, tr(localFileNameClashMessage).arg(QDir::toNativeSeparators(_item->_file)));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Won't work for translations, you need to have the string literal inside the tr(). Yes, that means having it twice in the source code, it's not too bad for user visible strings, they tend to diverge over time anyway.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@er-vin Indeed. Thanks. Fixed, and, squashed everything already. Not a huge change anyways so should be easy to see the difference.

@allexzander allexzander force-pushed the bugfix/vfs-local-name-clash-error branch from 231b970 to 54a4280 Compare April 30, 2021 15:52
@allexzander allexzander requested a review from er-vin May 3, 2021 06:48
Copy link
Collaborator

@mgallien mgallien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks

@allexzander
Copy link
Contributor Author

/rebase

Signed-off-by: allexzander <blackslayer4@gmail.com>
@github-actions github-actions bot force-pushed the bugfix/vfs-local-name-clash-error branch from 54a4280 to 1952221 Compare May 5, 2021 17:35
@nextcloud-desktop-bot
Copy link

AppImage file: Nextcloud-PR-3239-19522210acf38a44ea77f48a7443954525485e26-x86_64.AppImage

To test this change/fix you can simply download above AppImage file and test it.

Please make sure to quit your existing Nextcloud app and backup your data.

@allexzander allexzander merged commit f66add8 into master May 5, 2021
@allexzander allexzander deleted the bugfix/vfs-local-name-clash-error branch May 5, 2021 17:43
@allexzander
Copy link
Contributor Author

/backport to stable-3.2

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

Successfully merging this pull request may close these issues.

Client 3.2 VFS "Couldn't create placeholder info"
4 participants