You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug Description
Folders in Backblaze buckets are really a bunch of files sharing the same parent path. Cyberduck does a great job representing folder hierarchies as "folders" in a file tree.
The bug is that Cyberduck does not show folder create/modified dates, so users cannot sort their root bucket/folder content by date. Instead it just shows "Unknown"
To Reproduce
Connect Cyberduck to any S3 bucket that has folders with files in them.
Expected behavior
The "Modified" column should populate with a date the folder was create/modified. Recognizing that "folders" don't actually exist and Cyberduck is creating the hierarchy based on file paths, the date should show as the date the last file was modified within that path/folder.
Screenshots
**Desktop **
OS: Windows 10
Cyberduck Version 8.9.0
Backblaze B2
The text was updated successfully, but these errors were encountered:
dkocher
changed the title
Backblaze B2 "Folders" don't show date created/modified
Shows last modification date of containing files for folder
May 29, 2024
Bug Description
Folders in Backblaze buckets are really a bunch of files sharing the same parent path. Cyberduck does a great job representing folder hierarchies as "folders" in a file tree.
The bug is that Cyberduck does not show folder create/modified dates, so users cannot sort their root bucket/folder content by date. Instead it just shows "Unknown"
To Reproduce
Connect Cyberduck to any S3 bucket that has folders with files in them.
Expected behavior
The "Modified" column should populate with a date the folder was create/modified. Recognizing that "folders" don't actually exist and Cyberduck is creating the hierarchy based on file paths, the date should show as the date the last file was modified within that path/folder.
Screenshots
**Desktop **
The text was updated successfully, but these errors were encountered: