| Age | Commit message (Collapse) | Author |
|---|
|
This relates to https://github.com/owncloud/docs/issues/618.
|
|
These issues were identified by @lazawan in
https://github.com/owncloud/docs/issues/618.
|
|
added removing the client
|
|
added a reference to the document describing removing the remnants of the windows client
|
|
It does not appear to support variadic lambda
|
|
so many manual steps here ... .sigh.
|
|
Users can rename a file *and* add/remove the vfs suffix at the same time
leading to very complex sync actions. This patch doesn't add support for
them, but adds tests and makes sure these cases do not cause unintened
behavior.
The rename will be propagated, but the users's hydrate/dehydrate request
will be ignored.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This was not required with 2.5 because a size of 0 was ignorted when comparing
size by the csync updater, to be compatible with very old version of the database.
But the we discovery will still think the file is changed if the database contains
a size of 0
|
|
Implements https://github.com/owncloud/core/pull/31851
|
|
|
|
owncloud/603-remove-merge-conflict-markers-in-troubleshooting-guide
[#603] - Remove merge conflict markers in the troubleshooting appendix
|
|
|
|
This fixes https://github.com/owncloud/docs/issues/603 and also cleans
up the file so that it renders correctly.
|
|
|
|
It seems that sometimes the tray implementation isn't ready on system
startup. Retrying later seems to not help. Delaying the start of the
client is the workaround that people have reported as effective.
|
|
|
|
|
|
|
|
It still reads and writes the old format too, but all newly stored
client certs will be in the new form.
For #6776 because Windows limits credential data to 512 bytes in older
versions.
|
|
Previously it depended on addFolder() / removeFolder() calls to adjust
watchers when new folders were added or removed. There also needed to be
complex move handling.
Now, any folder creation/move-in notifications automatically trigger
watcher additions and folder deletion/move-out triggers removal.
|
|
By default, plugins are only searched next to the binary or next to the
other Qt plugins. This optional build variable allows another path to be
configured.
The idea is that on linux the oC packaging probably wants the binary in
something like /opt/owncloud/bin and the plugins in
/opt/owncloud/lib/plugins.
Similarly, distribution packagers probably don't want the plugins next
to the binary or next to the other Qt plugins. This flag allows them to
configure another path that the executable will look in.
|
|
reference to brand-items.php added for keep in sync warning.
|
|
Qt-5.12.1 is more relevant than Qt-5.10.1 these days.
|
|
|
|
|
|
When owncloud is started during desktop startup the tray may not yet
be running when the client starts. This will make the client attempt
to create a tray icon again after 10 seconds if there's no tray
during initial startup.
|
|
This makes sure that the conflict list can be updated if a user resolves
a conflict by deleting the local conflict file. Previously one had to
wait for the next sync run.
|
|
There was a period of time between local discovery of a new folder and
the folder receiving a filesystem watcher. Any changes to its contents
during that time were missing, leading to misbehaviors.
|
|
Previously it gave up if "expiry required" was enabled. Now it'll create
a link share per day with the default expiry for these setups.
|
|
The location in windows FS was missing, so I added it.
|
|
From issue #7015, the code is wrong because the path is the file system path and
not the path on the DB.
But since this is a conflict, this means the reconcile will still want to download
the file from the server next sync, so we need not to worry about this case
|
|
This could fix a problem where the client incorrectly decides to delete
local data.
Previously any sqlite3_step() return value that wasn't SQLITE_ROW would
be interpreted as "there's no more data here". Thus an sqlite error at a
bad time could cause the remote discovery to fail to read an unchanged
subtree from the database. These files would then be deleted locally.
With this change sqlite errors from sqlite3_step are detected and
logged. For the particular case of SyncJournalDb::getFilesBelowPath()
the error will now be propagated and the sync run will fail instead of
performing spurious deletes.
Note that many other database functions still don't distinguish
not-found from error cases. Most of them won't have as severe effects on
affected sync runs though.
|
|
|
|
|
|
For issue #7054
|
|
|
|
They are always rebuilt due to the switch to msvc.
|
|
|
|
Previously they were detected as DELETE+NEW because if "a" is renamed to
"A" then QFile::exists("a") will still return true on Windows.
|
|
doExpand() is called when the selective sync editing mode is enabled in
the folder settings view. Previously it'd set the expansion to be
exactly the root items. Now, it just expands any root items that are
currently collapsed, leaving all other item expansion unchanged.
|
|
Since the rename is triggered by the client process the folder watcher
didn't pick up on it on OSX.
This does not need to be merged into master.
|
|
Due to QTBUG-73947 and #7020.
Use OWNCLOUD_HTTP2_ENABLED=1 to enable anyway.
|
|
Previously it'd handle all verbs as if they were our own.
|
|
|
