FAQ for Jeffrey’s Plugins for Adobe Lightroom

This page covers the answer to common questions that I (Jeffrey Friedl, an American software guy and hobby photographer in Kyoto) get about my plugins for Adobe Lightroom. Most days, it seems, I spend more time answering emails than I do developing new features or fixing bugs, so this page is an attempt to become a bit more efficient all around.









  • I get “An error occurred while reading the schema for the plug-in. The plug-in will be disabled.” What's wrong?
    · Last Updated: Tue Jun 18 22:51:52 2013 UTC

    That's the general “something went wrong” message that Lightroom gives when it has trouble loading a plugin; that message does not contain information about what went wrong, so you have to look further for the cause.

    Check the upper-right and lower-right sections of the plugin manager for diagnostics.

    In the lower-right section, you have to save the diagnostics to a text file, then inspect the text file to see the error messages... only the first message matters. (Anything after that is a ripple effect that doesn't help point to the root cause.)

    If the diagnostics are not helpful, it could just be that your plugin install became corrupt (a file in the plugin got deleted somehow, or maybe the entire plugin was moved or deleted?), so perhaps it's easiest to simply delete all copies of the plugin from disk, replacing with the latest version from my site, perhaps re-adding the plugin via the plugin manager if the location on disk you choose for the latest download is not where it was before. In any case, all plugin data remains intact; you never loose any data by deleting the plugin and reinstalling.

  • Every time I start Lightroom, I get a message long the lines of “Lightroom needs to configure your system for the $$$/xxx=....... plug-in.”.
    · Last Updated: Wed Apr 29 00:28:05 2015 UTC

    This is an issue with Lightroom's installer; the plugin does not need to be reinstalled.

    To fix it, either uninstall/reinstall the Lightroom application, or open a command window and run

        "C:\Program Files\Adobe\Adobe Lightroom\lightroom.exe" -register

    (Do include the quote symbols shown on the line above; also, you may need to adjust the drive name and folder path to match the location of your Lightroom install)

  • Lightroom warns me “Your catalog must be updated before it can be used with the following plug-in....” What does that mean?
    · Last Updated: Sat Apr 5 02:55:19 2014 UTC

    I think this is a really stupid “warning” to bother the user with. Just choose “Update Catalog”.

    Some background: a Lightroom plugin can save data it needs to perform its work in various places and in various ways... in the Lightroom catalog, in Lightroom's preferences file, on your hard disk, etc.

    Normally the plugin is left to do what it needs to do, how it needs to do it, without the user being bothered with every detail, but for some unknown reason in one specific situation, Adobe feels that Lightroom must announce the incredibly vague and uninformative “there's some kind of change” message and ask “permission” of the user (even though the user seeing the message really has no idea exactly what they're being asked permission for).

    When a plugin stores information in the Lightroom catalog, the style and form of that data can change with a new version of a plugin. Depending on the details of the change, the change just happens silently in the background as a matter of the plugin's business, or, in other cases, the user is pestered with this dialog.

    There's really no information by which the user can determine how to answer this dialog, except ”do you want to use the plugin?”, but that's already been answered by virtue of the user trying to install/upgrade the plugin.

  • I can't install the plugin... I get various errors when I try to install it in the Plugin Manager
    · Last Updated: Mon Apr 8 22:11:06 2013 UTC

    Did you follow bad advice and actually remove some modules from your Lightroom app? Don't do that. Reinstall Lightroom and try again.

    Next, check the upper-right section of the plugin manager.... are there any messages there that give a hint?

    If not, then look in the lower-right section of the plugin manager... are there any diagnostics? If so, save them to a file and look at the first one (Lightroom shows the last one in the dialog, but only the first one has any meaning). If the message is about the inability to load a file of some type, you likely have a corrupt download or corrupt unzip. Simply clicking on the download link on the plugin home page works fine for the vast majority of people, but some small percentage of people get a corrupt download. (I've heard of issues with Google Chrome not always downloading properly, and of issues on 64-bit Windows 7, though most users in either case have no troubles.) Try a different browser to do the download, or a different utility to unzip the zip file.

    If none of this helps, drop me a note with details, such as what the first message of the lower-right diagnostics are, that you indeed checked the upper-right section and found nothing, the versions involved (plugin and Lightroom), etc...

  • I had the plugin installed before, but suddenly it's missing... where did it go?
    · Last Updated: Mon Jul 5 23:26:36 2010 UTC

    Two possabilities come to mind: that you deleted the plugin from disk, or that your Lightroom Preferences file has started to go corrupt. For the latter, see this FAQ.

    If you deleted it from disk, just download and reinstall again, and try not to delete it this time :-).

    Part of the problem is that “installing” a plugin in Lightroom is really just letting Lightroom know where on disk the plugin resides, and Lightroom expects to find it there from then on; Lightroom doesn't make a copy for itself, or anything like that. (This applies to all Lightroom plugins, by the way, not just mine.)

    So, after downloading and unzipping the plugin, but before “installing” it into Lightroom's plugin manager, make move the *.lrplugin plugin folder to where you'd like to keep it on disk. Most anywhere is fine as far as Lightroom is concerned, but it's best if it's a place that Lightroom can write to (that is, don't pick a place that requires administrator privileges to install to if you're not going to be running Lightroom as an administrator), because then the plugin can't update itself, leading to this problem.

  • The “remove” button in the Plugin manager is grayed out, and I get an error when I try to upgrade.
    · Last Updated: Thu Mar 22 01:08:11 2012 UTC

    Lightroom provides for two ways to install/manage plugins.

    The original way to manage plugins in Lightroom 1 was to place plugins into Lightroom's system plugin folder (mentioned on this now-obsolete page). You can still do that with modern versions of Lightroom, but management of plugins installed this way — adding, removing, upgrading — must be done manually, via the file system (e.g. via Explorer or Finder). The only way to remove such a plugin is to remove it from the special plugin folder.

    Since Lightroom 2, the normal way to install a Lightroom plugin is to place the plugin somewhere on your drive where you don't mind leaving it (perhaps in a “Lightroom Plugins” folder you create in your home folder), then point Lightroom at it via the plugin manager's “Add” button. Users with multiple machines often keep their plugins on a shared Dropbox folder.

  • I get an error when upgrading the plugin via the built-in “upgrade” button.
    · Last Updated: Sun May 30 05:44:45 2010 UTC

    Yeah, it happens sometimes, sorry. I developed the built-in upgrade system myself, so it's not as widely tested or robust as if Adobe had done it, and I'm sure I have not foreseen all possible machines setups out there.

    If you're on Windows, perhaps give a try to running Lightroom “as administrator” (from Explorer's right-click menu) for the upgrade.

    If in the end it doesn't work for you, please just do a normal manual install, as described on my Lightroom plugin install page. Before or after downloading/unzipping/installing the new copy of the plugin, you can safely delete any old copies you have on your local disk; all plugin settings and image data remains intact.



  • Uploads to Zenfolio have been really flakey lately... lots of timeouts and “Unexpected HTML reply” errors. Wassup?
    · Last Updated: Fri Aug 14 11:03:20 2015 UTC

    Since the spring of 2015 Zenfolio servers have been having widespread intermediate “issues” with my plugin (mostly “Unexpected HTML reply” errors), especialy when interactions involve a mix of new and replaced images.

    It's been a slow process, but I've given detailed debugging information to Zenoflio about it, and I'm told that they're researching it. Some parts of their customer-service team may not have gotten the memo and will refer you back to me, but there's nothing I (nor you) can do but wait and hope they track down the source of the bug.

  • When trying to authenticate my login, my browser says it doesn't know how to handle “lightroom://...” links; what's wrong?
    · Last Updated: Fri Jul 5 22:19:17 2013 UTC

    It looks like Lightroom's URL handler is not properly registered with your OS. A soft reinstall (no need to remove it first) of Lightroom should handle it.

    To re-install, first try “Help > Check for Updates”, because you may as well make sure you're on the most recent version while you're at it. Otherwise, perhaps visit Adobe to download the latest version of Lightroom. (The “trial version” is just the normal retail version without a serial number, which, if you already have, remains active across the reinstall.)

    Older versions of Lightroom (e.g. Lr5's latest) are available separately: Mac · Windows.

    Creative-Cloud and Mac-App-Store users may need to reinstall differently, I don't know.

  • I keep getting “Security Error” when trying to upload.
    · Last Updated: Sun Jun 6 01:11:22 2010 UTC

    Nothing in Lightroom would generate this error natively... it's a problem outside of Lightroom and the plugin. I know of three possible reasons...

    1. The date on your computer is off. Secure networking doesn't work unless you have a reasonably accurate clock. Check carefully... I've had people complain to me that their clock was correct, when in fact it turned out to be exactly one day off, one month off, or one year off. I kid you not.

    2. You have some kind of security app prohibiting Lightroom from using the network (in general, or to the specific site the plugin is trying to upload to). Common examples are Little Snitch and Zone Defense. You might try disabling them temporarily to check, but going forward you should be able to add a Lightroom-specific exception.

      Please check carefully...I can't tell you how many times people have told me “I've disabled everything and I'm still getting the error!”, only to come back a day or a week later and say “aaah, I had forgotten about....”.

    3. [SmugMug only]   You need to install a particular SSL cert to work with SmugMug's API servers: Download the “Starfield Class 2 Certification Authority Root Certificate” from here, double-click to install, and restart Lightroom.

  • I keep running into networking errors (“Unexpected reply...”, “no reply...”, “timeout...”, etc.)
    · Last Updated: Thu Sep 27 22:48:01 2012 UTC

    It's almost certainly not specifically related to the plugin or even Lightroom, so there's not much I can do but to suggest the standard things:

    • If you're on Windows, be sure to disable “SSL 3.0”. See here for instructions.
    • Make sure you don't have some kind of security app interfering with Lightroom's networking. You may need to add exceptions with each major version of Lightroom.
    • Reboot your router / computer.
    • Make sure your system clock is set accurately.
    • It could be your ISP or the upload destination is having “issues”, so perhaps you just need to give it time. (Many upload services have different upload endpoints between their own web-based uploads and the 3rd-party API that plugins use, so it's possible their API could be having issues while their web-based tools continue to work, and vice-versa.)

    Larger uploads obviously increase the exposure to networking errors and timeouts, so consider at least testing with smaller uploads. One way to make a smaller upload is to use a lower JPEG quality setting. For example, as described here, a quality setting of 93 doesn't usually represent a perceptibly better image than a quality setting of, say, 77, but the resulting upload can be a good 4× larger(!)

    Another way to reduce the upload size is to lower the pixel-size of the upload in the Image Sizing section of the Export/Publish dialog.

    Also, do make sure you're using the latest version of Lightroom.



  • I get a “missing destination cookies” error when trying to publish.
    · Last Updated: Sun Oct 14 14:32:19 2012 UTC

    This rare error is caused, as best as I can tell, by an error in Lightroom that causes it to lose/forget important plugin data. I've never been able to track it down, but the end effect is that all the data the plugin saved about a particular Publish Collection has been ripped out from under the plugin, leaving it with no way to continue.

    The only way to recover is to delete the Publish Collection, then recreate it. The “Populate” feature of my Publish plugins can allow you to recreate it quickly and easily, though it's somewhat of a fragile processes.

    It's unknown what causes Lightroom to suddenly lose this catalog data, but it's possible that it's simply one manifestation of wider catalog corruption, so it's prudent to perform a backup and integrity check on the catalog. To do this, visit Lightroom > Catalog Settings... and at the bottom of the General tab, set “Back up catalog” to “When Lightroom next exits”, then exit Lightroom. That will cause the backup dialog to appear. Be sure to enable the “Test integrity before backing up” option. It doesn't hurt (and likely helps general Lightroom responsiveness) to also enable “Optimize catalog after backing up”).

    The automatic backup selection that you put to “When Lightroom next exits” will revert back to whatever it was before. If it had been “Never”, perhaps take this opportunity to set it to make occasional backups. It's also prudent to back up all the myriad of Lightroom's ancillary configuration and preset files, so consider Matt Dawson's LR Backup plugin.

  • I get a “corrupt collection settings” error when trying to publish.
    · Last Updated: Mon Sep 2 23:12:32 2013 UTC

    This is the same underlying problem as the “missing destination cookies” problem above, with the same frustrations and the same potential workarounds.

  • The SmugMug plugin won't let me set the image Caption and other “New SmugMug” things
    · Last Updated: Mon Sep 2 23:12:32 2013 UTC

    SmugMug has not yet updated its third-party API for their summer-2013 redesign, so there's not much I can do but wait. I hear that SmugMug's own plugin may already handle the new redesign, but their plugin's home page still documents things as of Lightroom 3 (circa a couple of years ago), so it's hard to tell.

  • I don't see Lightroom editing changes in the copies uploaded to online photo-hosting service...
    · Last Updated: Tue Aug 19 04:31:14 2014 UTC

    Check the “File Settings” section of the Export/Publish dialog, and ensure that “Image Format” is not set to “Original”. That's because “Original” does not mean “the same format as the original master image” as might seem obvious.... Adobe has inexplicably made “Original” mean "The original pixels from the master image file (without any Lightroom changes), but with new metadata from your catalog".

    I have no idea how this is useful or desired, but that's how it is. You probably want “Image Format” to be “JPEG”.


  • When I try to upload to Facebook, I get the error “(#200) Requires extended permission
    · Last Updated: Sat May 2 03:17:11 2015 UTC

    On May 1, 2015, Facebook updated how their back-end servers work with app permissions. I thought my plugin was prepared for this since last year, but they made a change since then that I neglected to notice. My bad, sorry.

    Update to version 20150503.385 or later and it should work, though you may need to deauthorize the plugin at Facebook (look here), then re-login from the plugin.

  • Can I upload pictures to my Facebook Fan/Business/Group page?
    · Last Updated: Fri Mar 16 12:07:33 2012 UTC

    Maybe. Facebook generally allows it for most people, but for some reason, they may not grant permission to the plugin to upload to some albums for some people. There seems to be no rhyme nor reason.

    The albums that are listed when you log into the plugin are the ones Facebook allows, and if your Fan or other page's albums are not there, perhaps check the following FAQs.

  • I get (#10) Application does not have permission for this action when I try to upload.
    · Last Updated: Fri Mar 30 02:29:58 2012 UTC

    You're trying to upload to an album that has wider visibility than you've given the plugin permission for. (E.g. you've said that the plugin can upload only friends-visible stuff, but you're trying to upload now to a publicly-visible album.)

    To fix, you can downgrade the visibility of the album, or upgrade the permission of the app. To do the latter:

    1. Visit your FB privacy settings by clicking on this link (or manually by clicking on the down-triangle in the upper-right of your home Facebook page, and select “Privacy Settings” from the dropdown menu).
    2. On the “Apps and Websites” row, click “Edit Settings”
    3. On the “Apps you use” row, click “Edit Settings”
    4. On the “Adobe Lightroom Export Plugin” row, click “Edit”
    5. Scroll down to “Posts on my behalf: Who can see posts this app makes for me on Facebook?” and choose “Public” or something that at least encompasses the uploads you'd like to do.

      Note: if you choose something more restrictive than “Public”, albums that are “Public” or otherwise less restrictive than what you set will not be available for uploading and will not appear in Lightroom.

    6. Click “Close” at the bottom of the app-settings box.
  • Why are some of my Facebook albums missing in the plugin?
    · Last Updated: Tue Apr 10 10:17:17 2012 UTC

    Two reasons come to mind:

    1. The first is that Facebook does not allow you to upload to Facebook albums whose Privacy setting is more open than the permissions you've granted this plugin “app” in your Facebook account.

      For example, if you've granted this plugin app “Friends Only” visibility at Facebook, Facebook does not let you use the app to upload to a “Public” Facebook album.

      For this reason, I recommend that you set this plugin's app permission to “Public” so that in theory you can upload to all your albums (though see reason #2 below for caveats). You can then use each individual album's Privacy setting to control the audience each photo is shared with... for example, even if this plugin's app permission is set to “Public”, photos uploaded with it to a “Friends Only” album are indeed visible only to Friends.

      To check this plugin's “app” setting in your Facebook account, go to your Facebook “Application Settings” page and click on the “Adobe Lightroom Export Plugin” item. At the top of the dialog that appears, “App visibility and post audience” shows the current setting (“Public”, “Friends of Friends”, etc..), and can be changed as you like. Again, I recommend “Public”.

      To check the Privacy setting for an album at Facebook, view the album web page and click the “Edit” button. In top area of the resulting page you can set the “Privacy”.

      Note: any changes you make in app or album privacy settings at Facebook are reflected in the plugin the next time you “refresh list” next to the list of albums in Lightroom's Export or Publish dialogs.

    2. The second reason I can think that an album might not show up is that Facebook has bugs. It's most often seen with the “Wall Photos” album as described in the next FAQ, but some users find many albums inexplicably missing. The best I can guess is that it's a bug at Facebook.

  • Why is “Wall Photos” not listed among my albums in the plugin?
    · Last Updated: Tue Apr 10 10:17:17 2012 UTC

    For some reason that I have not been able to figure out, Facebook allows some people to upload to their “Wall Photos” album, and not others. Check your privacy settings as per the previous FAQ about missing albums, but otherwise, I have no idea why “Wall Photos” is listed for some but not others. For what it's worth, mine is not listed for me, either.

  • Why do I keep getting “Error reply from Facebook: (#240) Requires a valid user is specified (either via the session or via the API parameter for specifying the user.” when I upload to Facebook?
    · Last Updated: Mon Jul 2 22:04:52 2012 UTC

    This is an intermittent bug at Facebook, experienced by users of different apps, so there's nothing specific about Lightroom or the plugin.

    UPDATE: See this comment by Oliver Winter for a reported fix.


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

Hi, great FB plugin… one question, when I have set the album to ‘only me’ and upload to a FB page I run… the album can be found in the page/album section by admin, but the privacy still does say ‘public’.

I don’t think it is actually public as no one commented or likes the album, this did only happen when I shared to the timeline.

Can you confirm though as I want to upload albums to a client fb page, where they will then need to cull some images and add captions before making it public.



The photo may be marked “public”, but the more-restrictive “only me” of the album overrides it. I guess. I don’t know why Facebook displays it that way, but I guess their idea might be that you can set the status for individual photos as you see fit, then remove the restriction from the album to make the individual photos as visible as each was indicated. I guess. —Jeffrey

— comment by Andy on November 10th, 2014 at 4:06pm JST (9 months, 18 days ago) comment permalink

Hi Jeffrey- Great pluggin for LR > Zenfolio. I do have a question. When I use the pluggin to upload JPG images to Zenfolio, I can’t figure out how to get the EXIF information to show. If I check the info on the uploaded photo, it shows the dimensions, original file size, and image type. Is there a way to attach the EXIF data to the exported JPG image?


It’s a two-part process… first you have to make sure that the data is include in what’s sent to Zenfolio, and then you have to configure Zenfolio to show what you want. The first part is in the “Metadata” section of the Export/Publish dialogs… if you choose (for example) “Copyright Only”, then everything else is not included in what’s sent to Zenfolio, so of course they can’t show anything even if you ask. You probably want to choose one of the “All” options. (If you have a need to selectively remove specific items, see my Metadata Wrangler plugin). —Jeffrey

— comment by David De La Vega on November 20th, 2014 at 2:35am JST (9 months, 8 days ago) comment permalink

I am running a MacBook Pro with Yosemite and Lightroom five. Today I just started getting an error message when uploading to send folio that wouldn’t allow me because of the server certificate not being recognized. I installed the update tried again and still no luck. Any thoughts on this.

Generally speaking, a server-certificate error is not one that should be ignored, especially if you’re using WiFi or public internet, because it’s what you’d see if someone were trying to hijack your connection. That being said, the last item of this FAQ used to apply when using Lightroom to contact SmugMug, so perhaps that’s what you’re seeing? —Jeffrey

— comment by Lawson James on December 1st, 2014 at 4:21am JST (8 months, 27 days ago) comment permalink

Hey Jeffrey, this is Matthew, in Washington, USA. Love the flickr plugin, thanks for your hard work. Would it be possible to build in an option to turn off automatic republishing? If develop edits are made, it automatically republishes. I’d like to turn that off at my option, and have an option to manually republish if desired. Currently I select the ones marked to republish and say “Mark as Up to date” but sometimes I forget. Thanks

Unfortunately, no. What you’re asking for sounds more like you want Export instead of Publish, but in any case, perhaps it’d be a good idea to get into the habit of selecting the new photos you want to publish, then holding down the option/alt key to turn the [Publish] button into [Publish Selected]. —Jeffrey

— comment by Matthew on December 2nd, 2014 at 4:20pm JST (8 months, 26 days ago) comment permalink

Hi Jeffrey!

Commenting from Laie, Hawaii.

Thanks for all the hard work you do on these. I will be donating in paypal for my first time.

I wanted to start using your SmugMug plugin, but I’m not sure it will solve my needs. I have been trying to republish only meta-data changes (not the actual pixel data), and saw that this was at one time possible with SmugMug’s own plugin as shown here at https://www.youtube.com/watch?v=U-k8trVmegw at 16:20. I can’t find that option anymore… i think it’s been removed from the plugin, sadly.

Then someone on a forum said your plugin can do it, but I see no option for it :*(

You can do it from the “File > Plugin Extras > SmugMug Extras” dialog. —Jeffrey

— comment by Daniel on December 22nd, 2014 at 5:19am JST (8 months, 6 days ago) comment permalink

Help! :(

That’s from right-clicking “Edit Gallery.” I can’t populate the hierarchy, because I keep getting this error.

Visit the Publishing Manager to edit the Publish Service. —Jeffrey

— comment by Daniel on December 22nd, 2014 at 5:51am JST (8 months, 6 days ago) comment permalink

Hi, I’ve been using the picasaWeb plugin for several years now with LR 3. Two or three times in the past I’ve hit the “missing destination cookies” issues, but the instructions on this page have always fixed it. This time around I can’t seem to find a fix. I’ve updated to the latest version of the plugin. Removed the plugin from LR, exited LR, restarted LR, re-install the plugin, but still get the “missing destination cookies.” When I re-install it remembers I’ve paid, so not all metadata is being removed when I remove the plugin using LR’s plugin manager. The description of how to fix this in the FAQ above talks about possible catalog corruption. My catalog shows no other signs of corruption and LR’s integrity check before a backup doesn’t show any errors.

Any help on how to get over this would be appreciated.

— comment by Charles on January 3rd, 2015 at 1:20am JST (7 months, 26 days ago) comment permalink

Hey, just searched all of the comments about the “missing destination cookies” and found a comment from Mike on February 10th, 2013 . I tried what he said (creating the album from within the plugin tool instead of a right-click/create in LR and it worked. I too am on LR 3. Fill free to not allow these two posts through since I found a solution.
Charles (USA)

— comment by Charles on January 3rd, 2015 at 1:28am JST (7 months, 26 days ago) comment permalink

In the Metadata of LR5.7, I want to see both “Location shown” and “Location taken”, similar to Photo Mechanic 5. Is this possible?
Greetings from Germany
Hans Knodel

I think so, if “Location Created” is the same as “Location Taken”. If so, check out my metadata-viewer preset builder. —Jeffrey

— comment by knodel on January 25th, 2015 at 7:00pm JST (7 months, 3 days ago) comment permalink

When I try to publish my galleries as of late I am unable to.

A lightroom dialogue box with Jeffrey’s Export-to-Zenfolio Plugin pops up with the following message:

Networking error when attempting http://up.zenfolio.com/johnmunnophotography/p961346/upload.ushx: The connection with the server was terminated abnormally

Sounds like they might be having “issues”, but do see the FAQ. —Jeffrey

— comment by John Munno on January 28th, 2015 at 11:27am JST (7 months ago) comment permalink

Where do you paste the Facebook authentication code? I’ve scrolled through the plugin settings several times and can’t find any kind of text box where the code goes.

You shouldn’t need to paste in anything… it should all be handled automatically, but if for some reason it isn’t, the plugin should pop up a dialog a few seconds after you click on the “Authenticate at Facebook” button. —Jeffrey

— comment by Jackalope Maui on February 10th, 2015 at 5:08am JST (6 months, 18 days ago) comment permalink

Having trouble re-registering my Flickr plugin (which is great BTW) after reinstalling Photoshop / Lightroom CC on a new computer. I can see your FAQ and can connect to your registration server (https://regex.info/). There is a Norton Firewall “Program Rule” that appears to allow full access to the correct version of Lightroom on my system drive. I also tried using a new activation code purchased via Paypal. I have installed and re-installed several of your plugins over the years and never had this problem before.

Sorry, my bad… I let my SSL cert expire. Working on it… —Jeffrey

— comment by Tim Lumley on February 15th, 2015 at 11:45pm JST (6 months, 13 days ago) comment permalink

Just wondering if there’s a way to handle re-edits to photos that already exist on Flickr? So, I have images on Flickr (uploaded via your plugin) from a few years ago, but now want to apply some different develop settings to those same images, but upload them as ‘new’ images to Flickr. Any changes I make currently (even to a virtual copy) just overwrite the older version on the site (obviously, as you’d expect).
Any way around this?
Thanks, Matt (UK)

If they’re currently in a Publish Service, then putting them in a separate Publish Service will see new copies (with the perhaps-different settings of the new Publish Service) sent to Flickr. Or, in any case, doing a normal Export (File > Export) and in the destination section be sure to not choose the “replace” and “delete” options. —Jeffrey

— comment by Matt on February 17th, 2015 at 12:04am JST (6 months, 12 days ago) comment permalink

I was getting the “Couldn’t render image: AgNegative:renderToFile: dng_error_write_file” error when exporting a handful of my images. Tried all sorts of things to fix it that did not work: fixing disk permissions, changing file mode, and rebooting/reloading various things. It turned out to be a bad character in the Caption field. Not sure which one (Jeffrey, might you have a good guess?). After clearing the caption on the offending photos they exported fine.

BTW, this was using the PicasaWeb plugin, but its likely it was the same thing with the gentleman who was doing a SmugMug export.

This surprises me… the dng_error errors are from deep within Lightroom, prior to any plugin getting access to the image. If you could restore the caption to one image, export it to its own catalog (“File > Export as Catalog”) being sure to include the raw file, then zip the result and email it to me (jfriedl@yahoo.com), I’d appreciate it. —Jeffrey

— comment by Steven Kishi on February 19th, 2015 at 3:44am JST (6 months, 9 days ago) comment permalink

On the facebook publish plugin, since some albums go missing time time to time, is there a way to batch download the whole album and republish?

I don’t understand the question… what albums go missing from where? Download what from where to here? Republish what? (“Republish” is not a word normally used with Facebook, since that means making new copies. Facebook doesn’t allow images to be updated in place.) —Jeffrey

— comment by Butch on February 25th, 2015 at 7:41am JST (6 months, 3 days ago) comment permalink

When trying to upgrade your Facebook plugin from within Plugin Manager I get a message that the current plugin is not installed in a location where Lightroom can write to it. My plugins are in the Lightroom root directory. Where should they be in order for an automatic update to work?

Brian from Spain

One never wants to put them in the app folder… that should be touched only by Adobe. As per the plugin install instructions, put them anywhere you control that you don’t mind leaving them… perhaps a “Lightroom Plugins” folder in your Documents folder or Home folder? —Jeffrey

— comment by Brian Davies on May 1st, 2015 at 3:05am JST (3 months, 27 days ago) comment permalink

I am using Lightroom 5.7 and your Plug in version 20150414.276. All was working fine until two days ago, when, after creating a new gallery under an existing group, I was unable to upload to this new gallery, receiving message, “unable to export: you have not chosen a destination folder”.

I have logged out of Zenfolio, logged back in, deleted the gallery, created the gallery again using your plug-in, saw in it the list to select, selected the destination, and still get the same message. I tried to chose other galleries (within the same group) from my list, where I have had no problem uploading to until two days ago, and still receive the same message, so I can’t upload to those galleries any more using the plug-in. No idea what is going on. I restarted the computer, tried again, still no luck. Any ideas what is going on?

Writing from Rochester, NY

The error “you have not chosen a destination folder” is Lightroom’s, from the “Export Location” section of the Export Dialog. It’s normally “temporary folder”, but I’m guessing that you somehow bumped it to “specific folder”. —Jeffrey

— comment by Mary on May 3rd, 2015 at 5:16am JST (3 months, 25 days ago) comment permalink

Colorado, USA
I can’t figure out how to get Google Drive to allow access by the plug-in application. Google Drive gives me a list of applications that can access the drive, but I can’t find any app in that list that seems to match Lightroom (I just upgraded to CC) or your plug-in. What do I need to do in Google Drive to make the connection work?

You don’t have to hunt for anything…. click the “Authenticate to Google Drive” in the plugin and it’ll lead you through it. —Jeffrey

— comment by Mike Bucher on May 3rd, 2015 at 8:11am JST (3 months, 25 days ago) comment permalink

Hi – is there a way to reorder the way the published albums appear in Lightroom under “Publish Services”? All the imported albums have been alphabetically ordered but I’d like them chronologically ordered.


Lightroom doesn’t allow the order to be set, so if you want them chronologically, you’ll have to lead with the date in a way that sorts alphabetically (e.g. YYYYMMDD). —Jeffrey

— comment by Matt P on May 5th, 2015 at 11:30am JST (3 months, 23 days ago) comment permalink

“lightroom needs to configure your system for the $$$/xxx=jf Google Drive plug in.”
I have tried the reinstalling ans the command lien script. Neither fixes the problem.

The plug-in has been removed but the message remains!

I am running LR 6 on Windows 7 SP1

Please help.

Please see this FAQ —Jeffrey

— comment by Winston Mitchell on May 12th, 2015 at 4:17am JST (3 months, 16 days ago) comment permalink

Hi Jeffrey, I’ve been unable to upload anything to flickr for the last week via the jf Flickr plugin, nor by publishing locally through jf Collection Publisher and uploading via flickr’s FlickrUploadr. I strongly suspect the problem is with flickr: have you heard of anybody else with the same problems?

I’m running Mac OS X 10.10.3, and using Chrome as my main browser.

— comment by Tim L on May 12th, 2015 at 6:42am JST (3 months, 16 days ago) comment permalink

It looks like it’s a universal issue: https://www.flickr.com/help/forum/en-us/72157652586472111/page2/#reply72157652208503020

Yeah, it seems they’ve really been having issues. Their normal “down for maintenance” message to the plugin isn’t even working, so they end up sending garbage that the plugin isn’t prepared for and the result is a generic error message that doesn’t really point to the problem (Flickr) —Jeffrey

— comment by Tim L on May 12th, 2015 at 6:49am JST (3 months, 16 days ago) comment permalink

‘lightroom.exe’ is not recognized as an internal or external command, operable program or batch file.

Sorry, I guess the instructions weren’t explicit enough… I’ve updated them to highlight that you need to reference the “lightroom.exe” in your Lightroom install folder. Please reload the FAQ page to get the updated instructions. —Jeffrey

— comment by Winston Mitchell on May 12th, 2015 at 11:17am JST (3 months, 16 days ago) comment permalink

Followed the updated instruction…still wants to configure the system.

I’d really love to be able to fix it, but I’ll have to refer you to Adobe. Despite the error message referring to my plugin, it’s a Lightroom problem that a plugin can’t deal with. As best I understand it, during installation Lightroom tells Windows that if the system gets a web address that begins with “lightroom://” (rather than the more common “http://”), Windows should pass the request off to the Lightroom app to handle (rather than a web browser). The error message seems to indicate that something about this OS registration, or of Lightroom’s detection of its success, is not working out. Unfortunately, it’s not an area that I know anything about. If a full Lightroom deinstall/reinstall doesn’t fix it, I would worry about what else the install is breaking. It’s a hassle, I know, but you should reach out to Adobe customer service… —Jeffrey

— comment by Winston Mitchell on May 13th, 2015 at 8:38am JST (3 months, 15 days ago) comment permalink

I want to use the new Google photos. Should I use the Picasa Plugin or the Google drive plugin?
Difference? Advantages?

Thank you very much!

Nice greetings from Germany

I don’t know. I’m hoping that they’ll open up a Photos-specific API to make things clear, but until then I think it’s a matter of experimentation as to the pluses and minuses of each. I don’t actually use either plugin enough myself to have formed an opinion. —Jeffrey

— comment by Max on May 31st, 2015 at 2:59pm JST (2 months, 28 days ago) comment permalink

With your folderwatch plug-in, is there a way to have it import from memory cards when they’re inserted/mounted?

Not specifically, no. If the folders just show up in the watched area, they’ll be checked, but the plugin wasn’t designed for this. Lightroom offers no hooks for the plugin to known when memory cards are inserted. —Jeffrey

— comment by Josh on June 7th, 2015 at 7:46am JST (2 months, 21 days ago) comment permalink


I am trying to post pictures directly to a business page. I have linked my Facebook account with the JF Facebook plug-in in Lightroom, but the only albums listed to post pictures to are personal albums. I cannot see my business page in the drop-down menu in the “Facebook Tools” section of the setup page, so how do I post directly to the business page without first having to post in a personal album? Help :)

Thank you in advance!

You should be able to do it if the permission-settings are appropriate, but see this FAQ for caveats. —Jeffrey

— comment by Krista on August 8th, 2015 at 4:29am JST (2 weeks, 6 days ago) comment permalink

i recently receive the following error when uploading to Zenfolio… Zenfolio is stating that it has nothing to do on their end….

Unexpected HTTP reply from http://up.zenfolio.com/arnophotography/p1021530381/upload2.ushx: 503

This error keep coming up after about 4-5 image upload to zenfolio….

Please help….

It is on their side, but the right hand doesn’t know what the left is doing. The hand that has a clue is looking into it. —Jeffrey

— comment by Arno Nasshan on August 10th, 2015 at 6:48am JST (2 weeks, 4 days ago) comment permalink

Jeff, thanks for your super helpful plugin! I have been using it for a couple of years but today ran into this issue and reading your answers to others did not help me much. I keep getting the same message after uploading 10 or so photos. Please help.
Unexpected HTTP reply from http://up.zenfolio.com/danisxxxx/p830614711/upload.ushx?replace=1121929309: 503

It’s an issue at Zenfolio. I’ve given them specific data to help them debug… hopefully something will come of that. —Jeffrey

— comment by Dani on August 10th, 2015 at 9:51am JST (2 weeks, 4 days ago) comment permalink

I keep getting the error “Create new album at PicasaWeb aborted: Unexpected HTTP status from Google: 500″ when trying to create a new album. It’s been happening consistently for the last couple of days. Is anyone able to create new albums or has Google stopped supporting albums, at least through this tool? Very frustrating that this is not more reliable. Have you tried reaching out to the Google Photos product team, given their big push in this area? I’d have thought they would be keen to improve connectivity with Lightroom given it’s so heavily adopted by the pro and prosumer market.

Mac OS 10.10.5
Picasaweb export plugin for lightroom 20150612.281

It’s just back-end issues at Google leaking in an unsociable way to their 3rd-party API. With some of the logs I’ve seen the root source of the problem seems to be related to user authentication (perhaps one of their back-end servers is out of sync with another?), and in these cases I wonder whether deauthorizing then reauthorizing the plugin might resync things, but since no one (outside of Google, and perhaps inside as well) knows why these errors are happening, it’s just a guess. Probably there’s nothing we can do but wait. —Jeffrey

— comment by barney on August 25th, 2015 at 11:53pm JST (2 days, 15 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 the following tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

Subscribe without commenting