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)

  • 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 (Lightroom 1) 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. Lightroom doesn't provide an upgrade system for plugins, so had to develop something myself, and it's greatly limited by the plugin infrastructure. It seems to work for most cases, but it's not robust when faced with nonstandard machine setups.

    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 PicasaWeb/Google have been really flakey lately... lots of timeouts, “Unexpected HTML reply” errors, and “unknown user” errors. Wassup?
    · Last Updated: Sat Aug 29 07:59:49 2015 UTC

    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.

    If you get the error while trying to create a new album, you can go ahead and create it at PicasaWeb then refresh the list of albums in the plugin. But if you're getting them during uploads, there's probably there’s nothing we can do but wait.

    Considering that Google has announced the death of PicasaWeb, it's unlikely that these errors will be fixed. Hopefully they'll create an API for Google Photos, and I'll be able to make a plugin for that...

  • 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: Mon Jan 18 07:28:47 2016 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. (Update: it is a bug at Facebook, but one we can usually work around; see the following FAQ.)

  • Why is “Wall Photos” not listed among my albums in the plugin?
    · Last Updated: Mon Jan 18 07:28:47 2016 UTC

    — Updated Jan 18 2016—

    As of plugin version 20160118.389, all your albums should be listed, even if Facebook tells the plugin that you can't upload to them. Due to a bug that Facebook has acknowledged but said they won't fix, they sometimes tell the plugin that an album is not a valid upload destination even when it is. For many users, “Timeline Photos” (apparently the new name for “Wall Photos”) was often damaged this way.

    So now the plugin lists all albums, and marks (via “Maybe”) those which might not actualy work. You'll know when you give it a try.

  • 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 216; see all), most recent last...

Hi Jeff. Just wanted you to know that the link to David Marx video tutorials is not working. Specifically the one mentioned in Picasa.

Thanks, it looks like he moved it to here. I’ve updated the link. —Jeffrey

— comment by Keir Briscoe on October 13th, 2015 at 7:48am JST (1 year ago) comment permalink

I was exporting from LR to facebook and this came up:

Error reply from Facebook: (#17) User request limit reached

How do I make it go away so I can continue uploading?

Thanks for your hard work on the plugin

I’ve never seen this one, but it appears to be the per-user sliding-window limit. If you’re using Publish, perhaps the background fetching of comments is killing your access quota. Check out the “Importing Comments from Facebook” section and switch to “Manually”. —Jeffrey

— comment by Scott S. on October 28th, 2015 at 2:28pm JST (1 year ago) comment permalink

Hi Jeffrey,
Yesterday I downloaded, installed and registered Metadata Preset Builder. It works great! Thanks for writing it.

One question: I had assumed that I would be able to add any Metadata field to my Custom Preset. For example, using “ExifTool GUI” I can see that there is a field named “VibrationReduction” and another named “ShutterCount” both of which I would like to add to my Custom Preset however, it appears that those fields as well as many others, cannot be added.

This is not a deal-breaker as I find the plug-in very useful but just wondered if there is something that I am missing that would allow me to add additional fields.

The Preset Builder lets you mix and match fields that Lightroom has been built to handle, but unfortunately can not extend the set beyond that. The best I can suggest for inspecting these kinds of fields is to use the User-Specified-Field option in my Data Explorer plugin. —Jeffrey

— comment by Lee on November 2nd, 2015 at 5:52am JST (11 months, 26 days ago) comment permalink

Hi Jeffrey,
Thanks for your quick reply and information. I will take a look at the link you supplied.

— comment by Lee on November 5th, 2015 at 12:36am JST (11 months, 24 days ago) comment permalink

Hi Jeffrey:
Love Plugin export from LR to Zenfolio. Have LR4 and use keywords fields to describe the who and what of photo. Want to export that data along with photo to Zenfolio, having the keywords go into Zenfolio’s keywords field. Can’t seem to figure how or if I can do that. Can you help?

They should go automatically unless you’ve told Lightroom to strip metadata (see the “Metadata” section of the Export dialog), or the keywords are not marked “Include on export”. Right click on a keyword in the “Keyword List” panel and “Edit Keyword Tag”, and ensure “Include on Export” is enabled. —Jeffrey

— comment by Gussie on November 9th, 2015 at 9:52am JST (11 months, 19 days ago) comment permalink

I’m testing your Picasa/Google Photo plugin, and I have a question as it’s the main reason I installed it:
I need to upload pictures to Google Photos using their feature that compress by itself the pictures and doesn’t use my Google Drive allowed data.
How can I do that with your plugin? When I manually upload files, Google Photo asks me if I prefer high quality picture that don’t use my allowed data (and compresses by itself) or original file.
Thanks for your help, and congrats! I already use the Flickr plugin, it’s wonderful!

Sadly, Google does not let third-party tools like my plugin to access any of these modern features, so it’s simply not possible unless you use whatever tools Google itself provides. The plugin is using the latest API they’ve made available, one that dates back to before Google Plus was unveiled. Yes, in the 4+ years since Google+ was released, they’ve still not provided an upload API, so I wouldn’t hold your breath for a Google Photos API any time soon. )-: —Jeffrey

— comment by Jean-Philippe on December 15th, 2015 at 5:56pm JST (10 months, 13 days ago) comment permalink

I am having Facebook problems with Lightroom CC 2015.3 on MacBook Pro. I have your plugin but get error “can’t upload to Facebook album named “OS X Photos”. Please make sure the app has permission etc (Settings/Apps/Adobe Photoshop Lightroom/Posts on my behalf) – well under the Lightroom App permissions, post audience is set to “Public” & the app can post on my behalf. So I’m not sure what more I can do?

Check the permissions for the album at FB… it’s likely set to something less visible than the “Public” that the app is set to. —Jeffrey

— comment by alan hassey on December 18th, 2015 at 2:44am JST (10 months, 11 days ago) comment permalink

I use a home computer with my main catalogue and a laptop a lot for underway. Can I swap Zenfolio plugin settings/configurations/ publish services between two computers?

The catalogs are nearly identical between computers.

It’s possible with some plugins.

Thanks, awesome plugin, I love it.

Some of the configuration is in the catalog itself, and some is in your preferences file. If you copy the catalog itself back and forth, you’ll have a good chance of getting it to work, but of course that’s only if everything else works with the catalog-copy scheme (e.g. folder layout and contents are the same). But it’s fraught with danger, having two copies of the same catalog “live”… if you forgot to copy from one to the other before using on the other, you’ll end up losing data. Lightroom isn’t really set up for multiple-computer use. —Jeffrey

— comment by Drew on December 28th, 2015 at 12:13am JST (10 months ago) comment permalink

Dear Jeffery, is there a way to link a single flickr photo (published before I started using your flickr plugin) to a lightroom image?
I have used the automatic detect feature but it sometimes selects the wrong image.

You can associate manually via “File > Plugin Extras > Flickr Extras”. —Jeffrey

— comment by Marc Verdiesen on January 13th, 2016 at 4:09am JST (9 months, 15 days ago) comment permalink

Nice Plugin Jeffrey…Very straightforward..
I am still very surprised Adobe does not provide a canned plugin for this, but kudos to you… you seized the moment..

— comment by Jay Goodman on January 24th, 2016 at 11:57pm JST (9 months, 4 days ago) comment permalink

Sending appreciation from California! Is there a way to add all of my collections, 1,500k+, to the publisher plugin all at once? I can only do it one at a time. I’m on the latest CC lightroom release. Thank you so much for sharing this plugin. You rock.

Unfortunately, not yet, except with the “mirror” feature” of my Collection Publisher plugin.. I may eventually be able to migrate the feature to other plugins, but not yet. —Jeffrey

— comment by Andrew on February 25th, 2016 at 4:23am JST (8 months, 3 days ago) comment permalink

Hi Jeffrey,
is there a way to synchronize the photos in my existing Flickr galleries back into LR ?
I have synchronized the folders / gallery names, and I can publish to them from LR, but I would also like to bring back in LR the photos sent to Flickr from other ways (iPhone..).

Also : no way to see my Flickr favorites in LR ?

Thanks !

Please see my answer at this comment about synchronization. You can see the Favorite counts for photos in a Publish Service (see the “Comments” section at the lower right of Library that appears when in a Publish Collection). —Jeffrey

— comment by Renaud on February 29th, 2016 at 6:47am JST (7 months, 28 days ago) comment permalink

Hi Jeff. First of all thanks for your work 🙂

I’ve lightroom CC and I’m trying the google drive plugin, I’m unable to create a new collection. I simply cannot find the button. Is that an issue? Is there something I could do wrong?


Right-click on the Publish Service header and select “Edit Settings…”. —Jeffrey

— comment by Giuseppe Lanzi on March 17th, 2016 at 8:06pm JST (7 months, 11 days ago) comment permalink

After your answer http://regex.info/blog/lightroom-goodies/faq#comment-55238 I get that I have to add the folder in Google Drive and only after that I have to refresh the list. Is that correct? Can I add the new folder directly from inside the plugin or not? In the settings I really didn’t find anything to do it.

Sorry if I misunderstand something


You are correct; currently, folders can’t be created from within the plugin, sorry. —Jeffrey

— comment by Giuseppe Lanzi on April 30th, 2016 at 9:57pm JST (5 months, 28 days ago) comment permalink

Hi Jeffrey, I’m wondering if your Lightroom Facebook plugin allows the uploaded images to be updated. I typically use your G+ plugin and am familiar with how it works. I’m hoping your FB plugin will allow me to operate in a similar way, relative to updating images and reposting them to the same FB post. Please let me know. Thank you.

No, Facebook doesn’t allow updates. —Jeffrey

— comment by Rick Rajewski on May 1st, 2016 at 8:56am JST (5 months, 27 days ago) comment permalink


I cannot use proximity search full catalog…. i have message :

“invalid font size attribute: tiny”

I use loghtroom 6

Merci beacoup

I’m really surprised that Lightroom is showing that error… it is (or was) indeed an error in the plugin, but one that Lightroom normally silently ignores. In any case, I’ve fixed it…. thanks for the report. —Jeffrey

— comment by palomar on May 7th, 2016 at 2:21am JST (5 months, 22 days ago) comment permalink

Hello Jeffrey

first of all – thanks again for your great plugin – this safes my life 🙂

Just realized one thing: i have around 20k Photos im my catalog and doing export with your plugin on several occasions and also to several locations (using them for web page with full scale and thumbnales)

i realized that my LR catalogue was growing strongly last month. Finally up to 1.4GB. I got a hint from another blog that development history is one of the reasons. Checking this with a SQlite editor, i saw that the “export message” from your plugin was around 80% of my history (600k entries in total, 100k without plugin entries). So i deleted those via SQL command, and my catalog shrinked down to 350MB (vs 1.3GB)

So maybe it would be helpful for other users too if the entry in the history could be disabled in your plugin? (not sure if you or LR does control this)

Best regards and thanks again, Cheers Torsten

Lightroom gives plugins no control over this. It’d be very nice if we could selectively clear out history, but it’s not possible.
As I’ve written in the past, history data can indeed be huge. —Jeffrey

— comment by Torsten on May 16th, 2016 at 11:36pm JST (5 months, 12 days ago) comment permalink

I registered and went through the FAQ’s and can’t save my settings in the JF Facebook plugin. It tells me to “Make a selection in the “Facebook: Albums in this Publish Service” section. It seems like I need to login and customize every time. I don’t know exactly what this means.

Second question, is it possible to update/upload the date from the photo metadata to FB?

In order to create a Publish Service, Lightroom requires at least one collection in it. The plugin is telling you to pick at least one of your albums (in the “Facebook: Albums in this Publish Service” section of the dialog) to be represented in the Publish Service as a collection. About metadata, Facebook ignores all image metadata. It’s pretty ridiculous. —Jeffrey

— comment by Arthur J Hushen on June 7th, 2016 at 1:51am JST (4 months, 22 days ago) comment permalink

Hi! Using a few of your plugins and loving them!

I was wondering: when uploading to an existing Facebook album, is there anyway to autotag the location on photos? They are geoencoded and have the correct information, but I’m thinking of something akin to the facial recognition: put in a place and have Facebook automatically recognize that location and tag it in the photo.

Thanks! Keep up the awesome work!

I wish they’d just use the latitude and longitude and show that info, at a minimum. They do allow a third-party app like my plugin to specify a location, but not along the lines of “Statue of Liberty”, but as the ID of the location’s entry in FB’s huge database. That doesn’t do us much good in this situation. )-: —Jeffrey

— comment by Ryan B. on June 24th, 2016 at 4:12pm JST (4 months, 4 days ago) comment permalink

Would it be possible to make the name “Data Explorer” of the created collection set (containing the isolated collections sets and collections) free customizable? ie “_Data Explorer”

I do have a lot of collection and it needs some scrolling or filtering to find “Data Explorer”


Sounds like a good idea. In the latest release, look for the “options” link in the upper-right of the results dialog. —Jeffrey

— comment by Bernd on July 6th, 2016 at 2:46am JST (3 months, 23 days ago) comment permalink

I was trying to use the collection publisher on several collections that have some video files in them. With the ‘publish videos’ selection checked, the sync process stalls (but no errors are generated). With the checkbox un-checked I need to confirm for each (sub)collection that it’s okay to publish without the videos. Any suggestions?

The “stall” is, I’m sure, just Lightroom generating the video files. It can take a loooooooooong time, and Lightroom gives no clue as to the progress, so you don’t know whether it’ll be another 24 seconds, 24 minutes, 24 hours, or 24 days. )-: —Jeffrey

— comment by John on July 14th, 2016 at 12:27am JST (3 months, 15 days ago) comment permalink

Hey Jeff, since you already have a SSL certificate, can you please allow the plugin archives to be downloaded over HTTPS? I checked by nothing is served by https://regex.info/, i.e. paths present under the non-secured site are not available on the secure one.

Bonus points if the “auto-update” from Lightroom also uses https.


— comment by Iustin Pop on July 14th, 2016 at 2:53am JST (3 months, 15 days ago) comment permalink

One question: Which settings should I use to upload Lightroom pictures to google photos using “high quality” instead of “original” file size? If this can be made to work, I will gladly donate for the full version of the plugin.

Google doesn’t allow for third-party apps like the plugin to do this. )-: —Jeffrey

— comment by Tom on July 15th, 2016 at 3:05am JST (3 months, 14 days ago) comment permalink

Location: St. Louis, Missouri, USA

I use the Export to Zenfolio plugin with LR 3.0.1 for quite some time, and depend on it for pushing out photos to my Zenfolio account. I normally use smart collections after making the galleries manually on Zenfolio due to the way I like to structure the groups by client, then a group for each shoot, and two galleries within that, one for edited and one for unedited images for a given client.

Every now and then a clerical error can occur and something needs to be renamed on the Zenfolio account’s galleries. This doesn’t break the ability to push up from Lightroom properly, but then the name of the smart collection in Lightroom may be different than the name on the Zenfolio side. For instance, a renaming due to a marriage or divorce. I do the rename on Zenfolio manually, but then I am at a loss to know how, or if, there is a way to force the associated smart collection(s) to rename on the LightRoom 3.0.1 side of things. I was hoping you could help enlighten me on this.

Thank you very much in advance and keep up the great work! I am a loyal fan.

In the “Zenfolio: Galleries in this Publish Service” section of the Publishing Manager, refresh the gallery list via the “refresh list” button under the list, then turn on the “forcefully rename…” option, then [Save] the settings. That should do it. —Jeffrey

— comment by Robert Greenfield on July 29th, 2016 at 3:53pm JST (2 months, 30 days ago) comment permalink

In your PicasaWeb plugin, I’d like to be able to use {Caption} as a Watermark to put Lr’s caption text on the exported image. I’m doing this because Google finally retired Picasa Web Albums and Google Photos cannot display captions on images. Supposedly, Mogrify does this but I’m a longtime user of your plugins and would like to remain with you.

I appreciate the sentiment, but the Mogrify plugin is the way to go here. Lightroom doesn’t give a plugin any way to interact with Lightroom’s watermarking, so if you want anything extra, you have to use an external program, and that’s exactly what Lr/Mogrify does. —Jeffrey

— comment by Noel on August 6th, 2016 at 12:13pm JST (2 months, 22 days ago) comment permalink

Hi Jeffrey

Thansk for all theses puglins. Im testing one for Google drive ans have a small issue;
i would like to use it to publish a dynamic collection. How can I do that?

I’m new with publishing services so I dont know if I do thinsg correctly but I could spot that with with Flickr for example (which is already integrated in LR), there is an option to publish collections.

is there any workaround for google drive to have something similar?


If you mean a “Smart Collection”, then sure, just click the “Smart” box instead of (or in addition to) the “Normal” box in the list of “Folders in this Publish Service” in the Publishing Manager. —Jeffrey

— comment by Liam on August 22nd, 2016 at 6:17am JST (2 months, 6 days ago) comment permalink

Hi Jeffrey,

I have installed your plugin but I’m not quite sure what I can do with it without breaking the LR Flickr service I have been using so far or removing anything unintentionally from Flickr…

I have selected a few of my Flickr collections to be used by the jf service to test. Entries for them have been created below “jf Flickr”, but the folders are empty. What do I need to do in order to see the existing images for these collections in jf Flickr service?

It seems that once I selected the “smart” publish collection for a photoset, then there is no way back. Is that correct, or am I wrong? Can I simply delete the smart collection under jf-Flickr, or does that mean the photoset will be then removed on Flickr as well? Same for the normal collection (which is still empty in jf-Flickr in terms of images).

Sorry for asking all these stupid questions.

BTW, does your plugin also support moving images from one photoset to another? The LR service obviously doesn’t without deleting the original image from the source photoset (with faves and comments attached) and reposting as a new image to the destination photoset.

Thanks for your support!


You’ll find basic Publish docs here, but in short if you delete a Publish Service or a Publish Collection, nothing happens one way or the other at Flickr. If you remove images from a Publish Collection and publish the changes, settings in the “Delete Options” section of the Publish Service dictate whether images are affected at Flickr. Deleting from the “photostream” collection actually deletes the image at Flickr (if “delete at Flickr” is enabled), while deleting from any other collection merely affects the set/group membership for the image. —Jeffrey

— comment by Karsten on September 11th, 2016 at 8:51pm JST (1 month, 17 days ago) comment permalink

After reinstalling all plugins, no matter what export plugin I use, I get the ‘LR needs to configure your system…..for the jf Facebook plugin’ referred to above.

I tried this “C:\Program Files\Adobe\Adobe Photoshop Lightroom 5.7.1\lightroom.exe” -register with no luck.

Any ideas short of uninstalling LR which will mean a bunch of time to get it back teh way I want it.



This bug is an Adobe thing… your best bet is to contact them, but I suspect that they won’t be interested in supporting such an old version. —Jeffrey

— comment by Lew Lorton on September 14th, 2016 at 6:23am JST (1 month, 14 days ago) comment permalink

Hi Jeff,

I could not upload to Facebook and it is giving me this error message “Couldn’t render image: AgNegative:renderToFile: dng_error_write_file”.

Please enlighten me what is causing this problem.

Thanks in advance,


That message is Lightroom’s (highly cryptic) way of saying that it can’t write the image file it’s preparing for the plugin. Perhaps you’ve run out of disk space. —Jeffrey

— comment by Joey Dela Paz on September 15th, 2016 at 12:03am JST (1 month, 14 days ago) comment permalink

Hi Jeff,

Thanks for the response. I found the solution to the issue. I hope this will be useful for those who will run with the same problem. I had run with the same problem before, but I remember LR had given me a different message. I think the message was “no temporary folder” or similar to that effect. What I did then was I created a folder with a LR Temp folder.

However, I thought it would be similar issue but different message. So i looked at the LR Temp folder, it was there but there were folders and photos there. So what I did was I deleted the LR Temp folder and then I created a new one. It worked.

Thanks again and your plug-in is really useful to me. I could not upload photos on FB without it.

Thanks again,


— comment by Joey Dela Paz on September 16th, 2016 at 11:21am JST (1 month, 12 days 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