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?
- Every time I start Lightroom, I get a message long the lines of “Lightroom needs to configure your system for the $$$/xxx=....... plug-in.”.
- I can't install the plugin... I get various errors when I try to install it in the Plugin Manager
- I had the plugin installed before, but suddenly it's missing... where did it go?
- The “remove” button in the Plugin manager is grayed out, and I get an error when I try to upgrade.
- I get an error when upgrading the plugin via the built-in “upgrade” button.
- I sometimes get “Assertion failed: packed” when using your plugins
- Why didn't you respond to my note about (insert something unrelated to my plugins, tangential, or something already answered on my site)?????
- What's the difference between your upload-to-xxxxxxx plugin and the one of the same name that comes with Lightroom?
- Do you have a plugin for uploading to (insert name here)?
- I'm running into troubles with the plugin... is there a log or something I can send that might help you diagnose the problem?
- About your LR/Mogrify plugin, could you please...
- I can't find my downloaded plugins in OSX Lion
- Do you have a plugin for G+ (Google Plus)?
- Why does the plugin sometimes fail with “The handle is in the wrong state for the requested operation”?
- 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.
- Photos keep showing up in “Modified Photos to Re-Publish” even though I didn't change anything.
- Uploads to PicasaWeb/Google have been really flakey lately... lots of timeouts, “Unexpected HTML reply” errors, and “unknown user” errors. Wassup?
- When trying to authenticate my login, my browser says it doesn't know how to handle “lightroom://...” links; what's wrong?
- I keep getting “Security Error” when trying to upload.
- I keep running into networking errors (“Unexpected reply...”, “no reply...”, “timeout...”, etc.)
- With my new Creative-Cloud install, I can't register my plugins because instead of the registration button the Plugin Manager shows "Plugin registration button appears here after Lightroom is registered with Adobe".
- I generated a transaction at PayPal (see, here's my PayPal receipt as proof)... when will you send me the registration code?
- When I try to register from within the plugin, I get a “Can't contact Jeffrey's server” error.
- The plugin says “Plugin registration button appears after Lightroom is registered with Adobe.”, but Lightroom doesn't give me a place to enter my Lightroom serial number.
- My plugin registration code doesn't work after upgrading Lightroom to the latest major release.
- I registered the plugin before, but now it's not registered... what happened?
- I get a “missing destination cookies” error when trying to publish.
- I get a “corrupt collection settings” error when trying to publish.
- The SmugMug plugin won't let me set the image Caption and other “New SmugMug” things
- I don't see Lightroom editing changes in the copies uploaded to online photo-hosting service...
- When I try to upload to Facebook, I get the error “(#200) Requires extended permission”
- Can I upload pictures to my Facebook Fan/Business/Group page?
- I get “(#10) Application does not have permission for this action” when I try to upload.
- Why are some of my Facebook albums missing in the plugin?
- Why is “Wall Photos” not listed among my albums in the plugin?
- 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?
- I'm seeing “GUMBY status” and/or “RPC status” errors when I try to upload to PicasaWeb
- The plugin tells me Google's video upload limit is 100Mb, but Google's docs say 1Gb. What gives?
I get “An error occurred while reading the schema for the plug-in. The plug-in will be disabled.” What's wrong?
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.”.
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
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?
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.
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.
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.
I sometimes get “Assertion failed: packed” when using your plugins
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)?????
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?
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)?
I'm running into troubles with the plugin... is there a log or something I can send that might help you diagnose the problem?
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:
Do not email logs; use the submission feature. I can work with them better that way.
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.
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...
I can't find my downloaded plugins in OSX Lion
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)?
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”?
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.
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.
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:
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.
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.
Uploads to PicasaWeb/Google have been really flakey lately... lots of timeouts, “Unexpected HTML reply” errors, and “unknown user” errors. Wassup?
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?
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.)
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.
Nothing in Lightroom would generate this error natively... it's a problem outside of Lightroom and the plugin. I know of three possible reasons...
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.
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....”.
[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.)
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.
With my new Creative-Cloud install, I can't register my plugins because instead of the registration button the Plugin Manager shows "Plugin registration button appears here after Lightroom is registered with Adobe".
Please update the plugin to the latest version, and it should work. (Updated July 8th, 2014)
I generated a transaction at PayPal (see, here's my PayPal receipt as proof)... when will you send me the registration code?
The registration code is in the PayPal receipt (the Unique Transaction ID or the Receipt Number, as illustrated here.
When I try to register from within the plugin, I get a “Can't contact Jeffrey's server” error.
If you're reading this on my site, my machine is up and working. If you can see the “you can connect” message on my secure server, then it's up and the problem is almost certainly some security/firewall setting on your machine (Zone Defense? Little Snitch? Norton?) blocking Lightroom from connecting to my machine. Please check your settings, and perhaps add an exception to allow Lightroom to freely use the network.
If you try to connect to my secure server with your browser and get a security-warning error, check your system clock. It must be reasonably accurate for any https/ssl to work. You would be shocked at the number of people who complain to me about things not working when it turns out that their system clock is one month or one year off.
The plugin says “Plugin registration button appears after Lightroom is registered with Adobe.”, but Lightroom doesn't give me a place to enter my Lightroom serial number.
I bet you're an “RC” (“Release Candidate”) version of Lightroom. For some reason, they don't let you enter your Lightroom serial number.
It's a hassle, but the best I can think of is to downgrade temporarily to the non-RC version; for example, if you're running a Lr6.1RC, reinstall Lr6.0 from Adobe's main Lightroom site and enter your serial number into that one. Then go back and reinstall the RC, and the serial will already be there, so you can then register plugins.
My plugin registration code doesn't work after upgrading Lightroom to the latest major release.
Yeah, sorry about that. A side effect of the registration system I built is that major upgrades like Lr5 → Lr6 (but not minor upgrades like 6.0 → 6.1) cause plugins to become unregistered. As described on the registration page, you can just generate new codes with 1-cent transactions if you like. It's a hassle, I know. sorry.
I registered the plugin before, but now it's not registered... what happened?
Most reports I get of this are because of three things: a Lightroom major-version upgrade (see the previous question), confusion about which plugin was registered, and a corrupt Lightroom-preferences file.
In case of the second one, pay careful attention to messages to see which plugin is and isn't registered. My plugins tell you clearly in the Plugin Manager.
If a plugin becomes unregistered due to Lightroom preferences becoming corrupt, you can try to reregister it (if you're not using a Creative-Cloud install, try the “forgot your code?” button in the registration dialog to automatically bring up your code for the current plugin and the current Lightroom serial number), and hope it “sticks” across the next Lightroom restart, but if it doesn't, you'll have to wipe your Lightroom preferences file and so that Lightroom can rebuild it when it next launches.
After you then start Lightroom and it creates a new preferences file for you, all your photo-related data remains unchanged, but many little personal settings (such as the default catalog to work with, the widths of the panels, etc.) will have reverted to their defaults. Depending on how much you've customized things, it can be a hassle to set things back up the way you like. )-:
You'll also have to re-tell Lightroom about the plugins you had installed. Visit the plugin manager and point the “Add” button at each plugin you had installed, and if they had been registered, re-enter the registration code as described above.
I get a “corrupt collection settings” error when trying to publish.
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
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...
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”
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?
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.
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:
- 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).
- On the “Apps and Websites” row, click “Edit Settings”
- On the “Apps you use” row, click “Edit Settings”
- On the “Adobe Lightroom Export Plugin” row, click “Edit”
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.
- Click “Close” at the bottom of the app-settings box.
Why are some of my Facebook albums missing in the plugin?
Two reasons come to mind:
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.
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?
— 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?
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.
I'm seeing “GUMBY status” and/or “RPC status” errors when I try to upload to PicasaWeb
This error started popping up toward the end of May, 2012. I have no idea what it is or why, but I've asked Google about it. Until I hear something from them, it remains a mystery.
The plugin tells me Google's video upload limit is 100Mb, but Google's docs say 1Gb. What gives?
For whatever reason, Google has a more restrictive limit for uploads via the PicasaWeb API servers that third-party apps like my Lightroom PicasaWeb plugin must use. Comments from their developers imply that it's a technical issue with those servers, but in any case they simply don't allow the plugin to do it, so the plugin aborts an oversized upload before actually spending the time and bandwidth to try.
For videos beyond the 100MB limit, you'll have to upload with Google's own tools, or perhaps go via Google Drive (Google does not limit my Google Drive plugin in the same way it limits PicasaWeb plugins.).