Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Publishing in Lightroom Classic, getting errors

New Here ,
Feb 08, 2024 Feb 08, 2024

I am trying to the Photoshelter plugin to publich images to my photoshelter account, but I am getting errors when trying to publish and/or synch.

 

For example, when trying to sync:

"./JSON4Lua.lua:207: Failed to scan constant from string <pre>Uncaught error: RedisException(Connection timed out) at starting position 1"

 

Or when trying to publish:

"An internal error has occurred: ./PhotoShelterUploadTask.lua:112: attempt to concatenate field 'status' (a nil value)"

 

how do I resolve these errors? The plugin is Photoshelters plugin: https://support.photoshelter.com/hc/en-us/articles/203373590-PhotoShelter-s-Adobe-Lightroom-Plug-in. I contacted Photoshelter and they say it is an issue with Adobe and NOT their plugin. I pointed out that their plugin states it is not compatible with newer versions of Lightroom Classic, but they still state that the plugin is working fine and that the error lies in Adobe.

 

How do I resolve these errors?

 

Thanks,
Jonathan

TOPICS
macOS
298
Translate
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
Community Expert ,
Feb 09, 2024 Feb 09, 2024

If Photoshelter states that their plugin is not compatible, then it is odd that they go back on this statement and claim it's Adobe.

 

-- Johan W. Elzenga
Translate
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
LEGEND ,
Feb 09, 2024 Feb 09, 2024

To build on Johan's reply, if the problem is with LR proper and not the plugin, then it is Photoshelter's responsibility to diagnose that and file a bug report with Adobe. Adobe isn't going to troubleshoot a third-party plugin and narrow down whether an unexpected error results from a bug in the plugin, the web service, or in LR itself -- Photoshelter has to do that work. 

 

If Photoshelter isn't willing to do that work, then consider finding another service that cares more about its customers and less about pointing fingers.

Translate
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
New Here ,
Feb 12, 2024 Feb 12, 2024

I appreciate this. However, how can I determine where the fault lies. Photoshelter is specifically saying it is an issue with Adobe. Are there errors indicative of an issue with the plugin or with the publishing service? I need some hard evidence to go back to either Adobe or photoshelter and provide proof it lies within their domain of work. Right now, I have everyone telling me it is the other guys fault.

 

I appreciate any insight!

jonathan

Translate
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
LEGEND ,
Feb 12, 2024 Feb 12, 2024
LATEST

"However, how can I determine where the fault lies. Photoshelter is specifically saying it is an issue with Adobe. Are there errors indicative of an issue with the plugin or with the publishing service? I need some hard evidence to go back to either Adobe or photoshelter and provide proof it lies within their domain of work. Right now, I have everyone telling me it is the other guys fault."

 

In general, it is usually very difficult for anyone except the plugin developer to determine whether the fault lies in LR or the plugin. For example, this error message:

"An internal error has occurred: ./PhotoShelterUploadTask.lua:112: attempt to concatenate field 'status' (a nil value)"

could arise either because an LR SDK API method is incorrectly returning a nil result, or (more commonly) due to a programming error in the plugin. Only a person intimately familiar with the plugin's implementation, using a Lua debugger, could determine which. Adobe certainly isn't going to invest the effort (they'd have to raise the price of LR significantly to cover their extra engineering costs).

 

The other error message you provide:

"./JSON4Lua.lua:207: Failed to scan constant from string <pre>Uncaught error: RedisException(Connection timed out) at starting position 1"

smells to me like a Photoshelter bug -- the Photoshelter server is returning an unexpected result from its Redis server, and the plugin is getting confused by that (Redis is popular open-source in-memory database used by many services). But that's just an educated guess.

 

Two more immediate points:

 

1. The plugin's download page:

https://support.photoshelter.com/hc/en-us/articles/203373590-PhotoShelter-s-Adobe-Lightroom-Plug-in 

 

says "this plugin is not compatible with Adobe Lightroom v12.4 and above.". Do the LR command Help > System Info to determine which version of LR you're running (the current version is 13.1). Did Photoshelter Support not raise this issue with you?


That they're not supporting LR 12.4 (released 6/13/2023) and later indicates they've stopped supporting the plugin.

 

2. I downloaded the version 1.12 of the plugin and poked inside it. One of your error messages mentions the source file "PhotoShelterUploadTask.lua", but there is no such source file in version 1.12. 

 

Do the command File > Plug-in Manager, select the Photoshelter plugin, and in the Status panel on the right, what version is displayed?  If it's not 1.12, you're running an older version of the plugin.  You could try installing 1.12, but Photoshelter says that's not compatible with newer versions of LR.

 

If Photoshelter didn't go through points 1 and 2 with you, that's more evidence that they're not serious about supporting their plugin.

Translate
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