Difference between revisions of "Nextcloud/issues"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
==UI Design Problems==
 
==UI Design Problems==
* When looking at the "deleted files" list:
+
There are a ''lot'' of issues with the design of the desktop and mobile apps, which I haven't even begun to catalog; this list is so far just about the web UI.
** No way to change the sorting (always starts with ''oldest first'', which doesn't make sense even as a default)
+
===Deleted files===
** No way to mass-restore files (by date, file mask, deletion source)
+
* No way to change the sorting (always starts with ''oldest first'', which doesn't make sense even as a default)
** No information about which user/client/IP deleted them.
+
* No way to mass-restore files (by date, file mask, deletion source)
*** The "Activity log" does indicate which user, but gives no other info.
+
** This is more of a problem than it seems:
** When there's a problem restoring a file or folder, no information is given, not even which file/folder had the problem.
+
*** Each restore takes several seconds.
*** There's just a drop-down which says "Error while restoring file from trashbin".
+
*** You can initiate multiple restores in parallel (just click "restore" for all the visible files on the screen), but this seems to be one source of the unspecified errors; if you wait between files, the errors seem to go away.
** No way to bulk-upload files from a backup (if web-based restore fails)
+
* No information about which user/client/IP deleted them.
** No way to clear the useless list of "error while" errors. The restore process is just badly designed overall.
+
** The "Activity log" does indicate which user, but gives no other info.
** If the user tried to restore a file and it failed, there should be some kind of visual indication of that (so you don't keep trying the same files).
+
* No information about the original path for a deleted file.
 +
** Are they even being restored to the right folders? I ''think'' so, but there are no cues to tell me this -- and if I don't know where a file is being restored to, it's difficult to find it (after restoration) to be sure.
 +
* When there's a problem restoring a file or folder, no information is given, not even which file/folder had the problem.
 +
** There's just a drop-down which says "Error while restoring file from trashbin".
 +
* No way to bulk-upload files from a backup (if web-based restore fails)
 +
* No way to clear the useless list of "error while" errors. The restore process is just badly designed overall.
 +
* If the user tried to restore a file and it failed, there should be some kind of visual indication of that (so you don't keep trying the same files).
 +
 
 +
About the only thing they got right was to make restoring one file a single-click operation. Why not also have checkboxes and an "actions" menu, as in the main Files app? (Addendum: there ''are'' checkboxes, but no action menu -- so the checkboxes don't actually ''do'' anything.)

Latest revision as of 14:45, 12 August 2021

UI Design Problems

There are a lot of issues with the design of the desktop and mobile apps, which I haven't even begun to catalog; this list is so far just about the web UI.

Deleted files

  • No way to change the sorting (always starts with oldest first, which doesn't make sense even as a default)
  • No way to mass-restore files (by date, file mask, deletion source)
    • This is more of a problem than it seems:
      • Each restore takes several seconds.
      • You can initiate multiple restores in parallel (just click "restore" for all the visible files on the screen), but this seems to be one source of the unspecified errors; if you wait between files, the errors seem to go away.
  • No information about which user/client/IP deleted them.
    • The "Activity log" does indicate which user, but gives no other info.
  • No information about the original path for a deleted file.
    • Are they even being restored to the right folders? I think so, but there are no cues to tell me this -- and if I don't know where a file is being restored to, it's difficult to find it (after restoration) to be sure.
  • When there's a problem restoring a file or folder, no information is given, not even which file/folder had the problem.
    • There's just a drop-down which says "Error while restoring file from trashbin".
  • No way to bulk-upload files from a backup (if web-based restore fails)
  • No way to clear the useless list of "error while" errors. The restore process is just badly designed overall.
  • If the user tried to restore a file and it failed, there should be some kind of visual indication of that (so you don't keep trying the same files).

About the only thing they got right was to make restoring one file a single-click operation. Why not also have checkboxes and an "actions" menu, as in the main Files app? (Addendum: there are checkboxes, but no action menu -- so the checkboxes don't actually do anything.)