One question though as it relates to Picassa. I have a “smart” publishing setup to go to one particular album, which works perfectly, but a copy of the image is also put in the “Photos From Posts” album. I’d prefer for this to not happen. What did I miss in the plugin setup that’s causing this?
This is the first I’ve heard of this, and is not something the plugin is doing. Wouldn’t surprise me if Google add stuff like this from time to time. Perhaps find that album and make it private? —Jeffrey

You’re not misunderstanding, except that you can just go ahead and use a PicasaWeb publish collection as a regular collection as well, then your problem is solved, at least for ones you create from here on out. What you’d like to do (ascribe Publish attributes to a pre-existing collection) isn’t a crazy idea, but is not something Lightroom supports. —Jeffrey

It’s hit-n-miss, mostly due to limitations with the metadata matching between Lightroom and PicasaWeb, or missing metadata at the latter. It’s an unsatisfying situation to be sure. —Jeffrey

On a similar note, a feature request: any way to add multiple line breaks? More specifically, adding two line breaks would be a useful way to separate part of the caption into its own paragraph (for those of us who write long captions). I currently work around this by using the lua token to manually print two “” tags.

Ah, it seems that PicasaWeb now allow line breaks in captions, so I’ve pushed a new version that allows it. Just include line breaks in the original source data and they’ll be transmitted to PicasaWeb as is. —Jeffrey

No, not at all. If you don’t want the “ongoing relationship” that is Publish, you can always do a normal one-off export, but if you want to publish, you generally need a separate publishing service only when you want a different export setting (size, quality, watermark, etc.). If that’s the same for every image in every album, one service will do you. —Jeffrey

I am currently testing the Picasa tool and have a problem on the export. In the publication service I have set my Mogrify signature and this is not added on the picture when published to Picasa. Anything else I have to do?

Thanks

Valerie

You should probably contact the Mogrify author, since Lightroom doesn’t give the photo to the Picasa plugin until the final image has already been made. —Jeffrey

One safety issue that really worries me is updating. When an image is updated in Picasa, the external link changes (this happens even with the Picasa application). That means if I’ve given out the URL to third-party sites, those links will break after the update.

Is there a good way to avoid the problem? I’d be happy with something that bypasses or prevents the update. Can I permanently disassociate some photos? I can Clear the “uploaded to Picasaweb” flag, but then an “Associate Images” step would probably link them back up.

I know this is really a lame issue in Picasaweb, but I’m hoping you might know of a workaround.

Thanks,
Jason

It sounds as if you really shouldn’t be using Publish… the whole idea behind Publish is the ongoing relationship between Lightroom and Picasa, but if you explicitly don’t want that, you’re probably better off using normal Export, ensuring in your case that that “Replace” option is never selected. —Jeffrey

Visit the Export Dialog and log out in its top section, then re-authenticate. —Jeffrey

Check out the collection’s “Edit Settings” in the context menu, and view all the sections of the resulting dialog. You’ll find what you’re looking for, and a lot more that is good to be familiar with. As for the instructions, they’re here. —Jeffrey