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

7 Votes
LEGEND ,
Aug 25, 2018 Aug 25, 2018

Copy link to clipboard

Copied

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:

RackMultipart2018082536816b11n-88fba7e7-2cc5-46d8-b6e1-a5e00263fec2-1226163259.png

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:

RackMultipart2018082529639s8lp-48e6c633-6dbf-49de-90ed-69212d0e72af-56975145.png



Bug Fixed

Views

12

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 2 Correct answers

Adobe Employee , Oct 15, 2018 Oct 15, 2018
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.

Votes

Translate

Translate
Adobe Employee , Aug 25, 2018 Aug 25, 2018
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

Votes

Translate

Translate
12 Comments
Adobe Employee ,
Aug 25, 2018 Aug 25, 2018

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
LEGEND ,
Aug 25, 2018 Aug 25, 2018

Copy link to clipboard

Copied

Thanks for the update.

Votes

Translate

Translate

Report

Report
Explorer ,
Aug 26, 2018 Aug 26, 2018

Copy link to clipboard

Copied

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 27, 2018 Aug 27, 2018

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Advocate ,
Aug 27, 2018 Aug 27, 2018

Copy link to clipboard

Copied

Patrick,

See the DxO forum for a temporary fix.

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

Votes

Translate

Translate

Report

Report
LEGEND ,
Aug 27, 2018 Aug 27, 2018

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Oct 15, 2018 Oct 15, 2018

Copy link to clipboard

Copied

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.
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
LEGEND ,
Oct 15, 2018 Oct 15, 2018

Copy link to clipboard

Copied

This is fixed in my LR 8.0, thanks.

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 09, 2018 Nov 09, 2018

Copy link to clipboard

Copied

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?

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 09, 2018 Nov 09, 2018

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Engaged ,
Nov 10, 2018 Nov 10, 2018

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Nov 11, 2018 Nov 11, 2018

Copy link to clipboard

Copied

LATEST
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.
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report