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.

Installing

General

Network

Registration

Uploading

Facebook

PicasaWeb


Installing

  • 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.

General

  • I sometimes get “Assertion failed: packed” when using your plugins
    · Last Updated: Sat Jul 30 13:55:28 2016 UTC

    This seems to be a bug in Lightroom. I've reached out to Adobe.

  • Why didn't you respond to my note about (insert something unrelated to my plugins, tangential, or something already answered on my site)?????
    · Last Updated: Sun Sep 5 04:55:01 2010 UTC

    Sorry, but due to some arm pain that limits my time on the computer, I've had to make a change in my priorities, and responding to emails and comments is now lower down on the list. Sorry.

  • What's the difference between your upload-to-xxxxxxx plugin and the one of the same name that comes with Lightroom?
    · Last Updated: Sun Sep 5 04:55:01 2010 UTC

    The plugins that come with Lightroom are very bare bones; my plugins are more complex, but have a lot more options, and also support normal (non-Publish) export as well. If your needs are very simple, the built-in plugins may be perfect for your needs. Give them a try.

  • Do you have a plugin for uploading to (insert name here)?
    · Last Updated: Sun May 30 05:31:22 2010 UTC

    If it's not listed on my Lightroom goodies page, then I haven't developed it, but that doesn't mean that someone else hasn't. Check out Adobe's Lightroom Exchange for lots of plugins and such.

  • I'm running into troubles with the plugin... is there a log or something I can send that might help you diagnose the problem?
    · Last Updated: Mon Jul 26 22:40:10 2010 UTC

    You can send the plugin log via the “Send to Jeffrey” button in the upper-right section of the plugin manager.

    Three important points to help me help you:

    1. Do not email logs; use the submission feature. I can work with them better that way.

    2. If you're reporting about a problem that you can reproduce, please first clear the log (via the button next to the “Send to Jeffrey” button, or by restarting Lightroom), and then do the minimum needed to reproduce the problem... the fewest actions with the fewest photos. The less activity in the log, the more likely I'll be able to zero in on the cause of the problem.

      Also consider enabling “Enhanced debug logging” prior to the test.

    3. Very Important: The send-log dialog offers a place to add a note to me. Please use it to describe why you're sending the log, even if you've already told me via email or a blog comment. I get a lot of logs, and I have a very hard time keeping things straight, so giving me the information I need to debug things along with the log greatly increases the chances that I will not let it slip through the cracks.

      Where appropriate, full and exact names of specific files, urls, etc., help a lot.

    There's also a separate, unrelated log kept by Lightroom, referenced in the lower-right section of the plugin manager. If it reports more than one diagnosis message, only the first is relevant: to access it, you have to save the messages to a file, then open the file to view. If I ask for these, please cut-n-paste them to an email or to the note box of the ”Send to Jeffrey“ dialog described above.


    If Lightroom is actually crashing, you can't use the “Send to Jeffrey” button to send it because the act of restarting Lightroom clears the log. In this case you have no choice but to find the log file, zip it up, and email it to me. The log file is kept in a “*-log.txt” file named for the plugin, in the system's temporary folder. (When Lightroom is running, you can see the location via the “Show” button next to the “Send to Jeffrey” button in the plugin manager.)

  • About your LR/Mogrify plugin, could you please...
    · Last Updated: Mon May 31 01:11:45 2010 UTC

    That's not my plugin... Lr/Mogrify was written by Tim Armes.

  • I can't find my downloaded plugins in OSX Lion
    · Last Updated: Tue Jul 19 02:51:53 2011 UTC

    If you had put them somewhere in your ~/Library folder tree, you'll find that OSX Lion now hides that folder. See this post for how to unhide that folder tree.

  • Do you have a plugin for G+ (Google Plus)?
    · Last Updated: Sun Jul 22 01:12:37 2012 UTC

    Google has no specific API for uploading to G+ yet, so the best we can do at this point is to upload to Google's PicasaWeb (sometimes referred to by Google as “Google Photos”). David Marx at TheLightroomLab.com made a series of videos detailing how to do this with my PicasaWeb plugin

  • Why does the plugin sometimes fail with “The handle is in the wrong state for the requested operation”?
    · Last Updated: Mon Dec 3 08:57:20 2012 UTC

    This is a Windows-only Lightroom bug that affects Lr4.0, Lr4.1, and Lr4.2.

    I'm told that it has been fixed in Lr4.3, so please upgrade (see “Help > Check For Updates” in Lightroom).

  • In the Geoencoding Support plugin, the “Geoencode selected photos from Google Earth” feature doesn't work... it results in an “Can't get location from Google Earth” error.
    · Last Updated: Mon Aug 17 10:32:45 2015 UTC

    It's a mystery why this feature doesn't work for some folks running Windows. Unfortunately, the behind-the-scenes method the plugin uses to acquire Earth's current location is no longer officially supported by Google, so if what used to work no longer works, there's not much we can do.

    I've spent many hours trying to figure it out, without success. It works for most, but not for some. Frustrating.

  • Photos keep showing up in “Modified Photos to Re-Publish” even though I didn't change anything.
    · Last Updated: Sat Oct 29 03:07:16 2016 UTC

    This central feature of Publish has, unfortunately, never been reilable. I've submitted bug reports to Adobe for years, so far to no avail. Sometimes photos just spontaneously move from “Published” to “Modified Photos to Re-Publish”, regardless of the settings in “Metadata that Triggers a Republish” and regardless of what's actually been changed.

    If this bug strikes you, the best I can suggest is either:

    1. Just let the photos be republished if republishing doesn't hurt things.

      “Hurt things” could be that it takes up more time or CPU or bandwidth than you'd like.

      Also, with Facebook republishing actually deletes the original (and its comments and likes and links to it), then uploads a new version of the photo as a new, apparently-unrelated photo. That's why the whole concept of Publish is really dicy to use with Facebook.

      With Flickr, they don't allow videos to be republished, so you can't take this option in the first place.

    2. Quietly move the photos back to “Published”. Select the photos in “Modified Photos to Re-Publish” that you know haven't changed (or, at least, that you know you don't mind not republishing), right click, and “Mark as Up-to-Date”.

      This can be done in bulk with the Mark Selected Publish Collections As Up To Date fetaure of my Bag-o-Goodies plugin.

    One other thing to consider, if you just want to get some specific photos published without having to deal with others, is to select them and then hold down the Alt/Option key. That turns the [Publish] button into [Publish Selected], which then deals with just the selected photos.

Network

  • 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 reinstall 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.

Registration

Uploading

  • 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”.

Facebook

  • 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.

PicasaWeb


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

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 (1 year 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”

Thx
regards
Bernd

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 (11 months, 19 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 (11 months, 12 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.

Thanks!
Iustin

— comment by Iustin Pop on July 14th, 2016 at 2:53am JST (11 months, 11 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 (11 months, 10 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 (10 months, 27 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 (10 months, 19 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?

Cheers,
Liam

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 (10 months, 3 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!

Karsten

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 (9 months, 14 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.

TIA,

Lew

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 (9 months, 11 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,

Joey

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 (9 months, 11 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,

Joey

— comment by Joey Dela Paz on September 16th, 2016 at 11:21am JST (9 months, 9 days ago) comment permalink

Hi Jeffrey,
I would like to know if you could help me with my issue,
I’ve installed the LR but I cant find the way to make the pictures go to my facebook page, they goes to my personal page instead.

Best Regards

Please see this FAQ. —Jeffrey

— comment by Alvin on October 29th, 2016 at 4:21am JST (7 months, 27 days ago) comment permalink

Hi Jeffrey,

I’ve had the “Lightroom needs to configure your system” error for some time, and I’d tried running the lightroom register command without any luck. I then tried running from an admin prompt and that worked, so that may well be worth mentioning in the FAQ.

Excellent plugin by the way!
Paul – London

— comment by Paul Walmsley on November 24th, 2016 at 8:50am JST (7 months, 1 day ago) comment permalink

hi Jeffrey,

I recently changed my lightroom. Now the Paypal ID my 2014 made purchase no longer applies
What is the possibility?

As described here, a major upgrade of Lightroom invalidates previous registrations. Sorry for the hassles… you can make a new registration code with a 1-cent transaction, if you like. —Jeffrey

— comment by Walter Kalweit on December 29th, 2016 at 2:46am JST (5 months, 27 days ago) comment permalink

Hi Jeffrey,

First of all thank you for doing this. The folder watch plug-in has been of great help.

Here is my question to you:
Is there a way to have a lock on taking the images out of Lightroom for any unauthorized or I should say, low-level user?
The ideal situation for my workflow is for many to use the library to capture and organize, but only someone with a code can export, email or even show the photo in the finder folder.

I don’t know if it’s possible or if you are aware of something that already exists.
Keep up the good work
Thank you!

Albert
California, USA

This is not possible with Lightroom. To do this securely, you’d have to have an app that holds all the data about the image, including its pixels, in its own encrypted storage. It wouldn’t surprise me if such apps exist, but I don’t know of any. —Jeffrey

— comment by Albert on December 29th, 2016 at 9:45am JST (5 months, 27 days ago) comment permalink

Hi. Great plugins, and great to see you are discovering / have discovered the many joys of cycling. I’ve been a keen (obsessive) cyclist for 38 years now (since age of 12). My advice would be – try everything – MTB, road, racing, CycloX, cafe racing, time trials, riding on your own, riding in groups. Its all brilliant!

Anyway. Would it be possible to enhance this data explorer plugin so that I could, for instance, group by folder hierarchy, but display various stats for each group, eg number of each colour label, or average exposure.

This would enable me to find folders where I have labelled too many photos, for instance.

I’d love to try all the various forms of cycling, right after I invent a 48-hour day! 🙂 About the data-explorer plugin, I can’t think of a general way to do that…. you may just have to manually apply the plugin to whatever groupings you want, one by one. —Jeffrey

— comment by David Roberts on January 4th, 2017 at 7:59am JST (5 months, 21 days ago) comment permalink

It would basically be a UI to specify the grouping (eg by folder, by aperture range “buckets”)
and to average/sum/count some other field (eg aperture, green labels) within that group. Ideally be able to choose multiple fields to ave/sum/count.

— comment by David Roberts on January 6th, 2017 at 6:30am JST (5 months, 19 days ago) comment permalink

Hi Jeffrey, I have been using the unlimited version of the Picasaweb plugin for Lightroom for over a year and have never had any issues. However, today, I was trying to upload some photos to my account and I keep getting a “Network Error: The connection with the server was terminated abnormally” message. I’ve tried logging out of my google account and logging in again, removing the plugin and reinstalling it, exiting lightroom itself and restarting my computer. But I am still getting the same error. Any thoughts?
Thanks for your help.
Craig

I’ve just updated with a workaround… it should be working again if you update to the latest version of the plugin —Jeffrey

— comment by Craig on January 29th, 2017 at 7:28am JST (4 months, 27 days ago) comment permalink

Hey Jeffrey, I’m having a hard time re-assotiating already published images in the LR catalog. Everything I do causes the image to appear one more time in the album.

This is what I want: There are albums on my FB fan page. Images already have likes and comments, so I want to keep everything. For some reason (I really have no idea), the publish collections in LR are empty.

Situation: The images show a link to the correct image in the FB album. The help text says something about marking it for re-publish. But that does not work if the image is not in the publish service. Do you know a way to publish in a dry run? To get them into the publish service without uploading them?

Please tell me if I should have posted this somewhere else.

Daniel

The only way to get already-published images in there is via the “populate..” checkbox seen here. Take extreme care, though, because Facebook does not allow images to be updated, so any re-publish is actually a “delete and send again” operation, destroying all likes and comments. If you want to keep track of all your FB images, perhaps it’s better to use a regular (not Publish) Smart Collection with “Uploaded to Facebook” as the rule. —Jeffrey

— comment by Daniel Bierstedt on February 4th, 2017 at 12:21am JST (4 months, 22 days ago) comment permalink

Hi Jeffrey,
I have been using the jf picasa web plugin for more than a year and i am happy with the way it is working. My LR and plugins are up to date. The new album created throws an error “insert not supported” followed by which the initializing is taking for ever. I am getting a missing destination cookies error when i tried to publish photos today. I have backed up my catalog and checked for integrity. I have also refreshed my list and nothing seems to help.

Is there something else need to be done?

Google is shutting down PicasaWeb, so many things don’t work anymore. The “missing destination cookies” error is unrelated, but not worth fixing because PicsaWeb won’t work anymore anyway. —Jeffrey

— comment by prav on February 15th, 2017 at 7:06pm JST (4 months, 10 days ago) comment permalink

Hello, the issue with the header: “Every time I start Lightroom, I get a message long the lines of “Lightroom needs to configure your system for the $$$/xxx=……. plug-in.”. “, should mention that it’s (sometimes?) necessary to run this as an Administrator, or it won’t have any effect.

Thanks for the plugins!
-Geir

— comment by geir on February 24th, 2017 at 3:40am JST (4 months, 1 day ago) comment permalink

Hi. I use your plug-ins for years and until the last Google Earth upgrade on my desktop, everything was fine. Since then impossible to get the location from Google Earth (same problem on my laptop) 🙁 I read here there is no solution but I’d like to ask two questions: 1 – to mitigate the issue I manually copy/paste locations from Google Earthe. Painful but this is the only solution. Therefore could you please update the plugin so that O is recognised as Ouest (West in French; my computers are in French). It would really be helpful. Today I have to change 1° 5’40.03″O by 1° 5’40.03″W so that the plugin understands it. 2 – Isn’t there another tool that could be used when Google Earth doesn’t work? Cheers.

I just pushed out an upgrade to the plugin that perhaps works… I couldn’t easily test it, so I’ll ask you to. 🙂 This Google Earth interface has become mostly irrelevant since Lightroom 4 came out with the Map Module five years ago, so that’s what I’d suggest to use. —Jeffrey

— comment by Greg on February 25th, 2017 at 10:53pm JST (4 months ago) comment permalink

Hi Jeffery from Tennessee in the USA. I have on occasion used your lightroom plugin for export to Flickr but find it to be more trouble than manual uploads, especially when trying to pick groups in the very small print they are displayed in the export window, sorry just my opinion. What I am wondering about is do you offer any type plugin for same that would during the upload also put the photo into different Flickr groups like barns, abandoned, city skyscapes, lighthouses, etc., picked automatically by keywording in the photo. I have a friend who did this by using some sort of spreadsheet he made to use along with your plugin. Unfortunately, he just told me about it and did not offer to help me do it with my photos. If you have such would you please direct me to it, because I want it and I’m sure others would too?

You can make a smart collection within the publish service that, for example, fills itself with images that have such-and-such a keyword, and also have “Uploaded to Flickr” of “yes”, and have the target of the smart collection be the group or groups appropriate for that keyword. Thus, after setting these up for the various groups you’re interested in, you need merely bring a photo to the Publish Service’s “photostream” collection and publish it, and the image will find itself in all the appropriate per-group collections as well that you can then publish. Or, to do it all in one step, instead of the “Uploaded to Flickr” thing, have the smart collections key off an additional keywords that you use to indicate “send this to Flickr”. Once you add that keywords, hitting Publish on the various Flickr collections (or invoking this) will take care of it in one step. —Jeffrey

— comment by Bobby Hicks on March 15th, 2017 at 5:02am JST (3 months, 10 days ago) comment permalink

Hi Jeffrey, question vis-a-vis the Google Drive plugin:
Are the “Keywords” from Lightroom uploaded? I tried to search for some in Google Photos after uploading photos to the Google Photos folder in Google Drive but none came up. Cheers! -Tim

Lightroom includes exportable keywords in the image unless you strip them out, but I don’t know whether Google Photos looks at them, but it sounds as if it doesn’t. —Jeffrey

— comment by Timothy Ryan on March 19th, 2017 at 11:49pm JST (3 months, 6 days ago) comment permalink

Writing from UK.
I am trying to download the EXIF viewer plugin – so useful – but winzip will not unzip any files with .lua extension and labels them as corrupt. What can I do, as I am stuck at step 1?

The “*lua” files are among those inside the ZIP file, so I’m guessing that your browser has unzipped the download for you. The folder that the *.lua files are in is the plugin. —Jeffrey

— comment by Victor Pace on April 16th, 2017 at 8:00pm JST (2 months, 9 days ago) comment permalink

Hi Jeffrey
I just Install your plugin, I show him in the plugin manager with the green light just next to, but not in publish panel on the left. (unable to configure my tumblr account.

I try to re install the plugin but nothing happen.

I’m working with the last LR version (cloud) on Mac OS X.

Thanks !

The Tumblr plugin is Export only, not Publish. You’ll find it via “File > Export…” —Jeffrey

— comment by Jean baptiste on April 20th, 2017 at 6:11pm JST (2 months, 5 days ago) comment permalink

Hey Jeffrey! This plugin is awesome, the built in FB one alway seems to get an authentication error when exporting. Just a quick question, is there a way to designate the temp folder where the exports are created before the upload? If not, where is this folder by default? I’m just concerned with storage space since my photos are on a different drive (HSS) than where my lightroom executes from (SSD).

You can have Lightroom write the files to whatever folder you want (it’s part of the dialog when you first set up a Publish Service), but in such a case the files will accumulate and remain there after the upload. That’s a feature if that’s what you desire. If not, use the “temporary folder” setting, in which case Lightroom will put the files into a folder it creates within your system temporary folder, wherever that happens to be, and will delete them the moment the plugin has finished uploading. —Jeffrey

— comment by Justin Jajalla on April 22nd, 2017 at 7:29am JST (2 months, 3 days ago) comment permalink

Hello Jeff,

My question is about the lightroom plugin.
I have a master catalog with several smart galleries that gave me a lot of work to put them up and running.
I need to import this catalog in a new one, but when doing that all my Zenfolio Publish service did not went to the new catalog.
In that condition two things are important to notice: 1) I will have to re upload all images to zenfolio and 2) I will have to recreate every smart gallery.
So, my question is how to import all the work done in the master catalog zenfolio plugin to the new catalog.
Greetings from Rio – Brazil

The short answer is, you can’t. )-: Lightroom doesn’t include Publish information in its catalog import/export. —Jeffrey

— comment by Thales on May 5th, 2017 at 12:23pm JST (1 month, 20 days ago) comment permalink

I am modifying picture within Lightroom and I want to export the modified picture to Zenfolio using the plugin. (ie: cropped picture)
What configuration setting needs to be changed to allow for this?

Thanks very much.

Greg

By default the latest changes are sent out when you Publish, perhaps you changed the option. See this FAQ. —Jeffrey

— comment by Greg D on May 31st, 2017 at 11:12am JST (3 weeks, 4 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