should make sure that the debug archive has a correct up to date view of
the sync client database
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
let unexpected new folders in read-only folders be read-write
would be done for folders that are inside a read-only folder and cannot
be uploaded because the parent folder is realy read-only
most probably those folders should never have been there
in case they would be read-only, users cannot delete them, in such
situation, letting them be read-write again should really help
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
sometime we need to create a folder on server because some local files
or folders modifications would be lost without that
in that case instead of locally deleting teh folder, we create it back
on server
when doing that, it is important to check the remote permissions such
that we do not try to create a folder in a read-only folder on server
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
in the contextual menu shown in files explorer will show encrypt menu
entry only for top folders that are non-encrypted and empty
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
with current end-to-end encryption only top folders can be encrypted
limit the availability of the menu entry to top folders
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
if a folder is read-only, when deleting content inside this folder, it
may be needed to make it temporary read-write
do this as required by the automated tests
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
the bckground of buttons on teh top bar of main dialog had a wrong color
not matching the top bar background color
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
with transparent backgrounds, most of teh time the result is hard to
read
that is mostly unintended and unless there is some blur added, the UI
becomes unusable
Close https://github.com/nextcloud/desktop/issues/6992
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
when receiving a shell integration socket command for ENCRYPT, a generic
interface and generic code paths was used
the assumption was that the listener socket would need (and remain)
valid while hanlding teh request
some code paths need to display error messages to the user via a
QMessageBox
the issue is that this will execute a Qt event loop that will handle the
socket disconnection while the socket variable from the caller seems it
will stay valid and alive
prevent that by not using a blocking method invocation such that life
time mishandling about the socket listener is not possible
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
we use the proper method from QByteArray to forward the data received by
GETFileJob to the socket connected to teh fetch data CfApi callback
Close https://github.com/nextcloud/desktop/issues/6769
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
- Never display "please wait" to users.
- Only start displaying status starting at 1. e.g. "0 f 6 files" => "1 of 6 files"
- Improve text for FolderStatusDelegate::FolderSyncText.
- Reconciling => Syncing.
- Syncing => Sync.
Signed-off-by: Camila Ayres <hello@camilasan.com>
