Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Mac - Old drives and folders cannot be deleted from catalog.

In the works
Jack W
Admin
  • Edited

When using a referenced catalog and deleting some folders from the library tool, they disappear but then reappear when opening the application. 

We've reproduced the issue and we're working on a fix. 

 

AZ#157291

0

Comments

6 comments

Date Votes
  • Official comment
    Thodoris Chorianopoulos
    Admin

    There is a separate post in the section for Win environment .

  • AJ Saulsberry

    Hi, Sorry, it looks like this issue is still outstanding in 16.2.0.1353.

    The "old" drive appears when you open C1 16.2.0 for the first time, then if you "Locate" the drive (or the top-level folder in the directory structure) at the new drive letter location the Locate process works correctly and the old drive is removed. But when you close and reopen C1 the old drive is back. 

    This also applies to deleting a drive with no folders or images in the catalog. 

    Perhaps it will help to note that the drive with the target images has just moved to a new drive letter and the structure hasn't changed, which is different set of circumstances than moving a directory structure to a new location on the same drive or to a different drive when both the original and target drives are still connected.

    Thanks and good luck with this.

    0
  • Jack W
    Admin

    Hi AJ Saulsberry - you're 100% correct and sorry for providing false information. I've corrected the post.

    0
  • Gary Blessington
    • Edited

    This is happening on PC too. Version 16.2.1.1384

    I have two drives showing (0 images on both drives), which I can remove, but they reappear when I reload the catalog.

    Both of these drives are where the catalog *used to* reside at some point.

    1
  • AJ Saulsberry

    The issue I reported is also related to Windows 10 and 11. Not sure if it coincides with a macOS issue or the issue title is just a typo, but it has been a consistent behavior through several C1 releases, including 16.2.1.1384. 

    1
  • David Edge

    Certainly happened to me on Mac, but I got round it by importing the catalogue into another. Obviously stops you working for a day or two and requires swathes of disk space, but it was a successful workaround.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post