Lightroom Classic: Do not collapse working folders after moving

  • 2
  • Idea
  • Updated 2 months ago
  • (Edited)
I ran the update to Lightroom Classic CC today. Currently running 8.4. There is new behavior today that is repeatable, and annoying. 

I have 2 drives that I work from. One is on my C: drive, and is my pictures folder. I have a secondary drive as well, which is the archive for photos after I'm done working. My workflow is:
  1. Import photos into Lightroom. This copies to my pictures folder, creating a Year/YYYY-MM-DD folder. This works great.
  2. I work on the photos while local. Export, etc.
  3. Finally, I drag the folder to the archive folder on my secondary drive. This process involves expanding several levels of folders to find the location where I store. (t:\photographs\2019, for instance.
The move works successfully, but after the move Lightroom collapses the folder structure for my C: drive, and collapses the folder structure for my T: drive. I'm left as if I hadn't expanded any folders at all.

I work with a lot of people training on Lightroom in my camera club. Many are confused about file structure, and file handling. Rolling up and putting away the folder structure is annoying to me, but would be very confusing to the less technical. This behavior is brand new in this version.

Photo of Geoff Faulkner

Geoff Faulkner

  • 35 Posts
  • 10 Reply Likes

Posted 2 months ago

  • 2
Photo of Sunil Bhaskaran

Sunil Bhaskaran, Official Rep

  • 439 Posts
  • 151 Reply Likes
Geoff,
Does the problem persist, even after a system restart? I tried to reproduce on a Win 10.
But couldn't.

Thanks,
Sunil
Photo of Platt Johnson

Platt Johnson

  • 1 Post
  • 0 Reply Likes
There are a lot of things like this. Generally speaking the user interface should never automatically change. It should always take user input to change.
I have Win 10 but there appear to be so many issues with this upgrade that I am not doing it yet.
Photo of Geoff Faulkner

Geoff Faulkner

  • 35 Posts
  • 10 Reply Likes
Yes, it is still a problem, even after rebooting. I setup a recording and it didn't roll up the C: drive this time, but it did roll up the T: drive. The behavior is inconsistent.

Here is the recording: https://1drv.ms/v/s!AogPqZ6mJBkXzYUl1uCeCsymGM2CNg?e=hjHHQG

Geoff