picasawev-20080729.1 does not work on my Lihtroom 2. I get information that there is something wrong in reading the schema. So the plug in is disabled. OS Windows XP.

Regards,
Erkki

LR2 “Update Catalog for Plug-in” message on first opening of catalog after copying files to the Modules folder. Win XP. Why is a catalog update needed?? I’ll update but am apprehensive…

Also found a second dialog “Access to undefined global: LrError”

I have a picture of it. Send me an email and I can send it to you.

Fixed in .3 —Jeffrey

Thanks Jeffrey! Works like a charm on WinXP SP3 + LR 2.0

Works like a charm! Thanks 🙂

I am using your picasa plugin with Lighroom in Leopard. I get the following error when I try to export images. No images to process. All were filtered out. Is this a bug?

Look at the All/Updated/New filter in the Upload Management section of the Export Dialog. You probably have it set to Updated or New, and have selected only images that have already been exported. —Jeffrey

Works smoothly with LR2 and excellent instructions. Thanks! Windows XP.

I can’t figure out how to rate it on the Adobe Website, but will give it five stars if there is a way.

Thanks so much for making your lightroom plugins freely available to everyone. I just sent you a little something to show my appreciation for your great service and outstanding workflow tools.

Hi,

First of all, thanks for the plugin!

One quick note–it doesn’t seem to be uploading all of the selected tags to Picasa Web Albums. Sometimes in lightroom I’ll have five or six tags on an image, but it will only upload two. If I retry and retry, it will always upload the same two tags. Any thoughts?

Thanks,
Robby

Are you sure it’s not the Lightroom keyword bug mentioned in the known issues? —Jeffrey

Since .24 mine has been updating fine from the Plugin Manager. I too am on LR2.1 RC1.

I can’t log in to PicasaWeb via your plugin:

Mac OS X 10.5.4
Lightroom 2.1 RC1
picasaweb-20080924.28

I suspect this is caused by one of two things:

1. The fact that I’m using an early release of 2.1; or
2. I have two Google IDs with the same e-mail address (the same one I used to submit this comment), which could be confusing your plug-in, or whatever Google service you try to authenticate with.

If it’s #1, then this might be an early preview suggesting your plugin might break for everyone when 2.1 is released. The rest of my post works with the assumption that #2 is happening (which seems more likely, for reasons discussed below):

* I have a normal “gmail-style” Google ID. This is what PicasaWeb uses when I try to log in on the web site (it only accepts this password with my e-mail address). Your plugin rejects these credentials as though they were invalid (BadAuthentication).
* I also have a “Google Apps for Your Domain” account with the same e-mail address. This account (password) doesn’t work with PicasaWeb. When I try to use this password with your plug-in, I get a very different error message:

INTERNAL PLUGIN ERROR
PicasaWeb login aborted

It’s as though the service you’re trying to log into is confused about which version of my ID it should try to use, and when it (wrongly) tries to use the Google Apps account, either PicasaWeb or your plugin chokes.

This “duality” of Google accounts has always been a source of frustration, because applications can’t treat them as equivalent, and sometimes it’s not clear which one they should use if an ambiguity exists; please feel free to complain to Google if they’re doing something wrong here, or if poor documentation allowed you to do something wrong. Thanks for your help.

(With David’s help offline, I was able to address this. The fix appears in .29 —Jeffrey)

Jeffrey,

thank you very much. Using your plugins made my decision to actually buy Lightroom to organize my photos. You should get commission from Adobe. I have a copy of your regex book in my office, excellent work!!!

Christian

Hallo.

This plugin used to have option NOT to upload Lightroom metadata and Lightroom Keywords. I really do not want my keywords to be uploaded.
Can you put this feature back, please?

Best regards, Filip.

It still does… you can strip most metadata with the “minimize” checkbox in the “Metadata” section. If you’d like more control, you can exercise a line-item veto of any item with my Metadata Wrangler plugin. —Jeffrey

Hello

First thanks for your plugin. I don’t know why, I have already exported several albums to my picasa web account with your plugin and suddenly, I have the following error :

?:13879: bad argument #1 to ‘?’ (string expected, got nil)

Do you have an idea ?

I have lightroom 2.1, I never had version 1. I tried to download the latest version, it is 20080905.17

Hello,

I want to develop a plugin for LR2.1 (1 workflow and 1 FTP).

Do you know where I can find resources and there is a book about the SDK?

thank you for your reply.

Many Thanks.
Eric

The only resources I know of are the SDK documentation and examples from Adobe, and the user-to-user forum. The docs contain a 187-page PDF full of details and examples. —Jeffrey

The picasa plug-in (version 20081123.43) is estimating 5 hours to upload 255 RAW images. (using fast ethernet connection, Vista OS, fast computer). Is there a way to speed up the upload process? Thank you for developing this.

The time to upload is most strongly influenced by your internet connection. Fast connection means faster upload. (Personally, I have 100 megabit fiber to my house, but I still hesitate to use “fast” when uploading big images). —Jeffrey

How do you clear the PicasaWeb Metadata in LR? I uploaded some photos and then deleted them in PicasaWeb and I want to have those changes reflected in LR.

Pull up the “File > Plugin Extras > PicasaWeb Extras” dialog. —Jeffrey

Is it possible to make this create albums which are sign-in on the privacy settings? I see it can create public and unlisted; Google recently added the Sign-in only viewing for albums and this would be great to create automatically.

Can you point me toward some docs? I can’t find reference to it in Google’s docs… —Jeffrey

Hello! What a great plug-in! great job there!
I wonder if there is a way to auto select the album date for picasa export! I am using the LR2 version!
Tks!!

Thanks for the quick answer… I’ve been looking all over the Internet and nobody seems to mention this issue. Looks like you’re the only one with a potential solution in your hands. I hope you will port run any command one day… Do you have any alternate suggestion in the meantime? I’ve tried to use LR2/Mogrify and specify my droplet there in the config screen instead of ImageMagick’s binary, but obviously that doesn’t work -must be trying to add parameters that the droplet doesn’t understand. I might be able to point to a .bat and strip the extra parameters and just send the filename to the droplet. Not sure this is gonna work, I will let everybody know.

As a side note, if ever you need a new export plugin idea… Would be great if you could do an export to Gallery!!!

Dale, you might be using special characters in your username/password. I know I had some problems with that before (with the old version of the plugin), I’m not sure how the new version behaves. I had to change my password to make it work, give this a try.

Hum, actually, about my last comment, Jeffrey has JUST posted a new “run any command” plugin so you can still use his export plugins with your beloved Photoshop Droplets! Think NoiseWare, Smart Sharpen, etc… Thanks buddy.

It’s at http://regex.info/blog/2009-01-27/1125

Hello, Jeffrey. I like and enjoy both your Flickr and PicasaWeb export plugins, that they’re very useful for me. I have only a little question: is there any chance they eventually could be full automatically updated without any user intervention?

Probably not. It’s generally considered rude for a program to update itself like that. I built the whole upgrade thing from scratch (none of it is built into Lightroom), and so it’s sort of fragile, and I still get occasional reports that it doesn’t work. Also, some updates are less stable than others, along the lines of “okay, I’m trying something here… let me know how it goes”, and each person should be allowed to decide for themselves whether to accept it or wait. —Jeffrey

Thanks Jeffrey for your efforts, hopefully you are seeing a little play money now from your work! I just registered the Picasa plugin, it’s probably the best $10 I’ve spent in a while – It has saved my a lot of time and makes pushing family photos online effortless!

In that vein, is it possible to parse and import new keywords and/or descriptions that have been added in Picasa Web into Lightroom?

My scenario is this: I am scanning family photos, and would like to put my family to work adding situational and people keywords on PicasaWeb. Then every few weeks, I’ll point the plugin (or something) to the Picasa album to snarf new/changed keywords and descriptions to get them into Lightroom. Does the Lightroom plugin API even allow for something like that?

Thanks again!

These kind of things are definitely on the to-do list, but this one will be tough. Indeed, the Lightroom plugin API does not allow for updating of keywords, and even if it did, without a timestamp on when each keyword was updated (in both Lightroom and PicasaWeb), it’s hard to make a robust sync. But until LR allows for a way to get keywords in from outside, you’re sort of stuck. )-: —Jeffrey

I am using the latest version of the Picassa plug-in in Lightroom 2.0. I’m not sure if I am missing something obvious or if this is actually a bug. However I figured I would report it.

If I make a smart collection and use the “Exported to Picassa” filter, Lightroom successfully identifies all of the pictures which I have exported to Picassa. Now, if I go to this collection and edit a file (Metadata, etc) and then re-export the updated image from this collection, the export goes just fine but for some reason it is REMOVED from the collection. I don’t understand why as it should still be tagged as ‘exported to picassa’.

If I then delete the Smart Collection and re-make it, Lightroom once again successfully identifies all of the images – included whichever one I just edited.

Does that make sense?

-martini

Version 20090325.68
Hey, thanks for this plugin!
I export edited pictures to picasa, but the original, unedited versions were exported.
To recreate:
1. Edit a picture with the “Develop” tools of lightroom
2. Switch back to the “Library” tab
3. Select the pictures and export it
4. Picasa shows the unedited version rather the exported “fixed” version of the picture

In the “File Settings” section of the Export Dialog, did you have “original” selected for the Format? —Jeffrey

Mac OS. Lightroom 2.1. Picassa Web Plugin.

What are the reasons for a REJECTED USER LIMIT error when exporting to picassa web?

Thank you,
Barry

As far as I’ve ever been able to determine, no one knows why Google sends back that error. It seems completely random (which makes it completely frustrating). —Jeffrey

Hi Jeffrey, thanks for the quick fix (this might be the fastest response from the developer I ever experienced!) It works perfectly now!

Although it is working all the time but, when I update the plug-in it always give me an

“Internal Error: Can’t load “Version.lua” (cannot open C:\Documents and Settings\________\デスクトップ\download\picasaweb-20090714.86\picasaweb-jfriedl.lrplugin\Version.lua: No such file or directory)”

error, then if I restart LR the plug-in seem properly updated (as I’m getting “You have the latest version” when I hit the update button.) As long as it’s working nothing major but thought you might want to take a look.

Odd, it seems something went wrong with the upgrade? Could you try a manual upgrade, and see how it goes? If you still have troubles, please send me the plugin log (via the “Send to Jeffrey” button in the upper-right of the Plugin Manager). —Jeffrey

I’m trying to export my images to Picasa and I have a number of Virtual copies with different exposure settings or some creative b/w settings. Only the main image is exported. If I select a virtual copy and choose export, the plugin says there are no images found that need updating. Is this a known issue?

Picasaweb 20090717.89 in Lightroom 2.4 64 bit

Hmmm, I’ll have to check. I’d think that each virtual copy is considered its own unique photo by the plugin (with the same filename, of course). I’ll take a look… —Jeffrey

Hello Jeffrey,

I’ve found you plugin very usefull to share pics with my friends via picasa. Unfortunately, I have discovered, that it does not transfer GPS location data to picasa therefore leaving me with terrible manual job.
LR used: 2.4 build 572242 Windows XP
Plugin: 20090717.89

Photos were taken with Eos 40D as RAW and geotagged with Geosetter v.3.1.16 (www.geosetter.de)
GPS data is visible in EXIF data of the file (checked with ExifPilot), however I didn’t manage to see it directly in LR.

Actually, All EXIF data were ignored ano in info on camera or exposure are transferred to webalbums.

Hope you can fix it to further improve this great product.

Thanks,
Mateusz

The plugin does send it, but it gets the information from Lightroom, so if you’re not seeing it in Lightroom, that’s your problem. If you geoencode with an external app, you should do so before loading into Lightroom. Geoencoding after might work if you Metadata > Read Metadata From File…. give it a try. You can also geoencode within Lightroom with my geoencoding plugin. In any case, you must see the geoencoding in the Library (either via the normal view, or in the case of my plugin, the “shadow data” view) before uploading to Picasa. —Jeffrey

Hello. Bo here from Copenhagen. I was happy to find your plugins for Flickr and for PicasaWeb.

I am on a Mac with Snow Leopard, using LR 2 and using PicasaWeb plugin 20090916.93 which I have a smaller problem with.

I uploaded a batch at jpg quality 60, which wasn’t satisfying, so I was happy to see that the was a obtion to replace new upload with existing pictures (delete copies previously uploaded)

But apparantly it doesn’t work because I get the following error messages (for every picture)

INTERNAL PLUGIN ERROR
unknown response (500) to delete query

Am I doing something? Or does this setting not work with PicasaWeb?

It worked for me… could be a temporary issue at Google. When I tried, the plugin had no problem deleting the previous version, and the new version showed up in the list of galleries at PicasaWeb, but when clicking through to the image itself, I got a 404. Because it showed up somewhere on PicasaWeb but not elsewhere, it seems evident that they’re having “issues”, so maybe you ran into a different version of that. If you get it again, please send the plugin log (via the “Send to Jeffrey” button in the plugin manager) and I’ll take a look, just to be sure. —Jeffrey

Hello,
I have dual boot on my PC, accessing the same lightroom library from the two OS’s. I registered two plugins on one OS, and they are “non registred” on the other OS…
Is there something simple to get the two plugins registered (by pointing on a common file or something) on both “sides” of my machine? (maybe just putting 0.01$ on each actually)
Thanks for your work
Greg
Plugins : Picasa export and the facebook export

Exactly as you suggested…. point to the same plugin folders from both sides (or to multiple copies of the plugin folders, one per side… doesn’t really matter). Enter the same registration code into the plugin manager on each side… it should all just work. —Jeffrey

Hey Jeffrey! Enjoying your great plugins over here in northern California!

I’m using the PicasaWeb export plugin version 20091023.97 with Lightroom 2.5 on Mac OS. I want to make two PicasaWeb export presets: one that adds photos to a set album and another that adds them to an auto destination. However, I can’t seem to make two PicasaWeb export presets with different settings. Is there a way to do this?

You should be able to…. just set what you want for the first settings and create a preset, then set what you want for the second and create a new (differently-named) preset… they should each encapsulate their own settings. —Jeffrey

Hi Jeffrey,

I have same error reported here before while exporting to Picasa web:
AgNegative: renderToFile:
dng_error_file_not_found
My version is picasaweb-20091118.98

I am able to export to local disk no problem.

Thank you.
Alexei

I very much doubt that you can export that same file to local disk if you’re getting that error during some other export.
In either case, though, it’s something you should report to Adobe… that error is way more basic than any plugin — it’s from the core of LR. —Jeffrey

Hi Jeffrey, the latest update of the Picasa Web Album exporter does weird things to the Aperture on export. For example, instead of Aperture 3.3 it says Aperture 3.3635857 now (I hope it’s really the plugin and not a new glitch in the Picasa Web Albums).

Regarding your comments on 20091203.100 – the 500 photo limit is only for the FREE version of Picasa Web Albums. As soon as you pay for extra storage, the limit is raised to 1000 photos per album (the other restrictions being 500 albums in the free version and 1000 albums in the paid version; I think this will eventually change now that Google has dropped the storage prices).

Keep up the good work.

Thanks for the clarification on the limits. About the aperture, where exactly are you seeing the problem? The plugin doesn’t touch the image’s embedded metadata, but can refer to it when creating captions if you ask…. —Jeffrey

Hi Jeffrey, I was wondering how to have the original date & time from when the photo was shot listed in Picasa Web? Right now all the pictures I upload have today’s date (i.e. upload I assume – though it might also be date added to LR catalog).

I can’t imagine you haven’t implemented this, so I’m surely missing something, but I’d appreciate a pointer nonetheless!

Cheers for the great plugin!

Chris from Amsterdam (NL)

As best I can tell it’s a bug at Google. I’ve just posted version v110 that works around it. —Jeffrey

Hi Jeff,

I notice that on Picasaweb the Aperture information is incorrect. Often A is close to the
largest aperture of the lens, but not quite. E.g 2.828427, see below
Example
Belichting: 1/160 sec.
Diafragma: 2.828427
Brandpuntsafstand: 100mm
Flitser gebruikt: Ja

See http://picasaweb.google.nl/MauriceSittard/UnusualFruit#5426319030935799474

Plugin version number is 2091216.107
Lightroom version 2.6 – 632038 – Camera Raw 5.6 – 64 bit
OS: Vista Home Premium / Service Pack 2

Another question:
– Is it possible to display in Picasaweb the name of the lens used next to the name of the camera used?
– Is it possible to display the focus distance?

Kind regards and thank you for the excellent plug-in,
Maurice

How about adding a configurable retry count to handle Error: 10 STORAGE_UNAVAIL (perhaps defaulting to 5 and respecting Google’s API guidelines of course)? That would take care of much of the pain…

OS Windows XP SP3
Lightroom 2.6
PicasaWeb 20100315.116

An error occurred while reading the schema for the plug-in “PicassaWeb.” The plug-in will be disabled.

(This is the message I get when I try to install your plug-in.)

Sounds like your install didn’t go properly… maybe try downloading/unzipping again? If that doesn’t work, email to me the diagnostics from the lower-left section of the plugin manager, and I’ll take a look. —Jeffrey

Just downloaded picasaweb-20100323.117.zip
Thanks ever so much!
One problem: I am in the UK, and when I try to order prints from my uploaded photos in Picasa, I only get USA companies as options. I presume that the plugin somewhere must say I am in the USA. Is there a way to change this so that Picasa knows I am in the UK, and will therefore offer me the option to order prints from UK companies such as Photobox?
Many thanks in advance,
Chris

The plugin doesn’t say anything one way or the other about where you are… I would think this would be part of your Google Account settings. Maybe they don’t offer print service in the UK? —Jeffrey

I am just new to PicassaWeb and am loving your plugin….really a time saver.

I want to have two gmail accounts…one for family and one for fine(r) pix. Can I save the plugin as a preset…one with one gmail signin and one with the other?

I tried it on LR3B2 and it seemed a bit flacky….the gmail accounts would kind of randomly rotate….but not in sync with the preset pushed.

It should work with the presets. Perhaps enable extra debugging (in the plugin manager) and try uploading one photo to each, then send the plugin log (via the button in the plugin manager)….—Jeffrey

John

Jeffrey,
Thank you for such wonderful plugins. I think you’ve saved me about 3 hours worth of work trying to do the same thing with Dreamweaver and Flash (making slideshows for bunches of photos). 🙂
My version numbers: WinXP SP3, LR 2.7 (666138)
Facebook plugin: 20100323.117
PicasaWeb plugin: 20100323.117

I’ve tried several things, but have now resorted to commenting here.

My situation:
It doesn’t matter which plugin I try installing first, but when attempting to install the second plugin in it get this error:
“An error occurred while reading the schema for the plug-in ” Facebook”. The plug-in
will be disabled.”

I’ve resorted to installing one of them and if I need to use the other, I first remove the first plugin and install the other.

Again, thank you very much for such wonderful plugins.

That error is from Lr telling you that the plugin files are incomplete or missing or corrupt. Are you sure you’re not unzipping them over each other, or something? Even after installing into the plugin manager, you have to leave them on disk because “installing” is really just telling Lr where they are. —Jeffrey

I have been using your plug in with registred code. Now it does not show in my export plug in manager anymore. Should I down load and install your plug in again ?.
Thanks

If it suddenly disappeared from the plugin manager, it’s either because you moved (or deleted) it from where it was when you told the plugin manager about it, or because your Lr preferences have gone corrupt. If it’s still on disk where you put it, it’s likely the latter. )-: You can try reinstalling it if you can find it, or downloading and installing, but if it doesn’t “stick” across a Lightroom restart, you’ll have to blast your preferences file and let Lr build a new one when it starts. —Jeffrey

Get the following error trying to export to Picasa:System returned “securityError” when Lightroom attempted to use the Internet: Are you sure that your system date and time are correct? System Date and time appear to be correct. Saw a fix for SmugMub, but that did not work for me.. Any help is appreciated.

Everything I know about “security error” errors is in this FAQ entry (which I just created, so it’s not your fault for not seeing it before asking 😉 ) —Jeffrey

Hi there,

Just upgraded to the full version of LR3.
I have installed the Picasa plugin and donated, but there was nowhere to add the registration code… I guess I’m too early for the new version!? Or is there something I missed.
picasaweb-20100510.119

Thanks, and by the way, great plugin, I used it in my Beta install of LR3.

Seth

It’s in beta, here —Jeffry

I am running LR3, never ran the beta. I previously had version 20100323.117 installed and running, but when I upgraded to 20100702.128 and enabled it, I found that I cannot remove the prior plug-in through Plug-in Manager. I went to the modules file and manually removed the plug-in, but it did not disappear from the Manager. Also, the new PicasaWeb is listed as now listed as “jf PicasaWeb”. How do I resolve this?

Lightroom doesn’t let you remove a plugin via the plugin manager if it’s installed in the folder that was the standard-install location for Lr1, so in that case you have to go to disk to physically remove the plugin folder. (You suggested that you did, but you probably removed a different copy.) I pretended “jf” to all my plugin titles because Adobe apparently doesn’t mind naming its Flickr plugin “Flickr”, even though I had one named “Flickr” for years, so seeing the writing on the wall, I changed the name of all my plugins. —Jeffrey

Thanks for all your hard work in updating those plug-ins Jeffrey – I’m a big fan of your product and I tell everyone who has interests in how publishing photos to Picasa and Facebook. (-; So I updated to LR3 few days ago, and just donated for the new version of this plug-in (BTW your plug-in has been working so well with my LR2.)

I was wondering, compared to the LR2 version, is there new stuff added to the LR3 version? Not expecting anything since your plug-in works great for my need, but just want to be sure. Also when I installed LR3 it picked up the LR2 plug-ins, as expected not working but do I just delete them off plug-in manager and install as new or?

Additionally, I have export presets in my LR (LR3 picked them from LR2 I guess,) if I upgrade to LR3 compatible version do I lose my presets? I have many presets so I’d like to avoid losing them as much as possible.

Again, thanks for your great product, and hanging there in Japan.

Nothing should be lost with the new versions, in Lr2 or Lr3, but in Lr3 you get support for Publish. Thanks for your kind words, but watch out for terms like “product”, which implies a business and related expectations. The plugins are free and are just a hobby, so best to call them “plugins” 😉 —Jeffrey

Hi Jeffery, after I upgraded my LR3 from Beta version, I reinstalled facebook plugin from your side. However, I do not know where i can get authorisation code after I have granted to access at Facebook. Can you help?

regards,
Hannah

After authenticating at Facebook and granting the plugin access, Facebook should redirect you to a page on my site that clearly gives you the long authorization code that you then cut-n-paste into the plugin dialog. Occasionally Facebook has issues and they don’t do the redirect correctly, but from what I’ve heard, if you log out of Facebook then log back in and try authenticating from Lightroom, it should work. —Jeffrey

Feature request: store passwords securely (e.g., in the keychain) or provide an option to not store them at all or to “forget” them. It looks like they’re being stored in preset files right now, obfuscated perhaps, but still…

Otherwise, great plugin, and I sent you a donation!

-Greg (Santa Barbara, CA)

picasaweb-20100715.131, Lightroom 3, Mac OS X 10.6.4

If you log out and edit the credential list to remove them, they won’t be stored anywhere. Lr3 now has provisions for secure password storage built in (it uses Keychain on OSX), so if I can get a million other things off the todo list, I can make use of it…. —Jeffrey

I figured out what caused the publishing problems that I reported in my last comment (Invalid JSON data in reply from PicasaWeb). I changed the setting on PicasaWeb for how the URL is displayed. There is a choice between either a unique identifier or user name. If you change this, the plugin doesn’t seem to like it. I’m guessing something is getting cached that is no longer valid.

>Dynamical creation of Album on Picasa and Facebook From Exif Parameters<

Hey Jeff,

In LR2, your plugin was able to dynamically create Facebook Albums (I do not know for Picasa) from Exif parameters. I used it with OriginalDateTime to create one album per day. This did not require any manual operation on Facebook.

Now, I used your Facebook and Picasa plugins and I cannot reproduce the automatic procedure. I need to create these albums in each web sites.

Is it possible ? Perhaps in a future release ?

Thanks for your great job, Jeff

You can do it in a normal export, just not (yet) in Publish. —Jeffrey

Hi Jeffrey and a big thank you for the picasaweb plugin – a wonderful contribution to making it simple to publish photos for my family/friends. Everything works fine, just done my first export but I have a question based on my base ignorance, low intelligence and general all round stupidity:

When I export from Picasa to Picasweb, I’ve always picked the resolution setting ‘1600 pixels for prints, screensavers and sharing’. I would like to use this setting when I export using the Picasweb plugin for Lightroom but don’t have a clue how to do so because it speaks the language of ‘quality’ 0-100%, ‘limit file size’ in K, image sizing (currently set at W640, H640 and resolution (currently set at 240 pixels per inch).

How do I make any of that bewildering array of settings add up to ‘1600 pixels for prints, screensavers and sharing’?

Try format=JPEG, quality=75, color space = sRGB,, resize to fit long edge = 1600 —Jeffrey

Hey J,
First of all, thanks for your work on this plug in – it’s great!
However, I’m having some problems currently.
I have set up a publishing service a little while ago, but has since stopped using it. I even deleted it at one point, and have just been exporting pictures regularly to my picassa.
Yesterday i have made some changes to my picasa account (transferred some pictures from one album to another, renamed one album and deleted another).
Today i wanted to set up the publishing service again. I read through your instructions, and have figured i should “Refresh all remote URLs” just to be safe. However, i am getting the following error:
“invalid json data in reply from picasaweb” whenever i do that.
any ideas?
I am using Lightroom 3.2 and plugin version 20100829.136, on Windows 7 64.
Thanks.
Oded

I just pushed a new version of the plugin… please give it a try, and if it doesn’t fix it, please send a log. —Jeffrey

Does this plugin support creating a new album? I’ve searched around but I was not able to find any information on creating a new album from the plugin.

The only way I’ve been able to create a new album is to go into picasaweb, create it, and then go into the lightroom and create a publish service using the new album.

You can create one from the Export dialog; I hope to add to the Publish dialog soon. —Jeffrey

Hello,

Have you had users of your Picasa export plug-in complain that your plug-in corrupted their account with Picasa Web? I am 99% sure your plug-in created a problem with my Picasa account. After uploaded this picture – http://picasaweb.google.com/kasia.atkinson/PictureOfTheDay#5516964645017502882 my account was messed up … I can no longer do thinks like modify captions, use any option in the EDIT drop down on a specific page, add a comment (I get an error message when I try).

Any feedback you have is appreciated. I have years with of pictures and a messed up account and I cannot find a way to contact Google to help.

Thank you!
Brandon

A third-party app like my plugin shouldn’t be able to cause that kind of havoc, so if it does, it’d be a bug with Google, but frankly, I can’t imagine how this might transpire. —Jeffrey

– PicasaWeb Export V. 20101217.143
– Mac OS 10.6.5
– Lightroom 2.7

Your plugin use to work like a charm but now I get this error message:

“PicasaWeb 404: attempt to index a nil value”

I can’t upload to Picasa any more 🙁

I think I’ve fixed this in 20110113.144 —Jeffrey

Hello
I tried to use your picasaweb plugin .But how do you create a NEW album directly from Lightroom (without choosing one existing already)

Thank your for your help

Vadim

See the “Tools” section of the Export Dialog. —Jeffrey

Hi Jeffrey,

do you think it would be possible to FIRST delete the images to be deleted THEN upload changed images and THEN the new images?

I am asking because Picasa has a limit of 1000 images per album, and currently I’m stuck as it always tries to upload new images before deleting the old ones, which of course fails.

Kind regards,
Uwe

The order is decided by Lightroom, not the plugin, so there’s little I can do. I think it’s a bug that they don’t let you invoke the deletions via alt-Publish the way they let you do selective Publish, and I’ve submitted the bug, but no word on whether Adobe even agrees that it’s a bug. —Jeffrey

Hi Jeffrey

I recently changed my google account password and this seems to have affected my ability to export to my picasaweb albums.

I cannot seem to to be able to do anything as all I can see is the phase – Oops, not properly authenticated, please log in from the export dialog box etc.

I can’t seem to figure this one out? Each time I try to log in I receive – Capture required, or – Bad authentication.

If I try to create another publishing service through your plugin, my picasa log in details aren’t recognised.

Any help with this matter would be appreciated.

Kind Regards

Brett Holland

I’m not sure when Google started requiring captcha on some accounts, but it seems new. Until I can update the plugin to handle it, the best I can suggest is to log out from within the plugin, then login from a browser. Hopefully that’ll reset the “needs captcha” flag, and then you can re-login from the plugin. —Jeffrey

Hello there – I’m using version 20110419.152, and I’ve discovered following problem with keywords.

I’m using LR3’s publish service. I would like photo to be uploaded to Picasa and tagged with some of the keywords this photo has in LR. Even though I’ve installed keyword wrangler, it looks like I can choose between following options:

– ‘Do not explicitly send keywords from Lightroom catalog’ checked + filtering in keyword wrangler = proper set of keywords in exif of the photo, but no “tags” in PicasaWeb (right-hand column on single photo view page).
– ‘Do not explicitly send keywords from Lightroom catalog’ unchecked = exif has proper set of keywords (filtered), PicasaWeb tags consists of all keywords (not filtered).

This sounds like a bug, right?

I’m not familiar with “keyword wrangler” (do you have a link?), but I’m sure my plugin isn’t working with it… it’s likely updating the image file, but the plugin is referring directly to the Lightroom catalog. —Jeffrey

MacOS 10.6.7
LR 3.4.1
Picasa Web 20110606.155

Hi, love the plug in, always worked brilliantly, however when I try to export now, I get a very strange error message “Retrying after mysterious Google error ‘STORAGE_UNAVAIL’ error,”

At this point I need to cancel to prevent continuous retries. Also, the first picture from a sequence of pictures are actually uploaded, but only the first, multiple times.

Apologies if you already have received this post, I was not sure if it had sent.

No one knows why Google issues this error. All uploaders seem to see it at times. Only thing to do is wait and hope. —Jeffrey

MacOS 10.6.7
LR 3.4.1
Picasa Web 20110606.155

Just about to upgrade to 20010613.156 but wanted to say that the mysterious Google error has gone away, just exported no problem. I had changed nothing my end, the plug-in is innocent!

> Use the “refresh list” button next to the list of albums. —Jeffrey

I did that several times, and I did it just now as well. The proper names appear in the Edit Settings dialog box, but they don’t update in the Publish Services collection. And I can’t change them there, either. When I double click on a gallery name, a dialog box for changing its name comes up, but the field is grayed out.

Oops, sorry, I read your original question wrong. It’s not possible to change the name of a gallery (due to bugs in Lightroom), so the best I can suggest is to delete it and re-add it, using the “populate” feature to refill it without having to reupload anything. —Jeffrey

Can you make your program run multiple processes in the future? I am sure that uploading is not a CPU intensive task so while it is doing that it could be processing other photos. Thanks

It should be able to handle multiple simultaneous uploads, though there’s a bug in Lightroom such that they might occasionally kill each other. —Jeffrey

I just upgraded to 20110821.167 and is warned to reauthenticate at the top of the Export Dialogue. Where exactly is that dialogue box?

The Export Dialog is the dialog that shows up when you click the “Export” button. —Jeffrey

Hi, i have a problem with your Picasaweb-Plugin.
I use the latest LR (3.4 ithink) and your latest plugin, i downloaded it nce agin right now. When i wonkt to export videos (mov) to picasaweb the export is stopped after a view minutes an an error message accours: “Attempt 1 (Error Connection Lost …).

Can you help me? The other functions are running well and also i can uplad a video to picasaweb “by hand”

Thanks in advance!

Markus

It sounds like the video is taking too long to upload, and your connection to Google is timing out somewhere along the line. Unfortunately, I don’t think there’s much I can do but to suggest more bandwidth… )-: —Jeffrey

Hi,
I’ve been using your plugins for a while now, but not since google started “merging” picasa and google+ photos.
Using version 20110908.169 of Picasaweb
Lightroom 3.4.1 on a 2010 iMac running OS X Lion

I’ve been able to authenticate to my picasa account.
When I try either to straight export pictures to PIcasa, or to use the Picasa publish service, the process will randomly stop with an error 400, 404 or 500. Sometimes it will have uploaded pictures, sometimes not.
I’ve also tried relinking pictures that are both on Picasa and in LIghtroom. Again, it works for one but not the other ….

I’ve tried variations in sizes (from 15 to 2 Meg) but it doesn’t seem to change anything.

Also, as a control, I have NO problem using the Picasa uploader from the site on exported jpg)

I’m probably missing something basic, but for the life of me i can’t figure out what. Would you have a clue ?
Thx

All I can guess at this point is flakiness at Google. It’s likely that their uploader uses different endpoints than my plugin, so I can understand one working but not the other. I’ve found bug reports by others of these kind of errors dating back to 2009, but no one has been able to pin them down. I’m not sure there’s much I can suggest but keeping your fingers crossed. —Jeffrey

First of all, let me say thank you. This plugin does so much more than I expected! I was thrilled at the ability to associate existing images in lightroom with those in picasa web albums. Unfortunately I seem to have run into a little problem. So I migrated from Picasa to Lightroom and in the process of doing that I also imported all of the original versions in the Originals and .picasaoriginals directories. This means that for images that I edited in Picasa I have two versions with the same name. It seems that the plugin will not attempt to associate images when there is more than 1 with the same file name in Lightroom. Just wondering if you can suggest any workarounds.

The whole “Associate” stuff is a big can of kludgy worms… the best I can suggest is to either associate them manually (which would be arduous if there are many), or to remove the .picasaoriginals images from your catalog, do the association step and hope for better luck, then add the picasaoriginals back. Not very elegant, sorry. —Jeffrey

Hi

Great plug-in! I had a question about upload quality.

I went for 100% (despite the warnings) on the basis that I want those who get my webalbums to be able to download and print them in high quality prints.

So two questions.

1. I noticed that when I uploaded the same pics via Picasa itself, the file size in webalbums is slightly smaller, even though I uploaded those at “original size (slowest upload)”. Not sure why this should be. Do you know?

2. Is there REALLY no benefit in uploading at 100% quality? If I those I share my pics with to be able to do high quality prints (indeed, to some extent I use webalbums as one of a number of backups, another reason to keep them high quality), then how low below 100% can I go: 90%, 80%, or … ?

Sorry about my naive questions.

David

When you say “the same pics”, do you mean that you first export with Lightroom, having the plugin save the exported copies locally as well, then you uploaded those locally-saved copies via other means, and the result is different? That would be strange. But if you’re comparing uploading an original JPG one way, and a Lr-generated JPG via Lightroom, of course they’ll be different. As for the 100% quality issue, in many cases, yes, there is really no benefit whatsoever, but “many cases” doesn’t mean “all cases”, so if you want 100%, go for it. I don’t. See my writeup on JPG quality to better inform yourself, then make your decision. —Jeffrey

Once authenticated can we save this authentication and authenticate to another account and save that one too. I have two Picassa accounts, one account where I store all photos with no download capabilities and one restricted account with download capabilities. It would be appreciated not to have to re-authenticate everytime I change accounts. Is this possible?

Sure, after having authenticated to the second account, when you next deauthenticate a popup menu button appears with the accounts for which you already have authentication, and you need just select one. —Jeffrey

Hi Jeffrey and thanks you for your work!
I set up “Export to PicasaWeb” Lightroom Plugin without any other your plugins but I do not see “Snapshots on Export” section in it. Where could be the problem?

Using version 20111012.173 of “Export to PicasaWeb”, Lightroom version: 3.5 [775451], Operating system: Windows 7.

WBR, Dmitry

That section is included only in a normal export, not in Publish. It doesn’t feel like it makes much sense in Publish….. do you think it should be there, too? —Jeffrey

Jeffrey, I don’t understand 🙂 If “Snapshot on Export” built in “Export to PicasaWeb” then:
1. How can I export to disk using this features (Snapshot on Export) if “Export to PicasaWeb” do export to Goggle Picasa Web only?
2. Where can I see “Snapshots on Export” section if I set up only “Export to PicasaWeb” plugin? I do not see this section in settings of “Export to PicasaWeb”. I do not see this section in settings of standard “Hard Drive” export plugin.
WBR, Dmitry

The stand-alone plugin is for any export, but you have to enable the plugin then add the “Post-Process Action” (see the lower-left corner of the export dialog). It’s already there in the PicasaWeb export, but not in the PicasaWeb Publish, but I think I’ll go ahead an add it in the next version. —Jeffrey

I’m currently using 20111216.177 and see that a newer version is now available but when I try the “upgrade now” button I get the message “The plugin does not seem to be installed in a location where Lightroom can write to it”

I have all my plugins in a common folder in the adobe/lightroom folder – is there something else I need to do to enable that “upgrade” button?

Thanks!

Nic

If the plugin can’t write to the parent folder, it can’t do the upgrade. Check your folder permissions, I guess. —Jeffrey

Using Picasa Web Version 20111222.178.

Thanks for making this plugin available. I’am hoping you can help me with one problem.

When I upload the my photos from lightroom to Picasa web using your plugin, non of my lightroom edits are uploaded with the photos.

What am I doing wrong. If I export to my hard drive, the photos are exported with all of my lightroom edits?

Am i doing something wrong?

It sounds as if you’re got the format set to “Original” (the original master image) rather than “JPEG”. —Jeffrey

Hey, thanks for this! It is awesome… with one issue: on a network timeout (I assume between me and picassa) there is a modal dialog telling me about a retry. The cancel button on this doesn’t work and the dialog never goes away. I have to force quit lightroom to continue.

Unfortunately, there’s nothing I can do about that. The cancel button merely leaves a note for the plugin to abort the next chance it gets, but if things are locked up deep within the OS networking code, Lightroom and the plugin never get a chance to act on it. It’s rare that the OS never returns control to Lightroom, but it seems that’s what’s happening in your case. )-: —Jeffrey

Hi Jeffrey, i would transfer from picasa app completely to LR, your plugin is a great help for me. But there are still some minor functions that would come handy. Either i didn’t get everything right from your plugin documentation, or these features are missing 🙂

Mainly my workflow is importing the photos to a dated, and named dir (Windows AutoPlay photo import) and use that as picasa album name. Is this doable with your plugin, or i should create some workaround?

Keep up the good work!

br, Lajos from Hungray

The rename during import is part of the normal Lightroom import, so once you get them into a folder with a name you like, you can use the plugin’s “auto dest” (automatic destination) feature to create the album as Picasa. For an example of the same kind of thing using my Zenfolio plugin, see this writeup, and apply the idea to your needs. —Jeffrey

Live in NY,writing from Mexico.
To make a new album for Picasa I have to go to edit settings and create the album but then I get a message that there are no photos to upload. I then have to go back to lightroom and drag the photos into the album. Is there, or, can there be a way to create the new album before going into edit settings?
Also, when uploading from Picasa there is the ability to choose the pixel count (1600) or original. I need to upload full resolution sometimes so people can then download for print. Any suggestions?

About the latter thing, you need a separate publish service for separate upload types (e.g. original vs such-and-such a size), but for one-off uploads of any type, it’s probably easier to just use Export rather than Publish. About the new-album-creation workflow, it’s not very smooth, I know. It’s the result of working around layers and layers of bugs in Lr3.0, and now that some have been fixed, I should revisit it, but that’s a lot of work in a fragile area, for relatively little gain, so I’ve been resisting… —Jeffrey

Picasa Limits:
http://support.google.com/picasa/bin/answer.py?hl=en&answer=43879

Maximum number of web albums: 10,000
Maximum number of photos and videos per web album: 1,000

Free Storage Limits:
http://support.google.com/picasa/bin/answer.py?hl=en&answer=1224181

Basically, keep your pics resized to 2048×2048 or less and they won’t count towards your storage limit of 1GB.

There is no way to contact you about other topics. Perhaps you could put that on your website somewhere? Any plans to make an upload to storage cloud option? Such as Amazons S3 or Google’s Developers Cloud Service?

Also how long are you planning on the plugin pages getting with all the posts and software updates on one page? :-p

KM

My email address is on the “About Me” page. I’ve no plans for cloud-storage plugins. Don’t know what to do about the long pages, except that doing nothing is easiest. 🙂 —Jeffrey

Hi – If I upload an image from my desktop to PicasaWeb will your Picasa plugin “Sync” with the Picasa web album and download into lightroom?

I’ve been using smugmug and picasa (with your plugins) and find I use picasa more so I’m canceling SM., but I just discovered they are promoting a plugin that “Syncs” which i really like …

Anyway, love your lightroom stuff – thanks!

S.

No, it’s a one-way Lightroom-to-PicasaWeb thing. —Jeffrey

Once I figured out how to use your plugin, Jeffrey, I think it’s pretty awesome! I love how you document how to do damn near everything with it, including associating catalog images with files already on PicasaWeb, Repopulating, etc.!

I have hit only one snag, however, and I am hoping you can help me with it: I cannot tell Lightroom that an image in a Smart Album in your plugin is already published on PicasaWeb. It still thinks it is a “New Photo to Publish”. If it were a regular Album, I could just repopulate, but this is a Smart Album.

The image is already associated with the one on PicasaWeb, so I tried using the “Resend Metadata…” button in the jf PicasaWeb Extras menu item. Unfortunately, it returned “Unexpected HTTP status from PicasaWeb: 404 No album found.” However, I know the album does exist, and it has the exact same name, capitalization and all! Your plugin was the one that created the Smart Album in Lightroom (using dummy criteria at first, of course).

Any idea how to get Lightroom to recognize that this image in the Smart Album has already been published? I don’t want to hit “Publish” again, in case it uploads the image a second time. Thanks!

It would indeed upload the image a second time, so don’t publish it. It’s a limitation in Lightroom, one we can hope will be lifted in Lr4 (and/or Lr3.8), but until then, it’s probably best to not include the photo in a smart collection. —Jeffrey

Hi from Viña del Mar (Chile),
I’m a jf-picasa plugin user, since many years and I don’t have any complain, just congrats.

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

Plugin version: 20120308.186
Lightroom 4 crashes when trying to upload an 80MB video. The crash happens after Lightroom finishes conversion

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

Lightroom 4.0 – Plugin Version: 20100308.186

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

Jeffrey, I’d love for the plugin to either let me edit gallery names in LR, or for it to automatically (or semi-automatically, through a Refresh button) get the changed gallery names from Google Photos. I have multiple galleries whose names I’ve changed online but can’t get LR to reflect it. If I remove the gallery and re-add it, I inevitably end up with photos that LR can’t match up to the ones already uploaded, so I’d rather not do that. Thank you in advance for any help with this!

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

Windows 7 x64
Lightroom 4.1 RC1
PicasaWeb 20120508.199
From Los Angeles

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

Hi Jeffrey,

Greetings from Chicago!

I manually uploaded a video to Picasa outside of your plug-in because the file was in excess of 100 MB. Then I manually associated it in your plug-in’s extras with the Picasa URL. I can’t find where I mark that file as up to date in Lr, so I can get it out of the queue in the plug-in the be published.

Thanks so much for a pointer to what must be obvious, and I’m just missing it today.

Peter

It’s a big kludge, but you have to have it added to the collection via the “claim” feature, rather than putting it in there yourself. It won’t work at all if it’s a smart collection, and my not work otherwise, but is worth a shot. —Jeffrey

The incorporation of the collections is something I was dreaming for… I used to have many services to keep some order in my catalog and was a nigthmare each time I needed to change a setting… now just a couple of services to keep different setting is enough.
Thanks

Hello,

Is there a way to export to a G+ page and not to the primary G+ account?

Regards,
Dan

I’m not sure what a “G+ page” is, but Google currently has no API to export to G+ anything yet… currently, the best we can do is upload to PicasaWeb and share to G+ from there. —Jeffrey

Helly Jeffrey,
Thanks for this wonderful plugin.
First I have a silly question, maybe already replied but I can’t find the answer: after a PicasaWeb album publish, do we need to keep the local copies which were written to the export folder? I noticed it looks like I can remove them with no harm to my published album or original collections. But is there any drawback to this?
Second question: do you plan to add a feature to copy & edit an existing publication service based on the PicasaWeb plugin? This would maybe allow to change the export folder that usually can’t be changed after initial setup, without re-creating the publication service from scratch.
Thanks again for your superb work!

No need to keep the local copies… the default is that they’re deleted automatically (because the default “Export Location” is “Temporary Folder”, which somehow you got switched away from). As for the second question, I think the inability to change the export folder in Publish is an anachronism that I can remove… I’ll look into it. (UPDATE: I had forgotten that Lightroom enforces the inability to change the setting, so there’s nothing I can do about that, so to make a change you’ll have to indeed recreate the whole publish service) —Jeffrey

Hey Jeffrey,
Thanks for making the world a better place to work in!! I’m writing from California high in the Sierras. Re: picasaweb-20120820.211, Maybe this is a no brainer, but unlike your facebook plugin, I can’t seem to find a way to publish to a google plus page associated with my account. Am I missing something or is it not an option?
Thanks,
-Erik J

Google has not released a publishing API for G+ yet. —Jeffrey

Writing from California.

One snafarkle that I encounter with upload to Picasa plug in (downloaded latest version today) has to do with updating a Gallery that was created using an export with sequence numbers. I use sequence numbers to establish the logical sequence of the pictures by rearranging photos in a LightRoom collection before I export to a new Gallery. Works like a charm for the original upload and I can always re-sort the Gallery in Picasaweb if I change something.

However, when I update a few pictures from the collection the uploaded images are assigned new sequence numbers based solely on the pictures to be uploaded. Ideally, I would have an option to re-use the old sequence numbers when updating.

I recognize that this option is not useful when I add new images to the collection, but suggest that the update-only case happens frequently enough that it is worth the complications of having another option.

Thanks in advance.

There is, essentially, no right way to do what you want. Lightroom doesn’t allow for it (the file-naming stuff is all built in, so whatever it does with sequence numbers is what it does). But in the parallel case of my collection-publisher plugin, I go to great lengths to “do the right thing” when the user wants sequence numbers in the filenames, but no matter what I do, someone comes up with a use case for something else. It’s a lose-lose situation to use sequence numbers in Publish. Overall, the right way to do this would be for the plugin to tell Google the explicit order found in Lightroom, but Google does not support this. 2½ years ago they said this support was coming “soon”. —Jeffrey

Hi Jeffrey (writing from Manhattan) – I’ve been using your facebook plugins for a while and have loved them, and am looking to switch to google+ but am having issues with the picasaweb plugin for lightroom 3 on mac – when creating a new album w/ the facebook plugin it asks for a local album name and a facebook album name, but the picasa pluggin only seems to ask for local name. When I create an album and hit “publish”, I get the error:
picasaweb#216 +2193.4: [x119a597f8] @Export line 834:
Missing destination cookies:
[x119a597f8] @Export line 834
[x119a597f8] @Debug line 1254

and
Debug:757: Assert @Debug:757
Am I doing something wrong? I just upgraded to make sure I’m up to date – version is 20121014.216
Thanks!
Eric

I’ve made a FAQ for this issue —Jeffrey

Hi: Do you plan to insert “name of the album” token?. It should be really useful. Thanks

This is perhaps possible, but a bit problematic with how things are built under the hood. I’ll give it some thought… —Jeffrey

As I understand the PicasaWeb Plugin. New Picasa Albums must be created by editing the plugin Settings. And this in turn creates a Publish Service Collection/Smart Collection or both. A Right Click on any PicasaWeb collection present the context meny that permits the Import of Smart Collection Settings creating a nes Publish Service collection that does not point to an existing PicasaWeb Album. Publishing this imported Smart Collection fails and I can understand why. If I create a Smart Collection and PicasaWeb Album via editing the Publish service settings, I get a default generic Smart Collection which can not be renamed. Is there a way to import an existing “lrsmcol” file into the existing smart collection created with the edit of the PicasaWeb Publish Service?

All of my Publish Services are managed by smart collections with complex queries so that they self populate. I can share these complex smart collections by exporting them from one Publish Service and importing them into another and modifying them slightly and (usually) renaming. This works well with all of the other ‘jf’ Publish Services but not the Picasa Web due to the restrictions notes above and I suspect imposes by the PicasaWeb API or LR.

No, sorry, this is a problem with Lightroom’s plugin infrastructure. Creating a smart collection that way does not work with any of my publish plugins… I can imagine only the most simpleton plugins could make that work. It’s really a poor design, but there’s not much I can do about it. )-: —Jeffrey

I would like to insert blank lines into my captions and I saw you can do this with newlines. I tried every combination of \r and \n that I can think of and can’t get it work. Can you give me an example of how you would use newlines to insert blank lines in caption templates. Would you just repeat the code if you want to insert multiple blank lines? Thanks!

Actually adding a blank line (via control-enter) or using <br> should do it. —Jeffrey

New York
Tried to create new album in Picasaweb. Getting message “corrupt collection settings”. Not getting drop down in Lightroom for “authentication code”. Have been using successfully for years. Problem seems to be with Google Plus. How can I correct, or, revert????

This sounds like a form of this bug. If you can’t revert to a backup catalog, the best I can suggest is to delete and recreate the collection. )-: —Jeffrey

Version 20130520.233

I’m new to video. I just tried uploading two videos to Picasaweb and the first got rejected because (according to the message) it was larger than 100MB.

I searched the web and it appears as if the limit is 1G. Do I need to enable something somewhere? The finder says it is 233MB.

Thank you for your time,
Perry

As noted multiple times above, Google allows up to 1GB through its own upload, but the max through the 3rd-party API is 100MB. —Jeffrey

Clear. Thanks for a good idea.

I do not think there is much future in picasa API or picasa as it stands. Everything is moving to g+ and gdrive. Note that in g+ you can add pics via gdrive so why not add this as an option and avoid all of the limits. Workflow would be LRto gdrive to picasa. Atleastan option for. Large videos.

Well, I do have a Google-Drive plugin that you can use as well. —Jeffrey

Jeffrey,

I emailed you yesterday regarding the “corrupt collection settings” error with the picasa plugin and LR5. I was able to cure the problem by performing a new authentification with picasa rather than choosing my existing username from the drop down menu during setup.

Hi Jeffrey
When I am exporting to Picasa in Lightroom 4, I am getting an error saying that the plug in cannot render because it cannot find my photos. Perhaps its been deleted or offline.
Any suggestion as to how to fix this?

I suspect Lightroom is telling you that it doesn’t know where your files are because it doesn’t know where your files are. Did you move them after pointing Lightroom at them? Delete them? Are they on a disk that’s not available at the moment? When you “show in Finder/Explorer”, do you see the files? —Jeffrey

Hi Jeffrey,
I am curious to understand whether it is possible to actually sort the picasaweb collections in Lightroom by name first. Much apologies if I overlooked this setting, but it appears that the sorting is by collection type (all smart folders first then regular collections) first, then by name. Can this be changed?

I am on version 20130701.241

Thank you in advance!
Regards, maik

The plugin has no insight here, so it’s whatever Lightroom allows, and to my knowledge, there’s no control over the display order. —Jeffrey

Hi Jeffery!

I’m writing from New Jersey regarding the Picassa plugin. I am using Lightroom 3 on a Win7 PC. I experienced the “missing destination cookies” error so, as instructed in the FAQ, I deleted the Publish Service and set it up again from scratch. Now I am receiving the “corrupt collection settings” error when trying to publish. What can I do to fix this?

Thanks,
Dan

The 2nd error is just a more general, less specific version of the first. Something seems corrupt about the entire publish service. )-:   I can only hope that if you create a new one (perhaps before even deleting the original) that it’ll be free of the corruption. I just don’t know; the plugin is as much a victim as you. )-: —Jeffrey

i upgraded to LR 5.2 and found that plugin i had installed earlier this year no longer worked. so i downloaded the most recent version, 0926.248 and tried to install this. using plug-in manager, i chose add (having deleted the old version from LR) and then selected the win folder within the unzipped downloaded file.
i got the error message “an error occurred hile attempting to load this plug-in.”

what am i doing wrong?

See this FAQ. —Jeffrey

Hello Jeffrey!

Is it possible to authenticate with this plugin against my Google+ page account?
Reason is – I’ve created a Google+ Page and would like to publish photos from LR5.2 to an Album on this site directly.

Thanks for your advice!

KR

Albert

Google still hasn’t provided an API for G+, so you still have to go through PicasaWeb, but PicasaWeb albums show up in G+ automatically, so you can get something pretty close that way. —Jeffrey

Hi,

I Like your plugins and have found them very useful!

I have comment or a question regarding the way Lightroom utilizes Export Plugins.

I often prepare sets that I want to share in several channels. I might want to share the same set:
1) on my hard disk to be syncronized via iTunes with my Apple TV in the living room
2) on Adobe Revel to show people from my iphone or iPad
3) on Facebook
4) on Picasa

I imagine having a set and then it should be able to tick boxes for each earlier preset channel.

Is there a way to send and update a set in several channels with your plugins or in some other smart way?

The short answer is “no”, Adobe doesn’t expose hooks that make it feasible. If there are common patterns of how you want to export, perhaps do it with keywords. It’s an unsatisfying answer, I know. —Jeffrey

Hi Jeffery,
I recently switched from a pc to mac and reloaded your most recent plugin in LR5. After editing many photos I have been reloading some to Picasa. Under “One image has been selected for import” in the Picasa Web: Meta data management section, the “replace the most-recent previously-uploaded copy” has been ticked. But it’s not replacing it like it did before on my pc, It’s just adding the new double copy. Is there possibly an issue because the images were not originally uploaded with my new computer?

Thanks,
Randall
Portland, OR USA

If you copied over the catalog from the old computer to the new, all the upload history should be with it, so I’d expect it to work. When viewing the photo in Library and selecting the “All plugin metadata” metadata-view preset, do you see “Uploaded to PicasaWeb: yes”? —Jeffrey

I’m trying to download and unzip your Picassaweb plug-in for Lightroom 5.3. I can download it but don’t seem to understand where to put it or how to unzip it to make it functional. Can you help?

See the install-instruction link in the upper-right of the page. —Jeffrey

I am exporting from smart previews (long edge set to 2048) and all the images end up being smaller than that and all with a different sizes, ranging from 1915 to 2010 pixels on the long edge. This happens with the current version and with the previous version of the plugin.

Windows 7, Lightroom 5.x, 20140204.252

The sizing is all done by Lightroom, so whatever results you get would be the same with a vanilla “Hard Disk” export. Perhaps you have the “don’t enlarge” option set? —Jeffrey

Hi,

I’m using latest Export to PicasaWeb (20140422.254) with Lightroom 5.4 on Windows 7 64bit.

When I’m uploading mixed set of pictures and 1 video to PicasaWeb, there is an error about video file size being over 100M (it is around 340M). However, after checking some web resources it looks like the maximum file size for picture is 100M and 1G for video. Are picture and video files being mixed somehow here, should the plugin be able to upload 300M video to PicasaWeb?

Thanks for wonderful plugins!

Their limit for 3rd-party apps is more restrictive. I’ve just added a FAQ about it. —Jeffrey

Do you answer cries/pleas for help?

Often. —Jeffrey

Hello from Italy,
you’re simply the best, very good job.
Now I’m trying the plugin and just trial period expires I will definitely donate to the work done

Lightroom version 5.5.0 build 968504 for Windows Windows 7 Home Premium Edition (x64)
Jeffrey’s picasaweb plugin for Lightroom, version 20140715.265

Uploading via the plugin does not trigger Picasaweb’s “Notify these people when photos are uploaded to this album” option that applies to albums that have been shared. Is this something you can check into? Thanks!

I just checked, and the API the plugin must use has no mention of any notification thing, so it’s not something I can enable. If they’re not honoring the album setting, it’s likely a bug that you should report to them. —Jeffrey

A comment re: http://regex.info/blog/lightroom-goodies/picasaweb#comment-52106

There is a setting called auto enhance which is buried deep in your Google + profile settings. Switch it to off. And yes, they totally do stuff to your pictures. 🙂

Due to APIs then, no chance of a plugin publishing to G+ Business page?

Until Google opens up APIs to G+, the plugin can publish only to PicasaWeb. For the last few years they’ve had PicasaWeb feed to G+ pages, but I don’t know whether that applies to G+ business pages… —Jeffrey

Hi from Greensboro, NC!

I received a message saying that the video I was uploading was larger than the PicasaWeb account limit of 100MB – the file is 128MB. But, in searching online, I believe the actual video limit is 1GB (if not larger). Is there something else going on?

Thanks!
-Bobby

Their limit for 3rd-party apps like the plugin is smaller than their limit for their own apps. —Jeffrey

First of all, thanks for great plugins – I use quite a few of them, and these are incredibly useful. Recently, I started to use PicasaDesktop app to tag faces in all my photos (as a first step in my workflow), to import it then into LR and then publish (to a few places, but importantly, to PicasaWeb) directly from LR using your jfPicasaWeb plugin (the latest version). This process works really well for keyword tagging (I use AvPicFaceXmpTagger to propagate Picasa tags into XMP; I also tried writing into XMP directly from PicasaDesktop). Now, PicasaDesktop also creates metadata for face regions (rectangles outlining faces with name tags), and when I use PicasaDesktop to upload to PicasaWeb this information is preserved (I can see face regions with proper names). However, if I use LR with jfPicasaWeb to upload the same file (that definitely contains face region metadata in all known formats), then I get the proper face rectangles in PicasaWeb, but all names turn into “Unnamed”. I don’t think this is an issue with jfPicasaWeb per se, as the same thing happens if I upload the same file into PicasaWeb directly (it seems that PicasaWeb ignores face nametag metadata). No matter what kind of metadata manipulation I performed on the uploaded file, the only way to get properly named face regions in PicasaWeb was to upload with PicasaDesktop.

First question, am I doing something wrong? 😉

If not, then I suspect that PicasaWeb is ignoring face nametags in metadata, and PicasaDesktop uses separate API calls to set these up on uploaded photos (there is even upload status line ‘syncing face tags’ or something like that). It seems that somebody looked at some of the face tag Picasa API: http://www.klick.com/health/news/blog/retrieving-face-tag-data-from-the-picasa-web-api

Would be great to get face regions working. I am even contemplating exporting output from the publishing sets into a folder, and then upload with PicasaDesktop. I would really prefer not to – sync provided by jfPicasaWeb publishing sounds awesome. Can it support face regions?

Thanks!

Unfortunately this is unlikely to get solved soon. The plugin doesn’t have easy access to the XMP data, and it would be a lot of work for few people. I’d bump it up in priority if face tagging ever gets more mainstream… —Jeffrey

Thanks Jeffery for making this plugin available. I’ve just begun using the plugin for Google+ (v.2015-206.279) and it seems to be working properly, EXCEPT for the ‘automatic’ publish feature which should be re-publishing based on further development, as well as changes to chosen metadata, but it doesn’t work. I don’t see anyone else complaining about this, so I must have done something wrong(?) Could it be that I changed the default “temporary” location to a folder I wanted to keep track of? …TIA!…

The “metadata that triggers republish” stuff has been flaky since it launched. I’ve submitted bug reports to Adobe, but well, no fixed yet. Lots of complaints across many plugins, so you’re unfortunately not alone. )-: —Jeffrey

After upgrading to Lightroom CC, I get a popup with the message “Lightroom needs to configure your system for the $$$/x289=jfPicasaweb plug-in.” After clicking OK, it then runs a command prompt with lightroom.exe -register. The first couple of times, this action completely froze my computer and I forced a reboot. I finally let it run for quite a while and it finished doing something, but the prompt still appears every time I start Lightroom and now it doesn’t seem to do anything. I did try completely removing the plugin and re-installing it, but nothing changed. depsite the persistent prompt, the plugin is working just fine.

Thanks for the awesome plugin,
Jeff from Texas

The word from Adobe on this is that if it keeps coming up, either reinstall Lightroom or run “lightroom.exe -register” as an admin. —Jeffrey

Hi, with LR 6 I do get the following error message when starting LR up: “Lioghtroom needs to configure your system for the $$$/x289=jf PicasaWeb plug-in”.

Tried to reinstall several times, no help.

All the other plug-ins work fine.

thanks!

Please see this FAQ. —Jeffrey

Picasaweb and Ipernity plugins were working fine till I upgraded my LR5 to LRCC (6). I’m running Win7 SP1 x64, and LR is x64 as well. After I upgraded, both Picasaweb and Ipernity would display the following message *every time I start LR”. Initially I clicked OK, and an elevated command window ran and exited so quickly I couldn’t see what happened. I soon discovered that this error displays every time I run LR, so I uninstalled both plugins. I was hoping the latest update would resolve the issue, so I just installed it only to find the same error is generated. I can’t attach a screen shot, so here’s the error: “Lightroom needs to configure your system for the $$$/x289=jf PicasaWeb plugin.” Sadly, once again I just uninstalled both plugins. Flickr and the other plugins I use all work fine. Thanks for your help!

Please see this FAQ —Jeffrey

I’m sure you’ve already thought of it 🙂 Can we get face regions exported in the PicasaWeb plugin?

Kind regards,
Øystein

I get the following dialog every time I start Lightroom: http://i.imgur.com/azzgEI3.png
When I click OK I get prompted to give “Windows Command Processor” admin rights, presumably to install something. I allow it but get no visual feedback that anything actually happened.

OS: Windows 8.1 64-bit
Lightroom 6 (latest updates, but not CC)
picasaweb-20150517.280.zip installed

Please see this FAQ. —Jeffrey

Hi,
I made some tests regarding using Google Photos with this plugin. I think that as long as I keep the file size to 16 megapixels it will not count against my limit.

However, there is a bug: The plugin currently prevents me from uploading videos larger then 100mb. This is no longer a limitation to Google: https://support.google.com/picasa/answer/43879?hl=en

I can actually upload videos as big as 10gb as long as they are still 1080p.

Can you please push a fix for this?

Thanks

Unfortunately, it’s a limit for non-Google apps. See this FAQ. —Jeffrey

Hello Jeffrey,

I use your PicasaWeb plugin with great pleasure for quite some time now and I would like to thank you for it. Sadly I now encounter a problem with creating a new album. The plugin (Lightroom) gives me the following message:
“Create new album at PicasaWeb aborted: Unexpected HTTP status from Google: 500”
I have the latest plugin (20150621.281), run Lightroom CC 2015.1
Could this have something to do with Google switching to Google Photos?

best regards,
Jeroen

It’s just Google having “issues” on their back end. It’s been pretty rough for a while now. Not much we can do but wait for them to get their act together. —Jeffrey

I have totally had it with Google Photos. Today, I tried to upload photos with your plugin. I tried to create an album, which resulted in an error. I then went into Google directly, created the album, and tried to upload photos from your plugin and received 403 errors. This is a site for my camera club and I need to upload about 70 photos each month. I want to move the site to Flickr. Is there some way that I can use your Flickr plugin to access two accounts, mine and the one I want to start for the camera club? Thank you

My Flickr plugin can work with multiple accounts just fine… you choose the account when you export, or when you set up a Publish collection. But you won’t necessarily find things are better there… Flickr has been really Flaky lately, with lots of upload problems. Like with Google they come and go, and if you hit them, the only recourse is to wait and hope. —Jeffrey

Would it be possible to have a setting to automatically create an album (or select it if it already exists) based on the directory name that the images are coming from? This way I would be able to save an export profile for picasaweb uploads. Currently it is mandatory that I visit the export dialog box and create an album prior to uploading. Thank you for all the hard work! I am a contributor, twice now!

Yes, you can do this via the “add/edit auto destination” link just below the list of albums in the Upload Destination dialog. The feature is used to similar effect in this blog post, so that should get you started… —Jeffrey

Using PicasaWeb Export ver. 2015.1215.284 with Lightroom 5.7.1. I can upload .rw2 files manually through the Picasa Web browser interface. However, when using the plug-in the final export dialog says “PicasaWeb does not accept “.rw2″ files for upload; aborting” when I try to use it. I am also blocked from uploading other types of RAW files such as “.cr2” and “.nef” with the plug-in. Is this a limitation of the API or can I get around this?

It’s an API limitation. The API has not been updated since before Google Plus was released, so it has no support for all the stuff added since then (e.g. Google Photos). If they ever release a new API I’m sure I’ll make a plugin for it, but considering it’s been so many years since Google Plus was released and there’s still no API, I wouldn’t hold my breath…. —Jeffrey

Hi Jeffrey,

Just wondering if will be possible to log in to different google accounts-roots at the same time using this plugin.

Right now, using the browser, the user can be logged to several google accounts but the plug in only allows to configure just one root & account.

Working professionally is very common to have different accounts to upload pictures. They can be owned or from clients

Thanks for you great work and comprehension

Best regards,

Luis Muñoz

It’s unlikely, sorry. It’s easy to switch among users with the plugin, and each Publish Service can have a different user (so in that sense any number of users can be active at the same time), and for non-Publish exports the Google account is part of an Export Preset so you can make a preset per account… —Jeffrey

Picasaweb is being discontinued as of May 1, 2016 (March 1, 2016 for Picasa desktop app). Hoping there will still be a way to export from Lightroom (5.7).

http://www.androidpolice.com/2016/02/12/google-decides-to-shut-down-picasa-directs-users-to-google-photos-instead/

I have the impression that you’ll still be able to upload photos. If/when they release a Google Photos API, it will be #1 on my to-do list to make a plugin for it. —Jeffrey

Jeffrey… I was using your pluggin years. I have close to 200 Albums. I realize now that I can upload full resolution all my pics now. Problem.. all my albums has been resized down to 1024 since storage was not unlimited before.. Is there any fast an easy way to change resolution to full (no resizing) for all albums that I already created and mantained on your PicasaWeb plug-inn estructure?. Plug-inn version 20151215,284. I write from Spain. Thanks a lot

BTW… I’m afraid of the lack of API support for your. I’m seriously thinking on moving to Flickr… any advise? Any way for migrate all my work to there?

Just edit the Publish Service and adjust the resize options to your liking. When you save the settings, Lightroom will ask whether you want to republish everything. Answer “yes” and do so, and the copies at PicasaWeb will be replaced with new copies. About migrating, I don’t know about tools at Flickr, sorry, you should check there. —Jeffrey

Ah, i just saw the hidden window. Here’s the error:
Assert Failed picasaweb#284 +42513.2: [x7faed548cc98] @OAuth2 line 132:
Couldn’t authenticate: result in refreshAccessToken not a string:
[x7faed548cc98] @OAuth2 line 132
… [x7faed548cc98] @PicasaWeb line 108

The superficial problem here is that my plugin does not handle this situation gracefully, but the underlying situation is Google being flaky. Considering that they’ve been really flaky for the last year or so, and that they’ve announced the shutdown of PicasaWeb, I don’t have much hope that their error will be fixed, and I’m reticent to spend the energy to make the plugin respond more gracefully. Hopefully Google will release a Google Photos API and we can all move on to there… —Jeffery

Hi Jeffrey: I’m planning seriously move from Picasa (now Google Photo) to Flickr. Seems like Google compress photos and videos (even if they are short or smaller than 16MP). Of course, the lack of support of your Lighroom pluggin is the final add to move to flickr. Problem: I already have 100 albums on Picasa, that would move to Flickr. Is there any way to do it smoothly?

Thanks

Flickr may well have migration tools, but other than that guess I don’t know of an easy way, sorry. —Jeffrey

Hi Jeffrey,

I’m able to authenticate to my normal google account with your plugin (@gmail.com), but my google apps account (@domain.com, grandfathered free plan) fails with a 404 unknown user. Anyone else running into this?

Thanks,
Allie

It’s not rare these days (see this FAQ), but I’m not sure whether it has anything to do with the “goodl apps” nature of the failing account. So far, it just seems to be random flakiness. —Jeffrey

Hi Jeffrey!

Thanks a bunch for this magnificent plugin. I’ve been using it for some years now on different machines and have always loved it. One thing I noticed recently though: when changing the star rating of an image, it reappears in the Republish section even though I unticked the box allowing the plugin to republish after a change to ratings (actually I unticked all the boxes just to be sure). I tried working with colours instead, but this makes the images pop up in Republish as well. Any workaround for this one? I’ve seen similar requests for changes to metadata where you explained this is actually a problem on Adobe’s side, but I kinda hope this is different (and therefore solvable!).

Thanks a lot for your great plugin!
C

If you’ve set things up in the “Metadata That Triggers Republish” section and it’s still not workin, then sorry, it’s not different…. still a bug in Lightroom. )-: —Jeffrey

Hi Jeffrey,

For my first series of photos only approximately 35 of the 364 total items that I was attempting to upload actually uploaded to Google Photos. I received this error message:

“Couldn’t render image: readNegative: dng_error_bad_format”

Can you help me get this to complete?

Ben

This is Lightroom’s cryptic way to say that your master image file is corrupt (or couldn’t be read well). —Jeffrey

I have what Google calls a “Brand Account” which somehow seems to under – or contained within – my normal personal account. I use the brand account for my photography business. My problem is that I can’t seem to figure out how to use your Picassaweb Publish Service plug-in to associate with this “brand account” . I already have your plug in set up to manage my personal account photos and want to keep that intact. How do I add a new Publish Service that points to the Brand Account?

Thanks — Dan

I’m afraid that I’ve never heard of a “Brand Account”, and can find no mention of it in PicasaWeb docs. They’ve let all this photo stuff wither on the vine, so it wouldn’t surprise me to find that it’s simply not possible. But who knows. )-: —Jeffrey

Hi Jeffrey
Lightroom cc latest version Picasa plugin latest version. macOS
Not used plugin for some time so needed to re register and allow plugin in google – getting the following error message

unrecoverable server error at Google it returned a normal web page instead the proper API reply

have logged out of Lightroom and restarted mac without any change

Please help

regards
Kelvin from North West UK

I’ve just updated with a workaround… it should be working again if you update to the latest version of the plugin. No guarantee that Google won’t break things again soon, though. )-: —Jeffrey

Jefferey-

Thanks for the replies to the comments above, I thought the problem was on my end for a day or so!

If I understand things correctly, you don’t have any ability to provide a workaround until Google supplies you with a Photos API? i.e. the picasaweb LR plugin is most likely permanently dead?

Cheers,

Jason

I’ve just updated with a workaround… it should be working again if you update to the latest version of the plugin. No guarantee that Google won’t break things again soon, though. )-: —Jeffrey

This maybe relevant from another plugin:
http://www.newpproducts.com/lightroom-plug-ins/support-faq/#27_Jan2017_8211Google_Photo_Picasa_Web_uploads_fail_82204008221_error
Thanks for the pointer. Rob Jones of New P Products got back to me with info on a workaround. My plugin now works again….. until Google next breaks it, at least.—Jeffrey

Hi Jeffrey!

Thank you – it work’s excellent again!

Best regards, Arnold

Hi Jeffrey,
Thanks a lot for the update, you save my day!

Hi Jeffrey,

Firstly, thanks for the awesome plugin – have been using for years and has been a key piece in completing my LR workflow.

Last night a new issue started popping up. After clicking publish with at least 1 new photo, a dialog box appears saying:
“Unexpected HTTP status from Google: 501
Update is no longer supported”

What’s strange is that if you have multiple images to publish, this message will appear, and after dismissing, it will seem like the publish action failed completely, with no images uploaded. However, in the album on Google Photos, the first image that was to be published will have been uploaded. If you then try and click Publish again, exactly the same happens, but a duplicate of that first image is added the collection (I had tried running publish a few times before checking the album, at which point there were 4 of the same image uploaded, but nothing else).

Let me know if you need any other recreation steps.

Thanks!

Michael

Lots of folks are getting this error (though I’m not yet). I think the writing is on the wall that they’re starting to wind down the service. —Jeffrey

Hi,

I am using your great plug on Light Room 5 for log time with no issues.

Effective last week I was unable to upload photos to Picasa.
I keep getting LR message – “Unexpected HTTP status from Google:501, insert no longer supported.
I updated to latest JF release – 20170130.288. Same, same.

When pressing PUBLISH – I get “Catalog Corruption Discovered” window with the message: Missing destination cookies.

I deleted all items from JF and selected just few catalog items for testing – Same same.

Also double check that Google does “know” JF and that it is enabled. No success.

Please support…

Thanks

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

I know about the trouble with Picasa, but the upload API is still working. Picasa photo upload and other tools can still upload. I think google will keep an upload on the long run. So why not fix the current issue?

I’m not sure what you mean by “current issue”… Google is shutting things down. Even uploads fail for some folks. —Jeffrey

Jeffrey I can no longer upload from Lightroom CC to my Picassa Albums. Can you suggest how to move my images somewhere else and maybe a place to move them. Many thanks as I have enjoyed this plugin so much and appreciate you maintaining it. I am from Choctaw Oklahoma USA and a freelance photographer.

Where to move them depends on what’s important to you. Lots of places are free or offer free trials, so give them a try, such as Flickr, Zenfolio, or SmugMug. Some places allow you to import from other places, or maybe just re-send from Lightroom. I don’t really have experience here, so can’t suggest much more. —Jeffrey

Hello.
I have been using Picasa Web for a LONG time, using your publish service mostly. I no longer use Picasa for uploading anything new, but I still have a large number of galleries still linked to my photos in Lightroom.
Now I am running into a big problem- As I go through my old collection of photos in attempt to delete anything I no longer need, I occasionally get this message when attempting to delete photos-
“The plugin’s authorization for your PicasaWeb account has expired… please visit the top of the Export Dialog to re-authorize the plugin for your PicasaWeb account.”
This leaves me unable to delete the photos. I have tried re-authorizing to no avail. I have tried removing photos from the publish collection galleries and that does not work either.

Do you know of any workaround that will allow me to delete photos?

Thanks in advance for any suggestions you may offer.

In the Publishing Manager for the Picasaweb plugin, there’s a section on delete options. Adjust that so that photos deleted from Lightroom are not deleted on Picasaweb, and hopefully it should work. You can also disable the plugin in the Plugin Manager. —Jeffrey

FWIW, I have now tried the Google Drive export plugin since there is now an option in the Google Photos Settings “Show Google Drive photos & videos in your Photos library”. It seems to work quite well so far. All Photos show up in the right place in Google Photos, only Videos have the wrong time stamp, but even updates to photos seem to work just as expected. Unfortunately the Keywords are ignored, but other than that I can see not too many downsides (except that it’ll probably count toward your storage limit)

Hi Jeffrey!

Google introudeced the Google Photos Library API: https://developers.googleblog.com/2018/05/introducing-google-photos-partner.html.
Are you planning to create an export6publish pugin to Google Photos?

Zoltán