Known Issues with my Plugins

Known Issues with Lightroom and/or my plugins...

PicasaWeb (Jan 30, 2017)

Uploads to PicasaWeb are working again in the latest version of the plugin. They had suddenly stopped working, and it seemed like it was because Google had abandoned PicasaWeb, and that may still be the case, but thanks to Rob Jones over at Lightroom plugin provider New P Products for cluing me in on an upload method that still actually works.

Also, please see This FAQ for issues commonly encountered with my plugins.


The 30 most-recent comments (out of 519; see all), most recent last...

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

— comment by SnapDragon on December 30th, 2016 at 1:52pm JST (7 months, 23 days ago) comment permalink

Zenfolio-20170117.294 LR CC 2015.8

Error during export
Unexpected reply from Zenfolio
3176699956238894711
Aborting export before any image was successfully uploaded.

Have been having issues with the plugin remembering my ZF password. Been having to enter it every time I use the plugin. not sure if related to message above or not.

Yikes, that error is because I screwed things up in that version… I’ve just pushed a fix. As for remembering the password, it sounds like your Lr preferences may be corrupt… please see this FAQ. —Jeffrey

— comment by Morey Behrens on January 17th, 2017 at 11:50am JST (7 months, 5 days ago) comment permalink

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

— comment by Gail on January 23rd, 2017 at 9:45pm JST (6 months, 30 days ago) comment permalink

Hi, I´m writing from Iceland – and I just love your plugins !
I see that you have posted today 28.01.17 a unknown error happens when publishing from lightroom to google+. Well the error I get is:
“Unrecoverable server error at Google (it returned a normal web page instead the proper API reply)”
Checked the FAQ – could not find solution…

Hope this helps – now just to wait for you to come up with the perfect solution to it 🙂
Keep up the good work you are doing.
regards,Gudbjorg

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

— comment by Gudbjorg on January 29th, 2017 at 2:47am JST (6 months, 25 days ago) comment permalink

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

— comment by Gudbjorg on February 1st, 2017 at 7:00pm JST (6 months, 21 days ago) comment permalink

Hi Jeffrey,
I’m writing from San Francisco. I’ve been having trouble uploading from lightroom to zenfolio. I updated your software but am still having problems. I keep getting error messages that say… ” Unexpected HTTP reply from http….. then SErver was unable to process request….. then Could not find the file…

Any idea what is going on?
Thanks, Hilary

They had some issues yesterday…. they’re telling me it’s all cleared now. —Jeffrey

— comment by Hood on February 8th, 2017 at 11:42am JST (6 months, 15 days ago) comment permalink

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

— comment by Marylene on February 8th, 2017 at 7:06pm JST (6 months, 14 days ago) comment permalink

Hi,

I have the same issue. Seems that Picasa will be unusable now.

What ideas regarding alternatives do exists?

Regards

Jan

Well, there are many image-sharing sites out there. Flickr is popular, as are paid ones (SmugMug and Zenfolio likely the most popular). —Jeffrey

— comment by Jan on February 12th, 2017 at 2:14am JST (6 months, 11 days ago) comment permalink

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.

— comment by RRiPPed on February 12th, 2017 at 2:35am JST (6 months, 11 days ago) comment permalink

I have just run into the exact same issues with the Picasaweb plugin as Marylene. I plan to try her workaround. I am hoping this is a temporary hiccup on the Google side. Your plugin has been wonderful for many years and I hope to be able to keep using it.

It’s not a hiccup… Google announced long ago that they are shutting it all down, and now they are. Best to transfer elsewhere while you still can. —Jeffrey

— comment by Meyer1128 on February 17th, 2017 at 12:50am JST (6 months, 6 days ago) comment permalink

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

— comment by Luis Muñoz García on February 17th, 2017 at 5:31am JST (6 months, 6 days ago) comment permalink

After Picassaweb is closed, is there a problem with the flickr plugin? I keep getting error messages Filetype not recognized, but the debug log
flickr#390 U[1488015887]+198.9:[F9135B8] @LrHttpDebug line 15: 117 bytes back from [https://up.flickr.com/services/replace/]
flickr#390 U[1488015887]+198.9:[F9135B8] @LrHttpDebug line 451: Not repeating becuase body (117 bytes) is not nil
Call time: 7.1988 seconds.
Return Body:
?xml version=”1.0″ encoding=”utf-8″ ?
rsp stat=”fail”>
err code=”5″ msg=”Filetype was not recognised” />
/rsp>
Any idea?

Flickr could be having issues, or there could be a problem with your network connection. “Filetype not recognized” is what they say if they get a corrupt file, such as one that got truncated in transit. —Jeffrey

— comment by Peter Marbaise on February 25th, 2017 at 7:03pm JST (5 months, 25 days ago) comment permalink

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

— comment by Mads Høgstedt Danquah on February 25th, 2017 at 10:31pm JST (5 months, 25 days ago) comment permalink

The images where uploaded via Google Photos webinterface, so the file should reach them pretty much untouched.

I just did some more debugging, and I think it’s all related to whether metadatawrangler is set up to strip keywords. I just sent a plugin log with all the details I could come up with including links to sample images.

Best regards
Mads

— comment by Mads Høgstedt Danquah on February 26th, 2017 at 7:52pm JST (5 months, 24 days ago) comment permalink

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

— comment by Mads Høgstedt Danquah on February 26th, 2017 at 9:03pm JST (5 months, 24 days ago) comment permalink

Hi Jeff,

Thanks for providing a great 3rd party plugin.

I have a question on the uploads to zenfolio (looks like you frequently get that kind of feedback).

It looks like uploading around 5gbs via their online web interface takes between 2-3 hours. Exporting via the plugin takes 15-16 hours.

Given that the web interface uploads faster, I concluded that it’s not my internet connection. If this is true, then could it be that the connection the plugin uses could be throttled? If so, is it impossible to fix?

Previous comments eluded to the fact that zenfolio could be prioritizing their traffic, but given that they explicitly reference your plugin, I would imagine it would make sense to give the same priority to your plugin as their own traffic. I mean, essentially they are advocating to use this plugin.

Thanks for your time!
Nelson

Unfortunately, from a plugin’s perspective, it’s all a black box. The plugin tells Lightroom “send this data”, and the plugin waits for Lightroom to say it’s done. Lightroom in turn asks the OS just as, I assume, your web browser asks the OS, so I don’t know where the slowdown might be coming from, but I don’t think there’s anything the plugin can do about it. It’s frustrating, I’m sure. )-: —Jeffrey

— comment by Nelson on March 1st, 2017 at 9:30am JST (5 months, 22 days ago) comment permalink

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

— comment by Bob Crnkovich on March 2nd, 2017 at 10:43am JST (5 months, 21 days ago) comment permalink

HI, I’m having issues with the plug-in for lightroom to zenfolio.
I keep getting a error message saying…The “nil” plug-in is not installed or not working properly.
I have to delete the plug-in from the LR plug-in manager, then re-install it for it to work. Once I close out of LR I get this issue all over again.

It sounds like your Lightroom preferences file has started to go corrupt. Easy enough to fix as per that link, but still a hassle. —Jeffrey

— comment by Don on March 10th, 2017 at 8:12pm JST (5 months, 12 days ago) comment permalink

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

— comment by John Cothorn on March 12th, 2017 at 6:25am JST (5 months, 11 days ago) comment permalink

Howdy!

Longtime fan of “Export to Flickr” Lightroom Plugin.

Sometime during the past few weeks, I make edits to images in Lightroom. I close Lightroom and edits are saved upon opening Lightroom next session.

I upload images to Flickr via plugin and edits are not present.

I’m expecting the plugin to blame Lightroom, and Lightroom to blame the plugin.

Is there *any* way to troubleshoot this issue that you know of either per the plugin settings or within Lightroom? I can’t find any setting and didn’t change anything before the ‘bug’ began.

Thanks in advance for your assistance.

I’m guessing that in the Publish Service settings, you’ve got the “Format” set to “Original”, which for some inexplicable reason Lightroom has mean “original unedited pixels, with new modified metadata”. Set it to “JPEG” and everything should work fine. —Jeffrey

— comment by Nick Normal on March 17th, 2017 at 12:58am JST (5 months, 6 days ago) comment permalink

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

— comment by John Samuel on March 24th, 2017 at 8:04am JST (4 months, 30 days ago) comment permalink

Ft. Lauderdale, Florida but at the moment in Savannah GA. I’ve used the plugin for years, thanks for that! Lately, I have had my export to Zenfolio simply stop, then a window pops up with the following –

Target url:http://api.zenfolio.com/api/1.8/zfapi.asmx
Unix timestamp of call start: 1492658920.2076
Unix timestamp of call end: 1492658920.656
HTTP Reply Date Field: Thu, 20 Apr 2017 03:28:39 GMT
HTTP Origin Field: WS002

When I click ok, the next window just pops up Cancelled, and the upload stops. Last night I set an alarm for every two hours to check on an export, and each time I checked it had stopped. After four restarts, I finally got everything up. Any ideas?

Without the full info it’s hard to guess, but the data you showed is shown for errors that the plugin thinks are Zenfolio’s fault (e.g. their servers might be having “issues” at the time). I suggest you forward it to Zenfolio, along with the full error message that went along with it. —Jeffrey

— comment by Jonathan Givens on April 20th, 2017 at 8:05pm JST (4 months, 2 days ago) comment permalink

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

— comment by Bernie de Hoedt on May 1st, 2017 at 5:51pm JST (3 months, 21 days ago) comment permalink

Hi Jeffrey, I am successfully using one of your other plugins with my (properly registered) installation of Lightroom CC, but the Metadata Wrangler plugin generates, immediately upon installation, the following error message in Plug-in Manager: “An error occurred while attempting to load this plug-in. The plug-in description script (Info.lua) is missing.” I haven’t done anything to the plugin file, nor modified Lightroom in any way. I have tried installing the plug-in in two separate folders, one of which is my Mac Desktop folder, and all other plug-ins (including your Custom Metadata plug-in) work fine. This is occurring with a download from your website as of today. Is there anything you can advise as to how I might troubleshoot this? Thanks!

I can only guess a corrupt install of some kind. Are you sure you’ve pointed the Plugin Manager at the right spot? It might be prudent to delete all copies of the plugin from your system (to make sure there’s no confusion about what copy is what), download the latest and unzip it (and perhaps peek in to confirm that there is indeed an “Info.lua” file, among many others), then re-point the plugin manager at it…. —Jeffrey

— comment by Brandon on June 28th, 2017 at 9:50am JST (1 month, 25 days ago) comment permalink

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

— comment by Morey Behrens on June 30th, 2017 at 12:58am JST (1 month, 23 days ago) comment permalink

A couple weeks ago I fixed a minor tag problem (changing “flowers” to “flower”) and 138 photos needed to be republished on Flickr. Unfortunately, since then, I get this error message:

Flickr is currently down (error returned by Flickr: Photo is temporarily unmodifiable)

The photos are all on an external drive; if I unplug it I can add upload new photos to Flickr just fine because the plugin lets me ignore the missing photos.

I’m not sure what’s causing this problem, but it appears not to be temporary. I saw in an earlier comment that perhaps some photo is locked or something at Flickr. Is there a way to isolate a problem photo? It’s not the end of the world if Flickr doesn’t get the updated keyword. It’s mostly in my own LR catalog that I care.

I’m using MacOS 10.12.6 beta on a 2016 MacBook Pro with LR CC 2015.10.1.

That’s really weird… I’ve seen the “unmodifiable” thing only a few times, and it had never persisted. I’d imagine it’s the first photo left showing in the Publish Collection (in the “new photos…” or “modified photos…” section) at the time the error pops up. —Jeffrey

— comment by Stephen Shankland on July 10th, 2017 at 12:53am JST (1 month, 13 days ago) comment permalink

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

— comment by Dennis Brown on July 10th, 2017 at 7:13am JST (1 month, 13 days ago) comment permalink

OK, so, recently I asked you about a permissions issue where I thought your plugin was ignoring the permissions settings I was asking of it. It turns out the issue is actually in Flickr Organizr, and I wanted to you know for others’ sake.

When I have loaded up a set of images to Flickr, go visit the Flickr Album on the website, and then “Edit in Organizr”, I can then make sure that the permissions are set properly by selecting “Batch Edit”, and then “Change Permissions”. When that dialog box opens, the permission “Anyone (Public)” is selected. What I have realized now is that that’s just the initial setting of that dialog, _irregardless of the permissions currently in the album_. You are setting permissions just fine – they’re set private and are not showing up in my public stream. It’s just that the Batch Permissions Edit dialog box’s initial setting doesn’t reflect the current permissions of the photos in the album.

Thanks again for the lovely plugin!

— comment by Carmine DiChiara on July 16th, 2017 at 12:19pm JST (1 month, 6 days ago) comment permalink

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

— comment by howard on July 16th, 2017 at 12:35pm JST (1 month, 6 days ago) comment permalink

Hello from Seattle, Washington, USA

I am running Mac OS 10.12.5 and just updated Lightroom to 2015.12 and then your Facebook plugin to 20170710.404

As has been the case for the last several plugin updates, upon the successful completion of the update all attempts to do anything in Lightroom or to access any other application simply yields the “bloop” error sound with each click. Again, I had to Force Quit Lightroom and restart Lightroom. While the Force Quit/Restart routine has so far not done any obvious damage, I now back up Lightroom before each update of your Facebook plugin.

It sounds like Lightroom’s got some kind of dialog open, but not visible. Try looking around for it… it might be
behind the main window, or maybe on a monitor that’s not turned on? This is a basic problem I’ve seen with Lightroom from time to time,
whereby a dialog is blocking all input but it’s not visible. —Jeffrey

— comment by Eric Johnson on July 21st, 2017 at 3:53am JST (1 month, 2 days ago) comment permalink
Leave a comment...


All comments are invisible to others until Jeffrey approves them.

Please mention what part of the world you're writing from, if you don't mind. It's always interesting to see where people are visiting from.


You can use basic HTML; be sure to close tags properly.

Subscribe without commenting