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
When I view folders of a S3 storage via the browser in Cyberduck, content is missing. If I use Go to folder and type the name of the S3 bucket followed by the folder name then I can see at least some of the content in the folder (the same folder that wasn't visible in Browser in Cyberduck). If I then type the subfolder name of one of the folders missing inside that folder then again I can see some content of the content of that folder and again need to use Go to folder to browse into the missing subfolder in that folder. Is there some limit inside Cyberduck that prevents me from using it unless I already know all the folders in S3?
The text was updated successfully, but these errors were encountered:
Someone more experienced with Cyberduck pointed out that I should select Show Hidden Files to see these folders. For S3 storage what does Show Hidden Files mean? These folders aren't marked as deleted, are publicly accessible and are shown in the AWS S3 web view of the content. When selecting Show Hidden Files in Cyberduck, the older version of the folder is shown as of kind file with a black rectangle as an icon and the latest version is shown as of kind folder and can be expanded to see more content.
When I view folders of a S3 storage via the browser in Cyberduck, content is missing. If I use Go to folder and type the name of the S3 bucket followed by the folder name then I can see at least some of the content in the folder (the same folder that wasn't visible in Browser in Cyberduck). If I then type the subfolder name of one of the folders missing inside that folder then again I can see some content of the content of that folder and again need to use Go to folder to browse into the missing subfolder in that folder. Is there some limit inside Cyberduck that prevents me from using it unless I already know all the folders in S3?
The text was updated successfully, but these errors were encountered: