Uploading to Facebook “page” from Lightroom CC, anytime I have an update to metadata, plugin works properly and recognizes a “republish”, when I update the image, it only creates a duplicate, or more depending on how many times I update, then I manually go to Facebook page and delete older photos. Where or what setting to I need to correct to prevent duplicate files / photos?

Thanks –

Snap Dragon – Singapore

Any republish to Facebook creates a new image at Facebook. They simply don’t allow images to be updated in place. That’s why I caution against using Publish with Facebook. —Jeffrey

Very recently, I started hitting the Twitter limit for photos nearly every single upload to Flickr. I checked the Twitter limits for photo sizes, and the official word is 5MB:

https://support.twitter.com/articles/20156423

Is it a different limit for API? Because the error message I keep getting is that the limit is just over 3MBs to post the photo to Twitter.

Twitter built a way for their servers to tell third-party apps what the limits are, and my plugin checks each day you use it. They are currently explicitly telling the plugin that the limit is 3,145,728 bytes. I’ve reached out to ask whether their servers or docs (or both) are wrong. —Jeffrey

Perfect!
Worked like a charm –
again keep up the good work you are doing – made a little donation …
Hava a wonderful day!
regards, Gudborg

Hi,

About PicasaWeb plugin.
I ve the last update 20170130, but it seems that :
1/ Creating a new album from plugin is not anymore possible. Message : “Creating a new album at PicasaWeb aborted: Unexpected HTTP status from Google:501. Insert is no longer supported.” ==> Workaround : So we have to create albums directly in Google Photo then Refresh list in the plugin to see the new album in lightroom.
2 / Publishing photo from plugin is not possible anymore. Message : “Unexpected HTTP status from Google:501. Update is no longer supported.”

Do you encounter these issues also ?

Regards,
Marylene

I’m not getting this error at the moment, but I’m getting many reports of it. I think it’s the writing on the wall that they’re rolling up the sidewalk. —Jeffrey

Ok so I’ve encountered this too. It happened from 2/8/2017 because my last album created by that time.

It seems Google have changed their API (or worst they’ve removed it). If you know any new information please share.

Dear Jeffrey,

I have just update the jf PicasaWeb Plugin to v. 20170130.288

I can create Collection Sets but I can not create Albums because it appears this message:

“Unexpected HTTP status from Google: 501
Insert is no longer supported”

Is there something you can do about it please ??

Thanks in advance

Best regards

No, Google is shutting it all down. —Jeffrey

When I upload images that has been through the metadata-wrangler to Google Photos, the date of the image shows up as “00:00”, I’ve reproduced the issue by doing two exports, one with and one without the metadata wrangler enabled (I configured the wrangler to leave everything in place.).

The weird thing is that if I compare the two images, all time/date related fields are 100% identical, and all in all they only differ on very few seeming irrelevant fields. I suspect the error is on Googles part, but it would be great to hear if anyone else has seen the issue and have any idea how I can get around it (without giving up the metadata wrangler that is).

I’ll be happy to provide a copy of the two images.

How are you uploading data to Google Photos? Could that software be looking at the filesystem date (which is somehow getting goofed up)? Have you tried other methods to upload to Google? Perhaps send a plugin log and/or copies of the files… —Jeffrey

And just to wrap it up, stripping the EnvelopeRecordVersion tag via

exiftool -iptc:EnvelopeRecordVersion=

Seems to fix the issue – no idéa if removing EnvelopeRecordVersion then breaks something else though 🙂

BR
Mads

Just another follow up on a couple other questions I had on uploading to Google Photos (Picassa Web Albums). Are you saying that once Google phases out Picassa that your Plugin will no longer work for Google Photos? Because now, it seems like whatever shows in Picassa also shows in Google Photos.

You suggest using a different photos depository/service like Smugmug, etc. but I would still prefer to use Google Photos since I have thousands of photos there in albums already. Is there a different plugin or procedure you could suggest to still use this service in the future when Picassa is deactivated? I can’t believe that Google Photos is also going to disappear, and it still has relatively good functionality and features which I can only assume will get better over time considering the number of users it has.

Thanks.

I’m not particularly familiar with Google Photos, seeing how serious photographers are clearly not in their target demographic, so I’m not the best person to ask about this, but I’ve heard of some folks using Google Drive to get photos to Google Photos. Like I said, I haven’t paid much attention to it, so I’m not sure. FWIW, I do have a Google Drive plugin. —Jeffrey

Regarding Metadata Wrangler and keywords:

I have read where you have determined how to handle the lightroom heirarchy. I noticed where you asked for some ideas. The plugin in works great for stripping keywords and prefixes, which would be EXTREMELY useful for some upload sites (agencies, etc.). I have noticed however:

At least with Flickr, you must have “Explicit export Lr keywords” unchecked in order for Metadata Wrangler plugin to have an effect. I’m guessing this has to do with the order in which they are processed but I’m not sure. That works okay of course (to leave it unchecked) but it does present potential issues with future keyword changes.

More importantly, the heirarchy:

The behavior is such that even if you strip a specific keyword, and that keyword has synonyms, or children below it, it does not affect the export of those words. That becomes the stumbling block in using the plugin for that purpose since more often than not you need to be able to strip those items as well.

Based upon some reading I’ve done on your blog, it at least appears that you have access to the parent, children, an synonyms of a keyword. The coding my be a bit of a pain, but as far as I can tell that would enable this to be a complete solution to problems I read photographers (myself included) frequently have with the way Lightroom exports keywords. Even the alphabetical order is a hindrance but I’m not sure there is much you can do with that part.

Would it be worth having a stand-alone plugin to deal with keywords? I think you would find it extremely popular and I for one would be more than happy to compensate for it.

Thanks

About the “Explicitly send Lr keywords” thing, the Flickr plugin doesn’t know that you’ve included the Metadata Wrangler plugin as part of the export, and has no idea that the latter is doing anything to keywords. For the most part, one sends the image file with whatever keywords you want (as perhaps modified by Metadata Wrangler) and Flickr extracts them from the image, but if you want to strip the image metadata, but still want Flickr to know about the keywords, you’d use the “Explicitly send…” option. As for better keyword control, I don’t doubt that there’s room for a plugin to give much more control, but unfortunately at this point my todo list is too long to write such a plugin myself. —Jeffrey

Regarding:

“Intermittent error encountered in Flickr’s back-end servers (Filetype was not recognised). Unfortunately, there’s nothing you can do but try again later and hope for better luck.”

I tried Library | Plug-in Extras | Flickr Extras | Refresh All Remote Urls

And the recalcitrant images all started behaving nicely again. So I think there is something you can do after all. 🙂

John Samuel, from just outside Kew Royal Botanic Gardens

I think the timing is just coincidence. The URLs being refreshed are not part of what’s sent to Flickr during an upload. It’s like you tried to call a friend but got a “lines down” signal, then contacted the operator to check whether you had the correct number in the first place, then retrying the friend and getting through: asking the operator about the number didn’t fix whatever problem the line had been having when you tried the first time. —Jeffrey

Hi Jeffry, I am using your Zenfolio plugin to export my images from LR5 to my webpages. When exporting, only the Title and Headline gets exported to display on the webpage – the file name doesn’t. I am unable to edit the template as Create New and Update options are greyed out. My workflow is that I use Photomechanic 5 to set the metadata through the IPTC Stationary Pad, Import selected file to Light room, Edit (not the metadata) and then export to my Zenfolio web page . Only the Title and Headline are shown.

Please can you advise how I can edit the template to get the information I need.

I am also looking to expert these to two places at once, my Zenfolio Webpage and a Hard Drive for Archiving.

Other than this is appears to work great.

It’s hard to guess why the options are grayed out without more info… perhaps send a plugin log after experiencing the issue, or maybe send some screenshots? About the “two places at once”, that’s easier: in Publish, see the third section of the settings dialog (“Export Override Location”). In Export, see “Export Location”. —Jeffrey

zenfolio-20170621.299
Unable to Export error
Error calculating automatic destination for “filename.dng” unbalanced ‘{‘ in “[Path:After=ImageLibrary\}”
Image Library\ is a folder name in the path to the filemane.dng. In fact the full path is “G:\ImageLibrary\Shared\2017\05-22_OR_Coast”
I’ll rollback to the prior release and see if this continues.

Oops, a case of unintended consequences for a different change. I’ve just pushed a fix. Sorry for the hassles. —Jeffrey

I just registered metadata wrangler and hoped it would solve a problem that I am having with scanned .tiff files edited in lightroom cc develop module then added GPS data from the map module all metadata saved to original files, then exported as .jpg files. All the metadata seems to get picked up during the export except the GPS data. I have checked all the settings in the export dialogue and in metadata wrangler and still the GPS data does not copy. I have scanned several thousand 35mm slides and negatives and only some groups of files display this behavior.
Please any suggestions what I should try.

Thanks for the great plugin, it did not fix my particular problem but it sure covers the ground.

The plugin wouldn’t add data that’s not already there (except for what you might manually add toward the bottom of the dialog), so it’d be good to figure out what Lightroom is doing. Try vanilla “Hard Drive” exports and check whether the location data is in the resulting JPGs on your system (perhaps via my metadata viewer). Lightroom has an option in one of the export-dialog sections to strip location info (including “City”, etc.), so look into that. —Jeffrey

Thanks for the plugin! I do know that google had changed things a few months ago and the plugin basically no longer works for exporting directly to google photos. so my question , then how come update it ? anyway, i do thank you again and do hope one day the plugin would work again…

More of a habit, since parts of it still seem to work for some. I’m not working on it directly, but if I update some of the libraries that make it up, I just go ahead and push out the update with those changes. —Jeffrey