Skip to main content
Adobe Photoshop Family

Champion

 • 

5K Messages

 • 

91.8K Points

Sat, Aug 25, 2018 3:47 PM

Solved

Lightroom SDK: LrApplication.developPresetFolders() returns buggy fake folders

In LR 7.5, the array returned by LrLrApplication.developPresetFolders() includes buggy fake folder objects intended to represent separator rows in the user interface.  Invoking folder:getPath() on one of these bogus objects raises the internal error:
?:0: attempt to index field '_pathForFolder' (a nil value)
This affects any plugin that attempts to access the develop preset folders. In particular, it broke a DxO plugin and my own Fix Presets plugin (which fixes many other preset bugs):

https://forums.adobe.com/thread/2528220
https://feedback.dxo.com/t/export-to-dxo-broken-after-update-to-lr-7-5/4514
https://forums.adobe.com/thread/2527232
http://www.johnrellis.com/lightroom/fixpresets.htm

The workaround is to detect such bogus objects by calling folder:getPath() and trapping any error with pcall().

Details:

Here are the results of calling folder:getName() on the array of preset folders:



Note that the bogusly named folders correspond to the presence of separate rows in Develop's Preset panel.

Here's the result of calling folder:getPath() on the second (bogus) array element:





Responses

Official Solution

Employee

 • 

85 Messages

 • 

1.8K Points

2 years ago

Hi John,

Thanks for reporting this. It is indeed a bug in 7.5 and we will fix it in next release. In the meanwhile, as you mentioned you can use pcall to trap the error or you can skip any folder name with value "__@@ThisIsASeparatorRow@@__".

Thanks,
Chinoy

Official Solution

Adobe Administrator

 • 

7.9K Messages

 • 

114.9K Points

2 years ago

Greetings, 

The Lightroom Classic CC was updated today and contains a fix for this issue. Please download the new version and give it a try and let us know how it works.

Adobe Photography Products

Quality Engineering - Customer Advocacy 

Champion

 • 

5K Messages

 • 

91.8K Points

2 years ago

Thanks for the update.

4 Messages

 • 

154 Points

2 years ago

17 Messages

 • 

284 Points

2 years ago

I now know why I am unable to transfer files from Lightroom CC Classic to DxO Photolab!
I have to say that this is not the first time an upgrade to Lightroom has broken the plugin.

587 Messages

 • 

11.2K Points

2 years ago

Patrick,

See the DxO forum for a temporary fix.

https://feedback.dxo.com/t/export-to-...

1 Message

 • 

80 Points

2 years ago

If you are not a programmer and this thread is too technical, you can simply use the Adobe Creative Cloud app to download Lightroom Classic CC ver. 7.4.  All will be well and you can wait for the fix to come out while continuing to work. Just click on the down arrow in the "open" box and select version 7.4.  Let it install.  Ignore update prompt.

Champion

 • 

5K Messages

 • 

91.8K Points

2 years ago

This is fixed in my LR 8.0, thanks.

1 Message

 • 

60 Points

2 years ago

I still havent seen an update to LR classic CC v8.0 in my CC App.  I have tried to check updates multiple times - is this being pushed one user at a time :-)?  Options?

Champion

 • 

5K Messages

 • 

91.8K Points

Try logging out of the Creative Cloud desktop app and then back in. That often pokes it into showing you updates.

97 Messages

 • 

1.8K Points

If I remember correctly, <Ctrl>R (on Windows) in the CC application.will usually make the update appear.

Adobe Administrator

 • 

7.9K Messages

 • 

114.9K Points

Close.  [Ctrl/Cmd]+[Alt/Opt]+[ R ]

Note: If your OS Is not supported, you won't see the install option in the Creative Cloud App.

Adobe Photography Products

Quality Engineering - Customer Advocacy