Lightroom: Drag and drop in folders not working

  • 1
  • Problem
  • Updated 2 years ago
  • (Edited)
when using the drag and drop in the folders inside of lr (to organise the folders and to make sure lr does not lose track of the images) it stops working after 2 succesful drag and drops. It can be done outside of lr and then update the folder location but that is much more work and when helping others who understand LR less it is very tedious. LR CC
Photo of kitty van gemert

kitty van gemert

  • 4 Posts
  • 0 Reply Likes
  • frustrated

Posted 2 years ago

  • 1
Photo of Harold P Anderson

Harold P Anderson

  • 12 Posts
  • 3 Reply Likes
Make sure you are dragging by the image and not by the border that surrounds it.
Photo of kitty van gemert

kitty van gemert

  • 4 Posts
  • 0 Reply Likes
This is not about images it is about dragging and dropping folders inside the folderstructure thats not working
Photo of Harold P Anderson

Harold P Anderson

  • 12 Posts
  • 3 Reply Likes
Ah...sorry.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3694 Posts
  • 963 Reply Likes
Please do Help > System Info and report the exact version you are running and version of Windows or Mac.
Photo of kitty van gemert

kitty van gemert

  • 19 Posts
  • 2 Reply Likes
lr cc 2015.5 and it happened on Mac El capitan and Windows 8
Photo of John R. Ellis

John R. Ellis, Champion

  • 3694 Posts
  • 963 Reply Likes
I'm not able to reproduce the problem in my LR 2015.5 / OS X 10.11.4 -- I can freely drag subfolders around in the hierarchy (many more than two times).   Can you make a QuickTime movie of your LR window, demonstrating the problem?
Photo of kitty van gemert

kitty van gemert

  • 4 Posts
  • 0 Reply Likes
i have a video of it yes but not sure how to add it?
Photo of Robert Cullen

Robert Cullen

  • 145 Posts
  • 40 Reply Likes
You have a 2016 sub-folder in a 2016 parent folder! Folder 2016-03-13 thinks it is already in a folder 2016! I think your OS would be confused by this.
You may have to do some folder shifting in Finder/File Explorer, then Update folder locations in LR.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3694 Posts
  • 963 Reply Likes
Kitty, thanks for posting the video -- it provides great detail of what's happening.  At first I thought Robert's observation was the cause (folder "2016" inside a parent folder "2016").  But I poked around more and believe that's a red herring. 

When you drag-and-dropped the folder and the Moving Files On Disk dialog appeared, did you cancel the dialog by hitting Cancel?  When you hit Cancel, you can no longer drag-and-drop that folder onto any other folder, until you restart LR.   I've filed a bug report on that behavior: https://feedback.photoshop.com/photoshop_family/topics/lightroom-cancelling-a-folder-drag-and-drop-p...

Try restarting LR and then dragging folders again. 
Photo of kitty van gemert

kitty van gemert

  • 19 Posts
  • 2 Reply Likes
Thanks for your reply. That cancel part is new to me. I would have to back in the chat for both issues to see if a cancel happend. Will let you know about that when i find it (both chats are over 2000 comments each so might take a while to find it). I personally wonder if the 2016 inside 2016 folder is an issue as i had it happen a third time recently. It confuses lr completely i think. The way around it is just time consuming (either in finder/explorer or adding extra drags and drops) so info on what causes this is much appreciated and sought after. Last instance was a2016 parent folder with an April 08 folder that had nstd 2 layers down an April 8 folder. Moving it up was not possible, even after renaming it to April 7 (but did not restart lr after the renaming, maybe that would have fixed it).
Photo of John R. Ellis

John R. Ellis, Champion

  • 3694 Posts
  • 963 Reply Likes
I tried replicating the "2016" folder structure in your video and couldn't reproduce the problem after numerous tries (on both Mac and Windows).  So if there is another problem you're encountering unrelated to canceling, there must be some additional context we don't understand.    That structure certainly wouldn't confuse Mac or Windows operating systems -- any problem would be specific to LR.

Without the ability to reproduce the bug, Adobe is unlikely to pay attention, unfortunately.