Fairly consistently, I’m getting the following error:
Unexpected HTTP status from PicasaWeb: 500
GUMBY status=105

It occurs after around 50 pictures or so have been uploaded to Picasa. If I click publish again, it will upload another 50-60ish and then give the error again. So basically I have to just keep republishing until all the pictures have been uploaded. Any help would be great. Thanks!

That certainly seems unexpected, though that “GUMBY” note makes me suspect it’s a problem out of my hands (at Google, or with your networking, such as some kind of firewall or web proxy). Perhaps send a log when you see it next. —Jeffrey

Unfortunatly i could not manage to associate the exiting photos with my catalog. After more then 4 days i canceld the action. It starts on a good speed an then slows down. Fetching the information from Picasa takes about 8 hours on a fast internet connection. Matching online photos with my catalog several days. Is there something i can do to speed up this, or do i’vd to delete my online photos und reupload them with yout plugin?

Regards Nicolas.

Even with 20k photos I wouldn’t expect it to take so long, so there’s probably a bug in the plugin somewhere. You don’t need to associate the images… that matters only if you want to push an update for an image, or if you really want to have Lightroom reflect exactly the state at PicasaWeb. For many users, it’s fine just to use it to push new images. —Jeffrey

That does seem to be quite the oversight, doesn’t it? I’ve added it to the (oppressively overcrowded) todo list. —Jeffrey

Windows 7
Version: 20120330.192
LR4.0

Are you sure it’s marked for export? See the info dialog via the context menu in the Keyword panel of Library. —Jeffrey

Publishing to picasaweb includes location info even though I explicitly said not to!?!

Jeff,

To start, great work on these plugins and I love your blog. I am not even sure if this bug I am reporting on is related to your plugin or not, however you probably have more insight than I do as to the root cause.

Ever since I installed Lightroom 4 I have been manually ge0tagging my photos for my reference. The locations I have tagged in LR4 are marked as “private” in the Map module, and I updated the Picasaweb Publish service to “Remove Location Info”, both of which I believe should prevent the location info from being published, yet when I now look at my web album every photo I uploaded now has GPS coordinates. One thing that might be helpful is that my workflow more recently adopted that I also save metadata changes to the file (ctrl-s/cmd-s) after I make them, so the GPS coordinates were also saved to the file and would need “stripped” out on publish (but I am also resizing, etc so it really should be creating a new file anyway…).

Thanks for your help in figuring this out!
~Aaron

The plugin has always (for years) uploaded the geoencoded location with the image, though I suppose now’s a great time to revisit that. Unfortunately it may be a few days before I can push out anything new because the plugin is currently in upheaval due to some really unfortunate (and unannounced) changes Google recently made to how PicasaWeb interacts with outside apps like mine, so I’ve been scrambling to come up with a workaround before it affects too many users. I have to fix that before I can work on other things, but it’s my #1 plugin priority at the moment, so it should be this week, I hope. —Jeffrey

Suggestion for your copious spare time: integration with Google+, such that I can, for instance, specify that an album is to be shared with my “Family” circle — directly in the plugin, rather than having to go to my Google+ page right after publishing. (In fact, I’d love to specify a default for all albums, and only modify as necessary.)

Another thing I noticed is that Google seems to sort albums according to when they were created, so to get them into the order I want, I have to again go to my Google account and manually set an “album date”. It might be nice if the plugin automatically set that date to the max or min date of all the pictures in the album, when the album is first populated anyway.

Again, thanks for your efforts, much appreciated!

G+ integration will have to wait for Google to provide an API. The plugin offers various album sorts… as many as I could figure out from the data Google provides, so perhaps they don’t provide exactly the same kind of date that they use themselves for the sort? —Jeffrey

Lightroom is not really set up for large exports, and the way Google’s API is designed exasperates the situation. 80MB may simply be too large for Lightroom on your system to handle. )-: —Jeffrey

When using caption scheme like this: “{Country}. {City}. {YYYY}. {Caption}.” the result is “. . 2012. Example caption.” instead of “France. Paris. 2012. Example caption.”

It is possible for PicasaWeb plugin to use address suggestions like normal (hard) in this situations whenever address fields are empty?

Lightroom doesn’t give a plugin insight into this… it’s all opaque to the plugin, controlled by a catalog setting about whether the suggestions should be used for export. This all seems less than optimal to me, so by all means make a feature request to Adobe… the more who do, the more likely they’ll pay attention. —Jeffrey

But I have a question: on the version 20111012.173 you wrote, “Include the account id (in addition to the full name that’s already there) in the Publishing Manager login section, to allow multiple accounts associated with the same real name to be easily differentiated”.

I don’t see this on my LR, I just see my name. And since I have at least three picasa accounts (including my google apps acounts) this is/would be a very useful improve.

I’m on (LR3.6) on a Mac with OSX 10.7.3

Regards,
Seba

Only the accounts you’ve successfully authenticated to with the plugin will be listed, so you can run through them… authenticate, logout, then authenticate to another, etc. Then they should all be listed in a dropdown on the login page. —Jeffrey

Yeah, it’s clunky, but a simple right-click create-album thing simply wasn’t possible when I first developed the Publish parts of plugin, due to a cascade of bugs in Lightroom. I’m still not sure whether it’s possible for a non-Adobe plugin, though with Lr4 coming out, I should check again… —Jeffrey