Skip to main content
Inspiring
April 19, 2012

P: Creating Directories in Inappropriate Locations ~/Documents

  • April 19, 2012
  • 48 replies
  • 3647 views

Adobe Lightroom 4 is annoyingly creating a directory in ~/Documents on Mac OS X. For example: /Users/smith/Documents/Adobe. Contained within this Adobe directory is an empty directory named "dynamiclinkmediaserver". This is an inappropriate place to create files or directories of this nature. OS X has other directories that can and should be used for settings, preferences, temporary files, and others of similar nature.These two directories are created every time that Lightroom 4 is launched, even after deletion. Please avoid creating these directories in ~/Documents and put them somewhere else in future patches and versions of Lightroom. I look forward to this annoyance being squashed. Thanks, and keep up the good work otherwise.

48 replies

johnrellis
Legend
October 14, 2024

"However, it can be a little confusing if, as in my case, the previous name - which was system generated - included the version number '13-4'"

 

Agreed. Overall, I think the new design will be less confusing to most users, once we get through the transition period of the old naming system.

 

Note that there is a new command File > Rename Catalog that makes it much easier to rename catalogs. I've got my own naming conventions, and it makes the upgrades much easier.

Participant
October 14, 2024

Ah, so the default catalog name after updating to 14.0 is the same as the catalog it replaces? Fair enough! However, it can be a little confusing if, as in my case, the previous name - which was system generated - included the version number '13-4'. I assume the correct course of action is to override the default name, by either removing the string '13-4' from the filename, or replacing it with '14-0'. Personally I think it's useful to see from the name which catalog format is being used.

johnrellis
Legend
October 14, 2024

@Street W ise: "Just noticed that when upgrading to 14.0. LR Classic zips the old 13-4 and creates a new catalog with default name also of 13-4. I suspect this is a bug, it should be 14-0 to reflect the version of LR."

 

This is by design. LR 14 changes the way catalog upgrades work, no longer appending the version number:

https://www.lightroomqueen.com/whats-new-in-lightroom-2024-10/

Participant
October 14, 2024

Just noticed that when upgrading to 14.0. LR Classic zips the old 13-4 and creates a new catalog with default name also of 13-4. I suspect this is a bug, it should be 14-0 to reflect the version of LR.  Anyway it's easy to fix via the Rename Catalog. 

Rikk Flohr_Photography
Community Manager
Community Manager
October 14, 2024

@Street W ise  

It should be safe to delete. I recommend renaming it and verifying that things are okay before permanently deleting it. 

Rikk Flohr: Adobe Photography Org
Participant
October 14, 2024

Thanks for the fix and letting us know. I note that after updating to the latest versions of my CC apps, the Adobe folder is still present in the MyDocuments folder.

  • Can you confirm that it is safe to delete this folder?
  • What is the location of the new folder?

Thanks in advance

Rikk Flohr_Photography
Community Manager
Community Manager
October 14, 2024

Greetings all, 

 

A new update for Adobe Photography Products has been released.  The October (MAX) update contains an update for this issue. 

If you do not see the update in your Creative Cloud Application, you can refresh it by hitting [Ctrl/Cmd]+[Alt/Opt]+[ R ].

Note: It may take up to 24 hours for your update to be available in your Creative Cloud app.

 

Thank you for being so patient.

Rikk Flohr: Adobe Photography Org
Participant
October 8, 2024

It seems incredible that a billion dollar company can't instruct an engineer to fix the location of a folder. 

Uhl
Inspiring
December 27, 2023

Adobe, log files also don't belong in one's Documents folder. Please also move LrClassicLogs to a more appropriate location:

 

Uhl
Inspiring
November 1, 2023

Wow, I can't believe this has been an issue since 2012! 🙀