Known Issues with my Plugins

Known Issues with Lightroom and/or my plugins...

SmugMug (Jun 13, 2018)

SmugMug seems to have turned off all production API servers for third-party apps like my plugin, except ones using a beta API. So, my plugin no longer works. )-:

(They announced the beta API four years ago, but I wasn't planning to consider it until it left the beta stage, which as of this writing it sill has not done.)

They announced the demise of the API my plugin uses a month ago, which is really short notice, but the brevity doesn't really matter because I didn't notice their announcement anyway. My bad.

Anyway, I'm scrambling to respond. Unfortunately, I'm in the same boat with other developers in that they simply ignore our questions, so it's difficult to move forward. )-:

Also, please see This FAQ for issues commonly encountered with my plugins.

The 30 most-recent comments (out of 542; see all), most recent last...

Hi Jeffrey, I am successfully using one of your other plugins with my (properly registered) installation of Lightroom CC, but the Metadata Wrangler plugin generates, immediately upon installation, the following error message in Plug-in Manager: “An error occurred while attempting to load this plug-in. The plug-in description script (Info.lua) is missing.” I haven’t done anything to the plugin file, nor modified Lightroom in any way. I have tried installing the plug-in in two separate folders, one of which is my Mac Desktop folder, and all other plug-ins (including your Custom Metadata plug-in) work fine. This is occurring with a download from your website as of today. Is there anything you can advise as to how I might troubleshoot this? Thanks!

I can only guess a corrupt install of some kind. Are you sure you’ve pointed the Plugin Manager at the right spot? It might be prudent to delete all copies of the plugin from your system (to make sure there’s no confusion about what copy is what), download the latest and unzip it (and perhaps peek in to confirm that there is indeed an “Info.lua” file, among many others), then re-point the plugin manager at it…. —Jeffrey

— comment by Brandon on June 28th, 2017 at 9:50am JST (11 months, 23 days ago) comment permalink

Unable to Export error
Error calculating automatic destination for “filename.dng” unbalanced ‘{‘ in “[Path:After=ImageLibrary\}”
Image Library\ is a folder name in the path to the filemane.dng. In fact the full path is “G:\ImageLibrary\Shared\2017\05-22_OR_Coast”
I’ll rollback to the prior release and see if this continues.

Oops, a case of unintended consequences for a different change. I’ve just pushed a fix. Sorry for the hassles. —Jeffrey

— comment by Morey Behrens on June 30th, 2017 at 12:58am JST (11 months, 21 days ago) comment permalink

A couple weeks ago I fixed a minor tag problem (changing “flowers” to “flower”) and 138 photos needed to be republished on Flickr. Unfortunately, since then, I get this error message:

Flickr is currently down (error returned by Flickr: Photo is temporarily unmodifiable)

The photos are all on an external drive; if I unplug it I can add upload new photos to Flickr just fine because the plugin lets me ignore the missing photos.

I’m not sure what’s causing this problem, but it appears not to be temporary. I saw in an earlier comment that perhaps some photo is locked or something at Flickr. Is there a way to isolate a problem photo? It’s not the end of the world if Flickr doesn’t get the updated keyword. It’s mostly in my own LR catalog that I care.

I’m using MacOS 10.12.6 beta on a 2016 MacBook Pro with LR CC 2015.10.1.

That’s really weird… I’ve seen the “unmodifiable” thing only a few times, and it had never persisted. I’d imagine it’s the first photo left showing in the Publish Collection (in the “new photos…” or “modified photos…” section) at the time the error pops up. —Jeffrey

— comment by Stephen Shankland on July 10th, 2017 at 12:53am JST (11 months, 11 days ago) comment permalink

I just registered metadata wrangler and hoped it would solve a problem that I am having with scanned .tiff files edited in lightroom cc develop module then added GPS data from the map module all metadata saved to original files, then exported as .jpg files. All the metadata seems to get picked up during the export except the GPS data. I have checked all the settings in the export dialogue and in metadata wrangler and still the GPS data does not copy. I have scanned several thousand 35mm slides and negatives and only some groups of files display this behavior.
Please any suggestions what I should try.

Thanks for the great plugin, it did not fix my particular problem but it sure covers the ground.

The plugin wouldn’t add data that’s not already there (except for what you might manually add toward the bottom of the dialog), so it’d be good to figure out what Lightroom is doing. Try vanilla “Hard Drive” exports and check whether the location data is in the resulting JPGs on your system (perhaps via my metadata viewer). Lightroom has an option in one of the export-dialog sections to strip location info (including “City”, etc.), so look into that. —Jeffrey

— comment by Dennis Brown on July 10th, 2017 at 7:13am JST (11 months, 11 days ago) comment permalink

OK, so, recently I asked you about a permissions issue where I thought your plugin was ignoring the permissions settings I was asking of it. It turns out the issue is actually in Flickr Organizr, and I wanted to you know for others’ sake.

When I have loaded up a set of images to Flickr, go visit the Flickr Album on the website, and then “Edit in Organizr”, I can then make sure that the permissions are set properly by selecting “Batch Edit”, and then “Change Permissions”. When that dialog box opens, the permission “Anyone (Public)” is selected. What I have realized now is that that’s just the initial setting of that dialog, _irregardless of the permissions currently in the album_. You are setting permissions just fine – they’re set private and are not showing up in my public stream. It’s just that the Batch Permissions Edit dialog box’s initial setting doesn’t reflect the current permissions of the photos in the album.

Thanks again for the lovely plugin!

— comment by Carmine DiChiara on July 16th, 2017 at 12:19pm JST (11 months, 5 days ago) comment permalink

Thanks for the plugin! I do know that google had changed things a few months ago and the plugin basically no longer works for exporting directly to google photos. so my question , then how come update it ? anyway, i do thank you again and do hope one day the plugin would work again…

More of a habit, since parts of it still seem to work for some. I’m not working on it directly, but if I update some of the libraries that make it up, I just go ahead and push out the update with those changes. —Jeffrey

— comment by howard on July 16th, 2017 at 12:35pm JST (11 months, 5 days ago) comment permalink

Hello from Seattle, Washington, USA

I am running Mac OS 10.12.5 and just updated Lightroom to 2015.12 and then your Facebook plugin to 20170710.404

As has been the case for the last several plugin updates, upon the successful completion of the update all attempts to do anything in Lightroom or to access any other application simply yields the “bloop” error sound with each click. Again, I had to Force Quit Lightroom and restart Lightroom. While the Force Quit/Restart routine has so far not done any obvious damage, I now back up Lightroom before each update of your Facebook plugin.

It sounds like Lightroom’s got some kind of dialog open, but not visible. Try looking around for it… it might be
behind the main window, or maybe on a monitor that’s not turned on? This is a basic problem I’ve seen with Lightroom from time to time,
whereby a dialog is blocking all input but it’s not visible. —Jeffrey

— comment by Eric Johnson on July 21st, 2017 at 3:53am JST (11 months ago) comment permalink


I’m experiencing that page posts between a period (a few months) disappear from the Facebook page. I can see them in the list of performing posts, but they are nowhere to be seen on the page.

I’m not totally sure if this “bug” is because of your plugin or not, but this has happened twice, and both times it has happened shortly after using the plugin to upload 4-5000 images in multiple albums created via the plugin.

Running on Lightroom 2015.12 on macOS 10.12.6

I have contacted Facebook about the issue again, but last time they just closed the ticket and said “they are continually working to improve facebook jadajada…”.

Have you seen this issue before?

I have not seen it, no. Since you mention uploading a large number of photos, I wonder whether you’re bumping up against some kind of limit? —Jeffrey

— comment by JK on August 28th, 2017 at 10:21pm JST (9 months, 23 days ago) comment permalink

Hi Jeffrey,

Until recently the Flickr plugin had been working beautifully but after changing the keywords on a number of previously published photos I’m consistently experiencing the following error “Flickr is currently down (error returned by Flickr: Photo is temporarily unmodifiable)”. It looks like it’s the same error as

I have also recently run the “Claim photos for photo stream” task, so I wonder if this could have contributed – prior to this I’d never seen the error.

I have tested deleting a few of the more recent photos from the feed, but no joy, and I’m reluctant to delete any more than I have because I’ll be loosing the attached Flickr history. I’ve updated the plugin to the latest version, refreshed user data and re-authenticated the plugin and the problem is persisting. Do you have any suggestions?



Writing from the UK.

I don’t think the Flickr error is related to the “Claim” operation, or anything else in Lightroom. My impression is that it’s a Flickr back-end issue that comes and goes, and other than reporting it to Flickr, the best you can do is just hope it goes away. An unsatisfying answer, I know. —Jeffrey

— comment by Tom on September 14th, 2017 at 6:07pm JST (9 months, 6 days ago) comment permalink

I keep getting this message when I try to export to zen.

Unexpected reply from Zenfolio: their system returned this error that the jf Zenfolio plugin doesn’t know how to handle: “50005: User is not an owner of an object.”

It might be an issue with Zenfolio, or perhaps with this plugin.

Additional information to pass along to Zenfolio support in case you contact them:

Target url:
Unix timestamp of call start: 1505432832.2852
Unix timestamp of call end: 1505432833.4348
HTTP Reply Date Field: Thu, 14 Sep 2017 23:47:26 GMT
HTTP Origin Field: WS001

Thanks for any help…

I’m pretty sure that’s an error at Zenfolio. It’ll likely go away on its own; if not, perhaps send them a note (including the information you copied here). —Jeffrey

— comment by Tim on September 15th, 2017 at 8:50am JST (9 months, 6 days ago) comment permalink


First of all: Thanks for your great work!

I installed your flickr plugin for Lightroom. Everything works fine, except one thing: When creating a flickr publish collection, the plugin shows “only” about the first 600 groups (in alphabetical order) and the rest of the groups are not shown – the box stays white…

Is that a known issue?

All the best

Lightroom’s dialog infrastructure doesn’t do well with really long dialogs, which a list of 600 groups would create. I notice the problem especially on Windows. 600 groups is a lot…. I think Lightroom just can’t handle it, at least as I’ve written the plugin. Sorry. )-: —Jeffrey

— comment by Götz on September 19th, 2017 at 2:08am JST (9 months, 2 days ago) comment permalink

Yesterday I noticed 5 or 6 photos on Flickr viewed with ‘camera roll’ were unavailable. I have tried a few times to republish them yesterday and today but I am getting the same message others here have “Flickr is currently down (error returned by Flickr: Photo is temporarily unmodifiable)”

Just now as I tested again to get he exact error message. They were all present and republishing worked so this is an intermittent problem it seems

Yes, it seems to come and go. It’s a problem with Flickr, in their backend systems, I’d guess. —Jeffrey

— comment by Hans Erken on September 27th, 2017 at 10:26am JST (8 months, 24 days ago) comment permalink

Hi Jeffrey, first of all, your software is fantastic. I am in Oakland, CA. For the last couple days I have been trying to upload photos to Zenfolio. I am getting this message:

Networking error when attempting The action must be retried

When I retry, same result. Advise please. Thank you,

Networking errors can be notoriously difficult to pin down. The best I can suggest is in this FAQ, but it’s just standard stuff and not satisfying if you’ve already tried all that. )-: —Jeffrey

— comment by Bradley Mart on October 3rd, 2017 at 3:43am JST (8 months, 18 days ago) comment permalink

Hi, I’m from the UK near London.

I started using your plugin when I wanted to upload to a business page, but the standard plugin wouldn’t allow. It works fine but, doesn’t seem to allow me to publish file names with each image? When I am uploading 100s of images and someone wants to buy one, the Facebook plugin when publishing to my personal page would name each image (as their original file name that came from the camera. With your plugin however, each image is blank, no file name attributed to the image? Obviously, with a file name, the images were easy to identify…
Any ideas?

See the “Facebook: Metadata Management” section of the Export/Publish dialog. There, you have considerable control over what you send to Facebook to use as the caption. —Jeffrey

— comment by Alan Harding on October 5th, 2017 at 6:35am JST (8 months, 16 days ago) comment permalink

Hi Jeff,

Thank you a lot for your publish plugins. I use mostly publish to Zenfolio.
I have a problem after upgrading LR CC to Lightroom Classic (v7). My publish services setup for zenfolio are gone (I had a few for different types of exporting: print (High Quality), previews (Low-Quality) etc.)

Can I get them back? I have upgraded your plugin to newest version and activated it

Thanks in advance for your help

Lightroom should have brought all the publishing services over when upgrading from Lr6 to Lr7… if it didn’t, it’s a huge bug (that I’ve not heard of yet). Perhaps try the upgrade again by trying to open the Lr6 catalog again from Lr7. —Jeffrey

— comment by Tomasz on October 23rd, 2017 at 9:17pm JST (7 months, 28 days ago) comment permalink

Hey Jeff. I just updated to Lightroom Classic and your Smugmug plugin stopped working. When I click on what remains of the publishing service it tries to open the following URL, but fails

I don’t want to try reinstalling it before I let you know. Im hoping it can be recovered.


It sounds like you were using a very old version of Lightroom’s SmugMug plugin, which they passed on to SmugMug itself many years ago. My plugin precedes (and is unrelated to) both. —Jeffrey

— comment by Keir Briscoe on October 29th, 2017 at 12:14pm JST (7 months, 23 days ago) comment permalink

why table with “System returned “securityError” when Lightroom attempted to use the Internet: Are you sure that your system date and time are correct?” turns on when I try to transfer my pictures from Lightroom to Zenfolio? …and it doesn’t allow to transfer any pictures. I didn’t change anything recently.
I’m writing from Canada.

— comment by Elijus on November 1st, 2017 at 12:14pm JST (7 months, 20 days ago) comment permalink

I am trying to upload pictures from Lightroom to Zenfolio and I keep getting System returned “securityerror” when Lightroom attempted to use the internet:are you sure that your system date and time are correct? My system time is correct I have checked it multiple times. I also don’t have any firewalls or anything. I have spent hours on this today. Does anyone know how to resolve this?? I can log on to Zenfolio just fine on the website.

— comment by Ashley Crook on November 2nd, 2017 at 12:17pm JST (7 months, 19 days ago) comment permalink

Thanks for all your terrific work. We’ve been running smoothly for years but now seem to have a problem with the Zenfolio plugin.

“System returned “securityError” when Lightroom attempted to use the Internet: Are you sure that your system date and time are correct?”

I checked the time, date, and year 3 times. Then I changed both the timezone and the date/time to be “Automatically” kept by the Apple OS. What else can we do?

A smattering of users are getting this. If you’re among them, and this FAQ doesn’t help, please report the exact version of your OS, your browser, and of Lightroom. I don’t know what the problem is, but I think it’s somehow related to SLL security certificates. —Jeffrey

— comment by Tim Harris on November 4th, 2017 at 4:41am JST (7 months, 17 days ago) comment permalink

I am getting the same error other users have mentioned, I get this message, “System returned “Security Error” when Lightroom attempted to use the Internet” Are you sure that your system date and time are correct?”

I checked time and date and it was all fine, I even reset it. I tried to switch to the Safari browser rather that MOZILLA firefox Nothing helped. I was trying to upload photos to my Zenfolio account from Lightroom 4. I had done a successful upload just two days ago. Please HELP!

Jolene Grabill

It turns out that this is an issue with your old version of OSX. Unfortunately, at this point the only recourse is to update the operating system, sorry. Please see this FAQ. —Jeffrey

— comment by Jolene Grabill on November 30th, 2017 at 6:06pm JST (6 months, 21 days ago) comment permalink

System returned “securityError” when Lightroom attempted to use the Internet: Are you sure that your system date and time are correct?

I have used your service for 4 year.. no problem until recently. Are you saying I need to update my macbook? Thanks for your advice. I am super bummed at the moment but hoping to find a fix

Yeah, sorry, as mentioned in the FAQ, Zenfolio just couldn’t continue to support the old insecure protocols. What’s inexplicable is how Apple didn’t support the secure ones until so late. Your browser likely works because the browser itself has the support, but Lightroom apparently relies on the OS for support. It’d be nice if Adobe included the support in Lightroom, but one doubts that they’d bother, since it would benefit so few people. None of that makes you feel any better, I’m sure, sorry. —Jeffrey

— comment by Karrah on December 11th, 2017 at 7:37am JST (6 months, 10 days ago) comment permalink

Hello Jeffery.
I managed to stumble upon you LR > Facebook plugin as I could not get the Native LR one to work. I’m experiencing a small issue which I hope you can help with…

I have my personal Facebook page (Geoff Moore) and then I have a 2nd page for my photography (Geoff Moore Landscape Photography)

Within the settings for your Plugin > Lightroom Publishing Manager > Facebook Tools I have selected (Geoff Moore Landscape Photography)

Within > Facebook: Albums In this Publish Service > I have selected Time Line Photos

The problem I’m encountering is that the image gets publish to the timeline on my personal Facebook page (Geoff Moore) and NOT (Geoff Moore Landscape Photography) and I cant figure out why. Can you assist?


What albums you can and can’t publish too has seemed to be a buggy area for a long time (see this FAQ). Your photo page is accessed via your personal-page credentials, so they’re all mixed as part of one Facebook account, and Facebook should be telling the plugin all the albums you can post to (personal and professional). The “Timeline Photos” album must be from your personal account, but apparently there’s none from your pro page? This is all usually a mystery to me (bugs that I have no control over tend to be that way), but you can try sending the plugin log after, and I’ll take a look. —Jeffrey

— comment by Geoff Moore on February 10th, 2018 at 10:52pm JST (4 months, 10 days ago) comment permalink

Thank you Jeffrey for creating such a great tool!

Getting the below error —

Plug-in error log for plug-in at: C:\Program Files\Adobe\Adobe Lightroom Classic CC\Flickr.lrplugin

**** Error 1

This plug-in’s post-processing task did not finish successfully.
Flickr API returned an error message (function upload, message Filetype was not recognised)

That’s Adobe’s Flickr plugin, not mine. Flickr’s complaining that the copy uploaded couldn’t be recognized as a photo. I doubt this problem is with the pluign… it’s probably a (hopefully-temporary) issue at Flickr. —Jeffrey

— comment by Singh on March 27th, 2018 at 12:13am JST (2 months, 25 days ago) comment permalink

Hello! I’m writing to you from Davis, California.

I’m having a sudden problem with your export from Lightroom to SmugMug plug-in.

After installing your most recent plug-in into the most recent version of Lightroom CC Classic I find that after some number (maybe 5 to 10) of images have been uploaded the uploads no longer work. It’s like your plug-in thinks the files have already been uploaded. I’ve tried uploading to a different gallery but that doesn’t work. I am able to export the image to a hard drive and then use the SmugMug web uploader to add the same image.

I’m using your plug-in 20180305.319 (I wish I could do a copy/paste out of your plug-in to get that) and using Lightroom CC Classic 7.3.1

Thank you for any insight you might provide.

I’ve provided in the Website field above a link to the gallery in which I’m attempting to upload images.

The next time you run into this issue, please send a plugin log, including a note that is explicit about which image you thought should have uploaded where, but didn’t. About the copy/paste idea, that’s great… I’ve added it to the new version that I just released. Just click the version number to copy it to the clipboard. —Jeffrey

— comment by Adam Bridge on May 12th, 2018 at 7:13am JST (1 month, 9 days ago) comment permalink

Hey Jeffrey,
Recently I have had an issue uploading images from LR Classic CC to Zenfolio. They upload with my name as the title of every image instead of the image name given in LR. Even when I check the button to rename using the file name.

Love the product. It has helped me immensely over the years. Thank you.

The filename used for export is unrelated to the title and caption sent for each photo. Those are set in the “Zenfolio: Metadata Management” section of the Publish/Export dialog. —Jeffrey

— comment by Jay on June 4th, 2018 at 10:52pm JST (2 weeks, 2 days ago) comment permalink

So sorry to hear Smugmug pulled the rug out from under you. I have submitted a comment to them specifically asking that they respond quickly to you and get this invaluable tool working again. Sheesh!

It’s not fair to say they they “pulled the rug out”…. they did announce it a month ago, and I simply didn’t notice the announcement, which is certainly not their fault. (I didn’t have their developer forum in my newsfeed; I do now.) The bigger issue for me is that they’re pushing developers to go live with a new API that they themselves explicitly call “beta”. I didn’t intend to bother looking at the new API until it left “beta”; why should I trust it if they don’t? I thought it was odd that they left the “beta” label on it all these years, but I suppose that they have their reasons. And anyway, my plugin continued to work fine with their original system so what did I care? So, now I care. We’ll see. They’re good folks over there, so I’m certain things will work out. —Jeffrey

— comment by Bob Powell on June 14th, 2018 at 8:56am JST (1 week ago) comment permalink

Bummed about the Smugmug issue but glad to know it’s not just us. Keep us posted! We love your plugins. Cheers.

— comment by Ben on June 15th, 2018 at 7:11am JST (5 days, 23 hours ago) comment permalink

Thanks for the update. Hoping this is resolved soon, thanks for your work.

— comment by Cody Sims on June 17th, 2018 at 2:31am JST (4 days, 4 hours ago) comment permalink

Longtime reader, user-of-plugins, and owner of you regex book.

Your plug-ins, particularly the SmugMug one, are a critical part of my workflow, so I will be eagerly awaiting a fix. Thanks for all your great work over the years!

(from NJ)

— comment by Steve Strickland on June 20th, 2018 at 6:34am JST (1 day ago) comment permalink

Hi Jeffrey

I too wrote to Smugmug …because your plugin is so much easier than theirs (or anyone elses!). So it’s been a real blow losing it…

This is what they said:
Jeffrey can update his plugin using our new API and everything will work as it was before – or even better since it is a new API – which I guess you already know looking at the above comments. But thought it might help make them more aware of third party developers’ needs!

Really looking forward to a solution.
John F

Sigh, I think that they don’t understand the meaning of the word “beta“. They also don’t respond to my questions about the new API. I’m just in a holding pattern until they bother to reply. )-: —Jeffrey

— comment by John F on June 20th, 2018 at 7:35am JST (23 hours ago) comment permalink
Leave a comment...

All comments are invisible to others until Jeffrey approves them.

Please mention what part of the world you're writing from, if you don't mind. It's always interesting to see where people are visiting from.

You can use basic HTML; be sure to close tags properly.

Subscribe without commenting