Known Issues with my Plugins

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

Flickr (Sep 2018)

If you're having trouble with the Flickr plugin, please upgrade to the latest version.

SmugMug (Jun 2018)

The SmugMug plugin is working again, but some fringe features have been lost. I'll work on adding them once the dust settles on the new version.

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


All 566 comments so far, oldest first...

OK, downloaded and installed the new release (today) of your Facebook plugin…

but still can’t retrieve my list of Facebook photo albums. But I went on, and in end got this error:

+45.9: At line 13463:Assertion failed(!)

Hit OK button to get me over “+100: At line 13463:Assertion failed(!)” and gave up… Had to Force Quit Lightroom.

I think I fixed this as of the 20080814 versions of the plugins. —Jeffrey

— comment by Keith Rowley on August 12th, 2008 at 11:59am JST (10 years, 3 months ago) comment permalink

I get the same error when I try oy export to flickr.

+45.9: At line 13463:Assertion failed(!)
Hit OK button to get me over “+100: At line 13463:Assertion failed(!)” and gave up… Had to Force Quit Lightroom.

I think I fixed this as of the 20080814 versions of the plugins. —Jeffrey

— comment by Ed on August 13th, 2008 at 12:03pm JST (10 years, 3 months ago) comment permalink

I get the same error. Uninstalled and reinstalled both Lightroom 2 and the plug-IN

the numbers increase each time I hit OK, I must use task manager to force lightroom to close.

I’m using Vista, so I wonder if this is a security issue.

I think I fixed this as of the 20080814 versions of the plugins. —Jeffrey

— comment by E Walker on August 14th, 2008 at 8:36am JST (10 years, 3 months ago) comment permalink

Hi jeff,
I wrote a comment before.
I’m still having the same problems with the plug. It’s the same as Ed, E. Walker and Keith Rowley.
+1449.3:At line 14006: Assertion Failed(!)
I press (OK) and the first number changes as many times as I press it, had to force quit Lightroom.
I just don’t see the time when I can use the plugin, it will be so useful.
Thank you very much for you job!

I think I fixed this as of the 20080814 versions of the plugins. —Jeffrey

— comment by Juanri on August 15th, 2008 at 9:23am JST (10 years, 3 months ago) comment permalink

I have had good success in uploading from LR to Smugmug. Now, I get the following after upload of one image.

smugmug.images.upload

Using Mac OSX 10.5.4 with LR2. I think I encountered this problem before upgrading to LR2 but I am not certain about that.

Thanks for any suggestions.

— comment by StafroPhoto on August 17th, 2008 at 2:41pm JST (10 years, 3 months ago) comment permalink

sorry – my previous comment was altered on posting.

smugmug.images.upload should read:

smugmug.images.upload

— comment by StafroPhoto on August 17th, 2008 at 2:48pm JST (10 years, 3 months ago) comment permalink

I apologize – the text of the message seems to convert to smugmug.images.upload. The message also states: “Smugmug encountered an unexpected an error”.

Sorry for the multiple messages but I cannot find an edit method.

— comment by StafroPhoto on August 17th, 2008 at 2:55pm JST (10 years, 3 months ago) comment permalink

Can’t export. First message: +17.6: At line 14225:Assertion failed(!).
Then I hit OK button. Second message: Unable to Export: An internal error has occured: ?:12809: assertion failed!
Those first numbers (17.6) changes every time.
LR 2 on mac leopard. Latest version on plugin.
Thanks for working on this!

— comment by Anders on August 18th, 2008 at 6:23am JST (10 years, 3 months ago) comment permalink

Hi Jeff, I’m still having the same problem:
+1449.3:At line 14006: Assertion Failed(!)
The infinite message is fixed and no Lightroom2 force quit, but can’t export images.
Thanks

— comment by Juanri on August 18th, 2008 at 8:15am JST (10 years, 3 months ago) comment permalink

Hi Jeffrey,

I’ve read your comments on this page, and understand how busy you are. I love your Flickr plugin, and am hoping you can help. I am experiencing the same “assertion failed” error that others have reported. I am using plugin version 20080817.11, OSX version 10.5.4, and LR 2.0. The specific numbers in the error message vary between attempts, but a representative error message looks like this: “+8.2: At line 14255:Assertion failed(!)” I can send you the log file if that would be helpful.

I have tried tossing and reinstalling the plugin. I have tried placing the plugin at different locations (currently at username/Library/Application Support/Adobe/Lightroom/Modules). I have tried reloading the plugin using the “reload” button in the plugin manager. I have tried tossing the LR2 prefs. I’ve tried using a different default browser, in case that makes a difference (Safari 3.1.2 and Firefox 3.0). I’ve tried different Flickr accounts. None of this has made a difference, and the failure is 100% consistent.

I would love to get your excellent Flickr export plugin working again! Please let me know if you need any additional information from me, or if there is anything I can do to help.

Thanks,
Ben

— comment by Bengeance on August 22nd, 2008 at 9:40am JST (10 years, 3 months ago) comment permalink

I have downloade the latest plugin for Picasa, execured the instructions for the keyword export problem. But I keep getting the following error:

“an internal error has occurred: ?: 17358 attyempt to call field “?” a nil value”

I could not finsd the cause of this on the web, but since i wanted to reload an entire album, it may be related to keywords. I did not change any keywordes in this album. so i just wanted to reload the inter album (now with all metadata).

Hope you (or someone else) can help me out!

Thanks beforehand,
Andre

— comment by Andre Bal on August 23rd, 2008 at 5:51pm JST (10 years, 3 months ago) comment permalink

I seem to be experiencing issues with the Flickr uploader on 2.0 (final).

In the midst of uploading a set of photos, I get the error:

Warning
Unable to Export:
An internal error has occurred: ?:17882: attempt to concatenate field ‘?’ (a nil value)

— comment by Taylor Meek on August 24th, 2008 at 6:19pm JST (10 years, 3 months ago) comment permalink

Hi, I used your plug in in version 1.4.1 of LR, now in version 2, I re-install the plugging by double clicking (I am on a mac OS X 10.5.4) and since then I can’t export at all it says “error number 3: bulean expected, got number”, I re isntalled, and used the pluggin as per your instructions and doesnt work either, I have reinstalled LR2 a couple of times repairing permissions and so on and the same problem happens.

— comment by Jorge on August 25th, 2008 at 5:17am JST (10 years, 3 months ago) comment permalink

Thanks for taking the time to create these fantastic plugins and sharing them.

I’d like to suggest some further ideas for the flickr plugin:

1. If the develop settings for a photo haven’t changed, but the metadata have (title, caption, keywords/tags, or security setting selected in the export dialog), and if the replace checkbox is selected, then sync the metadata up to the server, without uploading the photo again.

2. Create a new metadata field associated with the plugin in LR that records the security status of the photo on flickr.

3. For the photos selected in LR and sent to the flickr export plugin, add the ability to — instead of uploading/updating the photos — scan those photos on flickr and (a) verify they’re still there (haven’t been deleted on the website) and update the records kept in LR accordingly, (b) sync any comments from flickr down to a new metadata field in LR, (c) sync any changes to the security status made on flickr back down to the LR metadata.

— comment by David on August 26th, 2008 at 9:03am JST (10 years, 3 months ago) comment permalink

I installed your LR2 (Mac OS X) plugin for Flickr and uploaded the first 16 of 70 photos perfectly. Then I received the following message:

“Error response from Flickr: 6”
“Aborting export after 16 of 79 images successfully uploaded”

When I try to export the remaining images I get the same message. I think I’m going to love the plugin if I can get this error cleared up. Thanks for any help you can provide! Regards,

Ken.

— comment by Ken Malvey on August 26th, 2008 at 11:36am JST (10 years, 3 months ago) comment permalink

20080817.11 still has the assertion failed error in every case. It no longer locks up lightroom though, click OK and it exits the export.

— comment by E Walker on August 26th, 2008 at 12:12pm JST (10 years, 3 months ago) comment permalink

Jeff – I found out the error message I asked you about in my previous post (“Error response from Flickr: 6”) is due to being over my monthly memory usage allowance on Flickr. I upgraded the account and am now uploading with 100% success! Thank you so much for writing this application – I love it! Regards,

Ken.

— comment by Ken Malvey on August 27th, 2008 at 8:50am JST (10 years, 3 months ago) comment permalink

Hi, I still get error ‘+130.7: at line 14317: Assertion failed’ in the latest release (
20080827.12).

I hope this will get fixed soon, as this is a most convenient plugin!

Jesse

— comment by Jesse van Oort on August 29th, 2008 at 1:31am JST (10 years, 3 months ago) comment permalink

Hi Jeff,
As I told you, the plugin is really working, but it doesn’t export my keywords. I’d read the known issues and followed carefully the instructions with the Adobe fix script (AdjustKeywordOptions.lua).
Before you corrected the assert problem I was exporting my files on disk and uploading directly from flickr and the keywords worked really well.
Thank you for your help.
By the way, I hope you had a great summer trip.

— comment by Juanri on August 30th, 2008 at 11:35am JST (10 years, 3 months ago) comment permalink

I’d love to see the next flickr/picasaweb versions, if possible, to include the scene and location metadata as keywords if at all possible – would take a huge amount of time out of my tagging and help remove my location/scene keyword mess which I now use in the iptc panel part 🙂

— comment by David on September 5th, 2008 at 7:05pm JST (10 years, 2 months ago) comment permalink

Hi Jeffrey,
Great fan of your plugin.
I recently upgraded to LR2.0. While exporting using Picasa plugin, I get the following error:
‘Whoa, “D:\…\Temp\E47C4…ED3\IMG_9767.jpg” does not exist immediately after waitForRender. Please let Jeffrey know.’

This is the first time I’m running this. Is this a known bug?

MK

I’ve gotten a few reports of it, but I can’t see how it can happen. I suspect it’s either some kind of rare bug in Lightroom, or some strangeness with the OS that Lightroom has not been prepared for (which is itself a bug). Is D: a local disk? —Jeffrey

— comment by MK on September 9th, 2008 at 1:12pm JST (10 years, 2 months ago) comment permalink

Firstly this is an amazing product that is much appreciated!

The only problem I’m having is with the ‘Location’ field, which doesn’t get exported as a Flickr tag. Country, State and City all work without problems, it’s just the Location field that doesn’t work for me. I’ve checked out the Adobe information on keywording issues with Lightroom via the link you provide, but it doesn’t seem to relate to this particular issue with the Location field.

I am using Lightroom v2.0 and version 20080905.21 of your Flickr plugin.

— comment by Chris Osborne on September 10th, 2008 at 2:36am JST (10 years, 2 months ago) comment permalink

Hi Jeffrey,

First, to echo the others, thank you so much for your work on these amazing plugins…they cut down on valuable workflow time.

I’m currently running into the following error messages when combining your Flickr export with the LR/Mogrify plugin. Both are the most recent versions.

First:

Then:

Any suggestions would be greatly appreciated!!! Thanks again!

— comment by Peter Martin on September 12th, 2008 at 3:49am JST (10 years, 2 months ago) comment permalink

Oops, let me try that again.

First:

Whoa, “/var/folders/46/46AMTf2wFge1I8WC4U2PrU+++TI/-Tmp-/66241122-D86C-4420-9E6F-2D8F265F0FC0/_MG_9200.jpg” does not exist immediately after waitForRender. Please let Jeffrey know.

Then:

Couldn’t open _MG_9200.jpg: /var/folders/46/46AMTf2wFge1I8WC4U2PrU+++TI/-Tmp-/66241122-D86C-4420-9E6F-2D8F265F0FC0/_MG_9200.jpg: No such file or directory

— comment by Peter Martin on September 12th, 2008 at 3:51am JST (10 years, 2 months ago) comment permalink

Hi Jeffrey and thanks again for your plugin,

You have in your todo : More control via tagging, e.g. to be able to indicate “Photos with tag xxxx should be marked public on upload, while those with yyyy should be marked private.”
I would be very happy if you implement such a feature for flickr “Sets” and “Collections”.

Best regards

— comment by Alex on September 12th, 2008 at 5:10am JST (10 years, 2 months ago) comment permalink

Hi again Jeffrey,

Just wanted to follow up…my issues with using your Flickr export and the LR/Mogrify plugin are happening on a Mac. OSX 10.54 on a 2.16GHz Intel Core 2 Duo iMac. Hope that helps.

Peter

— comment by Peter Martin on September 18th, 2008 at 5:37am JST (10 years, 2 months ago) comment permalink

OK I’ve downloaded the zip file (flickr-20080918.28.zip) but it doesn’t seem to contain a plugin!

I’m sure this is me and it’s something really obvious but I’m not seeing what it is.

The zip file contains a single folder, flickr-jfriedl.lrplugin, that is, itself, the plugin. Don’t navigate into it. —Jeffrey

— comment by John on September 19th, 2008 at 12:55am JST (10 years, 2 months ago) comment permalink

Jeffrey –

Re: Feature Request

Great work, and thanks for your tremendous effort.

I believe there would be great interest in a Shutterfly plugin for LR 2.0. Shutterfly offers popular photo books and calendars, as well as great quality printing. Some Scott Kelby literature explicitly recommends Shutterfly for its print quality. I think there would be a lot of photographers (including me) interested in a Shutterfly plugin.

Thanks again.

— comment by Dan on September 19th, 2008 at 1:01am JST (10 years, 2 months ago) comment permalink

new one click doesn’t seem to work on LR2-Vista. I click on “upgrade now” it reloads 20080831.16 (my existing version) even though it says that there is 20080920.25 available. Tested with Both Picasa and smugmug plugins.

Could you try testing with a version that actually contains the fixed code? (You have to upgrade manually, of course, to get it.) —Jeffrey

— comment by dj montoya on September 20th, 2008 at 5:52pm JST (10 years, 2 months ago) comment permalink

Tried downloading your Flickr plugin for Lightroom 2 and I can’t get LR PluginManager to recogize it. In Plugin Manager, when I click on “browse” then click on the “flickr-jfriedl.lrplugin” folder…

I’ll interrupt here to say that at this point, don’t click Open, click Add Plug-in. That folder, itself, is the plugin. —Jeffrey

….and click on OPEN, it shows me the WIN folder, if tell it to OPEN the WIN folder it appears to be empty, and the “no items match your serch” message. What am I doing wrong? I extracted the files. I know this is an operator malfunction, but it appears that Plugin Manager is looking for a lrplugin FILE, and not accepting the lrplugin FOLDER. Thanks.

— comment by Dave Youkers on September 23rd, 2008 at 3:02pm JST (10 years, 2 months ago) comment permalink

Adding Plug-In to Lightroom.

I knew it was an operator error and it shows that old habits and assumptions are hard to break. The “usual” process in working with Explorer in Windows is to “Open” the target file or folder. I didn’t even see the “add plugin” box at the bottom of the window.

Thanks for your help.

Believe me, you’re not the only one. Adobe has actually addressed this issue a bit in the 2.1 release candidate, but I still think they haven’t gone far enough. I guess it’s a work in progress )-: —Jeffrey

— comment by Dave Youkers on September 23rd, 2008 at 9:40pm JST (10 years, 2 months ago) comment permalink

Hi Jeffrey,

Waou very good Flickr export !!
I love it… But, it missing some options to be perfect (for my usage 🙂

1. Tokens replace. For example, I want to convert a lens info to an other : 24-70 mm f/2.8 -> AF-S Nikkor 24-70 mm f/2.8G ED, or ¹⁄₃₂₀ sec -> 1/320 sec.
2. Set privacy of my photo in Flickr base on color label, is more graphic in the grip view in Lightroom than tags.

3. Set resolution of the export base on privacy. Example, public photo to 1600×1600 pixels, other full resolution.

4. It will be nice is I can reexport only the tags, not the picture in Flickr (I don’t now if is possible with the Flickr API)

Et voila 🙂

— comment by Lucas Janin on September 25th, 2008 at 3:11pm JST (10 years, 2 months ago) comment permalink

Oups… one more..

5. Assigne group to a photo in Flickr based on tags will be fantastic !!!

— comment by Lucas Janin on September 25th, 2008 at 3:18pm JST (10 years, 2 months ago) comment permalink

About the report I just made, here’s another example that just occured

Picture at http://flickr.com/photos/_mll_/2903077576/
Keywords in lightroom: anophèle, light, lumière, mosquito, moustique, mur, n&b, wall
Tags in Flickr: anophèle, mosquito, n&b, lightroom (the latter being auto-added per my settings by your plugin)

So, 5 tags dropped in this case !!!

Are you sure that this is not the dropped-keywords Lightroom bug mentioned earlier on this page? Have you run the fix-it script provided by Adobe? —Jeffrey

— comment by mll on October 1st, 2008 at 6:25am JST (10 years, 1 month ago) comment permalink

Thanks for your reply Jeffrey. When I went to see the link you provided, I read “Keywords from Lightroom 1.x not included on export from Lightroom 2”. I realize I may have misunderstood this sentence, and maybe this case actually applies to me. Testing and I’ll tell you back.

— comment by mll on October 1st, 2008 at 2:40pm JST (10 years, 1 month ago) comment permalink

Well the problem was actually mine, and is solved now. Sorry about the annoyance, and thanks for your help.

— comment by mll on October 1st, 2008 at 2:52pm JST (10 years, 1 month ago) comment permalink

First of all: I loved your plugin! An I hope will love it again, soon… 😉

But now I upgraded to LR2 and so I had to update the plugin to the latest Version.
The Plugin-Manager says the Plugin is active…
But the Plugin does not appear in the Export-Dialog.
So, where is the trick?

— comment by Andi on October 1st, 2008 at 6:23pm JST (10 years, 1 month ago) comment permalink

I love your Metadata Viewer configurater.

Now that I can see the Longitude/Latitude and Altitude Fields, is their anyway that they can be made to be manually edited within Lightroom?

Ina

Sadly, no, Lightroom’s plugin infrastructure doesn’t allow for it (which is, to me, maddeningly frustrating — Lightroom lets a plugin modify all the fields that no one cares about, and does not let the plugin modify the fields people actually care about, like GPS, keywords, etc….). —Jeffrey

— comment by Ina on October 2nd, 2008 at 2:13am JST (10 years, 1 month ago) comment permalink

I used your SmugMug plug-in version 2008831.20 in Lightroom 2 until it expired the other day. I tried numerous times to add the uploaded new version 2008924.32, but all I get is a message saying there is an internal error. What can I do?

The automatic upload didn’t work properly with the older versions, sorry. You’ll have to manually install a recent version. The whole point of having the plugins expire is to force people to move beyond the original buggy versions. Things are gelling with the plugins, so soon I’ll push the date beyond the one-month-ahead that it’s set to now… —Jeffrey

— comment by Kathy on October 2nd, 2008 at 10:46am JST (10 years, 1 month ago) comment permalink

I get badServerResponse, nativeCode=12152 when exporting to picasaweb very often. actually it usually takes 2-3 retries to export album

I’d guess that your internet connection is having issues. I’ve not had other reports of this kind of error. —Jeffrey

— comment by vitaliy on October 7th, 2008 at 3:22am JST (10 years, 1 month ago) comment permalink

Hi Jeffrey
I read that you intend to work on writing a geotagging plugin
May I suggest Geosetter which is free and excellent
It allows manual geotagging as well as geotagging by synchronizing with a geotag logger

The “ideal’ plugin (for me) would be
1 Make a selection inside LR (or define a collection)
2 Go to Geosetter for geotagging and writing XMP information: city, location, etc..
3 save XMP file inside Geosetter
4 go back to LR and automatically read from XMP file

second option
1 make a huge selection inside LR of already geotagged photo (through step one)
2 Go to Geosetter to use its research engine like “find photo within an xxx (km or miles) radius from selected photo”
3 go back to LR with selection (or collection)

Thank you if you like this idea

Herve

Those are fine ideas, but unfortunately, Lightroom still doesn’t offer the plugin the ability to do it. Once Lightroom allows the plugin to update GPS metadata (either directly, or through automatic XMP updates) then it’s more integrated to just go ahead and do it all within the plugin, so that’s what I’m looking forward to. Even now, I could write something that computes which photos are closest to a selected photo (I do this on my blog: geoencoded photos have a “nearby photos” link, such as this link). Unfortunately, I don’t see an easy way to communicate that back to the user, other than to present a textual list, which is not very useful. Again, the problem here is the limited Lightroom API, which still needs time to mature. —Jeffrey

— comment by Herve on October 7th, 2008 at 6:52am JST (10 years, 1 month ago) comment permalink

hmm.. don’t this this is problem with my connection, this is definitely something related to lightroom because never had problems when exporting from Picasa even right after export from Lightroom failed.

in any case thank you for all your plugins

— comment by vitaliy on October 8th, 2008 at 3:19am JST (10 years, 1 month ago) comment permalink

When I used your plug-in in LR 1 it allowed me to resize photos in inches instead of just pixels (which is what I’m seeing in LR 2, plugin 20081007.xx). I’d like an option to resize in inches or mm.

— comment by Alan on October 11th, 2008 at 5:18am JST (10 years, 1 month ago) comment permalink

Got a couple of these error messages:

“An internal error has occurred: ?:15940: attempt to compare string with number”

— comment by Simon King on October 12th, 2008 at 4:09am JST (10 years, 1 month ago) comment permalink

I’ve got a strange display bug. Running Lightroom 2 retail with your latest plugin to date (), and whenever I perform any function that’s supposed to bring up a window, the window no longer appears. This is true for trying to open the plug-in manager, or going to “file -> export” or any other similar functions. Mind you, the window is actually there, you just can’t see it! I know this because Lightroom stops responding until I hit “Esc” which closes the invisible window. If I hit “enter” it uploads the photos to the last Smugmug Gallery I had chosen (under file -> export of course).

OS: Vista Home Premium
Graphics: nVidia GeForce 8400

— comment by Dirk H on October 13th, 2008 at 7:23am JST (10 years, 1 month ago) comment permalink

While going insane and pulling out my hair, I figured out what the exact issue is in my last post! Dual displays! I occasionally hook my laptop up to an external LCD monitor when I need accurate colors, and I had left the export dialog and plugin manager on the external monitor.

Most programs will open windows on the primary display if the secondary is disabled, but apparently not lightroom.

Needless to say, this is a LR2 bug, and has nothing to do with your plugin, which I find incredibly useful, so thank you!

— comment by Dirk H on October 13th, 2008 at 7:59am JST (10 years, 1 month ago) comment permalink

I am using plugin for uploading from LR2 to smugmug. Only recently have been getting the message: Warning Unable to Export

couldnt render image: readNegative:dng_error_end_of_file

I don’t know what this means except that I can’t add images to my Smugmug account.
Please advise.
JFR

— comment by James Romer on October 16th, 2008 at 2:52pm JST (10 years ago) comment permalink

Hi, Great Plugin thanks for creating it.
I have downloaded the Facebook exporter and i think it’s great. I have recently set up a “business” page in face book and would ideally like to send the pictures there instead of to a gallery on my normal page. I have had a look round your site but cant find any indication that this is possible. Is it possible and if not available yet is it an enhancement you would consider in a future update. Of course if it is already possible could you point me in the right direction to make it happen.

Many thanks

— comment by Mark Miller on October 17th, 2008 at 6:57am JST (10 years ago) comment permalink

Thanks for creating this tool (am using latest version) to export to FaceBook. I am using LR 2 RC1 (need Nikon D90 support). All works successfully so far.
1. Where is the Metadata Wrangler button / access point? There seems to be no mention of it in my Export dialogue?
2. Any chance i can ask for an item on you to do list: the ability to add a watermark to images as they are exported. Either simple text that can be located in the usual user configured locations (btm left /right, centred etc.) OR even better a an over lay transparent gif watermark image that embeds on the picture?
cheers
Rod in Sydney AU

The Metadata Wrangler is a separate plugin, available on my Lightroom Goodies page. For watermarking, you can use Tim Armes’ LR2/Mogrify plugin. —Jeffrey

— comment by Rod Sydney on October 17th, 2008 at 8:07pm JST (10 years ago) comment permalink

The zip file for version smugmug-20081015.33.zip appears to be invalid. I’ve tried downloading and opening on my Windows Vista machine a couple times over the last few weeks and Vista and WinZip are unable to open it. The file size is 141kb when downloaded. Can you check this file?

Thanks alot for writing these plugins!

mike

— comment by mikeli77 on October 18th, 2008 at 1:42pm JST (10 years ago) comment permalink

I found the issue: http://www.flickr.com/help/forum/en-us/83926/
I live in Belgium!

— comment by Mike on October 22nd, 2008 at 5:31pm JST (10 years ago) comment permalink

I am having the same probem:
I get badServerResponse, nativeCode=12152 when exporting to picasaweb for large format images (I use to send to PicasaWeb so I can then use Shutterfly to print…would be awesome to add Shutterfly plug-in)

I load 50% sized photos and it works splendifourously.

Great stuff otherwise, thanks!

— comment by joe T on October 25th, 2008 at 12:07pm JST (10 years ago) comment permalink

Ahhhh. I just loved the Flickr upload. amazingly useful software. Worked fine for LR 2.0 but just after I upgraded to LR2.1, it does not work. Just a head’s up., I can still load up Flickr, the old fashion way.

— comment by Marty -Seattle on October 26th, 2008 at 1:02pm JST (10 years ago) comment permalink

Hi Jeffery,

Just updated Lightroom 2 with the Lighroom 2 Smugmug plugin, I had been using the version 1 plugin before checking for a new one.

Unfortunately I keep getting:

+286.5: At =(tail call) line -1:
Return header ERROR
———————————————-
errorCode = “badServerResponse”
name = ‘The requested header was not found

nativeCode = 12150

The number following the “+” changes.

Sometimes the upload works, sometimes it doesn’t.

These are large files I’m uploading, 10-15 meg, but that shouldn’t matter.

Any ideas?

Thanks

Roger

P.S. I do appreciate your time and effort writing and supporting these plugins.

— comment by Roger on October 27th, 2008 at 11:59am JST (10 years ago) comment permalink

Hi Jeffrey,
I’ve just downloaded your Flickr plug-in for LR2 – thanks for this.
When I hit ‘Export’ in LR2, a dialogue box appears over the main Flickr export plug-in dialogue ‘+2219.4: At line 16508:?:17366: attempt to index field ‘?’ (a nil value). I hit ‘OK’, then in the main dialogue it tells me at the bottom that it is unable to export as an upload destination has not yet been set. However, I’m unable to enter anything into this line ‘upload to your Flickr Photoset’, even the ‘auto dests’ button doesn’t help, showing ‘+1924.1: At line 16508:?:17366: attempt to index field ‘?’ (a nil value). I don’t think I have any photosets on Flickr as I’m a new user on that site.
Could you please tell me where I’m going wrong as I’d love to be able to use this facility?
Manythanks.
Paul

— comment by Paul on October 31st, 2008 at 2:05am JST (10 years ago) comment permalink

bug report flickr plugin with LR 2.1:
when uploading an image to flickr with more than 40 keywords no keywords at all are displayed on the flickr website although flickr has set the limit to a maximum of 70 keywords. Please note that all keywords are still in the file itself but those keywords do simply not appear anymore on the flickr website except when you click on ‘more properties’ but that’s not the way it should work.

Inserting more than 40 keywords using the website interface of flickr gives no problem.

So I suspect either a problem with the flickr plugin or a hard limitation being set for uploading pictures with the flickr api.

Can you have a look on this bug please?

Thanks
Fabian

It seems to be a Flickr bug… the magic number for me was 26. If I include more tags than that, they’re all ignored. I’ve send a note to Flickr to ask about it…. —Jeffrey

— comment by Fabian Dierckxsens on October 31st, 2008 at 5:18pm JST (10 years ago) comment permalink

hello Jeffery, first of all thank you for the awesome/unique plugins. I hope adobe compensates you for the service you provide.

Im having trouble exporting to flickr on my vistaX64 machine with 20080814. also the auto update plugin button seems to be broken. upon selecting the plugin it gives me some error gibberish but still works (uploads). even slightly broken I still love it. works fine on my mac. thank you again sir.

— comment by Deacon MacMillan on November 4th, 2008 at 10:28am JST (10 years ago) comment permalink

Hello Jeffrey –

I’m getting the same type and syntax of error as Paul on October 31, but using the Facebook plugin. The line numbers the error occurs on are different, but the error syntax is the same.

Mac OSX 10.5.5, Lightroom 2.0. I have LR Mogrify2 installed, as well as the latest Flickr plugin, which works just fine for me.

If my error log would be useful, I’m happy to send over for your review.

Thank you very much for all that you’ve put into these amazing workflow tools, I appreciate them very much.

Steve

— comment by Steve on November 5th, 2008 at 3:44pm JST (10 years ago) comment permalink

Hey guy, really love the plugin. I use them to upload to Flickr. However, it would be nice if I can select multiple sets when I export.

cheers.

— comment by melvin foong on November 6th, 2008 at 1:33am JST (10 years ago) comment permalink

Hi Jeffrey,

Good job with the plugin. Small cosmetic change request/bug. I use a 24 hour clock (H:mm:ss, Dutch regional settings). When I do so the plugins reports for example: “ETA: 6.5 hours, tomorrow at 2:15%p”. The %p at the end is not needed I think, at least not for me.

Keep up the good work with the plugins since they really contains good feature and integrate well!

Regards, Ben

— comment by Ben Ootjers on November 9th, 2008 at 3:49am JST (10 years ago) comment permalink

I keep getting this error on when using the facebook export plugin. It worked at one time, but now it doesn’t.

+11373.8: At line 15578: ?:16440: attempt to index field ‘?’ (a nil value)

Thanks for your plugins and any help you may offer for this problem.

— comment by HWP on November 10th, 2008 at 6:43am JST (10 years ago) comment permalink

I am getting the same issue.
+11.4: At line 15578: ?:16440: attempt to index field ‘?’ (a nil value)

It won’t export to facebook anymore… 🙁

Thank you for your wonderful work.

For me to make any sense of the numbers in the error message, I need the exact version number of the plugin. I put this as an annoying flashing red warning on the comment-submission page, but still, sigh, most people still don’t take the 10 seconds required to tell me the version number. If someone doesn’t care enough to spend an extra 10 seconds, I’m not sure I’m going to bother wasting my time trying to address the issue (an issue that may well already be fixed in a subsequent version). —Frustrated

— comment by Cathy on November 10th, 2008 at 9:57am JST (10 years ago) comment permalink

same thing… with version 20081103.35
I’m getting:
+227.8: At line 15578: ?:16440: attempt to index field ‘?’ (a nil value)

It seems to result in the dropdown for the Facebook albums not getting populated. None of the album related options work any longer… and this of course results in not having any destination to be able to upload to. It used to work with older versions of the plugin.

Help?

— comment by Josh on November 10th, 2008 at 5:22pm JST (10 years ago) comment permalink

Oh, and if it helps, I’m on Vista SP1, with Lightroom 2.1

— comment by Josh on November 11th, 2008 at 2:50am JST (10 years ago) comment permalink

New version installed today automatically and Facebook export is broken. I was demoing this in class tonight and will have to cancel that demo.

Essentially, the pull-down for selecting the Album is frozen and blank. The program will not export until that is populated. It worked prior to today’s update.

Behavior verified on Vista and Vista 64 bit, Lightroom 2.1 on two separate machines.
20081111.37

The Flickr update worked fine however.

I just have never been able to figure out what it is about some people’s account/machines/situation/karma that causes this not to work. Maybe it’s a Vista thing? I dunno )-: —Jeffrey

— comment by Rikk on November 13th, 2008 at 6:26am JST (10 years ago) comment permalink

I’ve downloaded & installed the flikr plugin but the “Export” button is greyed out and it says “Upload destination not yet set.” However, when I try to enter anything in the upload destination dialogue box, it won’t let me & the drop down box won’t do anything. I’ve tried restarting lightroom but to no avail. Help please.

Fixed in version .46. I’d send this to you directly if you’d include your email when you leave a comment, but you didn’t. —Jeffrey

— comment by Doug on November 13th, 2008 at 1:41pm JST (10 years ago) comment permalink

I’m another one of your fans!!!

I understand “moonlighting” and hobbies, so please consider this as input to what I’m sure is a difficult problem with little time… I kick off one large export (> 300 photos, may be less to repro but I’m not sure). When it is going, I do anything with the plug-in and I get errors which causes the export to fail and abort. This can be launching the plug-in manager or trying to export another gallery (even to the file system, but it won’t let me get there). I have snapshots of the errors if you want them.

Basically, the first dialog info box is +84.3: At line 18317: photohistory: not logged in

Let me know if you need screenshots, more details, etc.

Again, thanks for saving hunderds (thousands) of us endless hours! You da man!

Gary

Oh. My. Goodness.

When I work on the plugins (which is always), I have the “reload plugin on each export” option checked (in the bottom-right “Plugin Author Tools” section of the Plugin Manager). That way, changes I make to the code are loaded right away, and my testing goes much more quickly.

I tried it today with the reload option turned off, and wow, I got the errors you reported. I realize now what the problem is, but an easy fix is not presenting itself to me. Until I can figure it out, please turn on that “reload plugin” option for all my plugins, and it’ll work just fine, and you can have multiple exports running at once.

What’s shocking to me is that this was not reported until now. —Jeffrey

UPDATE: fixed as of versions posted on Nov 11 2008 —Jeffrey

— comment by Gary on November 13th, 2008 at 2:16pm JST (10 years ago) comment permalink

Problem reported yesterday on ver 20081111.37 is still there with 20081111.38 downloaded this morning. Except that the Blank destination field has been replaced with a message.

I was able to restore the plug in by logging out and reauthenticating the Facebook access after a Lightroom restart. So, bottom line, 20081111.38 is working now. I have tested on Vista 32bit and will test on 64 bit later. Cross fingers!

I think this is finally fixed in .40! —Jeffrey

— comment by Rikk on November 13th, 2008 at 10:01pm JST (10 years ago) comment permalink

Hi Jeff,
Great work on this plug-in!
One thing you may want to think about adding to the feature list is the uploading of camera metadata. It seems that camera make, model, lens info, etc. gets lost during the upload process.
Thanks and keep up the great work!

Camera make, model, etc. should not get lost during upload… which plugin? Some sites ignore it all (e.g. Facebook), but otherwise, it should all work as if you’re using the site-specific uploader. —Jeffrey

— comment by Ed on November 17th, 2008 at 9:44am JST (10 years ago) comment permalink

Camera make, model, etc…. uploading to Flickr, used version 20081113.46.
info still not showing up.

It’s probably one of your plugin or Flickr settings, but I’m not going to try to debug this via comments. If you want help, leave your email address next time. —Jeffrey

— comment by Ed on November 17th, 2008 at 10:50pm JST (10 years ago) comment permalink

Jeff,
“minimize embedded metadata” was filtering the camera info; once unchecked, the data appeared fine.
Thanks,

— comment by Ed on November 18th, 2008 at 8:28am JST (10 years ago) comment permalink

Hi! I’m trying to export from LR2 to SmugMug. It seems that around every third photo I get a message saying that the file size is too large, even though it shouldn’t be. I’m exporting 12MP RAW files to full res JPEG. Other files that are the same size upload just fine to SmugMug. The dialog box gives me a choice to continue or stop the export (a total of 35 images). Exporting a single “too big” image also fails to work.

I’m pretty new to both LR2 and SmugMug, so it’s probably just something I’ve overlooked… but maybe you could give me some ideas to try? Thanks for your generosity – I feel fortunate to have come across your site!

— comment by chi on November 20th, 2008 at 12:10am JST (10 years ago) comment permalink

Just downloaded and installed v .45 of the SmugMug plugin, and I’m afraid the bug is worse than you thought: it won’t let me login regardless of whether I am already or not. All I can get is a “can’t find host” message. I went to my Smugmug page, logged in, and still get the “can’t find host” error.

Besides there’s a warning from the plugin manager that this one version expires in 4 days.

— comment by Michael Corbin on November 20th, 2008 at 11:51pm JST (10 years ago) comment permalink

Still having authentication issues. This has been going on with every version for the past 45 days or so up to .50 not sure what to do

Oops! Flickr can’t find a valid callback URL.

An external application has requested your login credentials and permission to perform certain actions on your behalf, but has failed to include all the required data.

Wow, I’ve never seen this one. Please send the log (referenced in the upper-right of the Plugin Manager) via email. Also, be sure you don’t have a local firewall blocking Lightroom…. I’ve heard reports of firewalls being an issue lately. —Jeffrey

— comment by A Dubs on November 22nd, 2008 at 2:48pm JST (10 years ago) comment permalink

Hi Jeffrey

Thanks for the great flickr plugin.

The problem that I have is that I have only recently started using the plugin and already have hundreds of photos uploaded to flickr. The plugin doesn’t know about them, and the metadata field shows them as not uploaded to flickr, which is obviously not the case… Also, I can see that this is going to become a problem if I delete an image from flickr.

The obvious quick fix is to make the metadata field that indicates whether an image has been uploaded to flick editable.

It’s already editable… see the “Flickr Extras…” item in the “Plugin Extras” File/Library menu items. That being said, I’m working on a scanning feature that will be released soon.

The ultimate solution would, of course, be the proposal 3(a) made by David on August 26th: being able to scan the images uploaded to the flickr account and synch the uploaded status.

Another observation that I have is that you have made the plugin able to pull the visibility, safety level, image type and public search settings from keywords. I would far rather have those settings implemented as metadata fields with the settings for each selectable, and (if you ever implement synch) synchable. I don’t really want to mix flickr status settings, which are flickr specific, with keywords, which should really be about the image and independent of the platform on which the image is displayed. So if you get the chance to implement metadata as an alternative to keywords for that info I would really appreciate it.

You can mark keywords in Lightroom as “don’t export”, and so you could create keywords like “flickr_public”, “flickr_family”, etc, all under one “flickr” umbrella. That’d segregate them pretty well from other keywords, and they’d never make their way outside of Lightroom, so wouldn’t pollute your keyword universe. Seems not too unwieldy to me, but then, I don’t use keywords or Flickr, so take that with a grain of salt. —Jeffrey

And thanks again for the hard work that you have put in to create a really great plug in.

— comment by Ric on November 23rd, 2008 at 3:31am JST (10 years ago) comment permalink

Thanks Jeffrey – hadn’t spotted the Plugin Extras…

— comment by Ric on November 23rd, 2008 at 6:40pm JST (10 years ago) comment permalink

After creating a new gallery from SmugMug: Tools, The upload destination and the drop down list doesn’t get updated until reloading the plugin.

version 20081123.47
Thanks

— comment by Wayne on November 24th, 2008 at 9:26am JST (10 years ago) comment permalink

Oh, I was referring to LR 2.0’s smugmug plugin
thanks

— comment by Wayne on November 24th, 2008 at 9:27am JST (10 years ago) comment permalink

Jeffrey,

Just downloaded your picasa plugin and am having some issues getting started. I get the error message as below.

Any help would be greatly appreciated!!

Execution/debug log for Jeffrey’s picasaweb plugin for Lightroom, version 20081123.43
Log started November 25, 2008 12:51AM local
November 24, 2008 10:51PM JST

Call time: 0.5469 seconds.
No body returned
+1.2: At =(tail call) line -1:
Return header ERROR
—————————————————————-

errorCode = “unknown”
name = “The system cannot find the file specified.


nativeCode = 2

_____ _____ _____ _____ _____ _____ _____ _____ _____
.

— comment by York on November 24th, 2008 at 10:57pm JST (10 years ago) comment permalink

Hello and your Flickr plugin is a real good work !

I just have a bug (when I change some export parameters) : AgDate.formatDateInUserFormat: %a specifier not yet implemeted

How can I export now to Flickr ? I’ve reinstalled the plugin, but the bug persists..

Thanxs !

— comment by Copeau on November 25th, 2008 at 5:35am JST (10 years ago) comment permalink

Hi Jeffrey,

I read a lot now about the plugin and may missed it.

Is there any way to say what size it should be exported?

I only seen the dpi field, but I want to only upload like a 600px version of the original file – any way to do that??
Thanks
Rolf

The Facebook version always outputs 604px on the largest size. That’s the maximum that Facebook allows, and there seems to be little reason to do anything else, so to keep the dialog simple the plugin just always does that. —Jeffrey

— comment by Rolf Hicker on November 25th, 2008 at 10:35am JST (10 years ago) comment permalink

Thanks for the info, makes total sense when you know more about facebook!
Nice plugin and very helpful. Thanks for sharing, it will make my life easier a lot!

— comment by Rolf Hicker on November 25th, 2008 at 3:40pm JST (10 years ago) comment permalink

Hi Jeffrey. Thanks for the great plugins! I’ve been using them for six weeks or so, but I’m having hit-or-miss results with the Flickr plugin. It gives me internal error messages about half the time I try to use it — even before I try exporting anything. There’s no other information given with it, simply “The plug-in had an internal error” when I first hit Command-Shift-E to export the selected photos and select the Flickr plug-in. I’d be happy to provide you with any information you need to further troubleshoot this, unless you already know what the problem might be, but I really miss the plug-in when it’s not there! 🙂 Thanks so much in advance for your help! –Billy

When you see the “internal error” bit, go to the Plugin Manager and grab the log referenced in the *lower* right section, and mail that to me. Thanks! —Jeffrey

— comment by Billy Halsey on December 6th, 2008 at 5:07pm JST (9 years, 11 months ago) comment permalink

Hi Jeffrey,

I installed the 20081204.58 version of the Flickr add-in, but it doesn’t add it to the export presets.

My upload plugins don’t add an export preset, they add an export destination. It’s all covered in the instructions. —Jeffrey

In the Plug-in Manager it appears to installed and running. Everything appears to be working like it is supposed to. You just can’t get to the plug-in from the export menu. Maybe I am doing something wrong in the installation, I am new to LR2. Flickr Extras… does show up in the Plug-in Extras menu, but when I click on any of the options that available it just locks up LR and I have to kill it in Task Manager. The dialog indicates that I need to login, but I haven’t seen any place where I can put my credentials in. Any help would be greatly appreciated.

thanks,

Ken

— comment by Ken Prochaska on December 8th, 2008 at 2:35am JST (9 years, 11 months ago) comment permalink

Hi Jeffrey,

Thanks for the answer. I got it to work and it works very nicely. I missed the step where you click on the title bar that reads “files on disk”. Once I did that everything fell into place. This is a great tool, I will use it all the time.

thanks,

Ken

— comment by Ken Prochaska on December 9th, 2008 at 1:16am JST (9 years, 11 months ago) comment permalink

Hi again Jeffrey. Re: my last comment (#29790), the log you wanted me to send you says, simply:

Plug-in error log for plug-in at: /Users/billy/Library/Application Support/Adobe/Lightroom/Plugins/flickr-jfriedl.lrplugin

**** Error 1

An error occurred while attempting to load this plug-in’s portion of the Export dialog.
?:17181: bad argument #1 to ‘?’ (string expected, got nil)

Thanks again for the help.

— comment by Billy Halsey on December 9th, 2008 at 3:23pm JST (9 years, 11 months ago) comment permalink

Hi,

a request which could be great could be to add in the group pools a feature which permit to tag with a keywork like “keyword prefix”_”name of my group” automatically add the photo to the group.

Best regards and thanks for all!

— comment by alex on December 11th, 2008 at 4:52am JST (9 years, 11 months ago) comment permalink

Jeffrey,
Great plugins – thanks! Just started using the Zenfolio Export plugin in the way you suggested (as a backup) and it’s working great… except for one thing.
How do I delete photos? Or at least how do I convince the plugin that the photo has gone and to stop looking for it? I can’t seem to manually edit the metadata field in Lightroom, and can’t see any way in the plugin to reset it. Any ideas?
Thanks,
David

— comment by David on December 16th, 2008 at 7:56am JST (9 years, 11 months ago) comment permalink

Hi Jeff,

Thanks for these great plug-in. Since last Lightroom upgrade 2.2, I have having issues using the flickr plugin. I have downloaded your latest one. The error message is

**** Error 1

An error occurred while attempting to load this plug-in.
The plug-in description script (Info.lua) is missing.

Thanks
James

This means that it was not installed correctly. Check the installation instructions to make sure you’ve done it correctly. The plugin *is* a folder (with a bunch of files, including “Info.lua”). —Jeffrey

— comment by James Sheng on December 22nd, 2008 at 11:41pm JST (9 years, 11 months ago) comment permalink

I too got the “Whoa, file does not exist immediately after waitForRender. Please let Jeffrey know” dialog
OSX 10.4.4; LR 2.2; Flickr Plugin with Metadata wrangler.
[img]http://img.skitch.com/20081223-87h32ygx4ca8ffyn32953mscti.jpg[/img]

Turned out the files I was trying to export were off-line 😉

— comment by René Damkot on December 23rd, 2008 at 8:00pm JST (9 years, 11 months ago) comment permalink

I just updated to the new (12/24) Flickr plugin and then began uploading some photos. Lightroom then froze; now when I open Lightroom I receive the “An error occurred when attempting to change modules” error message and I have a limited menu and can’t do anything in Lightroom. I tried deleting my preferences file (~/Library/Preferences/com.adobe.Lightroom2.plist) but still no luck.

— comment by Holly on December 27th, 2008 at 5:29pm JST (9 years, 11 months ago) comment permalink

The Smugmug / Lightroom 2.0+ (Actually 2.2) is saying “Can’t use plug-in Smugmug” “The pluf in had an internal error”

— comment by Robert on January 2nd, 2009 at 1:21pm JST (9 years, 10 months ago) comment permalink

Same problem as above – LR 2.2 doesn’t support the Smugmug upload plug-in after installing LR 2.2 per Adobe. It may be that the plug-in isn’t where 2.2 expects it to be, but why wasn’t any new location of plug-ins a part of the installation? Need this fixed whenever you can. Planning to use a little free time this month for massive uploads to Smugmug.

— comment by DonD on January 3rd, 2009 at 10:13am JST (9 years, 10 months ago) comment permalink

After updating to the latest flickr plugin, it no longer updates the image. It simply appends the image to the end of the set. I have update checked.

I don’t understand what you mean; could you be more verbose (and provide an email address so that I can continue the discussion that way)? —Jeffrey

— comment by Adam on January 5th, 2009 at 6:31am JST (9 years, 10 months ago) comment permalink

Whenever I create a new gallery on SmugMug using your plugin (2008.1228.56) it is created as public even if I select the private option. I have to correct this manually each time. Thanks for a very useful plugin.

— comment by Mark Goddard on January 5th, 2009 at 9:42am JST (9 years, 10 months ago) comment permalink

Hi Jeffrey, thanks for a great smugmug exporter from lightroom2
I just updated to the latest version and am having some problems.

Error response from smugmug: wrong format (ByeCount given: 3309379, received: 3309739. MD5Sum given: ____, actual: _____.)

Aborting export after x of x images successfully uploaded

The number of images uploaded varies – sometimes 1, sometimes 5 sometimes 20 before this error happens – but haven’t been able to upload fully once yet.

Only thing different about these photos is that I have geotagged them in the exif

Any ideas?

Thanks, Jason

— comment by Jason on January 9th, 2009 at 7:11pm JST (9 years, 10 months ago) comment permalink

Typical – after 5 or so attempts and then I post here, the next time it worked 😉

I’ll let you know if it persists.

Thanks for a great and free plugin 🙂

— comment by Jason on January 9th, 2009 at 7:29pm JST (9 years, 10 months ago) comment permalink

I am handling NEF+JPEG in one folder to get fast results uploaded. Unfortunately the export plugin tries to upload everythig to GOOGLE.

The Webalbum does not understand NEF files and therefore fails. A filter to neglect the NEF files would be more than helpful in this case.

You’re saying that my plugin tries to upload NEF files to PicasaWeb? Are you selecting NEF files, then invoking the export with “ORIGINAL” as the format?
If so, don’t do that. 🙂 —Jeffrey

— comment by Olaf on January 14th, 2009 at 7:28am JST (9 years, 10 months ago) comment permalink

I wish the plugin did not have an expiry date. The previous version of the plugin I was using worked great… Now the newest version of the plugin gives me errors with flickr constantly – I can’t even upload a series of 50 photos without errors. I’m not sure if it’s flickr being semi-broken. Thankfully the export option includes ‘new’… without which I would be lost.

— comment by ryan on January 14th, 2009 at 5:15pm JST (9 years, 10 months ago) comment permalink

Ah I hate to follow up… The error is “unrecognized filetype” from flickr.

One other major difference with the new plugin is that it seems to require lots of logging in and retrieving of data from flickr every invocation, even if they are mere minutes or seconds apart.

I know, huge laundry list, I just want my previously working plugin to work!

— comment by ryan on January 14th, 2009 at 5:17pm JST (9 years, 10 months ago) comment permalink

Great job!! Thanks a lot. It makes me easier upload to flickr.

I have found a “bug”, on Spanish i can tag in lightroom letters like ñ , á, é, í, ó, ú, ü that it disappear when i export with your plugin to flickr.

I will be very pleasure if you add it to your todo list.

Thanks.

— comment by Manuel on January 20th, 2009 at 8:17pm JST (9 years, 10 months ago) comment permalink

Jeffrey,

Thanks for the great tool.

A couple of problems with the new scrolling gallery list on the Lightroom to Zenfolio plugin 20090119.54:
* Ampersands in gallery names show up four times: “Cindy &&&& Darren”.

Just pushed new versions (20090126.*) that fixes this.

* If you choose a group that has several galleries whose names have not been loaded, the names are downloaded, and the first sub-gallery appears selected. If you export without changing the selection, it appears to succeed, but no files are uploaded. You need to change the selection for it to “take”.

I don’t understand what you mean here…group? “take”? Could you be more verbose (perhaps via email)?

* There is no way to scroll horizontally so that you can see the end of very long gallery names (or gallery paths) . A tooltip on hover with the full path would also work, although not as well.

Added the tooltip.

As a personal preference, I find the red triangle, black rectangle, and horizontal bars an odd look. The “select” button is also a break from the platform standards. I wonder why you couldn’t use a regular listbox. I think the horizontal scroll is a good idea.

It all looks odd, but it’s the best I could come up with given the limited nature of the Lightroom plugin API. The plugin infrastructure is pretty mature when you consider how young Lightroom is as an application, but it’s horribly restrictive when considered in the light of decades of UI design. It simply doesn’t offer ways to do scrolling (in any direction), but I figured out a way to fake it into looking like it’s scrolling in one direction. It’s all built up from very basic parts, as if I built a digital watch from a pile of Radio Shack transistors. It looks horribly wonky, but if you have more than a few items in the list, it’s more practical than the “popup menu” UI element that Lightroom does offer. —Jeffrey

Thanks.

— comment by Silverhalide on January 23rd, 2009 at 2:41pm JST (9 years, 10 months ago) comment permalink

Ok, found a different bug. Both Resend Metadata option and export replace will not update the description field with an updated caption.

I don’t have a “Resend Metadata” option, and “replace” is explicitly defined as “replace the image; don’t touch the metadata”. —Jeffrey

— comment by Rubin110 on January 25th, 2009 at 10:07pm JST (9 years, 10 months ago) comment permalink

Hello Jeffrey,

You obviously have done a great job providing photo enthusiasts with tools simplifying uploads. Would you be interested to add a flavor of the Lightroom plugin for ShutterPoint? We provide a very straight-forward public API, please see ShutterPoint API here. Please feel free to e-mail us with any questions or comments!

Thanks!

— comment by Ken on January 27th, 2009 at 11:04am JST (9 years, 10 months ago) comment permalink

Hi Jeffrey,
First of all, thank you for the great SmugMug plug-in! It really makes life much easier! And now that it doesn’t work for me, I cannot understand how could I live without it…

Anyways, as I said, it doesn’t work. Since SmugMug had their maintenance few days ago, whenever I try to export pictures to SmugMug, it tries to conect to the server and never manages… I have the latest version of the plug-in. Is there a real issue there, or it is only me?

Thanks,
Rovhazman

— comment by Rovhazman on January 30th, 2009 at 11:47am JST (9 years, 10 months ago) comment permalink

Hi,

there seems to be a problem in the Flickr Export plugin, in the Dialog box that allows you to define you description templates.

I have the following template:

{CameraModel}, {Lens} Lens

{FocalLengthMM} {Exposure}, ISO {ISO}, {Flash}

I go into the Edit/Add dialogue box, change the Preset Title to “My Caption”, paste the template and click “Create new”.
When I click, the linebreaks in the template disappear and the OK Button changes to “Abandon Changes”.
Back In the Export dialogue, the example description isn’t visible but after the images are uploaded to Flickr, they have the correct description. The newly created template also doesn’t survive a Lightroom restart.

What I’d expect the dialogue to behave like is:

1. Correctly save the template, _without_ removing the linebreaks
2. Make the button read “close dialog” then
3. In the preview (example description) it would be ok to remove he linebreak
4. Don’t lose the Preset when quitting lightroom 🙂

I’m at a loss to explain why they don’t survive across restarts, but my guess might be a corrupt Lightroom preference file. Take a look in it for “info.regex.lightroom.export.presets” to see whether anything there looks familiar…. that’s where the presets you create are stored.

As for the other things, I’ve just pushed a new version that should at least start to address the issue of multi-line descriptions. Let me know how it goes. —Jeffrey

— comment by Jan on January 31st, 2009 at 9:15pm JST (9 years, 10 months ago) comment permalink

Thanks!

Works like a charm now.
The preset is properly saved too and survives restarts now.

— comment by Jan on January 31st, 2009 at 11:21pm JST (9 years, 10 months ago) comment permalink

Hi for the smugmug plugin (Jan 30th update but even before that upgrade): bad server reponse, looks lie a lot of people having this problem, any suggestion (logout / login does not work…) Thanks, excellent work, by the way. Tom (I have Windows XP)

I’ve alerted SmugMug… awaiting a response. —Jeffrey

— comment by Tom75 on February 4th, 2009 at 10:21pm JST (9 years, 9 months ago) comment permalink

It always worked fine, but now all of a sudden when I export to Flickr it says “youre not authenticated to flickr…” so I click the button and read “I’ve authenticated at flickr.com” and then it takes me back again to “youre not authenticated…..What happened? My Export to Zenfolio works still okay.

— comment by Yolande on February 5th, 2009 at 5:33am JST (9 years, 9 months ago) comment permalink

When uploading images to Flickr which have tags in Hebrew they appear as gibberish. I fix them manually in Flickr (which does support all languages in tags). I guess you’re just not using UTF when uploading the tags.

p.s – love the plugin!!

I am using UTF-8, but Flickr has all kind of tag-related bugs, and this is one. Several notes from me to them about it have not been answered, so there’s not much I can do… )-: —Jeffrey

— comment by lior shapira on February 8th, 2009 at 4:44pm JST (9 years, 9 months ago) comment permalink

I noticed that when exporting to Zenfolio the status text above export progress bar says: “50 of 88, ETA: 21 minutes at 9:51 %p”. That %p should probably be something else. 🙂

BTW, thank you for your excellent work, I’m very happy user of your export plugins!

The %p is a bug in non-English versions of Lightroom. It should be fixed in the 2.3beta, I think, but I haven’t tested it yet. —Jeffrey

— comment by David on February 9th, 2009 at 4:52am JST (9 years, 9 months ago) comment permalink

@Jeffrey – I’m using English version of Lightroom, but I don’t have English settings on my OS. So the problem might be that Lightroom doesn’t interpret my settings correctly.

Thanks for you answer, it’s just a cosmetic flaw, no worries. Take care.

— David

— comment by David on February 9th, 2009 at 7:58am JST (9 years, 9 months ago) comment permalink

Hey Jeffrey, thanks for the great Facebook export plugin. Everything is working great except for the limit of 60 photos per album. Although this used to be the case, it seems like a lot of users (such as myself) can add up to 200 images per album. Can the plugin be updated to support this?

You can have up to 1,000 images in the “application default album”, but according to Facebook’s API documentation, the max for other albums is still 60. I have no idea why they have such an arbitrary limit, but there it is. —Jeffrey

— comment by Jesse on February 9th, 2009 at 3:21pm JST (9 years, 9 months ago) comment permalink

Hey Jeffrey, I think that information may be outdated. I can add up to 200 images to any of my albums and so can most of my friends. This started happening around the time they released the New Facebook last year. In fact, today I uploaded 60 images to a new album using your plugin, and then manually added 13 more via Facebook web uploader to make it 73/200 images in the album.

— comment by Jesse on February 9th, 2009 at 6:37pm JST (9 years, 9 months ago) comment permalink

Hello,
Thank y0u for taking the time to develop these wonderfull tools that make our lives much easier. I am an avid user of the Flickr and Picasa plugins.
Since Spaces.Live.com started giving 25GB free space for photos, I found myself using it more and more, because it also makes my life easier when it comes to control who sees which photos.
And this is when I started to feel the need for a Lightroom uploader for Live Spaces 🙂
Are you planning on developping an “Export Plugin for Live Spaces”?
Thanks again,
J

— comment by JoaoC on February 10th, 2009 at 3:58pm JST (9 years, 9 months ago) comment permalink

I just started to use Flickr and wouldn’t have done without your excellent plugin. Thanks for your efforts. It’s very much appreciated.

I experience one unexpected issue: The Month / YYYY function or possible the date functions in general don’t consider the “Date Original” metadata, but rather the date when the photo was post processed.

Is there an option to be able to use the “Date Original’?

Reinhard

— comment by Reinhard on February 13th, 2009 at 9:38pm JST (9 years, 9 months ago) comment permalink

Hi – last 2 version do not add copyright watermark (am currently on 20090923.75). Any solution for that problem? LR2.2 current.

Oops, sorry for not responding to this sooner. The plugin doesn’t have any influence over Lightroom’s limited watermarking features, so whether it’s there or not is dependent on the plugin settings. Perhaps you just unchecked the “add watermark” box by mistake? —Jeffrey

— comment by Maciek on February 24th, 2009 at 5:33am JST (9 years, 9 months ago) comment permalink

First, thank you for taking the initiative to create these plugins. Perhaps Smugmug will offer a little financial reward since they recommend your plug.

Several times over the past few weeks I have tried to download your flickr plug-in. My PKZip almost always reports an error with the ZIP download file. In addition, when I click on the file, my explorer crashes. There is something wrong with this file.

I have successfully downloaded your smugmug plugin several times and I do not have this same problem…the problem is only with the flickr plugin.

Thanks!!
Brad

The zips for all the plugins are created in the same way (by the same code) and served from the same machine, so they should all unzip the same, unless there’s a problem related to the contents. What error does PKUNZIP report? —Jeffrey
By the way, about SmugMug and “financial reward”, they’ve created a great and popular service whose very existence makes the financial reward of my donationware plugin possible. When I’ve run into issues, they’ve been very responsive (and it’s turned out that the problem has been mine at least half the time). I’m very appreciative of them, so much so that when one of the founders mentioned as an aside that he’d like multi-login support, that immediately became my number one priority. I’ve had the same good experience with the folks at Zenfolio. —Jeffrey

— comment by Brad Schulz on February 26th, 2009 at 5:41am JST (9 years, 9 months ago) comment permalink

I seem to have problems during authentication with both the Flickr and Facebook plugin after upgrading to 2.3. I’m at the latest version for both, and the logs are pretty empty… I have sent them anyway through the procedure in the plugin manager.

— comment by Mike on March 4th, 2009 at 5:00am JST (9 years, 8 months ago) comment permalink

Using XP, Lightroom2, and downloaded smugmug-20090302.77.zip . When I try to open with Lightroom Plugin Manager, I get “An error occurred while attempting to load this plug-in”. I downloaded it 3 times with no avail. Please help!

Please send mail with more info, such as any diagnostics that might be found in the lower-right section of the Plugin Manager. —Jeffrey

— comment by JohnnyG on March 4th, 2009 at 1:43pm JST (9 years, 8 months ago) comment permalink

There is no other info. Just a window that pops up with the message above. The Plugin Manager only reads, No lightroom plug ins have been added to this computer

I’m not sure what to suggest, then…. I’ve heard no other reports along this line. Just to be sure, you downloaded the zip file, unzipped it to create a smugmug-jfriedl.lrplugin folder, and attempted to point the Plugin Manager at that folder name (and not, for example, any file inside the folder?). —Jeffrey

— comment by JohnnyG on March 4th, 2009 at 11:05pm JST (9 years, 8 months ago) comment permalink

I found the problem. User stupidity. I forgot to unzip the file. Duh! Thanks and I will include the “dummy tax” when I register and donate. Talk about FAST replies!!!

— comment by JohnnyG on March 5th, 2009 at 12:45am JST (9 years, 8 months ago) comment permalink

Still not able to use smugmug plugin. Vista system. Lightroom 2.3..

Plug in had an internal error.

An error occurred while attempting to load the plugin portion of the export dialogue.

? : 18540 : bad argument # 1 to ‘?’ (string expected) got nil.

That is what it says. Please help.

Plugin version number? —Jeffrey

— comment by Lorin on March 5th, 2009 at 1:32am JST (9 years, 8 months ago) comment permalink

Hi Jeffrey, first I take the opportunity to thank you for this great plugin. Making it donationware forced me to fight my procrastining tendencies and send you what to hava a couple of beers. 🙂

Now, for my problem. For some time (maybe 1 week) now, whenever I righ-click on an image > Export > [a flickr preset export here], I get an error message : “could not log in to flickr – Internet connexion down?”

If I right-click > Export… then manually choose whatever FLickr preset, it works.

Thanks for any help to debug this.

I’ve seen this before and am not sure exactly what is going on, but I think it’s because you created the preset while not logged in. Visit the export dialog, click on the preset name, make sure you’re logged in, then right-click on the name and resave to the same preset, and it should work. I hope. —Jeffrey

— comment by mll on March 8th, 2009 at 9:15pm JST (9 years, 8 months ago) comment permalink

Jeffrey: thanks ! It works – at least it goes on to the next bug – read on :

I upgraded today to the very last version, and when I try to oplad now, after the photo is produced locally, the upload to flickr fails after 2 dialogs are displayed :

one with something that looks lige debug info, the picture tags list wolled by “true” ; upon clicking on OK, then I get : “Impossible d’exporter – foo” (“unable to export – foo

Oh my, how embarrassing! That’s some of my debugging code that I forgot to take out before pushing it. I guess I shouldn’t try to code when my brain is fried with a fever. My brain is still fried (this cold just won’t go away), but I just pushed a new version without the debugging code. Sorry for the hassles. —Jeffrey

— comment by mll on March 9th, 2009 at 3:02am JST (9 years, 8 months ago) comment permalink

LOL – OK, you’re forgiven 🙂 Thanks four your quick response despite your cold. Get some rest and heal yourself ! 🙂

— comment by mll on March 9th, 2009 at 4:32pm JST (9 years, 8 months ago) comment permalink

Hi Jeffrey, with the latest version I have an Authentication problem ! When logged onto Flickr there is no automatic response and using the Authentication button then entering login details results in an HTTP 404 error. I’m using LR 2.3 and the latest plug-in ver .83 , I have tried restarting LR and uninstalling the plug-in then reinstall

Still unable to Authenticate !!

Two other people have reported this and I have not been able to figure it out. Still digging! —Jeffrey

— comment by Jon Petty on March 10th, 2009 at 5:14am JST (9 years, 8 months ago) comment permalink

Thanks for your great LR plug-ins, they definitely make life a lot easier when it comes to managing online albums! I am using the latest version of Lightroom and your smugmug plugin v20090305.79.

I have encountered an issue that is actually caused by a limitation put in place by SmugMug it is in relation to the image file size, the error i am receiving is “Image to Large” (basically it is 12.5mb max for power users and my new camera has caused the image size to end up at approx.. 14-18mb meaning that i now need to export them manually and upload using their tool, or manually specify a new size on each export depending on the raw file size.

I have contacted SmugMug to see if anything can be done about this at their end and their response was as follows:

“Thank you for contacting SmugMug. That’s actually the Lightroom uploading plugin that rejects the photos. Your Power account doesn’t allow uploading JPG photos that are larger then 12MB, Only the Pro account allows for up to 24MB big files.

If you could upload these larger files using our Simple uploader, it would accept them and we would automatically resize the photos for you. You would have to ask the developer of the Lightroom plugin if he would be able to add this as a feature to his uploader.”

I have no idea how big the job it is to make this change or if it is just a matter of working out what their up-loader does differently to your plug-in however if i cant get it to work i think i will need to create a whole new workflow 😐

Any help would be very much appreciated 😉

The photo has already been rendered to the pixel size and compression quality you specify in the Export Dialog before the plugin ever gets its hands on it, so there’s not much the plugin can do. If the plugin allows you to upload a file that has too many bytes, SmugMug returns an error, so my having the plugin pre-check the size before uploading saves you the wasted bandwidth. It’s possible, I suppose, to embed some kind of rerendering program into the plugin, but how would you suggest the plugin reduce the file size? Lower the JPG quality setting? Lower the pixel size? (Reduce? Crop?). It’s not a trivial problem to solve to everyone’s satisfaction. —Jeffrey

— comment by Zappa on March 13th, 2009 at 12:21am JST (9 years, 8 months ago) comment permalink

Your Zenfolio downloader for Lightroom is the next best thing TO Lightroom.

That’s why not having it is so painful.

I upgraded to Vista Ultimate 64 and Lightroom 64. Since then, my attempts to use the plug-in result in “TimedOut” errors. My computer has broadband connectivity and I have no issues accessing Zenfolio from my browser and I show good values in network testing and pings.

Do you have a firewall or other kind of security thing that may need to have Lightroom added to a list of some kind? —Jeffrey

Any suggestions?

— comment by Mike Brant on March 18th, 2009 at 10:48am JST (9 years, 8 months ago) comment permalink

Hi Jeffrey, I have done a bit more reading on both Lightroom and Smugmug and have created a new workflow that is actually much better then the way i was working before (and much faster) plus the file size is no longer an issue 🙂

I will be donating to register each of your plug-in’s as i think they are great! and i look forward to the continued development of each one (unfortunately i can only afford to reg one at a time, so Smugmug will be first 🙂 )!

Thanks again!

— comment by Zappa on March 18th, 2009 at 12:50pm JST (9 years, 8 months ago) comment permalink

Hi Jeffrey,

I use Kaspersky for my security. I’ve both verified Lightroom is a permitted App. and run the test with the firewall disabled. Neither had an impact on the problem.

Hmmm, it’s usually a firewall issue when I hear of this kind of problem. Ah, wait… Vista 64… I think I remember something another user reported…. it was really esoteric. Let me see whether I can dig it up… —Jeffrey

Okay, I’ve got two ideas. One user fixed a similar problem by disabling “TCP checksum offload” in his network card properties. Another idea is that Vista might be trying to use IPv6, and if so, you may need to disable it. See this and/or this (in that latter case, in step 5, choose option “b”). Let me know whether any of these help. I hope so(!). —Jeffrey

— comment by Mike Brant on March 18th, 2009 at 10:27pm JST (9 years, 8 months ago) comment permalink

Just another comment of high praise for you and your work Jeffrey. I absolutely love this facebook plugin for LR 2 in addition to your Flickr Plugin..

Hopefully deviantart will open up it’s sandbox for you to play in one of these days..

— comment by Joseph Palmer on March 21st, 2009 at 1:59am JST (9 years, 8 months ago) comment permalink

Hi,

I have updated my Smugmug plug-in 20090331.84. The only problem I have is that I do not have a slider to navigate through my galleries. Yes, I have looked both left and right sides- no slider. I did the re-load several times.

Help!!!
Bob from California( or our great governor
would say- Kalifornia)

The slider went away recently when I figured out how to add a real scrollbar (which hopefully works!). —Jeffrey

— comment by Robert T Higaki on April 1st, 2009 at 10:51am JST (9 years, 7 months ago) comment permalink

Love your plug-in but since upgrading to LR v.2.3 it won’t export to Flickr. I get the following error message:

INTERNAL PLUGIN ERROR
Bad upload: empty response

When I try to check for updates I get:

INTERNAL PLUGIN ERROR
Reply from the version server not understood:

404 Not Found

Not Found
The requested URL /LightroomPlugins/v/2.3/flickr was not found on this server.

Looks like the new version is incompatible. Please fix! Thanks!

What version are you using? If not the latest, please upgrade. If you still get the errors, please send (via email) the log referenced in the upper-right section of the plugin manager. —Jeffrey

— comment by Julie on April 7th, 2009 at 3:07pm JST (9 years, 7 months ago) comment permalink

Upon uploading to flickr, , I get this error:

This plug-in’s post-processing task did not finish successfully.
?:14323: attempt to index field ‘?’ (a nil value)

The upload seems fine and all the metadata is in tact. This happens if I have “select at export time” for the photoset selected and define no new photoset as my set. This is run as a preset directly.

Plugin version? —Jeffrey

If I run it using the normal “Export…” it is fine and I get no errors.

— comment by Linh on April 17th, 2009 at 11:54am JST (9 years, 7 months ago) comment permalink

Hrm, I don’t know how to edit my comment, but I’m using the latest version, 20090403.89.
As a preset, I get the same error if I try to make a new set. Again, it says it can’t upload, but it’s already done and seems fine otherwise.

Just pushed a fix (.90). Sorry for the hassles… it was a silly mistake on my part. —Jeffrey

— comment by Linh on April 17th, 2009 at 12:08pm JST (9 years, 7 months ago) comment permalink

Hi
Thanks for the Facebook plugin. Just registered for this plugin because it makes uploading photos from LR to FB so easy.

Unfortunately I’ve encountered an error tonight I was hoping registering would solve but it didn’t. I’ve selected one photo and trying to upload it to my Profile album on FB. It’s throwing an error that says:
“Error response from Facebook: Error uploading image: Invalid album id. Aborting export after 0 of 1 images successfully uploaded”. The album is my Profile album so why would it have an invalid album id?

While I’m reporting issues… here’s a less critical one.
I have noticed that when I select a currently selected album there are some radio button choices below the album selection area.
Albums: sort alpha., recently created first, recently updated first
Albums go: at tope of list, at end of list
If I want my 5 selected photos to be added to an existing album I want them to be added first in the list of that album’s photos. However when I selected recently updated first, the photos uploaded at the end of the album. I had to organize the photos later in FB. Seems the radio buttons you provide don’t work for me. I’m not sure that the Albums radio buttons work either. Order of the albums seems unaffected by the radio button choices.

After getting that error, could you send me the plugin log (with the “send to Jeffrey” button in the upper-right section of the Plugin Manager? About the sorting, those buttons all refer to how the items in the list should be presented to you, not how images are sent to those albums. The sorting order of the list becomes important when you start to have dozens and hundreds of items. Unfortunately, FB does not give an external app like mine the ability to do much more than shove an image to their service, so I can’t do anything about the sort once it gets there )-: —Jeffrey

— comment by Bruce on April 20th, 2009 at 3:09pm JST (9 years, 7 months ago) comment permalink

Forgot to mention the plugin version… I’m using the latest, v. 20090403.70.
I tried posting the 1 image to another album and that worked fine. But then FB doesn’t let me move that image to my Profile album either. So I had to delete and try something else.

I also noticed that when I saved the 1 image to my local disk and uploaded using FB interface instead of your plugin, it offers the ability to frame the photo for thumbnails used on FB for any postings/comments I make.

I don’t know a lot about FB, but I understand that there’s a per-album limit that’s 60 for most people (unless you find yourself in some super-secret never advertised small test group, in which case the limit is…. something else). So, maybe your Profile album was full? As for the thumbnail “frame”, what do you mean? Do you mean that it actually adds a frame around the image for you? You can do that when exporting from Lightroom with Tim Armes’ LR2/Mogrify plugin. —Jeffrey

— comment by Bruce on April 20th, 2009 at 3:33pm JST (9 years, 7 months ago) comment permalink

Hi Jeff

There is an Adobe forum at http://forums.adobe.com/thread/414360?tstart=0#
where Lightroom users including myself are complaining that the Caption acquires the camera name or other text immediately on import into Lightroom and then becomes completely uneditable: All changes to templates or presets are also ignored. This occurs because Olympus and some other cameras write their name to the EXIF ImageDescription field and is a serious nuisance because it affects every photo, not just those uploaded to Flickr.

I have tried removing your plug-in and re-starting Lightroom, but the Captions remain unalterable. I don’t know if the other posters to the Adobe forum are using your plug-in and I realise that it could be due to something else such as a corrupt Catalog, but do you have any suggestions?

Thanks
Tony (from England)

— comment by Tony Braime on April 26th, 2009 at 12:23am JST (9 years, 7 months ago) comment permalink

Having a problem with an error message of “Warning – no images to process – all images were filtered out due to the settings in the “upload Management” section of the Export Dialog”
I am uploaded the current version 20090422.87, but it did not help. Using LR 2.3 with windows Vista. This happened once before, then it just started working. Am I missing something? I cannot find an “upload Management” section of the Export Dialog.

Ah, perhaps I need to adjust the warning message to be specific to the plugin, sorry. I’m guessing that you are using the SmugMug plugin? Look for the All/Update/New radio set in the Upload Destination section of the Export Dialog. —Jeffrey

— comment by John on April 28th, 2009 at 11:31am JST (9 years, 7 months ago) comment permalink

Hi !

I believe your plug-in for Lightroom 2.x is great ! I tested it, I liked it, I had decided to buy it, BUT I need to ask your help to kindly correct a BUG of it :

OS : Xp with SP3
Version : 20090429.89
BUG : special chars in gallery name, gallery listing and category listing, so basicall all over are NOT shown correctly.
Special chars for me are : “éáűőúí” and their capital version : “ŐÚÉÁŰÍ”

Could you be so kind to correct it pleae ?

Many Thanks for your response and help,

Andras Bakos

I think this is a bug in SmugMug, but I just pushed version .90 that attempts to work around it. Let me know how it goes… —Jeffrey

— comment by András Bakos on May 2nd, 2009 at 1:54am JST (9 years, 6 months ago) comment permalink

Hey Jeffrey,

I have the latest Flickr plug (20090429.94) in and LightRoom 2.3. When I upload to Flickr, I often get “out of memory” errors – I’ve got a pretty newish laptop – Core2 Duo 2ghz, 3gb ram. Everything starts fine, I leave it for a few hours only to come back and find that it’s stopped uploading! It’s worse if I try and export 2 sets at once (i.e. 2 exports simultaneously). Usually, I try and upload 100 or so photos in a set. I never had this with version 20090403.89. Any ideas?

rob

Could you describe exactly the error message, and how it’s being presented? A screenshot mailed to me would be fine. I need to determine who is running out of memory (Lightroom, or some sub-process spawned by the plugin). —Jeffrey

— comment by Robert A on May 2nd, 2009 at 9:13pm JST (9 years, 6 months ago) comment permalink

great plug-ins! I just updated and registered. I saw that you’ve updated the FaceBook plug-in to match their new 200 photo limit. When trying up upload more than 60 photos to an album, it gives me an error after the 60th photo uploads. I’ve tried reloading the plug in as well as restarting Lightroom, with no luck…

Yeah, sorry, it seems that Facebook hasn’t quite got everything updated yet (sort of a right-hand not knowing what the left is doing?). I’ve reported it… hopefully they’ll finish rolling it out, soon. (And when they do, be sure to express your appreciation to them for all that they provide so freely.) —Jeffrey

— comment by Brett on May 22nd, 2009 at 2:55am JST (9 years, 6 months ago) comment permalink

Hi
Of the photo services you provide upload plugins for from Lightroom, which one do you like the best (visually most attractive interfaces, geotagging, other features, etc)? I have my own preferences but was curious which one you think is best?

Personally, I don’t use any of them (except I use Zenfolio as backup storage). Visually, I think Flickr, PicasaWeb, and Facebook are pathetic, but fine for family snapshots where the memories are compelling, not the photographs. Zenfolio and SmugMug are in a wholly different class. —Jeffrey

— comment by Bruce on May 22nd, 2009 at 12:39pm JST (9 years, 6 months ago) comment permalink

Boy I couldn’t agree more with your comments. I would prefer Zenfolio the most from an attraction perspective but they have no support for geotagged photos yet. I wrote to them about that and they said they didn’t support it. I responded that they should add it as it was the up and coming thing in photos. Smugmug has it but it’s rather unobvious. Picasa has it too, with a small map panel showing a location pushpin on it for the album location but their albums have no “skins” or themes. I would love to see an attractive well done small map with pushpin like that for each photo since it will vary from photo to photo in most cases. I encourage all your fans to please email Zenfolio and request they support geotagged photos. Maybe then they will get the “message”!

— comment by Bruce on May 22nd, 2009 at 12:54pm JST (9 years, 6 months ago) comment permalink

Feature request for SmugMug export: Would it be possible to only poll the categories that are user-created and omit the default SmugMug ones?

Thanks for all of your hard work!,
Robby

— comment by Robby on May 30th, 2009 at 12:42am JST (9 years, 6 months ago) comment permalink

Thanks so much for your great Zenfolio Lightroom plugin. I just installed the update and was very excited about the Twitter addition. Maybe I’m doing something wrong, but the URL that is posted to Twitter takes people to a login page, and not directly to the image or even to the gallery. For example, I just uploaded an image and this is the URL on Twitter:
http://www.zenfolio.com/sumsion/p215065366/home.aspx

Clicking that redirects a user to:
https://www.zenfolio.com/zf/login.aspx?login=NGh0dHA6Ly93d3cuemVuZm9saW8uY29tL3N1bXNpb24vcDIxNTA2NTM2Ni9ob21lLmFzcHgA

I think this new option will be a great addition, but it would be great if the user could click to get directly to the new image or the gallery.

Thanks!

Writing from Northern Utah, USA. 🙂

Good point… my bad. Just pushed a new version that should fix it. Thanks for catching that. —Jeffrey

— comment by sumsion on June 5th, 2009 at 5:48am JST (9 years, 5 months ago) comment permalink

Your plug-ins are great. Don’t have a problem with paying/donating. But –

1. I have downloaded 3 plug-ins. To activate them I have to make 3 donations. I discovered this late so I made a $15 donation and then had to go back and make a $1 donation and then another $1 donation. You’re a clever guy surely you can fix this.

2. But it gets worse. It appears that plug-ins are associated with catalogs. So I have to install the plug-ins in each and every catalog I use (currently 4). Now I need to make a new donation for each catalog?. I have 2 computers w/ lightroom so I’ve use up my 2 install per donation budget. And I have to keep track of which donation goes with what plug-in. Is this correct? Is this what you wanted?

Plugins are installed on the computer, not per catalog, but plugins that maintain per-photo data (as many do) store that per-photo data in the catalog, along with Lightroom’s other per-photo data. I don’t think LR should bother you with the “update this catalog for use with this Plugin” dialog, but it does, so you have to suffer pressing the button for each plugin for each catalog. But the plugin need be installed/registered only once per computer. As for #1 (one registration per plugin), it’s described pretty clearly on the registration page – if it’s not clear, let me know where my prose is lacking – and it’s also mentioned that those with special needs can contact m. Thanks for your kind gift. —Jeffrey

— comment by Tony on June 7th, 2009 at 1:53pm JST (9 years, 5 months ago) comment permalink

I got error message

“Error response from facebook:
Error uploading image: An unknown error occurred

Aborting export after 2 of 39 images successfully uploaded”

It also happened to my friend’s computer as well and it has been 4 days… Does it have anything to do with facebook increasing photo quota per album? Thank’s

I don’t know what causes it (it’s “unknown” 🙂 ), but it’s at FB and the plugin is just reporting that back to the user. I’m getting floooded with reports but there’s nothing I can do. —Jeffrey

— comment by Velwin Wibowo on June 10th, 2009 at 3:43am JST (9 years, 5 months ago) comment permalink

updated to 20090602.82 yesterday after registering

when uploading it thinks long and hard about doing it, and try’s but then I get:

“error response from facebook:
error uploading image: An unknown error occurred
aborting export after 0 of 40 images successfully uploaded”

Error at FB. —Jeffrey

— comment by harry butcher on June 10th, 2009 at 5:10am JST (9 years, 5 months ago) comment permalink

I just updated all of my plugins and am very excited about the Flickr to Twitter option. i attempted to authenticate, which requires me to login to twitter and then gives me a security code to enter into the plugin, but when I go back to the plugin and select ‘I have authenticated with Twitter’ (or something like that) it does not give me an option to enter the code from the Twitter page and tells me the authentication failed. Anyone else getting this?

— comment by Glenn Higgs on June 12th, 2009 at 4:41am JST (9 years, 5 months ago) comment permalink

From Tucson, Arizona, United States.

The issue that sumsion has is still present. We are testing the plugin on Mac OS 10.5.7 / intel duo core (latest updates as of June 16th, 2009) , Downloaded recent update as of June 16th, 2009 of plugin. Instead of going directly to the image gallery/ image on zenfolio we get the login screen every time. It seems not to save the user ‘s email and password preferences for zenfolio. What happens is after export safari opens up and goes to the users home page sometimes ( not logged in as user ) and sometimes it goes to the main zenfolio login page. So a little bit weird. All other things considered it is / looks like a life saver for the client I am consulting for.

I think you’re confusing the browser and the plugin. Whether you are logged in via one has no impact on the other… the plugin tells your browser to visit some url, but if that url requires login credentials that it doesn’t have, Zenfolio will prompt for them. —Jeffrey

— comment by laurence zankowski on June 17th, 2009 at 12:47pm JST (9 years, 5 months ago) comment permalink

Im using the Flickr plugin w/LR 2.3 and for some reason the files that are exported to Flickr are not being named correctly. There is no filename. I am choosing the out of the box Custom Name – Sequence option and on flickr nothing is entered.

Any thoughts?

I can’t imagine what might be wrong, and I can’t contact you because you didn’t leave your email. Try sending a log (with the “Send to Jeffrey” button in the upper-right section of the Plugin Manager) after experiencing the problem. —Jeffrey

— comment by josh on June 27th, 2009 at 2:14am JST (9 years, 5 months ago) comment permalink

When a tag has a non-standard character in it (e.g. “ë”), the tag appears twice in Flickr. Once correct and once the character is replaced with a question mark.
For example: in Lightroom I add the tag “tëst” to a picture. I export it with the “Export to Flickr” plugin. It appears once as “tëst” and once as “t?st”.

I am using version 20090514.98, but I couldn’t find in the release notes that it was updated in a newer version.

I’ve finally figured this out….. it’s a Mac-only bug in Lightroom. I’ve reported it to Adobe. I’ve just pushed a fix for the plugin to work around it. —Jeffrey

— comment by Van der Hoorn on June 29th, 2009 at 8:55pm JST (9 years, 5 months ago) comment permalink

I was using the plugin fine a few days ago but just yesterday I tried exporting some photos and I get two dialogs as soon as I select Export->Flickr.

1) “The upload-to-Flickr plugin has new group pool support. If you’ve made Flickr export presets that use group pools, please resave them.”

then

2) “Could not log in to Flickr. Internet connection down?”

After dismissing the second one, it just aborts the export process. The only thing that’s changed since my last successful export is that I registered the plugin and updated to the latest version, 20090630.115.

Thanks!
Marc

You apparently updated from a pretty old version, which is why the first note popped up. As for the second…. perhaps your internet connection was down? If you get it again, but you know it’s not down, send the plugin log (via the “Send to Jeffrey” button in the upper-right of the Plugin Manager) —Jeffrey

— comment by Marc Novakowski on July 2nd, 2009 at 1:21am JST (9 years, 4 months ago) comment permalink

I’ve used past version of your flickr plugin, and it worked great.

After a new computer, new Lightroom, and re-downloading the plugin, things no longer seem to work like they used to…I’m using Lightroom 2.0 481478, and I get the following error with the Flickr app:

“Error response from Flickr
Filetype was not recognised

Aborting export after X of 433 images successfully uploaded”
– where X is any number from 1 to 5

I’m guessing that the upload got cut off halfway through, and the resulting partial chunk of data didn’t make a complete photo, so Flickr reports that. If you could send a log after getting this error (via the “Send to Jeffrey” button in the Plugin Manager) I can see the exact form of the error message, and replace it with something along the lines of “Your Internet connection seems flakey”… —Jeffrey

— comment by Matt Conrad on July 2nd, 2009 at 8:23am JST (9 years, 4 months ago) comment permalink

Ok, there appears to be a problem with Flickr’s uploader too – so it might not be an error in the plugin

— comment by Matt Conrad on July 2nd, 2009 at 8:31am JST (9 years, 4 months ago) comment permalink

I also have been getting “Filetype was not recognised” and sent you the log file. Probably should have checked here first and would have seen Matt C’s message.

Love the plug-in, it’s part of the reason I chose Lightroom in the first place.
Chris
(from sunny Belmont, California)

— comment by Chris Dant on July 2nd, 2009 at 8:49am JST (9 years, 4 months ago) comment permalink

Seems to be OK now – must have been on Flickr’s end.

— comment by Chris Dant on July 2nd, 2009 at 11:21am JST (9 years, 4 months ago) comment permalink

Yep – going through fine for me. Glad to see this wonderful plugin is still working as promised! Great work!!

— comment by Matt Conrad on July 2nd, 2009 at 2:04pm JST (9 years, 4 months ago) comment permalink

As a followup to my previous problem with the “Could not log in to Flickr. Internet connection down?” prompt – yes I am connected to the Internet. Also, I just discovered that if I use Export->Export with Previous from LR, it works! However, since it’s just using all the settings from my last export I can’t go in and change anything.

From all accounts, it seems as if Flickr’s problems are intermittent, but somehow related to file size. In any case, they’re not specific to the plugin. —Jeffrey

— comment by Marc Novakowski on July 2nd, 2009 at 3:47pm JST (9 years, 4 months ago) comment permalink

I have tried to create a new album with the Facebook plugin, but any new albums I create are not showing up in the list of albums. I have quite a few albums, so I was wondering if there was some kind of limit. I can see the albums on facebook, but they still are not in the list.

It’s a bug on their side… they know about it, and even told me they fixed it last week, but it remains. They know about it, but I don’t know whether they intend to fix it. —Jeffrey

— comment by Josh on July 5th, 2009 at 11:13pm JST (9 years, 4 months ago) comment permalink

Hi Jeffrey –

The flickr plugin is great, but it seems to limit upload to flickr. I have a flickr pro account and registered the flickr export plugin, but when I upload a batch of photos, it stops at the 7th image or so and says that I have reached my photo limit.

I do not recall this being a problem in the past… is there a setting I am missing?

thanks

Derek

Sounds odd to me, but I’m not sure what “it” is (that is limiting you to seven uploads). Is it Flickr? Another plugin? Perhaps send a screenshot (by mail) or a plugin log (via the “Send to Jeffrey” button in the Plugin Manager)… —Jeffrey

— comment by Derek on July 13th, 2009 at 8:05am JST (9 years, 4 months ago) comment permalink

I love your LR to SmugMug plugin – smooth as silk. I was doing some filtering in LR and thought wouldn’t it be good to be able to collect everything I’ve put into SmugMug. Lo and behold, you have anticipated this with the “Uploaded to SmugMug” filter. That’s great, however it shows everything that has ever been uploaded including those shots that have since been removed from SmugMug. Is there any way of changing this so that the filter shows only those shots that are currently in SmugMug?
Regard
Bob from Oz

That would involve having to check each photo at SmugMug to see whether it’s still actually there, a fairly time-consuming task (at least if you have thousands of images). Still, it makes sense to allow it if you want, so I’ve added it to the todo list. —Jeffrey

— comment by Bob on July 20th, 2009 at 4:33pm JST (9 years, 4 months ago) comment permalink

From the UK.
The Twitter authentication number is now 7 digits, but your plug in is asking for a 6 digit number. Help!

Update your version of the plugin. I fixed that the same day Flickr made the sudden, unannounced, change. —Jeffrey

— comment by Alan Bennett on July 21st, 2009 at 7:29pm JST (9 years, 4 months ago) comment permalink

Was experiencing a problem with my new Asus Eee PC, where LR and the plugin were claiming “Lightroom can’t connect to the internet.” Turns out it was the Parental Control and Privoxy programs that came installed as default. Removing them fixed the problem.

— comment by Brandt on July 27th, 2009 at 9:48pm JST (9 years, 4 months ago) comment permalink

When uploading to facebook it seems like a rather aggressive sharpening is applied to the images even though I’ve un-hid the sharpening options and turned sharpening off. This doesn’t appear to be happening with the SmugMug plugin which I also use. It’s been happening for quite a few versions and I’m not sure if this is a known issue or not.

Thanks!

You might try setting the Image Location to a local folder (rather than a temporary folder that LR removes after the upload completes), then compare the local “as uploaded” files to how they end up on Facebook. I suspect that Facebook is applying the sharpening. —Jeffrey

— comment by Ryan on July 31st, 2009 at 9:32am JST (9 years, 4 months ago) comment permalink

I am missing a step on the install of this plug-in. I download/extract to the folder named. Then when I go to “add” the plug-in from LR2 I can’t seem to be able to drill down to that folder where it is located. I am on Windows Vista 64-bit and LR2. What am I missing?

I suppose it depends on where you’ve placed the folder after unzipping. The Plugin Manager apparently can’t see some hidden system folders, even if you use folder-options to make them visible to Explorer. Try placing the thing on the desktop, and if it works, you know it’s that kind of situation. Maybe make a MyPlugins in your MyDocuments folder? —Jeffrey

— comment by Myra Reneau on July 31st, 2009 at 11:55am JST (9 years, 4 months ago) comment permalink

-Myra

This is a Vista issue where, as Jeffrey says, certain “Browse for Folder” dialogs won’t see System folders regardless of what your Hidden/Visible settings are for them. For all plugins that I use, I manually install the first time by dropping the plugin into the Modules folder via Windows Explorer (they all go into C:\Users\Jason\AppData\Roaming\Adobe\Lightroom\Modules which I browse to myself). After a Lightroom restart, they all appear in the Plugin Manager and in the case of Jeffrey’s, will also update through there. The only downside is that if you want to actually remove a plugin completely, the “Remove” button in the manager is grayed out. Not really a big deal for me since I know the path to the folder so I can do it myself.

If you want to use the Add/Remove buttons in the Plugin Manager, you’ll need to put them all into a folder that’s not part of the system (which is the only reason to move them outside of the Adobe\Lightroom hierarchy).

— comment by JasonP on August 2nd, 2009 at 12:59am JST (9 years, 3 months ago) comment permalink

[Feature request]

Jeffrey, firstly, let me say great job!!!!

I am sure you are one of those who are aware of the “don’t touch that mouse” paradigm. I try to do anything I can with the keyboard. As a heavy keyboard user I tent to use the CTRL+ to delete an entire word. Have you considered adding this feature to the LR Export to Flickr plug in? It would be highly appreciated.

Plugins have very limited interaction with the Lightroom UI at that level, so there’s probably nothing I can do, but I’m not quite sure where you mean. Do you mean in input boxes like “extra keywords”? If so, nothing I can do, other than to suggest a general request to Adobe… —Jeffrey

— comment by udi on August 2nd, 2009 at 2:27am JST (9 years, 3 months ago) comment permalink

HTML in the ‘Caption’ metadata is being escaped. How can I turn this off so I can embed HTML as I have in this photo?
http://www.flickr.com/photos/kptyson/3780973486/

From your example it looks like you figured it out: set the radio button from Text to HTML. —Jeffrey

— comment by kptyson on August 2nd, 2009 at 11:08pm JST (9 years, 3 months ago) comment permalink

From San Francisco area, thanks for the Flickr and Zumfolio plugins.

I would like to see the Metadata fields Uploaded to Flickr and Uploaded to Zumfolio changed to be searchable. That way I know which photos I’ve already uploaded by doing a “Any searchable plugin field” type search in LR.

Thanks.

You can use those fields in the Library Grid filter, and in Smart Collections… is there an organizational need that doesn’t fill? —Jeffrey

— comment by Frank on August 5th, 2009 at 2:44am JST (9 years, 3 months ago) comment permalink

Jeffery, when I went to look for those fields in the Library Filters, I looked under under Text>Searchable metadata and Text>Any Searchable field and didn’t find them.

Thanks for letting me know they are under Metadata instead. It’s just what I needed!

— comment by Frank on August 5th, 2009 at 12:36pm JST (9 years, 3 months ago) comment permalink

Hi Jeffrey!

First of all, thank you for your wonderful plug-ins! I have been using both the SmugMug & flickr plug-in’s for quite some time. I just recently upgraded the flickr plug-in to the latest version on my iMac running the latest version of the operating system (OSX 10.5.8). When I try to authenticate my Twitter account nothing happens. Well, I do get the Twitter authentication window to pop up in Lightroom, but the Twitter authentication page is blank. Not sure what the problem is, and I am wondering if you had heard of this issue before.

Thanks,

Noel
Los Angeles, CA

Sounds like Twitter might have been having issues…. give it some time, and try again. If it continues to fail, send a plugin log (via the “Send to Jeffrey” button in the upper-right section of the Plugin Manager). —Jeffrey

— comment by Noel on August 16th, 2009 at 8:24pm JST (9 years, 3 months ago) comment permalink

Jeffrey
Thanks for the great Geocoding plugin. Writing from South Africa and am using Qstarq Q1000x data logger. We are getting ready for a trip to Peru! Am using your pluin, because the Qstarq software do not support the Raw format for geocoding photo’s.

One issue: The data logger I use store up to 200 000 waypoints and when I use your plugin to view the track log on Google Earth I get a message “Insufficient memory” . I did manage to view the traclog on Google Earth by by passing your plugin – would be nice if you get get around the waypoint limitation.

All the best

HenriS

— comment by HenriS on August 17th, 2009 at 4:56am JST (9 years, 3 months ago) comment permalink

Jeffrey… I’m using the Smugmug export plug-in for Lightroom 2 on a Mac. I tried using it to upload photos to my Power account yesterday and today. It renders and begins to upload the first image; however, after about 2 minutes of nothing happening, a dialog box pops up that says a Timeout occured (or some such) and I can’t cancel it; it just freezes and I have to force quit. My internet connection is working fine and I can access Smugmug and my Smugmug-based web site just fine.

They’ve been having sporadic hard-to-track-down issues lately. Another commenter says that they seem to be fixed… let’s cross our fingers… —Jeffrey

— comment by Berger on August 18th, 2009 at 9:14am JST (9 years, 3 months ago) comment permalink

Hi Jeffrey,

First of all thanks for these fantastic additions to lightroom. Secondly, thanks again 🙂

.. Thirdly, I wanted to ask you whether there are any plans for or whether you would consider incorporating watermark support into any of your export plugins.

Sure, LR2/Mogrify can watermark, but having to export a folder then re-import or manually upload to flickr etc. is inelegant (not to mention that I believe you lose all LR2 keywords, captions, title etc.)

While I’m here, I thought I would also mention that I cannot find any way to add a line break in the facebook export plugin’s caption template. If I insert a line-break myself, it does not carry over to Facebook – however if I log into facebook and manually chuck in the break myself, it works fine.

Thanks (again!) and enjoy your holiday!
Jeremy

The LR2/Mogrify plugin works in tandem with my uploads plugins (or any other export plugin), so it’s all seamless from a user’s perspective… it’s exactly what you’re asking for. I’ll look into the FB LB issue… —Jeffrey

— comment by Jeremy on August 19th, 2009 at 1:21am JST (9 years, 3 months ago) comment permalink

Jeffrey,
Thanks for the quick response, looks like i dropped some text while rushing to make a comment.
yep, I mean being able to use ctrl+backspace to delete an entire keyword from the “extra keywords” box for example.
If it’s an adobe thing, I guess we’ll just have to wait till adobe make it right.
thanks

— comment by udi on August 24th, 2009 at 5:54pm JST (9 years, 3 months ago) comment permalink

Just found Metadatawrangler. Downloaded it successfully but it will not work. File exports from Lightroom 2 but it tells me error running metadata removal command.
Log.txt file says ” Can’t open perl script “C:\Documents and Settings\Administrator\My Documents\My Pictures\Lightroom\Plugins\metadatawrangler-jfriedl.lrplugin\doit”: No such file or directory”.

I operate on XP64.

Thank you

Does the mentioned file exist? If not, you’ll have to download and unzip again…. —Jeffrey

— comment by James on August 27th, 2009 at 3:53am JST (9 years, 3 months ago) comment permalink

Hello Jeffrey,
I’ve been using the export to Zenfolio for LR2 which has been working great!…. however, I recently tried using the Twitter notification and have not had any success. When I click on “Authenticate at Twitter” I’m taken to Twitter where I click on the button to allow access to the plug-in and then receive a pin #. When I return to LR I am unable to do anything… every where I click I hear “the bad sound” and end up having to force quit LR. I’ve tried this several times over several different days with the same result. I’m using a Mac with OS X 10.5.8. What am I doing wrong?
Thanks!

Sounds like the LR dialog (generated by the plugin, for entering the PIN) is getting hidden behind LR proper. Try hiding the app, then unhiding, or other things to look around for the dialog… it’s there, somewhere…. —Jeffrey

— comment by Bill on August 27th, 2009 at 2:10pm JST (9 years, 3 months ago) comment permalink

Great Plugin!! My issue is when uploading to Smumug… As I started to upload 55 images, It started processing each image and putting them in a folder and then said it was uploading 1st image… then there was a timeout from Smugmug and a dialog for me to cancel the upload.. Lightroom continues processing all 55 images.. The problem is when I go to upload again, there is no choice to just upload remaining images without reprocessing them all again.. Am I missing something? thanks for your time..:)

No, you’re not missing anything… the plugin is not as graceful as it could be in the face of errors. SmugMug had a lot of intermittent upload problems over the past two months, but they think they got them fixed a couple of days ago, so I’m distressed to hear about your timeouts. Were the copies you uploaded not sRGB by any chance? —Jeffrey

— comment by Stewart Volland on September 1st, 2009 at 12:20pm JST (9 years, 2 months ago) comment permalink

This is a great plug in and I will be registering shortly. I saw the update on the known issues on Aug 24th that smug mug is having problems but I continue to get the “wrong format” error. It seems to be on pictures that are >12 MB and I have the item checked to automatically reformat to smaller. It seems to hang and then get that error intermittently. It sometimes works and sometimes does not. I was wondering if you have any update from smugmug on that error. Thanks for your time and the plugin it will save me a lot of time!

— comment by Jason Ewing on September 4th, 2009 at 4:54am JST (9 years, 2 months ago) comment permalink

Hi Jeff,

As of today I’m still getting the “wrong format” error from Smugmug when uploading. I’m working with CR2 files in Lightroom then exporting them through the plugin into jpegs and into Smugmug. I have the “Upload Anyway” option checked for images over 12MB but I still get the error. I know this isn’t news I just wanted to make you aware that SmugMug is still having problems as of today.

P.S. I’m writing from Hillsboro, OR and I love this plugin. My business website is integrated with SmugMug and I do almost all my work with Lightroom so this is such a great way to streamline my workflow. I was more than happy to donate.

— comment by Justin on September 17th, 2009 at 2:38am JST (9 years, 2 months ago) comment permalink

since I migrated to Sony A900 with compressed Raw of 24Mb and full Raw of 36MB, the flickr export plugin is crashing out of memory 60% of the time (works fine on some photo until 24.3 MB but crash on some others 24.5MB and above)
I get errors messages in 2 pop up box:
1 not enought memory
2 an internal error has occured : not enough memory

plugin version 20090916-125
LR 2.5
Intel core 2 duo,
3GB RAM , 1.7 GB used in system monitoring, plenty of memory free during export
lightroom using 667644KB of memory
CPU used vary between 60-80% , global CPU go up to 100% during export
Vista home premium

This sounds like a LR problem that the plugin is merely reporting. What happens when you export only to disk? If that’s okay, the problem is probably with Lightroom’s networking…. try exporting one file and after it fails, send me the plugin log (via the “Send to Jeffrey” button in the plugin manager)…. —Jeffrey

— comment by marc-104 on October 3rd, 2009 at 2:56am JST (9 years, 1 month ago) comment permalink

Jeffrey,

Been using your Zenfolio plug-in for over a year now, and it’s great.

I’d like to put in a feature request. In addition to a title and caption, galleries and photos can also have categories. It would be great if I could specify these on export.

Thanks.

Oh, cool, I must have missed that. Will check it out, thanks! —Jeffrey

— comment by Silverhalide on October 4th, 2009 at 12:27pm JST (9 years, 1 month ago) comment permalink

Hi Jeffrey,
How do I stop the plugin automatically adding the city, state, country, country code meta data into the flickr tags automatically? I can’t figure out how to turn that off.

That’s not the plugin, that’s Flickr. I, too, find it highly annoying. To stop Flickr from doing it, you have to strip those field from the image metadata before sending it (perhaps with my Metadata Wrangler plugin). —Jeffrey

— comment by Syd Low on October 11th, 2009 at 2:05pm JST (9 years, 1 month ago) comment permalink

I’m running Lightroom 2.0 on a Mac and am having an issue with the Facebook plugin. when i try to enter a “new album name” in the export dialog, an error comes up at the bottom, saying “unable to export: Entering new album name.” Am I only able to export it into existing facebook albums?

You need to commit the new album creation right there in the dialog… it’ll then become the selected album for export, and you can continue along your way… —Jeffrey

— comment by Melissa on October 15th, 2009 at 9:12pm JST (9 years, 1 month ago) comment permalink

Not sure why or if it is true, but I see a warning saying “are you sure you want to upload non-sRGB photos…” although I do have sRGB selected as my export format.

Hmmm, could you send more details (perhaps a screenshot) via email, including which plugin you’re using? —Jeffrey

— comment by eric on October 16th, 2009 at 4:58am JST (9 years ago) comment permalink

Hi, i’ve just tried the LR to Facebook plugin… i find it very usefull but something bothers me, there is no way to select a color profile when exporting. I shoot Adobe RGB 1998 and when i send pictures to the web with this profile, they appear washed out… i would like to be able to choose the profile before uploading the pictures (to Facebook or Flickr) just like the standart LR export plugin does… (or maybe i’m missing something…) Thanks.

The plugin forces sRGB for the export to Facebook. No other choice makes any sense for Facebook, so I just have the plugin do it and I removed the selector to simplify the dialog. —Jeffrey

— comment by Colin on October 21st, 2009 at 8:27am JST (9 years ago) comment permalink

Thanks for your answer Jeffrey, because some browsers discard the embedded profiles (even the sRGB one), i’m using a special compensated profile in order to display properly my pictures under any environment… do you think there will be a hope of seeing this profile selection option shown in some future versions of your plugins ? Thanks.

What you’re saying (“compensated profile to display properly under any environment”) is not possible. That you write it suggests that you’re doing the opposite, ensuring improper display under any environment. You may find my digital-image color spaces writeup informative. —Jeffery

— comment by Colin on October 22nd, 2009 at 7:52am JST (9 years ago) comment permalink

I must have explained myself badly, what i meant is the conversion to this profile compensates the picture so that the display of it is the same with or without profile interpretation… something like that, i really don’t know how to put it in english though…

You explained yourself perfectly (and your English is much better than my Spanish, that’s for sure!), but what you are explaining indicates that you do not understand digital-image color spaces and color profiles. I can tell that you think you do, but you do not. Sorry to be blunt, but what you’re writing here is complete nonsense.

The point is, do you think you will enable the profile select option on the future versions of your plugins (something maybe only shown in the advanced options). Thanks.

No, I don’t plan to add it. It could only cause problems (even if the user thinks it’s helping, it would hurt). —Jeffrey

— comment by Colin on October 22nd, 2009 at 9:19am JST (9 years ago) comment permalink

Colin – You need to make your images look good for Flickr on web use independent of this plugin, and making them look good on Flickr etc means sRGB, so you’ll need to tweak your images in LR before you export, with this plugin or manually.

Flickr and FB are a bit different cases because Flickr respects and preserves embedded color profiles; Facebook does not. But really, that doesn’t matter that much because there are still a lot of browsers that don’t respect anything (can anyone spell “IE”?), so sRGB color data remains the best shot-in-the-dark guess (which is why the FB plugin forces sRGB, and the Flickr plugin warns loudly if you choose something else). —Jeffrey

— comment by Syd on October 22nd, 2009 at 11:42am JST (9 years ago) comment permalink

Guys you’re way off… i can tell you that it took me some time to developp this profile and that it really works. I remind you that some browsers (like IE6, Fireffox 2 and 3) discard totally the sRGB profile, which means that on the screen the picture will look like just exactly if you untick the embed profile in the Photoshop’s save to web option : completely washed out.
Now Syd if you compensate this on lightroom prior to exporting and still embed the sRGB profile… your picture may look good on certain browsers (the ones that discard the profiles) but it will look over saturated on Safari (which interprets the profiles right).
Jeffrey what i say can be a total nonsense to you, but i know that my trick works for having tested it on many computers, screens, systems and browsers since showing my pictures right everywhere was one of my early preocupations when i started this job of photographer, and i can assure you that the sRGB method is NOT working on all the browsers that doesnt handle color management, and there is no other way to do so !
And by the way, loading pictures into a SWF file (still !) does the same thing, even when you load the SWF in Safari.
I’ve read the page you sent me with all pictures with and without the embedded profiles ? But which solution do you bring ?… Discarted sRGB display is not close enough for me… so once again, it may looks wrong, but believe it, it really works.

If you’re happy with your results, well, that’s all that matters, but there is simply no way you can make unprofiled data look good on everyone’s system unless you can ensure that everyone’s system is the same (same settings on the same monitor with the same graphics card). If wishing it so would make it true then you and I together would have gotten it done years ago, but geez, if one employee in a TV store can’t get the big display of screens to have even remotely similar displays of the same show, how do you expect the billions of people on the other side of the Internet to have the same settings that you happen to be testing with? Of course, maybe you’re doing the same thing that some TV stores do, which is punch up the saturation and colors and brightness to grab the viewer’s attention, even though it’s at the expense of realistic colors. It’s a very effective technique with TVs, but if you want your photos to have that kind of punch, I’d think you’d ramp up the settings in Lightroom where you have a chance of judging the results on a case-by-case basis. Using a color profile for that is like using a shotgun to perform brain surgery….. while blindfolded. —Jeffrey

— comment by Colin on October 22nd, 2009 at 3:57pm JST (9 years ago) comment permalink

Well of course i’m not gonna say i’ve tested this on all the computers and screens of the planet, and of course my solution is not perfect… i know that on some old CTR it doenst work quite as well, but however on recent quality monitors it was close enough to what i wanted, and the most important of all… MUCH closer to the actual look of my Adobe RGB 1998 picutres than showing a converted to sRGB picture on a non color managed browser (firefox 2, 3, IE6…), which will definitly look dull and washed out.
Since you don’t seem to have a better solution i will stick with mine which kept me happy enough on all the situations i’ve tested (PCs, macs, CTR, TFT, LED screens at home, friends, clients, etc.).
Now brain surgery with a shotgun ? Come on… that doesnt make any sense… letting show a sRGB picture on some place when you know the profile will be ignored, that looks more like brain surgery with a shotgun to me !
Anyway the reason of me coming here was not to enter in an endless discussion about color management, it was to check out a functionnality that i need and your plugins don’t and won’t, so i think i’ll pass. Thanks anyway.

— comment by Colin on October 22nd, 2009 at 9:24pm JST (9 years ago) comment permalink

Hi Jeffery,

Great plug-in! I use it to export to smug mug. Can you explain why the color space is shown as “unknown” in Smug Mug info? Thanks.

Sounds like they’re not recognizing the embedded color profile, at least for the purposes of that message. There’s an Exif metadata notation about the color space, but Lightroom doesn’t include it, and it doesn’t matter because Lightroom includes a full color profile. The “unknown” must be referring to the Exif metadata notation. —Jeffrey

— comment by Doug on October 29th, 2009 at 11:14am JST (9 years ago) comment permalink

Thanks for the quick response. I thought it might be something like that. Exporting from PS CS doesn’t have the same problem so I would assume it writes to the exif.

— comment by Doug on October 29th, 2009 at 11:56am JST (9 years ago) comment permalink

Hi Jeffrey! Thank you so much for this wonderfl plugin – I have been using it extensively!

I don’t know if this has been an issue in the past versions, because I haven’t try this before.
When I am exporting to DNG and strip all the metadata from it, the lens information and the serial number of the camera from the camera exif remain. If I export with exactly the same options, but to JPEG, all the metadata are striped. It would be great if you could make it possible to strip all the metadata also from DNG files, especially the camera exif.

I think it also would be useful to split the entire Data block (IPTC) into seperate otions – as it would be useful to strip only e.g. the keywords or the location from the files.

Thank you again very much for this wonderful tool, and I wish you happy travels if you are still travelling!

Hadn’t heard about the DNG issue… I’ll test it, thanks. About breaking out the IPTC stuff, that’d be cool but there are lots of things above it on the todo list. (Since you’re the first to ask for it, at least now it’s on the todo list 🙂 ) —Jeffrey

— comment by pavla on October 29th, 2009 at 9:12pm JST (9 years ago) comment permalink

** Hello Jeffery, i hope you don’t mind me posting this response, please drop me an email if there is any issues.

Hi Colin,

I know there has been a large amount of discussion around this already however i thought i would just make a few comments that may assist with your profile issues.

I have been studying Colour Management for quite a while now and am still not an expert by any means, however my reason for the research was due to the fact that i had exactly the same issue that you are experiencing where i would see my images on a website and they would look nothing like they did on my fully calibrated wide-gamut monitor and i couldn’t figure out why.

As noted by Jeffery, sRGB is the best profile to use for image display on the internet as this is exactly what the sRGB ICC profile was created for (originally proposed by HP and Microsoft) a good article on where sRGB came from can be found here: http://www.w3.org/Graphics/Color/sRGB.html

I just wanted to highlight a few key points that may save you from a lot of profile heartache in the future:

– Firstly, as you have already done, Adobe 1998 should be the base profile for shooting and post production, however you will require a different workflow for web then you will for print (eg; you will end up with different final profiles for each purpose). Unfortunately by creating a “custom” profile that attempts to mimic Adobe98 you will only cause major issues when it comes time to print and its highly likely that your printed image will end up very different to the onscreen version as most professional print labs will reject your ICC profile during production.

– When you are exporting an image to the web with a defined ICC profile (regardless of what it is) that will then become the embedded ICC profile for that image and the original profile is discarded for example; if you export an image shot in adobe98 to the web with an sRGB profile (or even your custom one) then a colour managed browser or device will now use that profile to display the image.

– sRGB was created to be the “preferred” colour management profile for the internet in attempt to provide some continuity across the millions of different viewing scenarios that may occur, hence the fact that Microsoft made sRGB the default profile for Windows OS.

– Its best not to send images to the internet in Adobe 1998 profile (unless you know that the people viewing the image can display it) this is because a lot of browsers have issues with this profile and the majority of end-user’s monitors cant even get close to displaying this profile correctly not to mention the fact that the majority aren’t calibrated either.

– A non-color managed browser is exactly that “a non color managed browser” meaning it doesn’t matter if you use your custom profile, sRGB or Adobe98, the fact is that the browser isn’t reading the embedded ICC profile and is displaying the image using its own default profile therefore the image will look exactly the same even if you don’t embed a profile at all, so by applying your profile you are making very little to no difference at all (test this by uploading 3 versions of the same image each with a different profile and then view them in IE6 on a non-calibrated monitor). The following site also gives some very helpful examples and explanations: http://www.gballard.net/psd/go_live_page_profile/embeddedJPEGprofiles.html

If you are finding that your images are coming out looking dull and washed out when exporting from LR, then you could also modify your web workflow so that the first step you take is to create a “virtual web-copy” of the image in LR and then update the profile to sRGB before you do any post production (this can be done in the Develop module -> Camera Calibration).

Some good Adobe resources that may also assist:

A Color Managed Raw Workflow – http://www.adobe.com/digitalimag/pdfs/phscs2ip_colormgraw.pdf
The Role of Working Spaces in Adobe Applications – http://www.adobe.com/digitalimag/pdfs/phscs2ip_colspace.pdf
Calibrating the Digital Darkroom Environment – http://www.adobe.com/digitalimag/pdfs/calibrating_digital_darkroom.pdf

I hope this is of some help 😉

Cheers

Z

— comment by Zappa on November 1st, 2009 at 2:31pm JST (9 years ago) comment permalink

I don’t know if this is a bug or not, but it seems that if you have two flickr accounts you can enter the saved credentials for each but you cannot save a preset export with each account. It says that you are “logged in as XXXX” but under that it lists the account you were last authenticated with, and it will always post to the previous authenticated account.

You must click logout, then pull down and choose the account you want, and then reexport. A tad annoying but at least I figured out what was up.

Hmmm, that’s unexpected. I’ll check it out. —Jeffrey

— comment by John on November 5th, 2009 at 2:20am JST (9 years ago) comment permalink

I think you can cross ‘create gps plugin’ off now 🙂
Perhaps going a bit far, but following Picasa/iPhoto/Flickr/Facebook face recognition would be awesome. Native support in LR would be great for auto-tagging etc (or even remove a number of ‘people’ tags) and cataloging people in photos – the ‘social web’ and all that is more important than ever, and I know LR is mainly a photog’s developing and cataloging tool (DAM) but this would rock. Currently I do this in Picasa 3.5 Win but cannot figure out how to import these tagged photos (I guess they’re stored in picasa.ini files in the photos’ folders, not the actual photos themselves) but perhaps this info could be pulled in somehow?

Thanks for the awesome work, really looking forward to LR3 to leaave beta and to get everything setup perfectly again (I’ve so many presets flying around I’m in a mess!)

— comment by David on November 7th, 2009 at 11:41pm JST (9 years ago) comment permalink

Konnichiwa,

I have recently started using Lightroom, and was delighted to find your Flickr Export plugin for Lightroom. I had a flickr photo set of images for printing MOO cards that I had prepared with Photoshop CS3 previously, but I updated it with some images exported directly from Lightroom.

I was surprised when the MOO cards arrive today to find that all the images that I had exported to Flickr from your Lightroom export plugin printed very darkly.

I thought I understood color space management, but just went ahead and re-read your artice about color space issues.

I have double checked the settings in your Export plugin to make sure that the image is being exported in the sRGB colorspace but in looking at the EXIF data from my Lightroom exported photos, I notice that I never see sRGB explicitly stated.

Clicking on your CGI based EXIF color tool link does show that there is supposed to be an embedded sRGB color profile, but I don’t see how it is being communicated.

example.

Have you heard of any issues when anyone has sent images exported using your plugin to MOO for print? It would seem to me that the images are still using the AdobeRGB color space profile that the camera had set, but I thought that the Lightroom Export plugin would override that setting.

Any help would be appreciated.

The example you cited indeed has an embedded color profile, so if that is representative of the shots you sent to MOO, the problem is at MOO (either that they don’t respect the color profile in the image, or that they don’t convert properly to a profile for the printer/ink/paper combination they’re using). I don’t know MOO specifically, but I’m often shocked at how ignorant professional print labs are about color spaces. I once asked a print shop what color space they preferred images in, and the guy had no clue what I was talking about. Once when preparing a book for Blurb, it was almost impossible to get a straightforward answer from them about how their process and printer dealt with what kinds of color spaces, and it took asking the same question over in slightly different ways before I could elicit the information I needed. —Jeffrey

— comment by Joshin Yamada on November 8th, 2009 at 8:13am JST (9 years ago) comment permalink

I just downloaded the LR/Smugmug export plug-in, and when I try to export to smugmug, I keep getting the same error: “error response from SmugMug wrong format ()”
I’m not sure what I’m doing wrong, and I am not seeing other comments reporting the issue, although I’m sure I could be missing it. If you have already addressed this on your blog, could you please direct me to the right place? That would be greatly appreciated!

“wrong format” problems have invariably been bugs at SmugMug… please contact your local SmugMug Support Hero…. —Jeffrey

— comment by Abbie on November 14th, 2009 at 3:43am JST (9 years ago) comment permalink

Jeffrey,
I am trying to upload to smugmug with the plugin and I am getting this: Unable to Export an internal error has occurred ?: 18304: invalid capture index
any ideas? thanks for your help
Alex from Salt Lake City, Utah

Sorry about that… just pushed a fix. —Jeffrey

— comment by Alex Gallivan on November 26th, 2009 at 2:05am JST (9 years ago) comment permalink

Just noticed that the “Don’t Export” flag on keywords is being ignored on export to Flickr plugin.

Running 20091125.134 but had the problem on an image uploaded on 20091123.

The plugin honors what Lightroom tells it, but there was a bug in LR2.0 with catalogs brought over from LR1.x that caused it to get confused about keyword exportability, so I’m guessing that’s what you’re running in to. Check Adobe’s site for a script you can run to fix your catalog… —Jeffrey

— comment by Rob Smith from Wishaw, Scotland on November 26th, 2009 at 7:36pm JST (9 years ago) comment permalink

Awesome plugin for Lightroom to Flickr exporting. I use it alot or at least I did until I started getting this error. It says “Invalid API Key” and I can’t export to Flickr anymore. Everything seems to be in order on Flickr as well as in Lightroom. I have not made any changes to my hardware or software nor any patching or anything like that. I’m using Lightroom 2 by the way. Any help would be greatly appreciated as I don’t know where to begin troubleshooting this issue.

My plugin’s key is still valid, so perhaps Flickr was having temporary issues. Just tested it and it’s fine at the moment. If you get again, please send a log via the “Send to Jeffrey” button in the Plugin Manager. —Jeffrey

— comment by Samuel on December 8th, 2009 at 12:30am JST (8 years, 11 months ago) comment permalink

Hi Jeffrey,

thanks for all the effort you put into this.

I’m currently trying to get the Facebook plugin to work, but always get stuck at a certain point:

* I set up the connection – very straightforward, no errors
* I create an album within LR
* I publish – again very straightforward, works like a charm
* I make alterations to an image in the album, which marks the image for re-publishing
* I hit the Publish-button and get following error message:

An internal error has occurred: ?:8625: internal error: image_still_exists not defined

Since I could not find any posts describing similar behavior, I’m pretty sure, that I’m doing something wrong here …

My specs:

LR3b
Mac OS X 10.5.8

Sounds like you’re not doing anything wrong…. just the first person to actually try this. LR3b is pretty rough WRT plugins, so I haven’t even tested much yet. Just pushed a fix (v100), though please realize that due to Facebook limitations, the plugin can only send a second (or third, or fourth….) copy of the photo… if you want to replace a photo, you have to manually delete the older version(s). —Jeffrey

— comment by Markus Mayer-Roth on December 12th, 2009 at 8:05am JST (8 years, 11 months ago) comment permalink

Photos uploaded to SmugMug don’t have keywords.

Check that you’re not stripping them via the “minimize exported metadata” option, and if your catalog originated in LR1, there was a bug in how LR2.0 upgraded catalogs that requires you to run a fix… search around on Adobe’s site and you’ll find it. —Jeffrey

— comment by Rutger Blom on December 17th, 2009 at 5:34am JST (8 years, 11 months ago) comment permalink

It keeps coming back telling me that flickr cannot accept “.TIF” files for uploading but I do it all the time.
Is there something I am missing or should be doing?

I suppose it matters what plugin “it” is, but it wouldn’t surprise me if you have the format set to “ORIGINAL”. Try “JPEG”. —Jeffrey

— comment by R. Mac Dunlap on December 21st, 2009 at 3:23am JST (8 years, 11 months ago) comment permalink

Yea I should have specified.
I am using the Flickr upload plugin.

Why would original make a difference when if I can upload them by their website or their seperate standalone app?

I don’t like JPG format because the artificts inherent in them.

Flickr indeed accepts tiffs, and my plugin should allow you to upload them. I just tried and got an error as well, so it’s a bug on my side. Thanks for the heads up. WIll check it out…. —Jeffrey

Just pushed a fix. Thanks again. —Jeffrey

— comment by R. Mac Dunlap on December 21st, 2009 at 7:36am JST (8 years, 11 months ago) comment permalink

First of all: this is a very useful piece of software. Thousand thanks to you, Jeffrey.

I have a similar keyword exporting issue like Fabian described it on October 31st, 2008. Do you have any updated information on how this problem exactly occurs. I could not figure out the count of maximum keywords which are processed – but they are more than 26 in my environment: Lightroom 2.6 (632083) with Flickr Export Plugin Version 20091223.143 on Mac OS X 10.6.

I think I figured a workaround for this… just pushed v144. It also works for resending tags (via the “Plugin Extras > Flickr Extras” dialog), so if you have images with lots of tags, resend after upgrading and they’ll be there. I think. —Jeffrey

— comment by Alex on December 29th, 2009 at 7:25am JST (8 years, 11 months ago) comment permalink

Phantastic, it works now (v144) with my massively keyworded images! 🙂 Thanks a lot.

— comment by Alex on December 29th, 2009 at 6:58pm JST (8 years, 11 months ago) comment permalink

Hi Jeffrey,

I’ve just noticed something funny going on. When I use your plugin to upload to Flickr with the sRGB colorspace it seems to miss this out from the metadata. Here’s an example:
http://www.flickr.com/photos/jonblock/4224936819/meta/

It isn’t a problem on Flickr as the colour still seems to be rendered correctly, but when my wife downloads the photos and uploads them to Facebook the colour is flat, as if Facebook is unable to correctly render the colorspace.

This is not an issue if I export to a JPEG and then upload.

I am using Mac OS 10.5.8, Lightroom 2.6 and I’ve just updated your plugin to check if it is a known problem that has been fixed.

BTW Keep up the good work! 🙂

Jon

The known problem is that Facebook doesn’t handle colors properly, as of a few weeks ago, in some situations. There’s a lot of discussion in the comments on my Facebook plugin page. —Jeffrey

— comment by Jon Block on December 30th, 2009 at 9:04pm JST (8 years, 11 months ago) comment permalink

Hello Jeffrey,
I noticed that recently (i.e. Dec) when I upload pic to Picasa using the plug-in, the Photo Information displays the upload date instead of the Date the Photo was taken.
If the photo is downloaded from Picasa Web — the file has the correct date taken listed in the EXIF.

Thanks for your work – I enjoy using your plug-ins.

Maria

Various dates are associated with the photo at PicasaWeb… are you saying that the “Date Taken” is the date of the upload? Be sure you don’t have “minimize metadata” option selected (in the “Metadata” section of the export dialog)… if you have that turned on, no dates are sent to Google, so they may be substituting the upload date. —Jeffrey

— comment by Maria on January 1st, 2010 at 5:40am JST (8 years, 10 months ago) comment permalink

Hello Jeffrey,
Thanks for the reply.

I do not have the “minimize metadata” option selected. I checked that first. All the metadata is being sent to Google just fine because if the photo is downloaded all the data is there. I found that uploading from PicasaWeb using FireFox causes the same problem however, if I use Internet Explorer the date displays correctly. I found other people have posted similar issue on PicasaWeb Help so the ‘issue’ might be a PicasaWeb issue not a plug-in issue.

here is one:
http://www.google.com/support/forum/p/Picasa/thread?tid=6dc0129a5f201385&hl=en

Thanks again for your work.
Maria

— comment by Maria on January 3rd, 2010 at 12:53am JST (8 years, 10 months ago) comment permalink

Hi Jeffrey,

Thanks for creating the laundry list of export (and other) plugins! Are you planning on creating an export plugin for Fotki.com? Not sure if you have received requests from other users before … if not, I’m happy to be the first.

Thanks again,
Greg

They don’t seem to have a public API. —Jeffrey

— comment by Greg on January 3rd, 2010 at 2:55pm JST (8 years, 10 months ago) comment permalink

First off thanks for the plugins, LR to Flickr is great. However I am having an issue with upload speeds never getting above 40kbps via the plugin, whereas via the web or Flickr uploadr it is consistently around 200kbps on the same connection. So uploads take 3-4x longer via the plugin. 🙁 The (qualitative) speed comparison is based on a comparison of upload time for the same set of files, and the outgoing network traffic in Activity Monitor, with nothing else using network afaict. My router has QoS enabled but I tested with no other active traffic (or machines) on my home network. I am running Mac OS 10.5.8, Lightroom 2.6. I had a look in the prefs to see if there was a cap for upload bandwidth but didn’t find one. Any ideas what else I can check?

Ben – Albuquerque, New Mexico

I have noticed this from time to time (though not quite as drastically as this), and have not been able to figure it out. It may be that the Flickr uploader uses a different endpoint at Flickr than they offer for third-party apps like mine. The plugin just uses Lightroom, and Lightroom just uses the OS network services. I, too, don’t know where to check next. )-: —Jeffrey

— comment by Ben on January 4th, 2010 at 2:17am JST (8 years, 10 months ago) comment permalink

I have noticed the Picasa export plugin has started using the wrong aperture value – in Picasa on the web, the minimum lens aperture is shown, not the actual aperture used. This appears to have started happening around the beginning of December 2009. To be fair, I don’t know whether this is a Picasa, Lightroom or Plugin problem, but I’d appreciate it if you could take a look.

Thanks

Andy

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

— comment by Andy Elliott on January 4th, 2010 at 11:10pm JST (8 years, 10 months ago) comment permalink

Jeffrey

First things, Google seem to have fixed the aperture bug, but haven’t made this public – probably coz they don’t want to have to tell people to re-upload their images to fix images uploaded during the approximately 4 weeks the bug existed!

This one might be the plugin, though… The aperture value is showing things like 5.600001 and the like – so rounding looks like an issue here. v20100130.110.

Thanks again,

Andy

— comment by Andy Elliott on January 26th, 2010 at 6:08am JST (8 years, 10 months ago) comment permalink

This may not be a Smugmug plugin issue, today I wanted to upload a new gallery to a subcategory but the plugin only showed the list of main galleries and no subcategories. I upgraded to your latest version but the same problem persisted. It maybe a Smugmug issue not plugin but I thought I’d let you know.

Sorry, my bad… fixed in v142, which I just pushed. —Jeffrey

— comment by Tim Tilden on January 31st, 2010 at 6:01am JST (8 years, 10 months ago) comment permalink

After associating images with my flickr account is there any way to download the tags that they possess on flickr as keywords?

Not in LR2. I’ll be able to add this feature once LR3 comes out. —Jeffrey

— comment by Jon Jaques on February 2nd, 2010 at 3:44pm JST (8 years, 9 months ago) comment permalink

On the same subject of syncing keywords (and hopefully Titles/Captions also) back into LR3, any thoughts on how it might handle keywords that are nested? I just recently spent a few hours cleaning up stray keywords and putting them back into their correct parents… but I’d imagine an automated import would have difficulty associating hierarchies, especially if the same keyword is found under two or more parents (“violet > color” and “violet > flower”).

Getting the Titles/Captions back into Lightroom is a task I’ve been putting off for a while, hoping that technology will advance and solve my problems 😉

This will indeed be a touchy situation. I’m not sure that there is a good solution, and since I don’t use keywords much myself it’s all the more unsure. We’ll have to see how it pans out… —Jeffrey

— comment by JasonP on February 3rd, 2010 at 1:54am JST (8 years, 9 months ago) comment permalink

Extra keywords when using diacritics.

Your LR plugin is working quite fine, except that I have problems with my Swedish keywords.

A keyword like snö, turns up as both snö and snš, so I get extra keywords with the Swedish characters replaced by something else.
I’m not sure it happens all the time, though, but it has happened many times with different versions of your plugin.

Flickr plugin version: 20100208.155

What’s happening here is a combination of two things. The first is that Lightroom dorks non-ASCII keywords in the copy of the image uploaded, and the second is that there’s no way for the plugin to tell Flickr not to read those keywords. One solution is to strip the metadata from Lightroom by enabling the “Minimize embedded metadata” option in the Export Dialog, and another is to use a feature I added recently to my Metadata Wrangler plugin, which can be used in alone or with other plugins. Toward the bottom of its section of the Export Dialog is an option “Overwrite IPTC:Keywords with a copy of XMP:Subject”. Enabling that will also solve this problem. —Jeffrey

— comment by Tobbe on February 9th, 2010 at 4:06am JST (8 years, 9 months ago) comment permalink

I tested the latest Export to Picasa Plugin and I have to say it is really great and much more than I expected, especially the templates for auto-destination folder and the auto-catpion feature. Since I plan use it for upload of about 10000 fotos to 400 albums the multi-folder-capability and the auto-folder is a real time-saver, many thanks for that flexibility!

There are only few features I am missing for the auto.folder:

How to automatically preset the contents of the folder description (a fixed text would be sufficient)?
How to set the album location automatically?
How to mark the album cover picture automatically?
How to limit the bandwith used while uploading (as Picasa offers)?
Is there a chance to consider those as enhancements?

They’re all good ideas, but I won’t likely be able to address them soon, but I’ll put’em on the list. (The bandwidth thing I can’t really do, except to pause between images. Lightroom doesn’t give a plugin that much control over the networking.) —Jeffrey

— comment by FlyFoto on February 9th, 2010 at 10:02pm JST (8 years, 9 months ago) comment permalink

Hi Jeffrey – First of all – I love what you’ve done…Thanks! However, I am using LR3 with the Flickr uploader (most recent v) and after I upload to Flickr, there used to be a copy of the uploaded file in an “exported” file in my HD. Now that doesn’t happen and I don’t know where to locate the uploaded file. Frustrating in that if i edit a photo on LR3, then upload to flickr, I cant upload that same edited file to another site… Any ideas?
Thanks!

There’s a bug in LR3b that required that I take out that setting, but revisiting it now, I might have a way around it…. we have company visiting tomorrow, so perhaps I can work it the next day. We’ll see…. —Jeffrey

— comment by Jeffdenberg on February 10th, 2010 at 9:00am JST (8 years, 9 months ago) comment permalink

You have said that importing metadata (keywords) from Flickr into Lightroom will happen when v3 comes out of beta. Does the Google/Picasa API also allow for this?

In a perfect world, keyword and facial recognition tags inputted on Picasa would be importable into my Lr3 catalog for perfect synchronicity.

Thanks for all you do, it’s a huge value-add for the Lr community!

To be clear, I said (or should have said) that it will be possible when LR3 comes out. I’m still scrambling to get stuff done. I would expect that Google allows for it, though I haven’t checked the details yet…. —Jeffrey

— comment by Mike Wren on February 12th, 2010 at 6:13am JST (8 years, 9 months ago) comment permalink

I love your flickr plugin for Lightroom. I just upgraded computers, and on my new computer (windows 7 64 bit) i can’t authenticate. when i click OK in the Authenticate at flickr dialog box, nothing happens in my default browser (firefox). Lightroom 2.6, latest flickr plugin. anyone else seen a problem like this?

— comment by Ken Fong on February 15th, 2010 at 1:17pm JST (8 years, 9 months ago) comment permalink

ok, never mind my previous blog comment. i found the workaround; i’m surprised i couldn’t find it on the internet somewhere. in windows 7, i had to use “run as adminstrator” to run lightroom in order
to get any of the browser links in the plugin to work.

— comment by Ken Fong on February 15th, 2010 at 1:24pm JST (8 years, 9 months ago) comment permalink

Just downloaded your Lightroom to Flickr and Zenfolio plugins. Thanks for all the fine work. I’m trying to export photos and include a copyright watermark. This seems to work for the photos uploaded to Flickr but not to Zenfolio even thought I have the “include watermark” box checked on both.

It could be related to the size of the images you’re sending to each… the built-in watermarking is not very smart. In any case, my plugin does nothing to influence anything about watermarking, including whether it’s done, so you’ll have to dig around in the non-plugin parts of the export to figure it out. FWIW, most people who want sensible watermarking use LR2/Mogrify —Jeffrey

— comment by Chuck Babcock on February 27th, 2010 at 11:31am JST (8 years, 9 months ago) comment permalink

Using the flickr export along with “Metadata Wrangler” on LR 2.6 Windows 7 64bit. If I export without the Wrangler, EXIF data shows up fine on flickr, but it’s everything. Wanting to strip it down, I use the Wrangler, but it doesn’t seem any combination of settings makes the EXIF show up in flickr. By that I mean there’s no “More properties” link on the photo. If you inspect the full size image on flickr, there is indeed EXIF data, but flickr doesn’t seem to recognize it.

You can see examples on my stream. IMGP2613 was exported with Wrangler. _IMG2586 was exported without Wrangler.

— comment by Ren West on March 4th, 2010 at 11:48pm JST (8 years, 8 months ago) comment permalink

Just want to report an issue with German umlauts. If you export to Flickr from Lightroom 2 and a tag contains a umlaut, the tag isn’t displayed correctly on the Flickr website.

Example: GelŠnder (should be Geländer)

This is a known bug in Lightroom. I thought the plugin handled it well, but I guess some still slip through. I just pushed a new version (v161) that should hopefully work better. Give it a try. But this problem will happen with any export, and FYI, a more general solution is to work around it with my Metadata Wrangler plugin, turning on the “Overwrite IPTC:Keywords with a copy of XMP:Subject” option toward the very bottom. —Jeffrey

— comment by Flo on March 6th, 2010 at 6:52pm JST (8 years, 8 months ago) comment permalink

I’ve searched through this page for “keyword” and haven’t found what I’m looking for. Really hoping I haven’t missed something obvious, but is there a way to send the keywords from Lightroom up to PhotoBucket and have them show up as the description? I see that the Caption field can be uploaded, but I rarely use that, preferring keywords.

Thanks!

Mark

I seem to not have a token for keywords… I’ll try to add one soon. —Jeffrey

— comment by Mark Fink on March 9th, 2010 at 5:12am JST (8 years, 8 months ago) comment permalink

Love your plugin for LR 2.6/Zenfolio and things have been smooth up to tonight.

I just upgraded to ver. xxx.104 tonight and now I keep getting the “this version can only export up to 10 files” error even though I contributed recently and the LR plugin manager still shows that the plugin is unlocked and unrestricted. I tried restarting everything and even rebooted the computer. Nothing is helping.

Any ideas?

Don
Are you sure it’s my plugin that’s stopping the export, and not, say, LR2/Mogrify or someone else’s filter plugin that you’ve included in your export? —Jeffrey

— comment by Don on March 9th, 2010 at 1:31pm JST (8 years, 8 months ago) comment permalink

Will this plugin resize my photos before uploading to Facebook? I ask since my pictures are prolly around 5-6MB.

Yes, it sets it to the maximum size allowed by FB (which is very tiny, 720 pixels on a side. If you want to control the size (to make it smaller), enabled the option in the “Tools” section of the Plugin Manager, reopen the Export Dialog, then look in the Image Sizing section of the dialog. —Jeffrey

— comment by max on March 9th, 2010 at 8:20pm JST (8 years, 8 months ago) comment permalink

re: SmugMug uploading…. After uploading a bunch of images and captioning them IN SMUGMUG, I realized I should be adding a copyright. I used Mogrify and added text for the copyright notice. I then proceeded to re-export using your plugin.
Now, everything was going quite well for several galleries – ie. the images were updating and the captions entered in SM remained.
But then I hit a gallery and, yeah, maybe I changed something, but instead of replacing the image and leaving the caption, I created a new image in the SM gallery.
I tried several permutations to see if I could make it work, but it’s just not.
My best guess is that at some point, the SM Export window stopped showing the selected images as updates and only would let me use ADD, which did just that.
If I’ve diagnosed this correctly – how can I get your addon to count my selected image as a candidate for updating?
Michael

The keys are that the images had to have been originally uploaded with the plugin, and that you have the “replace” option selected. If you’d uploaded them some other way, the plugin doesn’t know how to do a replace. This is on the short list to try to find a good workaround. —Jeffrey

— comment by Newmarket2 on March 12th, 2010 at 6:22am JST (8 years, 8 months ago) comment permalink

Hi Jeffrey,

Southern New England here.

Does the Facebook plugin require you to reauthenticate each time you do an export? I’ve found that it’s asking me to go to Facebook’s site the first time I use the plugin in each Lightroom session (subsequent exports don’t require it as long as I don’t quit Lightroom). It would seem to me that it would/should be able to store that info, but is it just a limitation of Facebook or is it a bug?

You should not have to reauthenticate. The symptoms you describe are classic for having a corrupt Lightroom preferences file… you’ll probably have to take the sometwhat drastic step of deleting it (or renaming it out of the way) and let LR build a new one when it launches. Then you’ll have to tell it about your plugins and other preferences from scratch. )-: —Jeffrey

— comment by Andrew Coutermarsh on March 20th, 2010 at 7:39am JST (8 years, 8 months ago) comment permalink

G’day mate,

I have a solution to some people who are getting the “Oops! Flickr can’t find a valid callback URL” error. Unfortunately it’s not an “all-encompassing” fix but it does shed a lot of light on the issue.

I’m on a university run network which uses a transparent HTTP proxy (aka Squid) requiring authentication to traverse it through to the Internet. We also have access to a special web page that when kept open will allow us to bypass Squid completely for applications that scream bloody murder when they encounter it.

I had this page open when I attempted to authenticate with my Flickr account, allowing applications free reign without touching Squid. What I forgot to take into account that I still had Squid configured in “Internet Options” of Windows (and Internet Explorer… AND Google Chrome (Why Google??!)). Switching Squid off and re-attempting to authenticate again worked.

So it might be a proxy traversing issue for some users, especially those on corporate networks. They might have Internet connectivity but really, HTTP proxies would be interfering with it, creating confusion.

Excellent set of plugins by the way, expecially the geotagging one. Works a treat with my Nokia N78 and Nokia Sports Tracker! When I get some funds my way, I’ll send a well earned donation to you. 🙂

Justin aka deltafalcon.

— comment by Justin on March 21st, 2010 at 9:59am JST (8 years, 8 months ago) comment permalink

I suppose I accidentally deleted the original plugin for Zenfolio from lightroom 2 I had which was phenomenal, so I had to update it today. All of a sudden whenever I attempt to upload to Zenfolio it now makes some kind of copy to my Pictures folder and I can’t change it even when logged into Zenfolio so it takes up hard drive space. It also doesn’t take all the pictures that I highlighted, only some of them. Some are psd copies if that helps. It used to work fine though so I don’t know what changed. Sorry I’m not more clear. Thanks though. I am registered so it’s a full copy.

Carefully look through all the settings in all the sections of the export dialog, to make sure you understand them and that they’re as you want. For example, in the Export Location setting, you’ll see that you have it set to save copies in your Pictures folder, and it sounds like you’d rather have “Temporary folder”. In the Upload Destination section, is sounds like “All” is not selected, but that you want it. —Jeffrey

— comment by Kerri W. on March 22nd, 2010 at 7:26am JST (8 years, 8 months ago) comment permalink

Hi Jeffrey,

Just a quick heads up. I downloaded LRs latest beta (BETA2) and I am getting the following error when downloading/syncing comments. http://dznr.org/cbm6

For photos with a lot of comments, i actually had to force quit the app as the popup would not go away.

Is there any way we can turn off comment syncing in the meantime? (not that I ever use it, to be honest)

Thanks,
Stephan

Sorry ’bout that… some debugging code. Just pushed a fix. But be warned that the Publish stuff is essentially random now… it will change, drastically, and the “connections” created in the public betas likely won’t work in the real LR3, or even in later versions of the plugin in LR3b2. —Jeffrey

— comment by Stephan Geyer on March 23rd, 2010 at 6:47pm JST (8 years, 8 months ago) comment permalink

Version no. 20100324.166
Flickr exporter

It was working fine up until recently. When I try to export i get the following message: “cannotConnectToHost”.
I’m using Vista.

Many thanks,
Denis,
UAE

Check your security apps… Little Snitch, Zone Defense, etc… something’s blocking LR from connecting, or maybe Flickr was just down for a moment. —Jeffrey

— comment by Denis Vahey on March 27th, 2010 at 3:25pm JST (8 years, 8 months ago) comment permalink

Hi Denis,

I notice you write from the UAE. As you know, Etisalat and Du have flickr blocked – that is probably the reason why you can’t connect to it (the host). Are you using some sort of VPN or tunneling technology?

Sorry to hijack this, Jeffrey – just thought I could help 🙂

— comment by Stephan Geyer on March 27th, 2010 at 4:10pm JST (8 years, 8 months ago) comment permalink

Thanks very much for the replies. Etisalat is not the problem because it has been workin no problem for a long time. Firefox brought out an add-on allowing you access to flickr from the UAE.

Under my McAfee Lightroom is allowed full access to the internet.

— comment by Denis Vahey on March 27th, 2010 at 5:13pm JST (8 years, 8 months ago) comment permalink

Hi Jeffrey, thanks for the good work! I use your SmugMug export plugin, and am finding it just perfect except for one small thing: I use the Location/City/Country fields, and only City and Country get exported as keywords.

I saw that you already had some comments about this, from more than a year ago, so I guess it’s not at the top of your todo list. I can code (I’m a computing phd student), so I’d be happy to go in and fix that if you gave me access to the source code. What do you think?

I don’t recall that the plugin is using the location et. al. fields as keywords, so that’s perhaps a SmugMug thing, but it’s easy enough to add those as keywords if you want… see the “template tokens” link near the “extra keywords” field. —Jeffrey

— comment by Olivier Pernet on March 30th, 2010 at 8:08pm JST (8 years, 8 months ago) comment permalink

Hmm, looking again, it’s true that the Export dialog doesn’t mention that. The “Resend Metadata” plugin extra does, though. But yes, I can use the keyword templates – never found out about the feature before, it’s brilliant! Thanks!

— comment by Olivier Pernet on March 30th, 2010 at 8:38pm JST (8 years, 8 months ago) comment permalink

calling from Calgary, AB…
My profile album only has 27 photos, but every time I try to upload an image, I get the “destination full” message. What could it be you think?
thanks!

Without knowing what plugin you’re talking about, I can only guess, but my guess is that “destination full” is trying to tell you that the destination is, er. full. Perhaps a “profile album” can have only 27 photos, or some certain number of bytes? Dunno. —Jeffrey

— comment by patrick on April 1st, 2010 at 12:38am JST (8 years, 7 months ago) comment permalink

sorry for not being more specific. 😐 it’s the facebook plugin for iphoto. I was able to upload to a different album, then switch the photo to my profile album, thus popping the limit on my profile album is not the issue. Other facebook plugins I’ve tried dont allow direct upload to profile album-perhaps this is the underlying issue?
BTW, thanks for replying so promptly!

I don’t know anything about iPhoto, sorry (my plugins are for Lightroom), but if FB is saying the album is full but you think it’s not, perhaps you should ask FB about it. —Jeffrey

— comment by patrick on April 1st, 2010 at 2:07am JST (8 years, 7 months ago) comment permalink

Hi Jeffrey,

I love the plugin for smugmug but recently I keep getting a wrong bytes sent error from the upload. Is this a smugmug error or something wrong in the uploader? I am using the latest version for lightroom and using lightroom 2.6

Thanks!

SmugMug seems to be having issues at the moment… they’re looking into it. —Jeffrey

— comment by Jason on April 1st, 2010 at 2:33am JST (8 years, 7 months ago) comment permalink

Hi Jeffrey!
First, fantastic plug-in (LR Zenfolio). This is what one would call very elegant software in that it does precisely the tasks for which it is designed. Not fat or showy, just works. And you are communicative, responsive, empathetic and diplomatic, all wonderful human qualities in a code slinger 😉 I write to you today from Gilroy, CA (yes, we’re the self-proclaimed Garlic Capitol of the World).

I am running Mac OSX 10.6.2 on a 2007 MacBook, 4GB RAM. I am on LR3b2 and on 20100323.106 of the Zenfolio plug in. I was on the previous beta of LR and had the previous version of the plug-in and all ran as expected! My problem right now is that when I publish out of any of my Zenfolio connections, Zenfolio is displaying the original photo, not the adjusted one. If I export from LR to a folder then Upload to Zenfolio, it works fine.

I saw the comments on the new snapshots functionality but I don’t think that is where I have a problem?. Am I doing something blatantly dumb (I am just a newer user so the chances are good!)? For now I am bypassing the plug-in altogether, exporting to a folder then uploading from within the Zenfolio interface – ugh!

Thanks for any help or insight you might be able to offer!

Regards,
Price Dempler
http://www.pdemplerphoto.com

Thanks for your kind words :-). As for your export, you probably have “Original” selected in the File Format section…. switch back to JPEG and you’ll be fine. —Jeffrey

— comment by Price Dempler on April 6th, 2010 at 9:38am JST (8 years, 7 months ago) comment permalink

A Big DO’H on my side!! and many thanks from Gilroy, CA…

— comment by Price Dempler on April 6th, 2010 at 11:50am JST (8 years, 7 months ago) comment permalink

Hey, so I’m having a problem here, I can’t find the solution.

I created an album and uploaded all the pictures of one day, then selected an other day when it was done, and started uploading it to the same album. It’s for my Ski Trip.

But when I get to the 4th pic of the second day, it gives me an error, saying: “Error Uploading Image: Incorrect Signature”

I really don’t know what to do. :/

It might be a good start to include basic information in your report like what plugin you’re using. —Jeffrey

— comment by Laptop_mini on April 7th, 2010 at 5:33am JST (8 years, 7 months ago) comment permalink

Hi Jeffrey,

I’m having the same problem as a few others… “Error Uploading Image: Incorrect Signature”

Everything was fine and normal up until today. When I try to export the other thing I’ve noticed is that I have no albums to select from. Again, yesterday it was fine, today it’s messed up. Basically I haven’t changed a thing (although I did update to the latest version to see if that would fix it, but no luck, just the same error message).

Any help is appreciated. And it should go without saying, i really dig the work that you’ve done and the time and effort you’ve put into these plugins for us lightroom users.

Cheers.

If it suddenly stopped working, it’s probably an issue at Facebook, hopefully temporary. If it persists, please enable enhanced debug logging in the Plugin Manager, try some exports until you get the error, then send the log to me (via the “Send to Jeffrey” button in the plugin manager). —Jeffrey

— comment by A.J. on April 8th, 2010 at 10:37am JST (8 years, 7 months ago) comment permalink

Sorry, I didn’t specify that it was the “Facebook” export I was talking about. Also, i’m writing from just outside of Toronto.

Thanks again!

— comment by A.J. on April 8th, 2010 at 10:40am JST (8 years, 7 months ago) comment permalink

Have tried using the Zenfolio uploader for the first time. Had a large number of images to load on my site. I got an error message after the first 16 images. When I attempted to restart the upload, I get a message saying all the file names are already present on the site, do I want to use unique names or overwrite the files (which aren’t really there). So I selected “unique file names” just to try to get things moving, but when I try to get the upload going again, it just sits. It says it’s uploading, until I get another message a long time later saying it’s retrying. The thing is painfully slow as well.

I’m using a Macpro with 6GB of ram and Lightroom 2. I have a DSL line.

The file naming thing is related to your selections in the File Naming section of the export. You probably want “temporary folder” so that the copies generated for upload don’t stay around on your local computer. As for why the upload is having troubles, I can’t speculate. Maybe Zenfolio was having issues, or perhaps your router or ISP…. ? —Jeffrey

— comment by George Cannon on April 15th, 2010 at 8:08pm JST (8 years, 7 months ago) comment permalink

Using the Flickr plugin (version: 20100324.166) the “Location” field in the metadata does not get turned in to a Flickr tag in the same way that the “City”, “State / Province”, and “Country” fields do.

Poking through the help I guess I could use “{Location}” in the additional tags field, but this feels like it should be the default.

The automatic tagification (taggifying?) of city/state/country is something that Flickr has chosen to do. If you think they should do Location as well, perhaps submit a feature-request to them. Personally, I think they shouldn’t auto-tag anything, but they don’t see fit to ask my opinion on these matters. —Jeffrey

— comment by Nik Clayton on April 20th, 2010 at 1:35am JST (8 years, 7 months ago) comment permalink

Trying to install picasaweb-20100323.117.zip into Lightroom 2.4.572242.
In plugin manager select a folder with unpacked picasaweb-20100323.117.zip and get this error:
An error occured while attempting to load this plug-in

What’s wrong?

There’s not much in your report to go on, but perhaps your zip was bad. After unzipping, you should be left with a folder named “picasaweb-jfriedl.lrplugin”, inside of which there should be lots of files, including “Info.lua”. Anyway, point the plugin manager at the “picasaweb-jfriedl.lrplugin” folder itself, and if all the files are in there from the zip, it should work. —Jeffrey

— comment by Shrike on April 20th, 2010 at 6:24am JST (8 years, 7 months ago) comment permalink

>There’s not much in your report to go on, but perhaps your zip was bad. After unzipping, you should be left with a folder named “picasaweb-jfriedl.lrplugin”, inside of which there should be lots of files, including “Info.lua”. Anyway, point the plugin manager at the “picasaweb-jfriedl.lrplugin” folder itself, and if all the files are in there from the zip, it should work. —Jeffrey

Hi.
Thanks! That’s was the problem – it didn’t name a folder as ‘picasaweb-jfriedl.lrplugin’ (it’s pretty strange for me that Lightroom is so picky to folder name)

— comment by Shrike on April 21st, 2010 at 6:13am JST (8 years, 7 months ago) comment permalink

Hello. I’m from Michigan. When I use the lightroom/smugmug plugin, my photos are not sorting properly “by date taken” and “ascending”, even though I have this option selected in my Gallery Settings in lightroom. They seem to be in a more or less random order. Does the plugin do something to alter the “date taken” information? Thanks so much.

The plugin doesn’t do anything in particular, but the Lightroom export can strip most of the metadata (including dates) if you turn on that feature (see the “Metadata” part of the export dialog). If you see the date in the photo data on SM, then it’s not being stripped and there’s perhaps a problem at SM. Hard to guess without more info. —Jeffrey

— comment by rose on May 1st, 2010 at 11:08am JST (8 years, 6 months ago) comment permalink

I am just starting to configure your zenfolio publisher. I am using a free account for my initial testing and plan to setup a full account later under my full name. There is a note in “Your Zenfolio Account” section that says the remote account cannot be changed. Two questions.

1. Does mean that use one Zenfolio account and if so is that per host or is this specific to the LR catalog?

2. If I start testing with my free account do I have to completely remove the setup and start over again with my full account information?

I am running on MacOS 10.5.8 and LR 3b2

Thanks,

-louie

It sounds like you’re using Publish with the Zenfolio plugin…. as I say on my site, Publish is not ready for real work, and won’t be until Lr3 comes out, so you’ll lose your Publish collections either way. But yes, if you change accounts later you’ll just have to re-authenticate with the new account and build your uploads to it from scratch. —Jeffrey

— comment by Louie Sherwin on May 6th, 2010 at 6:11am JST (8 years, 6 months ago) comment permalink

Regardless of what photo I try to upload, I get this:

smugmug.images.upload

Also, when I click the manage plugins button, I get ‘Access to undefined global: titleColor’ message from LR.

I’m running 20080411.40 of plugin, it says that 20080717.48 is available, but when I click on the button, it takes me to the same smugmug-20100323.153.zip. Should I uninstall this version and install a new one, how?

I’d recommend a manual install of the latest version. Just download and unzip, move to where you’ll keep it, then Add it via the plugin manager. You can simply remove the old one from the plugin manager and delete it from disk. —Jeffrey

— comment by Alex Curtis on May 24th, 2010 at 2:03am JST (8 years, 6 months ago) comment permalink

Hi, Jeffrey. Flickr Export Plugin for Lightroom (v20100324.166, LR2.7, Win7 64bit) is great and i’m finding it very useful. However, it seems to not be uploading everything, and not really putting the ones it does upload where i ask. Example: i select 111 photos, mostly two versions of the same image (with and without LR and a few PS edits). Upload to a new flickr set. After the upload, there are 46 images in that new set of 107 that are uploaded. In the flickr set organizer i drag-drop the others into the set, but i have 4 that won’t upload. The odd thing is it doesn’t seem specific to a version. One upload sends the original, another attempt might send the edit, but never both. Any ideas what might cause this? A setting somewhere? It easily could be operator error or ignorance, but i haven’t figured it out yet. Any help? Thanks! -bill

Sounds mysterious… could you send a plugin log (via the “Send to Jeffrey” button in the plugin manager) along with a note giving a specific example of the problems? —Jeffrey

— comment by bill weaver on May 25th, 2010 at 12:35pm JST (8 years, 6 months ago) comment permalink

Hi, Love your tool, it saves me so much time. The only thing is the list of groups… I want to see as many as possible at a time so I don’t have to scroll too much so I always configure it to 20 groups per view. However, it keeps resetting back to 5. Is there any way it can be locked to 20. Or maybe you can set 20 as default? – Cheers, Saskia.

Sorry about that… I’ll be able to push a fix once Lr3 is out. —Jeffrey

— comment by Saskia on May 27th, 2010 at 3:49pm JST (8 years, 6 months ago) comment permalink

Hi, I just installed the flickr-20100324.166.zip plug-in, but am getting stuck in the authenticating process. Web page opens up in Flickr, and am able to authorize the account fine there. but when i get back to Lightroom 2, it stalls saying ‘Unable to export: awaiting dialog’… I end up having to Force quit out of L2, as the export page just freezes.

Thanks for any suggestions. Writing from Berkeley, California.

This one’s got me stumped… could you give a try with the version linked from this page? —Jeffrey

— comment by brian on June 4th, 2010 at 1:02pm JST (8 years, 5 months ago) comment permalink

I love the flickr plugin but when adding to an existing set the photos uploaded do not appear in my photostream, or they do but they are not the latest/newest in the photostream. Am I just missing a setting here…

When creating a new set it seems to add the photos to the top of my photostream. Thanks.

Atlanta, Ga.

this is jess…

Check out the bottom of the “Flickr: Metadata Management” section of the export dialog… there’s an option for setting the date for the photostream order. —Jeffrey

— comment by jess on June 8th, 2010 at 1:20am JST (8 years, 5 months ago) comment permalink

Jeffrey,

Is it possible to set the “already published” flag manually? I have a bunch of pictures that, being scans, don’t have correct timestamps on them, and so comparing them to their Flickr counterparts didn’t add them to the Flickr photostream in Lightroom – I would like to add them manually, but obviously I wouldn’t want them to be uploaded to Flickr again.

Thanks,

David.

Not yet, sorry. On the todo list. —Jeffrey

— comment by David Navarro on June 10th, 2010 at 1:39am JST (8 years, 5 months ago) comment permalink

Hey Jeffrey, I manually downloaded the latest version of your plugin today and installed it in Lightroom 3 after upgrading from Lightroom 2. I lazily added it without removing the old, defunct version and was “promptly” assaulted with a barrage of error dialogs. Luckily Lightroom didn’t crash but unfortunately I didn’t copy any of the messages for you. Maybe this is the cause of some of the more recent comments.

Best,

Marc from Guelph

I have more than 20 plugins, and can’t guess which you may be referring to. —Jeffrey

— comment by Marc Tytus on June 12th, 2010 at 2:30pm JST (8 years, 5 months ago) comment permalink

I’ve loaded LR3 and started looking at the published servcies and i already had your Flickr Plugin which provides a lot of details.
One query, in the facebook option when i made some changes and pointed it at another collection on the facebook site and saved it, saved as another photoset in LR3.
When i tried to do this for the flick, it keeps just saving the same “master settings” is there a way to do this with flickr so that i have different settings in LR to publish to different flickr photosets?

Perhaps Publish isn’t what you want, since it’s intended to set up an ongoing relationship, so if you change the settings for a photo, they are reflected back to Flickr. If you want different looks in different photosets, you’ll probably want to make a virtual copy, so that they’re considered different photos as far as Publish is concerned. —Jeffrey

— comment by Keith on June 17th, 2010 at 12:15am JST (8 years, 5 months ago) comment permalink

Hi Jeffrey,

I’ve never used the plugin before and downloaded it today for Facebook to use on LR3. Everything seemed to go well until I tried uploading, which I am receiving ” Attempting # (i.e. 1, 2, 3, 4 and so on) Error “badServerResponse”, pausing (and then the number of seconds) before trying again”. I’m assuming there is something wrong on Facebooks end? I authenticated everything, which went fine. Thanks!

Kristina

Could be FB, could be your ISP, could be your router…. hard to tell without additional info, but I’m sure it’s not the plugin. —Jeffrey

— comment by Kristina on June 23rd, 2010 at 12:54pm JST (8 years, 5 months ago) comment permalink

REQUEST: If uploading of a particular image upload dies, do not stop the upload process with a dialog that has to be cleared manually, and instead just continue on doing he rest of the images as if I had acknowledged the error message, myself.

Perhaps it is SmugMug or perhaps it is my home and work internet connections, but I have been getting 504 errors from SmugMug every few images, and the warning dialog that communicates this error must be cleared manually every time. Once cleared, the upload seems to continue with the next image, leaving the image that had the problem ready for uploading on the next Publish operation.

It would be very useful if the upload would auto-continue when it received an error, or at least for particular errors, so a large Publish would mostly complete unattended. The way it is, now, I have to give my computer almost constant attention for the hours it takes to do a large publish. I would prefer being able to leave a batch running unattended for hours or overnight and just republish to catch the few images that had a problem.

Even better would be an auto-retry mode where the Publish operation would start over again, to re-publish any stragglers until the entire set had completed. This would allow completely unattended operation. Even if SmugMug is in readonly mode due to a problem on their end, an auto-retry would eventually be able to get through.

Have you considered such an enhancement, or does the LR api make this impossible?

It’s not really practical to continue in the face of networking errors because, well, if the network is down or unstable, it’s unstable. I could try retrying, as I already do for a certain class of errors, but right now I’m concentrating on getting basic functionality stable in in the new Lr3 version, so I’ll leave this on the todo list for the moment. —Jeffrey

— comment by Steve Sprengel on June 27th, 2010 at 5:19am JST (8 years, 5 months ago) comment permalink

I’d love to be able to use this plug-in but I experience problems using it with LR3. I’ve included the error message I get when trying to export pictures to my SmugMug page. Any additional information you need, just send me an email and I will gladly provide. Thanks for your time and hard work with this plug-in!

Error response from SmugMug
incomplete file (ByteCount given: 1483225, received: 565020. MD5Sum given:
93a9c072b209ce1cc02b604f3712e762, actual: 12829574a50a32cdbac3dff70611dd29.)
Aborting export after 6 of 34 images successfully uploaded

Unfortunately, this is a known issue without a known solution. —Jeffrey

— comment by Rich on June 27th, 2010 at 6:33am JST (8 years, 5 months ago) comment permalink

The other error I continue to receive from the SmugMug publishing plugin:

Error response from SmugMug
wrong format()

Aborting export after 0 of 10 images successfully uploaded

That’s discussed here. —Jeffrey

— comment by Steve Sprengel on June 27th, 2010 at 3:33pm JST (8 years, 5 months ago) comment permalink

I just downloaded version flickr-20100630.188.zip. I am trying to upload to a set already in my flickr account, but I cannot find the list to select what set to upload images into. I just started using the program 2 days ago and that version had an option to pick the set. Could you please let me know if that was removed, or if I am just missing something. I have looked under each category, but cannot seem to find it.

Thanks,

Doug
Palm Beach, FL, USA

Sounds like you’re looking at the Publish Service setup dialog. You probably want to do a normal export, which works the same way as it did in previous versions. —Jeffrey

— comment by Doug on June 30th, 2010 at 11:02pm JST (8 years, 5 months ago) comment permalink

From the muggy South (Marietta GA): I’ve been using your LR2 plugin for Smugmug for quite a while and like it. I’ve begun using the LR3 Beta version and it’s working, but the automatic updates aren’t. I’m getting the notifications, but the install fails. I have to do the manual install, which works. What’s changed? These always worked for me in the past.

I don’t know… probably permission issues of some kind, but it’s a mystery to me. —Jeffrey

— comment by Carl Bickers on July 5th, 2010 at 3:04am JST (8 years, 4 months ago) comment permalink

I used the Lightroom plugin on LR3 Beta2 to upload to Smugmug and it worked very nicely. Now with LR3 (released version), I too am getting the “Got the “Incomplete File (ByteCount given:….” error message from Smugmug. What is curious is that if I have a very small gallery ( say, 1 picture), I can get the plugin to work. However, it fails all my other pre-existing smugmug galleries. I have the plugin selected for “Newly-added collections should be named: Hierarchically” and I have “Normal” and “Smart” selected for the gallery listing.

-Dave

The incomplete-file errors and the like are not well understood by SmugMug, but it does not seem to be related to the version of the plugin nor the version of Lightroom, so the timing you experienced is likely coincidental. It does seem to happen more often when the upload is a replacement, which means it would hit Publish more often. —Jeffrey

— comment by Dave on July 12th, 2010 at 12:59am JST (8 years, 4 months ago) comment permalink

Using the latest version of the plugin (just updated to see if this bug would go away), on Lightroom 2.5 and when I try to use the Flickr Extras to re-up my tags I get the following error

“Access to undefined global: ReconnectRemoteForEntireCatalog”

I opened the Export dialog to make sure I was logged in to Flickr and that didn’t help either.

Help!

P.S. Coming at you from Shanghai, China

Sorry about that… just pushed a new version that should fix that. —Jeffrey

— comment by Alex on July 13th, 2010 at 11:37pm JST (8 years, 4 months ago) comment permalink

Hi Jeffrey,
I was using the Picasweb plug-in with Export in LR3 and everything is fully functional. With Publish the Twitter feature of Picasaweb is not there, which is a pity because Publish makes things so much easier than Export. Is this a bug or do you intend to add it in?
Thanks
Robert

There are a few issues I need to work out before I can get it working in Publish, but I intend to. —Jeffrey

— comment by Robert Ardill on July 16th, 2010 at 7:58pm JST (8 years, 4 months ago) comment permalink

I’ve upgraded from LR 2 to LR 3 and now the Smugmug plugin won’t connect to that site. The plugin is OK – I’ve downloaded and installed it three times, and the panel says it’s operational, enabled. I’ve installed the correct Starfield certificate and I’m running Windows Defender (which reports all is OK).

The problem is connectivity. Maybe there’s a port access problem here? I’m getting fine service for every other app I use, including those that use https, etc. I really miss this – I can upload through a browser but it takes time to copy and more care. I don’t know any way to troubleshoot this. TIA.

Sounds exactly like a security issue on your side… you’ve granted security exceptions for Lr2 to contact the network, but not for Lr3, so Little Snitch or whatnot is blocking it. That’s what it sounds like, at least. —Jeffrey

— comment by Don Dement on July 18th, 2010 at 11:43am JST (8 years, 4 months ago) comment permalink

Hi,
I have a strange problem with the Picasa-Plugin but I do not really know where it comes from:

Whenever I try to publish pictures via LR3, the picture is queued for re-publish again. Only two of my Pictures which are JPGs (other than RAW, PSD and TIF) show up under published pictures

It is like the simple act of uploading the picture changes it, so it has to be uploaded again.

The Log says only that it has been published.

I guessed it was an interference with some other plugin, so I disabled ALL but jf PicasaWeb… but the effect is still there.

Unfortunately I can not say when this behavior started. When I first installed the plugin everything was fine.

I hope I described the problem understandable and got all the terms right. I use the German version so I have to translate the German translations back to English which is not lossless 😉

regards
TOM

I’ve gotten a few reports of this in the past, and have logs waiting to be investigated (I have hundreds of emails yet to get to )-: ), so maybe I’ll be able to figure it out, but if you’d like to send a log after seeing the problem, it might help. —Jeffrey

— comment by TOM on July 22nd, 2010 at 1:53am JST (8 years, 4 months ago) comment permalink

Hi,

Thanks for the great work! I’ll bet it’s better than the image sites would do themselves if they hadn’t left it to you 🙂

I’d like to offer a feature request: to be able to update image metadata without re-uploading the image. I often edit keywords, captions etc after uploading and would like to be able to update that information online without having to re-render and upload the image.

Thanks again.

I don’t know which plugin you have in mind, but some of them have a metadata-resend feature in File > Plugin Extras —Jeffrey

— comment by Mat on July 23rd, 2010 at 12:52pm JST (8 years, 4 months ago) comment permalink

> I don’t know which plugin you have in mind, but some of them have a metadata-resend feature in File > Plugin Extras —Jeffrey

Oops, sorry for neglecting to mention: the PicasaWeb plugin. I in fact had never noticed the Plugin-Extras option, but unfortunately it appears updating metadata isn’t supported. Thanks for your response.

— comment by Mat on July 23rd, 2010 at 9:37pm JST (8 years, 4 months ago) comment permalink

Plugin: jf SmugMug
Version: 20100726.173

Description: Renaming a gallery on smugmug.com doesn’t update publish service text (target is correct)

Long Description / Reproduction: Add a gallery via smugmug.com, and then add that gallery via the Publish Services menu. Go back to smugmug.com and rename the gallery. At that point, it seems impossible to get the name to update back in LightRoom. This only affects the display. The publish target remains correct.

Yeah, that’s one of the many small details that still remains on the (very long) todo list… —Jeffrey

— comment by Jakob Heuser on August 4th, 2010 at 2:15am JST (8 years, 3 months ago) comment permalink

Hi Jeffrey
Thanks for all your work.
I am just starting on Picasa and have run into some problems. I like the program and offer these comments as feedback from the field, and not as complaints.
There seems to be a weakness in communication between the plug in and picasa, once the pix have been uploaded in that:
– if I delete a series in LR, the change does not show up on Picasa
– if I delete or modify images in Picasa, LR does not hear about it.
Wrinkles in setup:
– I cannot create a series directly from LR: I have to go online to Picasa, create the series in Picasa, then back to the plug in settings, refresh the list to include the new series, save, and then I get the new series.
– no ability in the plugin to set the level of privacy in the new series (I often use “by invitation”)
– if I set a series as “by invitation” from within Picasa, and then load some images from the plugin ,I cannot see those images in Picasa when I click on “visit album on Picasa”. This returns a Picasa error “You do not have access to these pictures, contact the owner…” . Of course, if I exit LR, and go to Picasa independently, all the images are there.
Thanks again
Bruce Shaw, near Toronto Canada

— comment by Bruce H Shaw on August 4th, 2010 at 8:57pm JST (8 years, 3 months ago) comment permalink

Question about the infamous “incomplete file” issue. After I get that error msg, I have been able to reliably upload my files using the Java uploader where you drag/drop JPG files. I initiate the Java uploader within 30 seconds of getting the error from the LR plugin.

Could it be the Java uploader is using a different upload scheme which might be immune to the “incomplete file” errors?

That could be, but I use SmugMug’s published API for third-party uploaders, so I don’t have much leeway. —Jeffrey

— comment by mike on August 8th, 2010 at 3:40pm JST (8 years, 3 months ago) comment permalink

I recently installed your new LR3 plugin. I used it tonight however, I have the “send a tweet after successful upload” checked. When it sends the tweet, the URL it gives (shortened version) goes to the upload page (requiring my login) and not the “customer view”. How do I fix that? or is that something that is integrated in the plugin. I dont remember it doing that with the LR2 version.

Thanks Jeffery.

Are you sure you’re using the latest version of the plugin? I thought I fixed this some time ago. If you are, but I didn’t, please send a log after uploading one photo and add a note giving the particulars of what it should have been and how that’s different from what you got. —Jeffrey

— comment by Jason Peckovitch on August 18th, 2010 at 1:25pm JST (8 years, 3 months ago) comment permalink

I am using Picasaweb plugin 20100817134
I have noticed that “replace” upload function does not preserve original captions while it does retain original comments. Any fix?

The idea of Publish is that Lightroom is the master source of your photo data, so it (should) always update Picasa to whatever caption/keywords/pixels you have in Lightroom. Comments are something not intrinsic to your Lightroom library, but rather, to PicasaWeb, so are maintained there. —Jeffrey

— comment by Sam Lee on August 19th, 2010 at 1:11am JST (8 years, 3 months ago) comment permalink

Jeff
Thanks for such a wonderful plugin for lightroom to smugmug. One question – when i do edits in lightroom and use your publish service, it uploads the master without edits. Where as when i select the modified photos in library and right click to export, it actually uploads the edited verions to smugmug. Which is good.
Does your publish service dont recognize the edited photos and do not upload the corrections ? Or i have not checked something in the publish plugin.
Please help

thanks
sameer, South korea

Sounds like you have “ORIGINAL” as the format in the File Settings section. Change that to JPEG and you should be fine. —Jeffrey

— comment by sameer chavan on August 21st, 2010 at 9:21pm JST (8 years, 3 months ago) comment permalink

I just upgraded to the latest release of your FB plugin. I followed the instrucions to delete the previous authentication to FB since it had change. I am able to authorize the application via FB, however the code you generate to copy and paste into the dialog in lightroom does not work, the OK buttons does not unshade and I am not completely unable to finish the authorization to be able to post to FB. What do I need to do to fix this?

Thanks, Stephen

Sorry about that… just pushed a new version of the plugin that should allow you to authenticate. —Jeffrey

— comment by Stephen on September 10th, 2010 at 12:06pm JST (8 years, 2 months ago) comment permalink

I’ve all-of-a-sudden started having problems with the LR3 Facebook plugin. It will not let me create a gallery. Every time I try, I get:
“facebook +145.6: [x1f8ea648] @Bottom line 1082:
Assert @Bottom:1082:
facebook +145.6: [x1f8ea648] @Bottom line 1082
facebook +145.6: [x1f8ea648] @Async line 66”

I click “OK” and get another popup box: INTERNAL PLUGIN ERROR Create new album at Facebook aborted

Click OK once more, and:

“An Internal Error has occurred
Debug:547: Assert @Debug:547”

I downloaded and installed just now the latest version of the plugin (20100910.139), tried quitting and restarting LR, and still no-go.

So I guess the question is: Is it something that I or the software is doing wrong? Or does this kind of thing “just happen” every now and then thanks to wonkiness on the FB end and I’ll just have to wait it out?

Facebook is either having “issues”, or has changed something without announcement or documentation. I’ll dig further, but we probably just have to wait for them to decide to fix it. —Jeffrey

— comment by Charles Robinson on September 12th, 2010 at 5:24am JST (8 years, 2 months ago) comment permalink

Try to export from L3, get these two errors:

Couldn’t render image: readNegative: dng_error_file_not_found

canceled

Lightroom can’t access your master image files; this would happen with any export when the master images are missing. —Jeffrey

— comment by Josh on September 20th, 2010 at 4:24am JST (8 years, 2 months ago) comment permalink

Hi Jeffrey, I still find the newest version of the flickr plug in will upload the pictures and make the pictures NOT PUBLICH SEARCHABLE. Can you help out with this problem?

Just pushed 20100930.203 which should finally fix this problem. —Jeffrey

— comment by Jay Jiang on September 29th, 2010 at 6:00pm JST (8 years, 2 months ago) comment permalink

The Zenfolio plug-in seems to be selecting “save original image” option which has allowed my photos to be downloaded by viewers and this is a big problem. Can this be fixed?

I don’t understand… I don’t think the plugin does anything with gallery options like that. —Jeffrey

— comment by Kyle on October 15th, 2010 at 10:34am JST (8 years, 1 month ago) comment permalink

I’ve had your smugmug plugin for a while & just upgraded. I received this error before & after I upgraded to the latest version which installed successfully. So not sure if this is a plugin issue or smugmug issue?? I’m getting an error message when it’s attempting to log me into smugmug: Internal Plugin Error- attempting login aborted. Then, I get another error: Internal Error: 671. Attempt to concatenate a nil value. I have the correct login information. The error occurs when the system is fetching my gallery list from smugmug. any advice? Thanks!

It was a bug at SmugMug, which they’ve now fixed. —Jeffrey

— comment by crhealy on October 22nd, 2010 at 9:55pm JST (8 years ago) comment permalink

I get this when trying to login/export to smugmug…”INTERNAL PLUGIN ERROR” Then I get, “SmugMug:671: attempt to concatenate a nil value” Any thoughts as to why?

Seems to be a problem with SmugMug’s API servers. I’ve got a note in to them about it… —Jeffrey

Update: SmugMug has fixed the error, so the plugin works fine again. —Jeffrey

— comment by Stephanie on October 23rd, 2010 at 1:46am JST (8 years ago) comment permalink

Hey Jeffrey,

Smugmug seems to have fixed itself and I am retrieving the gallery list correctly now.

I wish they would be a little more proactive with their status blog, this lasted several hours.

John

— comment by John Blakney on October 24th, 2010 at 2:13am JST (8 years ago) comment permalink

Hi Jeffrey
I’m on LR3.2 , on both Mac and PC using Zenfolio Exporter V20101217.128. The Mac works like a dream but on the PC the exact same plugin leaves behind the metadata on upload – ie the metadata that shows in LR3 does not show in the Zenfolio page. If I do the exact same thing from the Macwith the same file, it’s fine.

Any ideas why this should be so?

Ta

Nick

Sounds like “Minimize Embedded Metadata” is enabled on your PC. —Jeffrey

— comment by Nick Rains on January 11th, 2011 at 5:05pm JST (7 years, 10 months ago) comment permalink

Hi Jeffery
This option is actually greyed out in the plugin configuration on the PC but your comment led me to look further down the config screen until I found the Metadata Management section – and there was my problem, this section was set wrongly on the PC and right on the Mac.
Thanks for the hint.
Nick

— comment by Nick Rains on January 11th, 2011 at 8:59pm JST (7 years, 10 months ago) comment permalink

Hello Jeffrey,
I have just upgraded to your Zenfolio plugin ver 20110113.129 but when I try to upload to my site I get:
Unexpected HTTP reply from http://up.zenfolio.com/tonybarranco/p804176531/upload.ushx:500
I have made sure I am logged in to my site. Using Vista Home Premium and Lightroom 3.3
Thank you
Tony

Zenfolio tells me that these errors should be fixed now… —Jeffrey

— comment by Tony Barranco on January 18th, 2011 at 6:35pm JST (7 years, 10 months ago) comment permalink

HI,

When I publish to ZF, the images just seem to move to “Modified Photos to Re-publish” rather than “published”. I know no other changes had been made in LR since I published since I pressed the “Publish” button on that collection just moments before. Publishing again does not fix the problem.

Windows/XP (SP2)
LR 3.3 (711369)

Thanks — Dan

It’s a well-known bug in Lightroom, though not well understood. It afflicts some users of all Publish plugins, but no one yet knows why. —Jeffrey

— comment by Dan Hartford on February 11th, 2011 at 5:50am JST (7 years, 9 months ago) comment permalink

When I export photos from Lightroom to Flickr, the plug-in uploads the original photo, not the version that I color corrected in Lightroom. I couldn’t seem to find a setting to correct this.

I’m on:
Mac 10.6.6
Lightroom 2
plugin version 20110120.212

In the export dialog, set the “Format” to “jpeg”, not “original”. —Jeffrey

I love using your plugin. Keep up the good work.

— comment by John D on March 18th, 2011 at 5:34am JST (7 years, 8 months ago) comment permalink

Dear Jeffrey,

I just found your tool and have tested it. There is one issue, which is important for me and maybe you know how to solve it. If this issue can be solved, I will use your metadatawrangler and donate you.

I export with Lightroom 3.2 a .jpg image with the option ” color space AdobeRGB”. When I open the .jpg image with photoshop and look into the data information, in the filed colour space is nothing written.

If I choose instead of “AdobeRGB” “sRGB” then this information is after the export included n the file and I can read it in photoshop.

Do you know this issue?

Thanks for your help.

Various methods are used to indicate the color space of an image. The most complete is to include a color profile, which is what Lightroom does. The Exif standard also allows sRGB to be notated in the ‘ColorSpace’ field, but they don’t make provisions for any other color space (because, in my opinion, the folks who created the standard are idiots, of which this is but one small example). A subsequent standard allowed AdobeRGB to be notated elsewhere, but basically, the whole notation thing is not very useful because they allow only “not specified, sRGB, (AdobeRGB if you know where to look), and “other”. Anyway, where you’re looking in Photoshop is apparently reporting just one prong of this multi-pronged color-space fork. You can use my online Exif viewer to see all the data, and you can read my introduction to digital-image color spaces if you want more details, but in short, Lightroom is doing just fine, and Photoshop I’m sure is doing just fine, though perhaps not telling you the whole story in whatever one nook you’re looking at. Whether other things that touch your image (people’s browsers, online hosting services, etc.) properly handle the color-space indications is anybody’s guess… —Jeffrey

Roger

— comment by Roger on March 22nd, 2011 at 7:52pm JST (7 years, 8 months ago) comment permalink

Jeffery,

As the long list of others have mentioned before me, thanks for all your hard work.

I just stumbled on to your blog tonight and downloaded the latest Picasa web plugin version. I don’t know if it’s related, but it does seem to be more than a coincidence. I thought it important to mention to you that right after I opened the zip file my virus software detected a Trojan. More precisely Trojan:Win32/Alureon.EX. Like I say, I hope it’s only a coincidence.

Thanks again,
Randall
Portland, OR USA

Please report it to your virus-scan company so they can identify why they gave a false-positive. Generally, they seem pretty quick to update signatures when you point out specific issues. —Jeffrey

— comment by Randall Dee on April 20th, 2011 at 12:37pm JST (7 years, 7 months ago) comment permalink

Thanks for the Picasa plugin!

Hey, if anyone else has this problem, maybe this will show up in searches: going crazy trying to figure out why the Lightroom Picasa plugin is silently failing to upload your photos? Do you have the “Replace the most-recent previously-uploaded copy” checkbox turned on? Turn that off.

(The checkbox even warned me of this, “The upload destination is ignored for images that are replaced”, but I wasn’t looking at that checkbox — I may have turned it on months ago, forgot to turn it off, and then it just silently lurks and has no effect until I do try to upload a photo into a second album.)

You might consider it a UI bug that “Visit destination album after upload” visits the *selected* destination, even if no photos actually upload there, all update a different destination. Is it possible to have it visit the album(s) actually affected by the upload?

Or is it possible, when “Replace” is checked, to query the Picasaweb API for a list of the albums into which uploads will replace photos? Even disable the “Currently selected” widget if nothing is going to go there? This would give some UI feedback, even if “Visit destination album” is not in use.

— comment by Eli on April 22nd, 2011 at 3:59pm JST (7 years, 7 months ago) comment permalink

Ah, my wife has what I think is a better UI suggestion than mine. Make “Replace in existing albums” an entry in the destination album selector, not a separate checkbox.

This does drop one case of existing functionality, “replace photos that are in existing albums and put the rest in this new album.” Maybe I’m just overlooking the use for that case, but… it doesn’t seem like a big one to me. If that can be spared, I think it simplifies the interaction.

— comment by Eli on April 22nd, 2011 at 4:15pm JST (7 years, 7 months ago) comment permalink

I have the latest LR 3 plugin for Zenfolio (as of May 11, 2011) for a Windows 7-64 bit system.
My uploads from Lightroom do not appear to have any of my LR edits included – no crop, no spot removal.
This prevents me from using what would otherwise be a very convenient plugin.

You probably have the Image Format set to “Original” (the original image, without edits) rather than “JPEG”. Set it to the latter, and you’ll be fine. —Jeffrey

— comment by Carl Ferreira on May 12th, 2011 at 12:02am JST (7 years, 6 months ago) comment permalink

You have such a range of plugins that it would be worth having separate bug reporting for each one so that people can more easily see current issues for their version.
Issues that are common to all LR (for example) plug-ins could have their own section.

Sadly, I don’t have the energy to even keep one page up to date. It’s pretty overwhelming. —Jeffrey

— comment by Carl Ferreira on May 12th, 2011 at 12:04am JST (7 years, 6 months ago) comment permalink

Hi Jeffrey,

I’ve been using your excellent flickr uploader for LR for quite some time, and only since I’ve upgraded to LR3 and your latest couple of versions of the plugin have I had this problem: My presets don’t fully update the fields in the export dialog. For example, I have one preset set up to add the photos to a specific set or flickr group. When I activate that preset, the sets and groups that should be used are only *highlighted* in the list, but they are not activated. It’s as if I clicked them once, rather than double-clicking them. Another example: I have presets that I use to upload to several different flickr accounts. After using one preset for a certain account, if I switch to another preset for a second account, the photos uploaded may go to the first flickr account if I don’t manually correct the settings. (Therefore, using “Export with Preset” is useless because I can’t trust the preset’s fields to properly propagate in the dialog.)

Any help or advice you can provide would be greatly appreciated.

Orrin in Los Angeles
v.20110513.219 in LR 3.3 on 2 x 2.66 Intel Mac running OS X.6.6

Thanks for the report… I think v.221, which I just pushed, fixes it. —Jeffrey

— comment by Orrin on May 16th, 2011 at 2:29pm JST (7 years, 6 months ago) comment permalink

Export to Facebook 20110519.161 – I have an album that had too many photos in it. I parsed and it’s now well below max. Can’t figure out how to get rid of the “(NOT ENOUGH SPACE)” warning however. The plugin appears to upload the photo, but what I seem to get instead is a duplication of the previous photo already in the album.

Try refreshing the destination list (there’s a button next to the list) to update the space-remaining note. And it seems that Facebook decided to remove the ability for third-party apps to manage photos, so the plugin can upload photos, but can’t delete old copies. Facebook continues to treat third-party developers, and the users of their apps, like dirt. —Jeffrey

— comment by Scott on May 20th, 2011 at 2:45am JST (7 years, 6 months ago) comment permalink

I have upgraded to the latest version of Facebook upload plugin (as of 05/28/11) and have 1 question. Does it support uploading to FB new “groups”? They finally allow albums and I am admin on 2 groups, but cannot upload directly to them using the plugin. Maybe I am missing something. Everything else is fantastic. thank you
Janine

My plugin does support it, but if you had authorized the plugin app at FB before FB added support for 3rd-party apps to access groups, you have to re-authorize the plugin by unauthorizing it at FB then logging out in the plugin and launching a re-authorize from the plugin. —Jeffrey

— comment by Janine Eastman on May 29th, 2011 at 3:28am JST (7 years, 6 months ago) comment permalink

Hi, great picassa export plugin which has always worked flawlessly, until now 🙁

MacOS 10.6.7, LR 3.4.1. picassa export plug in 20110606.155

When exporting, its starts ok but then reports an error “retrying after mysetrious Google error ‘STORAGE_UNAVAIL’ retrying now”

what actually happens is the first picture is uploaded repeatedly rather than all the photos selected for export. I have removed the plug in, reloaded it, restarted lightroom, etc.

As the message says, that Google error is mysterious. It’ll go away when it goes away… no one knows what it means or what triggers it. It affects all upload apps, including Google’s own. Nothing to do but wait and hope. —Jeffrey

— comment by Michael Avis on June 13th, 2011 at 1:00am JST (7 years, 5 months ago) comment permalink

Hey Jeffrey,

I really appreciate all the work you do here. Just answering all the correspondence and keeping the release history updated must be a ton of work.

I’m the guy that reported a problem with the LR presets not properly updating the information in the export dialogs. Unfortunately, the problem persists. “Radio buttons” update, and flickr set and group names get highlighted per the preset, but they don’t activate.

Let me also give you a little more detail on the problem I’m having with multiple flickr accounts.

If I have been using a preset to export to flickr account “A” and then click another preset that I use to upload to account “B”, the user name in the (is that called a drop-down? I will refer to it as an interactive field) changes but it happens so quickly that I know it can’t possibly have logged into a different account and loaded the set and group names. In fact, the descriptor line just below the account name does not change. Therefore it will read

Logged in as Account B [in the interactive field]
Account A’s full name [in the descriptor field]

If I click a different account name (“Switch to: Account C”) in that interactive field, the export dialog takes a few seconds to actually connect to the requested account and it updates the sets and groups, and the description line beneath the interactive field confirms that the correct account is connected. In fact, I also get brief status messages in that area reporting that the plugin is “Fetching user information from flickr” and “fetching photo set information from flickr” during the short wait.

I hope that’s clear. Let me know if you need clarification. If this can’t be fixed, I can certainly work around it now that I understand what’s happening, but it would be really wonderful if the plugin functioned as smoothly as it used to do.

Thanks!

Orrin in Los Angeles
v.20110603.225 in LR 3.3 on 2 x 2.66 Intel Mac running OS X.6.6

Lightroom’s plugin infrastructure does not make handling this properly an easy thing, and it’s still fragile, but I think I’ve done it in v.226, which I just pushed. —Jeffrey

— comment by Orrin on June 19th, 2011 at 4:01pm JST (7 years, 5 months ago) comment permalink

I’ve noticed a problem with albums created and published to Picasa via your LR plugin. In “normal” (ie, non-LR) circumstances, creating an album on the Picasa website or using Google’s Picasa software will result in an email notification being sent out to people who have favourited me, telling them that I have uploaded new photos. However, with your LR plugin, it seems that the email notification is not sent out.
Thanks!
James.

It doesn’t seem that Google has exposed this to the API (this is the first I’ve heard about it), so I don’t think there’s anything I can do… —Jeffrey

— comment by James on July 1st, 2011 at 11:24pm JST (7 years, 4 months ago) comment permalink

Having refreshed my screen I have fixed the problem of uploading to a blank page, thanks but the photo goes to the main gallerey screen rather than the edit screen. Can I change the destination?

Also, when I click “export” to export to the Zenfolio site I now get a weird error message “An internal error has occurred:LRPhoto:getRawMetadata:must be called inside withReadAccessDo or withCatalogdo”. I click the red x button and the message disappears and I can export as usual (except for it going to the gallery screen as mentioned above).

Are the two connected. It doesn’t happen using your plug in to Flickr

I think I’ve fixed this with the new version I just pushed out… give it a try.. —Jeffrey

— comment by Greg Bond on July 2nd, 2011 at 5:57pm JST (7 years, 4 months ago) comment permalink

Right clicking on a Collection or Photo and selecting “Visit Photoset at Flickr” Generates a “Can not find the URL for this published collection”

Have been updating the last 3 or so versions of the Flickr plugin, and they all seem to behave the same.
Is this a misconfiguration on my end ?

Thanks
(Version 20110708.232 on Win 7 x64 using LR3.4.1 )

Not a problem on your end… likely a bug with Lightroom or my plugin. I’ll look into it. —Jeffrey

— comment by Adrian on July 9th, 2011 at 12:34pm JST (7 years, 4 months ago) comment permalink

1) When I delete a photo within the FB plugin, the photo will not be deleted on Facebook.
2) When modifying a photo in Lightroom it will be republished in Facebook but it will not replace the already published version of the image. In other words: the old and the new photo are existing in Facebook now (has something to do with(1)???)
3) when republishing a photo in Facebook it will be appended to the end to the album. Is it a bug or a feature? I would expect that would be placed at the same position than the already published image (something related to (2)???)

Nevertheless, thanks for the plugin!!!
Lars

Facebook does not allow you to delete your own photos via a third-party plugin. Facebook does not allow you to replace your own photos at all. There is no “republish” in Facebook’s world, so everything is a “publish” and is treated as such by Facebook. —Jeffrey

— comment by Lars on July 10th, 2011 at 9:46pm JST (7 years, 4 months ago) comment permalink

Hey Jeffery, Thanks for the Plug-in.

I’ve been using the LR 3 Plug-in for a while now and just got an error, an “internal error UTf8:57 attempt to get a nil value” I looked through past questions and found something similar for a Smugmug user and you said the error was on Smugmug. Is this the same thing, or what? I’ve never gotten this one before.

Thanks, Danen

Sorry ’bout that… just pushed a fix. —Jeffrey

— comment by Danen on July 12th, 2011 at 5:35am JST (7 years, 4 months ago) comment permalink

My Facebook Page albums are no longer available in the list of albums. It used to show my personal FB albums along with my FB page albums, and I had selected just the FB albums to be shown in the ‘Library’ view. I tried publishing some pics to one of the albums and it said “(#120) Invalid Album ID”

when I go into the FB plugin settings, they’re longer visible in list..just my personal acct albums

You could try disabling the app at Facebook, then re-enabling and then re-authenticating in the plugin, but no one knows what Facebook is up to these days, so one can only guess whether it’ll make any difference. —Jeffrey

— comment by Jim O on July 22nd, 2011 at 1:34pm JST (7 years, 4 months ago) comment permalink

When I attempt to install the flickr export plugin, I’m getting the following errors in the diagnostic log. The plugin cannot be enabled. This is with version 20110816.239 on LR 2.7. Any ideas? I am happy to help debug in any way I can.

Plug-in error log for plug-in at: C:\Users\jeff\Documents\Lightroom Plugins\flickr-jfriedl.lrplugin

**** Error 1

An error occurred while attempting to run one of the plug-in’s scripts.
Access to undefined global: RemoteJSON

I’ve pushed out a new version that should fix this. Sorry for the hassles. —Jeffrey

— comment by Jeff Mealiffe on August 18th, 2011 at 2:42am JST (7 years, 3 months ago) comment permalink

Hi Jeff,

I’m using LR3 with the latest version of you plugin. I’m been playing around with replacing existing photos with your plugin. I’m doing this because I don’t want to loose the visitor count if I deleted the gallery and reload. While the replace function seems to work on photos uploaded by your plugin (ie replace low res with higher res) it does not replace galleries where I’ve uploaded via zenfolio with that java uploader. The file names are exactly the same. The plugin ends up uploading another copy of the same image instead of replacing them. Any idea as to why this is happening? I would love to be able to replace older images with higher res version without loosing my visitor counts.

Thanks,

Ray

The “replace” feature works only with images that the plugin knows to already be at Zenfolio. If you haven’t uploaded the photo with the plugin, there are items in the “File > Plugins Extras > Zenfolio Extras” dialog that allows you to tell the plugin where each image is at Zenfolio, or to have it try to figure it out automatically. —Jeffrey

— comment by Ray on August 30th, 2011 at 6:24am JST (7 years, 3 months ago) comment permalink

Hi Jeff,

Thanks for the wonderful plugins you are making. Really makes life easier!

I am trying jf Flickr plugin and for privacy reasons I would like to prevent the City (which is managed by LR) to show up as a keyword (and of course I would still like to use that field in LR).

Any idea how I could achieve that? Even a limited number of tags I would want to remove would do it, I would only want to remove the city I live in. So the opposite of the “Extra tags to register with exported images…” would be ideal for me.

Thanks,

David

Flickr extracts the city from the Exif data and adds it as a tag, and they offer no options to control this, so the only thing I can suggest is to strip the city from the Exif on export. My Metadata Wrangler plugin can do that. —Jeffrey

— comment by Daved on September 1st, 2011 at 12:41am JST (7 years, 2 months ago) comment permalink

Howdy – love your facebook plugin. Small issue, but important to me: this week facebook made changes to photo viewer and now larger view size is available. It would seem that images being uploaded via your plugin are not displaying in the larger size in spite of the fact that I have changed the setting to 1500 pixels. What is curious is that the photos download and open at 1500 (or whatever I have it set at) meaning of course that they are on the facebook server at that size, but they don’t display at that size. I have tried different browsers and compared to uploading directly from the desktop. When I upload from the desktop – even to the same album – the photos DO display at the larger size so it seems something is going on via the plugin. As a comparison, If you go to my page, https://www.facebook.com/CrestoneCreations – the last 2 photos in the gallery demonstrate the issue. The first was uploaded via the plugin with 1500 px long edge setting. It displays “small.” Then I downloaded that exact image (it shows it is 1500×1000 – so the plugin put it up on the server at the requested size) and then uploaded the recently download image BACK to the album independent of the plugin – where it sits side by side. As you can see it displays larger. I would love for the images I upload via the plugin to display large and take advantage of the new facebook size. Thanks very much for anything you can offer on this! Regards, Clyde Lovett

The plugin allows you to upload at Facebook’s maximum storage size (2048 pixels on a side); what Facebook decides to show on the web site is up to Facebook, and from what you’ve written it sounds as if they’re artificially limiting photos that were not uploaded with their tool (or, perhaps, they’re specifically targeting me). With Facebook, you never know, and having to deal with Facebook is the price you pay for dealing with Facebook. —Jeffrey

— comment by Clyde Lovett on September 1st, 2011 at 3:48pm JST (7 years, 2 months ago) comment permalink

Hi Jeff,
I’m a new user of your flickr plugin. Just came back from vacation and saw the message that the trial period has ended. I’ve liked the plugin and decide to register via paypal (the receipt is available if you need it). Well it’s not working anymore. The only message I’m getting is the “can’t access internet……”. I can’t register and I can’t export any more photos either. I’ve deleted the plugin, update to the new version and reinstall nothing changed. You can check my flickr account if you want to see the photos I’ve uploaded with the plugin before vacations (1 month ago)
Let me know if something like that is a know issue and if there is a solution. Thanks in advance for any help
Regards Georgios

— comment by Georgios on September 3rd, 2011 at 6:03am JST (7 years, 2 months ago) comment permalink

I’m trying to replace proof photos uploaded (to Smugmug, flickr, Picasa, ExposureManager, etc). with final edited versions. If the final edited version is edited solely in LR, no problem, LR tags the image as ready to replublish. But if the photo requires edits outside of LR (e.g. in Photoshop), the moment the .psd is created LR treats this as an entirely new “photo” and it shows up in the Publish Module as a “new photo to publish” instead of a previously published photo that has been edited and is ready to replublish. To my way of thinking, the root of the problem is that one can’t stack images in Collections, and Publish uses Collections. If I could stack my images, I could put the PSD on top of the previously published RAW, and LR would mark it as an edited photo to republish, and all would be fine!

I asked on the lightroomforums site if there was some way to stack the versions in the Publish Module, and they claim this is a problem with the publishing API, rather than a problem inside Lightroom. That doesn’t make any sense to me. Can you help me understand where the problem lies, and what the best method is for fixing it?

Being able to stack images wouldn’t magically solve this problem; the root of the problem is that you’re creating a second, separate image. In this case, you know you want it to be considered the final version of the first image, but in someone else’s workflow the exact same actions might result in a completely different image that indeed should be kept as a separate image.

So, what’s required is a way for you to tell Lightroom (or, at least, the plugin) that you want the second image to swap with the first. It’s not impossible, but it’s not something that Lightroom makes easy, nor that I’ve had a lot of requests for, so it’s not bubbled to the top of the todo list. There’s an ultra-kludgy way you can handle it, but it’s really a pain: select the first image and remove it from the published collection (only in Lightroom; leave it on the remote site!), then visit the File > Plugin Extras dialog for the plugin and use the “clear” button to remove all remote data as far as Lightroom is concerned. Then select the second image and in the same plugin-extras link the online version to Lightroom via the “Manual Associate” button. Now, the second image is considered the master source for the remote version, and you can then visit the Publish Service to “populate” it back into the appropriate collection. Ugly and klugy, but that’s the best I can suggest at the moment. —Jeffrey

— comment by JC Dill on September 7th, 2011 at 5:56am JST (7 years, 2 months ago) comment permalink

Hi Jeffrey,
I have exactly the same problems like Sammuel had about 2 years ago:

“Awesome plugin for Lightroom to Flickr exporting. I use it alot or at least I did until I started getting this error. It says “Invalid API Key” and I can’t export to Flickr anymore. Everything seems to be in order on Flickr as well as in Lightroom. I have not made any changes to my hardware or software nor any patching or anything like that. I’m using Lightroom 2 by the way. Any help would be greatly appreciated as I don’t know where to begin troubleshooting this issue.”

And this was your answer: “My plugin’s key is still valid, so perhaps Flickr was having temporary issues. Just tested it and it’s fine at the moment. If you get again, please send a log via the “Send to Jeffrey” button in the Plugin Manager. —Jeffrey”

I have no idea where to begin to solve this: I’m using the latest plugin within lightroom 2, I have a pro-account on flickr and I’m using windows 7. I’ve renewed the app conection, I have removed the plugin, and reinstalled it. But I still receive the same errors. “Invalid signature”, or “Invalid API key”.

Any new ideas since then, to solve this?
Oh, I must not forget to tell you you make wonderful stuff. Many thanks!

Peter

Next time you get the error, please send the plugin log (as described here) and I’ll take a look. —Jeffrey

— comment by Peter Beheydt on September 14th, 2011 at 5:37am JST (7 years, 2 months ago) comment permalink

Hey Jeff,
I am a photographer in Charlotte, NC, US. I am trying to re-publish photos that have been edited in lightroom onto my Zenfolio site, and continue to recieve this error message: Unexpected HTTP reply from http://up.zenfolio.com/replace=333585342: 503 which will not allow me to publish the photos. Is there anything I can do to fix this?

I have the latest version of the plug-in and have tried refreshing my galleries and nothing helps. Any advice would be GREATLY appreciated! Thank you so much!! ~ Meghan

Zenfolio seems to be having sporadic issues these days… I’ve just pushed a new version of the plugin that reports the error more clearly, but it’ll be up to Zenfolio to solve the underlying issue with their servers, whatever it is. —Jeffrey

— comment by Meghan on September 14th, 2011 at 7:01am JST (7 years, 2 months ago) comment permalink

I would like to have Lightroom 3 show the entire file name in the Loup view (using one of the Info configurations). Currently it cuts it off and replaces the missing text with ellipses. I have used your font configuration tool (and others which I very much enjoy) but it doesn’t change this font or the filename field size. Is there a way to do what I am attempting? Can you add this capability to the Lightroom configuration tool?

Best regards,

Michael
http://www.michaeljoconnell.com

It’s not possible as far as I know, sorry. —Jeffrey

— comment by Michael J. O'Connell on September 22nd, 2011 at 12:45am JST (7 years, 2 months ago) comment permalink

I just installed the current version of the FB plugin and authenticated, but albums in my “groups” don’t show up (neither existing ones nor new ones). I tried both “secret” and “closed” groups with me as the admin, but no dice. Am I missing something?

The plugin can give you access only to what FB allows. For whatever reason, they don’t include everything for everyone. No one knows why. —Jeffrey

— comment by sharad mathur on November 4th, 2011 at 11:55pm JST (7 years ago) comment permalink

Win7 x64,
LR3.6
Metadada Wrangler 20111210.75
Tampa, Florida USA

Exporting JPG from Nikon NEF raw file. No matter what I do I can not get MDR to replace the JPG Capture time with the Original file’s capture Date/Time . The only date that I can get carried through the export is the “extra” section’s “set the image file’s modification date to to the image date.” For legal requirements I need the original image’s capture Date/Time carried over the the exported JPG file. (I still can’t believe that Adobe didn’t provide an option to do this.)

Hoping someone here can tell me what I’m doing wrong. Or if this is even possible. Would be great if we had a forum to help each other.

Happy New Year everyone! (especially Jeffrey for all of his unselfish hard work.)

You might try using ExifTool and my run any command export filter to copy metadata fields around as you like. —Jeffrey

— comment by Jim on January 2nd, 2012 at 12:58am JST (6 years, 10 months ago) comment permalink

Hi Jeffrey,

Lately I can’t seem to use the Twitter feature on any of your plugins (export to facebook, flickr and zenfolio. I get the following error:

Couldn’t authenticate at Twitter
Unexpected HTTP error reply #401 from Twitter

I’ve tried revoking authorization on twitter to try re-authorizing, but I get the error before I’m asked to authorize. Any thoughts? (I am using the latest versions of all your plugins.)

Thanks,

Mike

Some people get this error, but I have not been able to figure out why. Everything seems right on my end, and it works for most people, but it could somehow be a bug in my stuff or at Twitter. I’ll keep digging. —Jeffrey

— comment by Mike on January 10th, 2012 at 2:47pm JST (6 years, 10 months ago) comment permalink

Hi Jeffrey!

Dittoing others kudos to you on your fine work on your plugins! I’m a software engineer as well as a photographer, so I appreciate all your hard work even moreso.

My issues are minor, more in the line of a feature request/confusion on one, and a GUI issue on another. Let me preface this by saying I am using this on a PC under Vista (with latest service packs), Lightroom 3.6, and Zenfolio plug-in version 20120114.175 (though will update soon to your latest).

#1) GUI issue is in the portion of the plug-in dialog where the “Galleries in this Publish Service” section is. The pathing for many of my galleries is very long, and there is no ability to scroll the sub-window dialog towards the right to view whatever the text is next to the gallery pathing. I can see it says “repop no” or “repop nc” (the rightmost character seems truncated in half) with the rest of that text not appearing. Can that window have a horizontal scrollbar added to it?

#2) Feature Confusion/Request is that I see the plugin trying to republish photos that don’t really need to be despite the flags selected on what triggers a republish. For example, I may have added a minor Metadata change locally for my own searching that doesn’t need to be populated up to Zenfolio. I see no way to tell the plugin not to bother republishing an image, or de-flagging one selectively. Is there a way to do this, or can that be added? I’m still getting used to all the features of Lightroom, so I may just be missing this somewhere.

Sincere thanks for your time and efforts!

Bob

I can’t do anything about #1, since that’s all Lightroom proper, except to suggest allowing for a wider sidebar, via my (now five years old!) Lightroom configuration manager. #2 is easy… in Lr3, see “File > Plugin Extras > Zenfolio Extras” and look for “unmark for republish”. In Lr4, it’s in the thumbnail context menu. —Jeffrey

— comment by Robert Greenfield on February 17th, 2012 at 1:03pm JST (6 years, 9 months ago) comment permalink

I am using Lightroom 3.6 and your Flickr plug-in 20120221.260 (Windows 7 Home Premium 64bit). When I use your plug-in to replace a photo that already exists on Flickr, usually the replacement doesn’t happen and the photo that I have just uploaded appears at the front of my photostream. I have checked to make sure that the photo was previously uploaded with your plug-in, and the “All Plug-In Metadata” shows the proper link to the photo on Flickr in the jf Flickr section.

So, I delete the photo that was improperly placed at the start of my photostream, I clear the metadata using the Plug-in Extras for jf Flickr, associate the image manually (using the exact same link location at Flickr that was there before I cleared the metadata) and then try to replace the photo again using the jf Flickr plug-in, and this time it works.

This behavior is very consistent and repeatable, and has happened for several versions of your plug-in. I point out that this does NOT happen if I re-publish the photo that is in a Publish Service using the jf Flickr plug-in; it seems to happen only when I try to re-publish photos that are not managed by Publish Services, but were previously uploaded using jf Flickr.

Try replacing one photo, and when it fails, send the log along with a note reminding me what the problem is, and I’ll check it out. —Jeffrey

— comment by Paige Miller on February 25th, 2012 at 10:02pm JST (6 years, 9 months ago) comment permalink

Hi Jeffrey,
I live in Tokyo, Japan and have been using your Flickr plugin for Lightroom 2 for awhile now. Unfortunately today when I tried to export some photos I found that the plugin had been disabled and couldn’t be reloaded via plugin manager.
No matter what I try (deleting and reinstalling plugin, downloading latest version and performing another manual install) nothing seems to work. I couldn’t find a way to submit the diagnostic log via the plugin manager so am just copying it’s contents here. I really hope you can help with this….


An error occurred while attempting to run one of the plug-in’s scripts.
LrPrefs: attempt to write complex table value to prefs key LoginCache4::77252230@N00

Upgrade to the latest version of the plugin and you should be fine. (Now I know that there are at least two Anthony’s living in Japan, the other being my 9-year-old boy) —Jeffrey

— comment by Anthony Knights on March 11th, 2012 at 11:40am JST (6 years, 8 months ago) comment permalink

I have a problem uploading RAW files to Smug Mug. I want to keep my crop settings, exposure adjustments etc. when displaying photos in the gallery. I used both DNG and Original settings. When using Original, the pure RAW file is uploaded without cropping (surprice!). When using DNG the image is getting chopped and looks funny. Look at the first picture in this gallery. http://drjoshua.smugmug.com/Other/Original/21931593_dcDQPQ#!i=1749246731&k=9fmk876

SmugMug allows only JPGs unless you have SmugVault, so if you’re uploading original raw files, or DNG raw files, it’s to SmugVault, and what they do with it there is up to them; I don’t think the plugin has much insight into that. You should probably ask them. —Jeffrey

— comment by Håkan on March 16th, 2012 at 9:40pm JST (6 years, 8 months ago) comment permalink

Hi Jeffrey:

Thanks for your great plug-in (Picasa One). Problem: after upgrade from LR3 to LR4, plug-in seems not work, since I cannot enable it. Plug-in says “Could not read the metadata spec from this plug-in.
Plugins are disabled; see upper-right section of Plugin Manager”. I have more than 60 folders published on LR3 with your plug-in. Do I have to delete all, install the plug and re-create all of them?!. Say me no please.

Alvaro

No, you don’t have to delete them and recreate them, but you should follow the instructions give (which as you quote, is to see the upper right section of the plugin manager). —Jeffrey

— comment by Alvaro on March 19th, 2012 at 10:24am JST (6 years, 8 months ago) comment permalink

A follow-up to my comment on geocoded uploads to Flickr. It seems the issue may be linked to running multiple uploads services (sets) at once. I re-published my photo sets one at a time (had to as I switched them to Smart Sets) and the geocoded data was reset correctly on Flickr.

Cheers,
Michel

— comment by Michel Rouse on March 24th, 2012 at 4:29am JST (6 years, 8 months ago) comment permalink

Hi and many thanks up to you for your great plugins.

I have one questions regarding the Metadata Wrangler plugin. Since LR4 has the built-in map support, you can define black holes where the GPS data should not be added to the pictures. Is this planned to add support for the black holes to the plugin?

Many thanks in advanced
Christian

Lightroom doesn’t give the plugin access to that information yet. I’ve submitted a request for it, so we’ll see. —Jeffrey

— comment by Christian on April 3rd, 2012 at 5:53am JST (6 years, 7 months ago) comment permalink

hey! I’ve noticed a pretty big bug, but I don’t know who’s end its on.

I have been using this plugin for a while, but VERY recently, I’d say maybe when support for LR4 came out, any uploads I put up, nobody is able to tag the pictures.

I have recently set public in my Home page, which I believe trickles down to the photography page permissions. but still nobody is able to tag despite new album creation and new photo uploads.

have you heard of anyone with a similar issue or know another setting to change to get a fix in?

I assume you’re talking about Facebook. I’ve heard of this from a few others, and haven’t heard back on any definitive fix, but I would look carefully into the permissions set for the app, the photos, the albums, and the folks involved in the tagging. If everything seems like it should be allowed, perhaps file a bug with Facebook. —Jeffrey

— comment by Ross G on April 16th, 2012 at 3:33am JST (6 years, 7 months ago) comment permalink

Yes sir – definitely facebook. I’ve checked:

album permissions (auto set to public)
lightroom plugin permissions (set to public)
Photo permissions fall under the permissions of the album when not in “mobile or wall uploads” so there is nothing to check there.
the people trying to tag have my page liked, so they should be able to.

We’ve filed a bug with facebook, but I expect to hear nothing back from them.

BTW – we are from NY here 🙂

thanks for the response!

— comment by Ross G on April 16th, 2012 at 7:38am JST (6 years, 7 months ago) comment permalink

I am using your latest SmugMug plugin to publish some photos to SmugMug which contain GPS coordinates. I check remove location info (they are also inside a private location in LR4). No matter what I do, the GPS data seems to still make it to SmugMug. I even tried metadata wrangler and the GPS data still stays around.

In Lr2/Lr3 it made sense for the plugin to always explicitly include the location, but now that Lr4 supports proper geoencoding, I’ve changed the plugin (as of version 20120423.224) to not explicitly send the location in Lr4+, so now the location is sent within the image if it’s there, and not sent if it’s not, so Lr “private” locations should now be respected. —Jeffrey

— comment by Mark Goddard on April 22nd, 2012 at 1:36pm JST (6 years, 7 months ago) comment permalink

Hi, many thanks for your excellent work.

I noticed a small bug with this Plugin: When the only change made to a picture in LR4 using the MAP module, the update is recognized by the plugin but are not published.

Editing other metadata will solve it, e.g. GPS location EXIF data appear in Flickr.

With kind regards, Claude

This is a known bug that’s been reported to Adobe, but no word on when/whether a fix will come…. —Jeffrey

— comment by Claude Schidlknecht on April 22nd, 2012 at 4:18pm JST (6 years, 7 months ago) comment permalink

There seems to be an ongoing problem with tagging on Facebook for pages. If I upload photos via the the plugin nobody except for me, the owner of the photo can tag it. If I upload the photos directly through Facebook anybody who has liked my photo can tag it. I’ve got the plugin permission such that photos should be public and people can see them just fine. They just can’t tag them.

I’ve heard about this recently but don’t know what happened, though I suspect it’s related to how various components of Facebook combine their privacy settings. I know it’s a change at FB because it was retroactive… images uploaded years ago with the plugin suddenly couldn’t be tagged anymore. Look at the app/gallery/image privacy settings, and if you figure it out, please drop a note. —Jeffrey

— comment by Steve Stearns on April 23rd, 2012 at 7:01am JST (6 years, 7 months ago) comment permalink

Photos Marked for Re-Publish Not Getting Published – I found a solution.

I started to send the de-bugging log but it was huge… You might already know about this, but if I mark a photo to re-publish it moves up to be published. Once I click the publish button, it goes through the motions as usual (but much faster)… when I look on Flickr, the photo has not been uploaded.

I had this happen several times for different photos. I experimented to find a solution and finally discovered that by going to File > Plugin Extras > Flickr Extras > Then clicking “Clear” to clear the uploaded to Flickr flag, that solved the problem.. Next time I marked the photo to be re-published, it was published correctly.

Oh, and I am from the metro Atlanta Georgia area. Your Flickr plug in, and all your plugins that I have seen are awesome!

Thank you so much for your work.

The problem with that is that it sends a second copy, rather than replaces the original. I’ve got some new info from Adobe recently that might help me solve this problem in general, but I’d take care with your solution until you’re sure you’re okay with the ramifications. —Jeffrey

— comment by Bud on April 23rd, 2012 at 10:45am JST (6 years, 7 months ago) comment permalink

My Flickr plugin is disabled and i keep getting these messages

Plug-in error log for plug-in at: /Users/Peter/Library/Application Support/Adobe/Lightroom/Lightroom PlugIns/flickr-jfriedl.lrplugin

**** Error 1

An error occurred while attempting to run one of the plug-in’s scripts.
LrPrefs: attempt to write complex table value to prefs key LoginCache4::50807374@N00

This exact issue is covered a few comments above. —Jeffrey

— comment by Peter on April 23rd, 2012 at 8:25pm JST (6 years, 7 months ago) comment permalink

Error reply from Facebook: I fail at picking lvols 🙁

Not sure what this means although the seamless upload that occurred before updating to LR4 & registering & donating for the upgrade bugs fixed…

what am i doing wrong?

This was bug at Facebook, which I’ve heard is now fixed. —Jeffrey

— comment by elstudio.pro on May 16th, 2012 at 12:50am JST (6 years, 6 months ago) comment permalink

Hi Jeffrey,
Just re-installed your Facebook on a new Win 7 running LR 2.7 and it will not load all the photo albums in the “Upload Destination” box. It only is showing the latest 2. I tried creating a new album and that doesn’t show up either. Refreshing the list doesn’t help. I have reloaded the plugin multiple times after restarting Lightroom to no avail. The new (empty) album does show up in Facebook (so it is creating new albums fine) but I can’t see it to select it as a destination for export. Any suggestions?

Check out this FAQ. —Jeffrey

— comment by Andrew on May 21st, 2012 at 7:45am JST (6 years, 6 months ago) comment permalink

Emailing from Markham, Ontario. Canada.

Since upgrading to LR4 – I’ve also updated the LR facebook plugin (using version 20120614.210)

When uploading a batch of photos as small as 8 photos, I’ve gotten this error message from the plugin:

Debug 1169: Unexpected HTTP status from facebook.com: 502
Got EOF while waiting for outstanding responses

in LR3 (v3.7) the upload process was very smooth with any errors – I’ve encountered the error above with almost every batch upload since upgrading to LR4. Any idea where this problem could be originating from or if you’ve heard of other reports?

Have not heard reports. Could it be some kind of security app on your system that was told not to diddle with Lr3 stuff, and needs to be told the same for the Lr4 app? —Jeffrey

— comment by Michael on June 23rd, 2012 at 4:57pm JST (6 years, 5 months ago) comment permalink

Hi Jeff! This morning I been successfully exporting photos from LR4.1 to my Facebook page https://www.facebook.com/PatrickRosalbaPhotography without any hitches. Later this afernoon when I tried to upload a new photo and also to update an existing photo I got this error msgs:

Debug 1169: Error reply from FB:(#240) Requires a valid user is specified (either via the session or via the API parameter for specifying the user.

As far as I know I’ve changed nothing with regards to the FB Publishing Service for this FB page which is linked to my personal FB user profile Patrick Rosalba. But I have updated by antivirus Avast in between. Can you help ?

Facebook Export Pugin for LR v.20120614.210
OS: Windows Vista 32bit SP2
AV: Avast 7.0.1451

p.s. I am based in London, UK.

thanks!

I’ve added this as a known issue… we just have to wait for FB to get around to fixing it. —Jeffrey

— comment by Patrick on July 2nd, 2012 at 2:45am JST (6 years, 4 months ago) comment permalink

I am trying to upload photos to my facebook fan page, I have had sucess with this in the past, but for some reason now im getting this error dialogue.

Debug:1169: Error reply from Facebook: (#240) Requires a valid user is specified (either via the session or via the API parameter for specifying the user.

I have tried looking over your FAQ and known issues but cannot seem to find a solution.

Facebook seems to be having issues… other users of other apps have reported the same problem suddenly. We just have to wait, hoping they address it. —Jeffrey

— comment by Oliver Winter on July 2nd, 2012 at 11:40am JST (6 years, 4 months ago) comment permalink

My previous comment regarding the error:

Debug:1169: Error reply from Facebook: (#240) Requires a valid user is specified (either via the session or via the API parameter for specifying the user.

I found out the fix.

Access your facebook fanpage when you are logged into your personel account. There is a new “voice” section and make sure “You are posting, commenting, and liking as the fanpage” not as your main profile. This will stop the error #240.

Hope that helps

— comment by Oliver Winter on July 2nd, 2012 at 11:38pm JST (6 years, 4 months ago) comment permalink

Seems to be working now (July 2nd, 2012)- I started paying very close attention to the security settings in LR4 and Facebook – I wonder if that’s the reason why I started encountering this Debug: 1169 problem?

— comment by Michael on July 3rd, 2012 at 5:48am JST (6 years, 4 months ago) comment permalink

I clicked to update the plugin, and after updating received: Your version of Lightroom, Lr3.4, is too old for this version of Jeffrey’s “PicasaWeb” plugin. Please visit “Help > Check for Updates” in Lightroom to download the free Lr3 update from Adobe.

Can you please code your plugins to check the version for compatibility BEFORE it updates? I have no idea how to undo the update and reinstall a working plugin. 🙁 Trying to get your LR plugin to work with Picassaweb has been a real bear. (*not* happy)

The problem is that I don’t know what incompatibility will develop in some future version when pushing out a version now, so it’s not like I could have known when I built the version you have what would develop later. And even if I knew, I don’t want keep workaround for bugs that have been fixed just so someone can avoid the two minutes it takes to apply the free update from Adobe. —Jeffrey

— comment by JC Dill on July 3rd, 2012 at 4:18pm JST (6 years, 4 months ago) comment permalink

RE: Debug:1169: Error reply from Facebook: (#240) Requires a valid user is specified (either via the session or via the API parameter for specifying the user.

Thanks Oliver for your fix / workaround suggestion! that seems to work okay now!
I don’t know if this is still a bug still on the Facebook side of things, but I will
go with this fix for now.

— comment by Patrick on July 4th, 2012 at 5:18am JST (6 years, 4 months ago) comment permalink

Okay, I understand what Oliver was referring to. I was looking for a literal “voice” section instead just changing under the page to “You are posting, commenting, and liking as [insert your page here]” fixed it.

thanks from Salt Lake City

— comment by Clayhaus on July 10th, 2012 at 6:16am JST (6 years, 4 months ago) comment permalink

On the “Filetype not recognised” issue some users are having with Flickr…

In some cases, large file sizes may be causing it. I’ve been scanning negatives into TIFF files, compressing them using DNG, editing in Lightroom, and then finally uploading them. The DNGs typically are around 35MB, but some are significantly larger. I’m getting the “Filetype not recognised” error on the big ones. If I skip them, I can upload normally.

Obviously, the API should return an error relating to the size of the photo, rather than the file type, but the problem could stem from the chunked fashion in which photos seem to be uploaded. One chunk that goes awry will look to Flickr like a bad file type.

This thesis has one flaw, however: I get the same error even when reducing the quality level to 10, which theoretically should reduce the file size significantly. I’m not sure what to say about that. Perhaps Jeffrey can set me straight…

One can only speculate… FLickr is a black box, so Lord knows why they complain on some images that seem fine. The chunked uploading in Lr4.1 is not chunked as far as Flickr is concerned… it’s just an internal Lightroom/plugin optimization, so I doubt that has anything to do with it. From what I can tell it seems to be random, but if you can find one image that always results in an error, I’d like to try to reproduce it, so I’d appreciate it if you could export the one image as its own catalog (being sure to include the negative file and exclude the previews), then zip it up and mail it to me along with details on the upload settings…. —Jeffrey

— comment by Brent on July 12th, 2012 at 5:10am JST (6 years, 4 months ago) comment permalink

Hi Jeffrey,

I’m from Seattle, Washington, USA and have quite a large number of images and sets posted from Lightroom to Flickr via the basic adobe plugin. I’ve successfully used your sync option to bring these into the jf local photostream but can’t seem to bring in the sets/folder names. Is it possible to do this automatically or for that matter manually? Despite you having written excellent documentation, I did not see any documentation or web discussions about this specifically and wasn’t sure if my sync is not working correctly or it is simply something that is not supported.

Thanks for your feedback and for creating these fantastic plugins!

Michael

You didn’t miss anything… it’s all manual at this point. I think it’s time I looked into a bulk creation tool of some sort, to make a 1:1 mapping from set to collection… —Jeffrey

— comment by Michael Cline on July 24th, 2012 at 9:52pm JST (6 years, 4 months ago) comment permalink

Hi Jefferey,

I’m using your most recent Flickr plugin and Lightroom 4.1 but whenever I upload videos (larger than say, 100Mb) I get the following error:

Error during export

Unexpected reply from Flickr:
oauth_problem=timestamp_refused

Aborting export before any image was successfully uploaded.

Thanks for you great plugins!

Mark

That’s a side effect of a slow/poor network connection…. by the time the upload completes, the security signature is too old to be accepted. I’ve seen it a couple of times suddenly this week, so the slowness could be on Flickr’s side. If it persists, I’ll have to have the plugin recognize the situation to report it more gracefully. —Jeffrey

— comment by Mark on August 24th, 2012 at 9:01pm JST (6 years, 3 months ago) comment permalink

Would it be wise for me to report this to flickr?

Mark

I don’t think they would even respond. Networking issues are usually on the user’s side (maybe your router needs to be rebooted, or your security app told to lay off Lightroom’s networking, etc), and are difficult-to-impossible to remote-diagnose. —Jeffrey

— comment by Mark on August 25th, 2012 at 10:11am JST (6 years, 3 months ago) comment permalink

Hi, I noticed on this comment page you were still diagnosing the HTTP Error 401 Unauthorized. My girlfriend recently encountered this error while using the Flickr plugin for Lightroom, immediately after clicking the “Authenticate to Flickr” button. By analyzing in Wireshark we discovered that Flickr was returning a timestamp_refused response. It turned out her computer’s system time was 12 hours off, and this was causing the OAuth request (based on it) to be rejected. It would be helpful if a clearer error message suggesting to check the system time were supplied in this case. Alternatively, the plug in could retrieve the current time from a well-known time server instead. Note: the Flickr plug-in that comes with Lightroom has the same issue, with even less useful diagnostics.

That’s just one reason for the refusal, but doesnt’ apply to my plugins because my plugins check your clock and report to you if your clock is off. I implemented that after having my time eaten debugging yet another person’s issues where it turned out that their clock was exactly one year or one month off. —Jeffrey

— comment by Derrick Coetzee on August 25th, 2012 at 1:13pm JST (6 years, 3 months ago) comment permalink

I am getting some odd errors when uploading to smugmug where exports just stop as if they were cancelled. Occasionally I get a message asking if my internet is down…note there is no other indications of my internet connection being faulty with video streaming or ftp downloads or vpn interruptions and lost connections. I did not have this problem prior to upgrading to LR4 64 bit from LR4 32bit.

It’s probably some odd error that the plugin is not reporting sensibly to you… next time you see it, please send a log and I’ll take a look. —Jeffrey

— comment by Clark on August 28th, 2012 at 10:46am JST (6 years, 3 months ago) comment permalink

Hi Jeffrey,

In attempting to visit a published photoset at Flickr I get a “Can’t show this published collection. Can not find the URL for this published collection.” error. I notice somebody else mentioned this in July last year. I’m logged in to Flickr, and can see the published collection in my browser if I visit it outside of the Lightroom shortcut.

I can successfully visit individual photos by the ‘Visit Photo at Flickr’ option, but not the photoset. Any ideas what might be happening?

Running L$ 4.1 on Mac OSX 10.7.4.

I don’t recall the specific technical details, but I was not able to get that to ever work when I first developed the plugin. I should revisit it, but the best bet at the moment is to view one photo, then take the link from that page to the set. —Jeffrey

— comment by Tim Lumsdaine on August 28th, 2012 at 5:03pm JST (6 years, 3 months ago) comment permalink

Jeffrey: Hello from Scottsdale AZ: Last night I was unable to upoload images from Lightroom 4.1 to Zenfolio. I have uninstalled both your plugin and Mogrify/Imagemagik, but still get the message from Lightroom — “couldn’t render image: The post-processing filter failed to render the file.” I have been using your plugin for years it seems without trouble. Thoughts?

Regards,
Peter

This is what happens if you feed raw files to the Mogrify plugin… you’ve apparently got the export format set to “Original” by accident. Mogrify can’t handle raw files. Tim’s been alerted, so hopefully future versions will handle this more gracefully. —Jeffrey

— comment by Peter Cohen on August 28th, 2012 at 10:56pm JST (6 years, 3 months ago) comment permalink

plugin generates an error and does not work!
flickr # 282 +5976.6: [21a33e68] @ Export line 832:
Missing destination cookies:
[21a33e68] @ Export line 832:

what do I do?

This “Missing destination cookies” bug is rare, and I think a result of Lightroom corrupting the collection data. The only solution I know is to delete and re-create the collection. )-: —Jeffrey

— comment by Uriy on August 31st, 2012 at 7:12am JST (6 years, 3 months ago) comment permalink

delete and recreate the collection did not help!

That’s unfortunate… maybe the catalog corruption extends to the whole publish service? When it comes to this kind of corruption, anything can break, so it may be best to try recreating the whole service. And to do a consistency check on the catalog. —Jeffrey

— comment by Uriy on August 31st, 2012 at 3:38pm JST (6 years, 3 months ago) comment permalink

Hi Jeff,

Having a regular problem with the LR 2 Facebook plugin. I’m Using LR4 on an IMac (OSX). The publishing process seems to freeze after a few uploads. The only way I can get it to kick off again is to Quit LR4 and restart the process.

Any suggestions as to why this is happening?

Look forward too hearing from you.

Definitely does not sound normal… do you know where it’s hanging up? If it’s during networking, there’s not much I can do but suggest the standard things like “reboot your router”. Otherwise, perhaps send a log after a failure… —Jeffrey

— comment by Stephen on September 17th, 2012 at 1:20am JST (6 years, 2 months ago) comment permalink

Hi from Georgia, USA. I’ve been using your plugin for Lightroom for about 6 months without issue. However, for the past month or two, I have been unable to publish my pictures to my Zenfolio site. I am running the latest update of LR4 on a iMac running the latest Mac OS X with all updates applied.

I consistently get the following message:

Debug:1205: timedOut

Network timeouts indicate a problem with your network, the destination system, or something in between. Please don’t report them to Jeffrey because there’s nothing he can do about them.

I understand the last sentence but because this has been going on for so long now, I’m beginning to wonder if this is a problem with the plugin or not. In that regard, I decided to report it to you because the problem continues to surface.

I am on a broadband cable connection and I can upload my pictures to my Zenfolio site by going on the webpage and uploading them manually but that defeats the purpose of having this plugin to begin with.

Is there any advice you can offer?

Tim

Sorry, no, there’s really nothing in the plugin that will unilaterally decide to go slow. It’s likely something with your system, your router, or your network, but there’s no way to guess from here. —Jeffrey

— comment by Tim S. on October 15th, 2012 at 1:22am JST (6 years, 1 month ago) comment permalink

Just upgraded to 20121020.205 and am now getting this error when trying to publish an album to Zenfolio:

zenfolio#205 +686.2: [x16c2fa038] @Export line 849:
Missing destination cookies:
[x16c2fa038] @Export line 849
[x16c2fa038] @Debug line 1254

Then, when I click OK, I see this:

Debug:757: Assert @Debug:757

As with other user above, deleting and recreating the album I was trying to publish did not help. I haven’t had any trouble using your great plugin before with publishing to either Zenfolio or Facebook.

Any thoughts?

Thanks for the great plug-in! Hope this will be easily fixed.

See this FAQ. —Jeffrey

— comment by Aaron on October 29th, 2012 at 4:54am JST (6 years ago) comment permalink

On LR4.1 on Mac and using plugin 20121020.205 getting 2 errors on Publish.

I think it might have something to do with Comments? Photos seem to upload fine, but the error is cryptic to me.

First Error
http://bit.ly/QR6koG

Second Error
http://bit.ly/QR6nAE

Oops, thanks… I’ve just pushed a fix. —Jeffrey

— comment by Chris on October 30th, 2012 at 11:41am JST (6 years ago) comment permalink

Just registered this plug-in. Great work. Question: Photos uploaded only reflect the original photo and they do not reflect any “develop” work I performed on them. The develop work was done before publishing via your plug-in. Is there something I can set to upload the developed version vs the original? I use plug-ins from 500px and Flickr and they always upload the developed version. Thanks for your assistance.

I don’t know which plugin you’re speaking of, but in any case, it sounds like you have “Format” set to “ORIGINAL” instead of “Jpeg”. —Jeffrey

— comment by Chuck on November 1st, 2012 at 11:20am JST (6 years ago) comment permalink

Hi Jeffrey, I’m getting more and more of these errors when trying to upload pics on Facebook: “Debug:1169: Unrecoverable server error at Facebook.com (it returned a normal web page instead of the proper API reply). Any idea on how to resolve that? It’s quite random, really. Usually the error will happen right after the upload suddenly stops (percentage stays still). Thanks

No, sorry, I share your frustration. —Jeffrey

— comment by Disinto on November 2nd, 2012 at 2:12am JST (6 years ago) comment permalink

Hi Jeffrey, I just registered ZF plugin 20121020.205 – it’s very useful and I love having data authored in “one” place (Lightroom). However, under “metadata that triggers a republish” I have nothing checked, yet when I change copyright or title, images are marked to Publish. I just want to update the metadata with Plugin Extras > Zenfolio Extras without re-uploading to image.

It’s easy to undo this with Mark as Up-to-date, but would rather not have that extra step. Thanks.

This is all handled by Lightroom internally, and has always been flaky. Drives me nuts. )-: —Jeffrey

— comment by Kevin on November 2nd, 2012 at 5:16am JST (6 years ago) comment permalink

Hi,
I’ve tried to install the LR4 plugin about 6 times. LR isn’t finding the PI. I’ve deleted and re-downloaded, unzipped etc….still can’t find it.
I can send you screen shots of the item list in the folder, but nothing displaying with .lrplugin ext.

Not getting an error message, just not finding the file :-/

I’m not sure what to tell you… when you download the zip file, your browser should leave a zip file on your disk, or perhaps unzip it for you to leave the *.lrplugin folder. This is all between you and your browser… Lightroom gets involved only when you tell the Plugin Manager where that *.lrplugin folder is. —Jeffrey

— comment by Shannon on November 4th, 2012 at 4:45am JST (6 years ago) comment permalink

Jeffrey, any pointer on the error I mentioned? Can’t we get more debug info from your plugin? I’m now virtually unable to use it since the upload process crashes so often. Extremely frustrating.
Thanks

You can try turning on enhanced logging and send a log and I’ll take a look, but I suspect it’s just Facebook being Facebook. —Jeffrey

— comment by Disinto on November 17th, 2012 at 8:29pm JST (6 years ago) comment permalink

Hi, I’m from London.

I’m having trouble with the Facebook plugin at the moment, the plugin creates an album, and when it tries to upload the photo, it gets error ‘networkConnectionLost’, Retrying…

It never managed an upload, did Facebook change it’s API so upload photo no longer works?

Please see this FAQ —Jeffrey

— comment by Stephen Lok on December 12th, 2012 at 7:29am JST (5 years, 11 months ago) comment permalink

Is there a limit of photos allowed to upload on the Flickr export? I had 400+ and I keep getting an error message and then it says “retrying”. I’m wondering if I did something wrong on the install or if it might have something to do with the number of pics being exported at once?

Thank you!

There’s no hard limit by the plugin or Lightroom, but Flickr and/or network flakiness often conspires to add hiccups. —Jeffrey

— comment by Sara on January 22nd, 2013 at 11:05pm JST (5 years, 10 months ago) comment permalink

Hello,

I’ve been getting an error for the past few months when uploading using the PicasaWeb plugin. The error I get is “Unexpected HTTP status from Google: 500”. It’s sporadic and all I have to do is acknowledge it and hit Publish again to continue my upload. This is not an issue most of the time but it makes it difficult to leave my computer when I’m uploading a large amount of photos. Any idea what this could be? I did a search on google for a similar error and the few things posted about it are very vague. Thank you for your help.

Paul

Google has its ups and downs, and they fail for a variety of random sporadic reasons. The problem about retrying these unknown “500” errors is that “500” means that the service is broken, it’s not necessarily the right thing to retry. But Google has gotten so flaky of late that it’s perhaps worth considering….. —Jeffrey

— comment by Paul on February 4th, 2013 at 12:14am JST (5 years, 9 months ago) comment permalink

Hello,
I’m currently testing both your Lightroom export plugins for facebook and flickr.
I am having a huge problem with the facebook plugin, however:

Republishing results in duplications instead of updates in Facebook.
When, e.g. I make the smallest change the image is set for republication. However the previous version stays at facebook, so that a new copy appears in the albums with every republishing.

At flickr, the previous copy is repaced and everything works as expected.

Please help…

All the best

Andreas Wistuba

That’s how Facebook has decided it works. That’s why I suggest not using Publish for Facebook on its docs page. —Jeffrey

— comment by Andreas Wistuba on February 7th, 2013 at 9:22pm JST (5 years, 9 months ago) comment permalink

Dear Jeffrey,
thank you very much. Hopefully, Facebook will change this. Do you think that there is hope?

Anyway, in you document, you write:

“Thankfully, Publish is an extra feature in addition to the “normal” export offered by Lightroom via this plugin (and earlier versions of this plugin). Most users should use the normal export to send images to Facebook.

Because Publish involves setting up an ongoing relationship, it’s more complicated than simply firing off an export. The length of this document, which covers only Publish and assumes you’re already familiar with normal export, attests to the extra complexity. But once the initial up-front fee has been paid with your time and attention, you’ll reap the benefits from then on.”

Well, to be honest, I think I know how to use your plugin to publish, with the nasty problem I ran into, but I have no clue, how to simply export without creating a relation.
Is this described anywhere?

Best regards and sorry for so many questions.

Andreas

“File > Export”, or the big “Export” button (where the “Publish” button is when not in a Publish Service). You can create an export preset that encapsulates your desired settings, if you like. —Jeffrey

— comment by Andreas Wistuba on February 8th, 2013 at 2:43am JST (5 years, 9 months ago) comment permalink

==================
STEPS TO REPRODUCE
==================

a. File
b. Export
c. right click on top of dialogue box => “jf Zenfolio”
d. scroll down to “Zenfolio: Metadata Management”
e. select the “Extra keywords to register with exported images…” textbox
f. try to create a token by pressing
{
g. The following error is displayed:
“Access to undefined global: CURRENTLY_EXPORTING_EXPORT”

=======
CONTEXT
=======
Windows 7 Pro SP1
Lightroom 2.7 (64 bit)
Export to Zenfolio plugin (v 20130206.214)

Have already submitted log file via the “Send To Jeffrey” button.

Thanks for the heads up. It’s an Lr2-only bug… I’ve pushed a fix. —Jeffrey

— comment by Pressacco on February 8th, 2013 at 12:43pm JST (5 years, 9 months ago) comment permalink

Sent you my log earlier today:

Tried 5-6 times to upload to an album on facebook (OSX 10.7.4, LR 4.3, CR 7.3)

Froze overnight at picture 7, in the “finalizing stage”
Froze in the morning at picture 14 in the “finalizing stage”
Froze later in the morning at picture 16 in the “finalizing stage”
The next freeze was in the finalizing stage, this time accompanied with a pop-up box about the “dreaded empty response”
Cleared log, set up export again. This time when it froze it froze during upload with a pop-up box “Facebook returned a normal page”

Finally resorted to a HD export and old fashioned facebook upload.

Facebook seems really flakey of late. Not much we can do but hope they fix it. )-: —Jeffrey

— comment by Kyle on February 23rd, 2013 at 11:18pm JST (5 years, 9 months ago) comment permalink

hello Jeffrey,
thanks for creating the Picasweb plug-in, very useful.
A question: if I delete a published album in Lightroom, nothing happens on the Picasweb side, I have to delete it seperately.
Is this as intended?
rgds, Cees

That’s the way Lightroom works… if you delete the individual photos, the plugin offers the option to delete them remotely, but if you delete the collection, it’s just gone. —Jeffrey

— comment by Cees Wouda on February 25th, 2013 at 12:41am JST (5 years, 9 months ago) comment permalink

thnx for the immediate answer, Jeffrey.
Deleting individual photos works via republishing.
Then just as a comment:
when deleting a complete published collection I get a question from Lightroom if I want to delete pictures on the service or not. Aparently this question is not making any sense.
rgds, Cees

Oh, if it’s asking, I guess I was wrong… (it’s been a long time since I was in that part of the code). If it’s asking, but not actually deleting, that would be a problem. If you run into it again, please send a log… —Jeffrey

— comment by Cees Wouda on February 25th, 2013 at 7:52pm JST (5 years, 9 months ago) comment permalink

Just installed the update for the lightroom plugin, i ran in a few issues wiht the auto install, as i run my vista account as a user and not admin, so the auto update ran into issues. I temporary changed my accout to admin to do an auto update, this saved me running lightroom under admin and getting catalog issues (new user new cat not good, requires extra cleanup to be done). Just a note to anyone else having an update issue.

— comment by Andy on March 18th, 2013 at 2:39am JST (5 years, 8 months ago) comment permalink

Hi Jeffrey

Love your plug in. However I registered it today and it no longer works…

It lost the Picassa user info so I tried to re-authenticate but it comes up with “Picassa Web logon aborted: Wrong User” message. I appear to have registered using my old Google account.

Is there anythign you can do?

Kind regards

Atu Saito

Log out in the plugin, then make sure you’re logged in to the proper account in your browser, then reauthenticate from the plugin. —Jeffrey

— comment by atu on April 2nd, 2013 at 7:18pm JST (5 years, 7 months ago) comment permalink

I’m trying to authenticate at twitter the Flickr export pluggin. I get a 7 digit pin code from the twitter website which I paste onto the LR dialog box. However, every time I try this (I’ve tried many times) I get “Couldn’t authenticate to Twitter: Wrong PIN”

Any ideas?

This was due to some inexplicably disrespectful moves by Twitter developers. I finally figured out what they did and worked around it, and have pushed a new version of the plugin. —Jeffrey

— comment by Pedro Castillo on April 9th, 2013 at 8:32am JST (5 years, 7 months ago) comment permalink

I just got done completely clearing my computer and re-installing all the programs. Upon trying to put your plug-in for Zenfolio back into my Lightroom 3 I got an error message saying my Lightroom version is too old to work with your plug in. Being able to export to Zenfoliois not an option on the list, but I can’t get it to enabe.

Upgrade to the latest version of Lr3. —Jeffrey

— comment by Christian on April 22nd, 2013 at 9:34am JST (5 years, 7 months ago) comment permalink

After using the zenfolio plugin for 6 week had the “cannot upload more than 10 photos” registration notification. I registered the plugin and enter the right value in the plug-in manager and it tells me I am good to go. However when I try and upload a batch of 22 photos I still get the “cannot do moe than 10” error. I ahve restarted LR, relaoded the plugin, restarted the comptuer etc. I am using LR4.4, plugin 20130412.231 on windows 7. I am also sending a debig log (not sure if that helps)

Thanks for any assistnace you can provide — I really do enjoy and depend on your plugins
Eric

Could it be another plugin that’s causing the 10-photo limit? —Jeffrey

— comment by eric on April 29th, 2013 at 9:06am JST (5 years, 7 months ago) comment permalink

I live in Colorado.

I’m trying to use the Metadata Wrangler plugin to preserve the camera metadata (e.g., AF Area Mode, AF Number of Points, AF Number of Points In Focus, etc.) to use in an iPad app called PhotoMeta.

I’m creating and publishing a collection in Lightroom 4, and setting all the Metadata Wrangler options to preserve the metadata. I’m using iTunes to sync the collection with my iPad. When I try to view the metadata in the iPad app (PhotoMeta), it’s not there.

I have a Canon Rebel T3i. I often shoot in RAW, but even when I shoot in JPG, the metadata I want is available on the original image.

Do you have any idea what I’m missing in the setting?

Thanks!
Susan

If you want to preserve all metadata, just omit the Metadata Wrangler altogether, and you’ll get all the metadata that Lightroom includes in an exported copy. Lightroom does not, though, include the Maker Notes section, which is proprietary to each camera make, and that’s where the non-standard fields like “Number of AF points” would be. I don’t think there’s a way to get them into exported copies. )-: —Jeffrey

— comment by Susan on April 29th, 2013 at 2:16pm JST (5 years, 7 months ago) comment permalink

Hi Jeffrey – I LOVE your plug in and have been using it for years. I just got a new iMac and everytime I have tried to export to SmugMug I get “Debug:1169: networkConnectionLost” and the connection drops out. Never had that before…. any thoughts or suggestions? Thank you!

Maybe a security app on your system needs to be told to give Lightroom unfettered access to the network? —Jeffrey

— comment by Sarah on May 1st, 2013 at 11:04am JST (5 years, 6 months ago) comment permalink

When I upload a large (>100mb) video to picasaweb using the plugin, I get an error that Picasaweb only allows videos <=100mb. However, in the Google FAQ I see two different numbers. At https://support.google.com/picasa/answer/1224181, it says all videos up to 15 minutes long are fine, while here https://support.google.com/picasa/answer/43879?hl=en it says the limit is 1gb. But both of these limits are much larger than the 100mb error the plugin is returning.

Is the error coming from the plugin or from google? Perhaps they used to have a 100mb limit and you thoughtfully built-in a check for these large files before uploading (but that limit should be updated)?

Thanks for your great plugins!

Adam – Connecticut, USA

Google imposes a 100mb limit for third-party uploaders like the plugin (as per this page). )-: —Jeffrey

— comment by Adam on May 10th, 2013 at 4:54am JST (5 years, 6 months ago) comment permalink

Can you add the capability to match on ad-hoc fields besides date/time? It would be nice to be able to say, match these photos if X lightroom metadata field matches Y flickr metadata field. Perhaps set via dropdowns in a list. In my case, the picture title is the same as the file name (excluding the extension), and would give a 1:1 match.

Thoughts?

A good idea, but a bit more involved than I can do right away. Added to the todo list. —Jeffrey

— comment by Leif on May 16th, 2013 at 4:48pm JST (5 years, 6 months ago) comment permalink

PicasaWeb is a much needed Lightroom plugin. I’m attempting to perform account setup and am encountering an error. Here are my steps:

– In LR Publishing Manager, Your PicasaWeb Account, click on Authenticate to PicasaWeb
– Dialog appears: You must visit Google to grant this plugin permission…. Click OK.
– Firefox tab appears: Jeffrey’s Lightroom plugins for PicasaWeb and Google Drive is requesting permission to: …. Click Allow Access.
– The web page changes to “An access token has been sent to LR…. Token is shown. Plus a dialog appears: This link needs to be opened with an application. Send to: Adobe Photoshop LR. Click OK.
– No opportunity to paste the token appears. Instead a dialog appears saying: Lightroom. Error. PicasaWeb login aborted: Unexpected HTTP status from Google” 404 Unknown user.

However, I’m logged in on Google+ and have a page open for my Picasa albums.

It’s a bit of a mystery and has occurred five times. Could you help?

Thanks, hope your family is doing well.

Jack

Lightroom should have installed its URL handler to your OS, so you shouldn’t have to have picked Lightroom as the application to handle the link. Reinstalling Lightroom may help that. As for the 404 you get, I’ve not seen that particular error before… perhaps send a log next time you get it? —Jeffrey

— comment by Jack H. on May 28th, 2013 at 11:30am JST (5 years, 6 months ago) comment permalink

I am having trouble uploading videos to Flickr with this message:

Unexpected reply from Flickr:
oauth_problem=timestamp_refused

You say this has to do with the speed of the network connection so there is probably not much you can do.
But you could help:
– Don’t abort the whole upload if one image fails. Try to upload the other files in the batch and at the end show a report that shows which files worked or didn’t work.
– In general it would be nice to be able to see a list that shows which files got uploaded recently and their status. That way we can at least know which files need to be retried.

What do you think?

I think you need to check your system clock. It’s probably off significantly, and the plugin probably warned you of such. Believe it. You can partition by the uploaded-or-not status in the Library filter. —Jeffrey

— comment by Hans on June 7th, 2013 at 12:23am JST (5 years, 5 months ago) comment permalink

I think you need to check your system clock. It’s probably off significantly, and the plugin probably warned you of such. Believe it. You can partition by the uploaded-or-not status in the Library filter. —Jeffrey

Jeffrey, my clock is set to synchronize with NIST so it should be up-to-date. It’s certainly within a second from the time my cell phone shows.

I haven’t seen a filter for uploaded status. Is this a Lightroom filter or do you mean the filter in your plugin that allows to select all/modified/new?

Don’t you think a simple log that shows which file has been uploaded when/where/successfully (or not) would be helpful?

I’ve had people respond as you do about the clock, only to realize later that it was off by a year, so do double check. 🙂 The filter is in the “Metadata” section of the Library Grid filter… “Uploaded to Flickr”. You can also use that in smart-collection rules. —Jeffrey

— comment by Hans on June 7th, 2013 at 1:53am JST (5 years, 5 months ago) comment permalink

Jeffrey, I’m getting a constant and erratic “Assertion Failed” notice popup whenever I try to upload a bunch of photos to Flickr. This has only started happening recently.

And while I have your ear, is there no way to completely disable downloading Flickr comments? I don’t want them in Lightroom.

I’m using latest version of Lightroom 3, and the most recent plugin. If you want me to send you more info or have a way for me to get a log or something, please email me.

Sending a log after encountering the error would be great. And no, as silly as it sounds, Lightroom gives no way to avoid fetching comments, but I’ve sort of half worked around it: if you set the comment-fetch to “manual” in the Publish settings, the plugin will pretend to fetch comments to appease Lightroom, but won’t actually do it. —Jeffrey

— comment by Mark Prince on June 7th, 2013 at 10:48am JST (5 years, 5 months ago) comment permalink

Not able to get album information from the Facebook Plug-in. And will not save without the album. Entering or creating a new album is of no help, it still will not get the album part to finish and save it. Version installed is 20130524.226

It sounds like you can’t save Publish Service settings… you have to select at least one album to appear as a collection in Lightroom. The problem is not creating new albums, but in selecting album(s) for the publish service. —Jeffrey

— comment by Ken on June 8th, 2013 at 1:36pm JST (5 years, 5 months ago) comment permalink

Visiting from Austin, TX 🙂

Question for you. I’ve got the plugin installed in LR5 (just got it and putting it thru the paces) but it won’t load.

These are from the error log and hope that it helps to figure out what I’m missing:

Plug-in error log for plug-in at: /Users/MercedesMorgan/Documents/Lightroom related files/plug ins/zenfolio-jfriedl.lrplugin

**** Error 1

An error occurred while attempting to run one of the plug-in’s scripts.
This version of the “Zenfolio” plugin is too old for Lr5; please upgrade the plugin. The plugin home page is shown in the “Status” section above.

I don’t see how it can be more clear. The plugin is too old for Lr5; please upgrade to the latest version. —Jeffrey

— comment by Mercedes on June 14th, 2013 at 1:05am JST (5 years, 5 months ago) comment permalink

re: ZF plug-in, frequently the images end up in the wrong gallery.

Like this: select images, Export via your plug-in, select intended gallery, export, all’s well.

If I export more images to the same target, without changing anything, about half the time the images end up in the wrong gallery.

“The wrong gallery” always the same gallery, and it happens to be the very first ZF gallery that I exported to using your plug-in.

I always double-check the settings before exporting. Quite repeatable.

If I had to guess it’d be that some are not first-time uploads, but replacements, in which case the destination is ignored. If that doesn’t seem to be the case for your images, after such a failure please send the log with details about what image when where (and where it should have gone), and I’ll take a look. —Jeffrey

— comment by David J Swift on June 22nd, 2013 at 4:53am JST (5 years, 5 months ago) comment permalink

I’m in Wisconsin… Installed LR5 and the plugin will not show up. I can see it in Plug-in manager and see that it is enabled, but it is not in the list for me to use when exporting. Sorry if there’s a published trick to getting this to work – I couldn’t find it.

I don’t know what plugin you’re speaking of, but it sounds like one that supports only Export (File > Export), and not Publish. —Jeffrey

— comment by Carol Schlintz on July 5th, 2013 at 6:52am JST (5 years, 4 months ago) comment permalink

So sorry!!!! I am using the export from LR to Zenfolio.

My Zenfolio plugin does support Publish, so perhaps I’m not guessing correctly where you’re expecting to find it but aren’t, so I need more verbose details, please. —Jeffrey

— comment by Carol Schlintz on July 5th, 2013 at 9:42am JST (5 years, 4 months ago) comment permalink

Re: Lightroom 5 with your Facebook plugin

For some reason if I publish into many of my existing Facebook albums, the photo seems to set itself in 2012 as far as Facebook is concerned. I have to manually edit the date in Facebook to bring it into 2013.

I’m not positive, but I think this is only happening in my older albums that were created last year. Newer albums haven’t had this problem.

All dates on my computer appear normal. All exif data seems to have the correct year and date. My camera dates seem OK, too. I’ve check every date I can think of, and everything appears normal other than when I publish into some Facebooks albums.

The plugin doesn’t send any dates along with the photos (because Facebook doesn’t allow for it), so any dates are coming from the photo metadata, or out of Facebook’s think air. —Jeffrey

— comment by George D. Nincehelser on July 25th, 2013 at 12:58pm JST (5 years, 4 months ago) comment permalink

I can believe that it is Facebook’s problem. It wouldn’t be the first.

I’m pretty sure it’s not in the photo data…yesterday photos from both my iPhone and Canon t3i had pictures mis-dated. The only thing in common was that they were destined for the same old album. When I published those same photos to a newer album the problem didn’t appear.

If I knew an effective way to do it, I’d report it to Facebook, but I never seem to get their attention.

Zuckerman isn’t returning my calls, either.

— comment by George D. Nincehelser on July 26th, 2013 at 2:05am JST (5 years, 4 months ago) comment permalink

When I upload to facebook, each and every image will show up on facebook as an single upload. In other words, I am filling the wall with single uploads of images. Really annoying for people. Is it possible to hold the publishing until all images are uploaded?

There’s an option in the export settings to disable the Wall post. Facebook may still eventually put a “just added X photos…” wall post, but I’m not sure how they decide when to do that. —Jeffrey

— comment by Alf Olsen on August 1st, 2013 at 2:30am JST (5 years, 3 months ago) comment permalink

I am on your latest version of the LR Plugin for ZenFolio. I have one gallery that has 970 pics. The LR plug says it has added more pics, but the gallery never shows them. Its as if I have reached some kind of limit. Zen says they have no limits, and suggested I contact you. I am going to try their uploader just to see what happens. Otherwise, this has been working perfect! 🙂

— comment by Chuck Condron on September 3rd, 2013 at 6:56am JST (5 years, 2 months ago) comment permalink

I unchecked the “Replace the most-recent previously-uploaded copy and it worked even thought I normally have had this on.

I uploaded the same images to another gallery so maybe something didnt take.

— comment by Chuck Condron on September 3rd, 2013 at 7:04am JST (5 years, 2 months ago) comment permalink

Hi Jeffrey from Berkshire County, MA, USA.

Does lightroom plugin work yet with “new” smugmug ?

Thanks . .

Well, sort of, as far as what’s backwards compatible. They haven’t updated their APIs for any of the new features yet. I expect they’ll do it when they want, if they want. —Jeffrey

— comment by Mitch on October 1st, 2013 at 8:00pm JST (5 years, 1 month ago) comment permalink

I downloaded and wanted to test the Facebook upload plugin. However, the plugin is not able to list my albums on facebook! When I create a new album from the plugin, only this new album is available in the album list.

See this FAQ. —Jeffrey

— comment by harmishhk on October 23rd, 2013 at 7:33am JST (5 years ago) comment permalink

Hi Jeffrey,

Greetings from Pennsylvania.

I’m writing because of trouble I am having during the past two weeks with the Zenfolio plugin. I can upload a few photos and then the upload stops because of a communication error. Sometimes I can get 5 or so photos uploaded before it stops. Other times it stops after 1 or 2. I have no idea what is going on and I do have the latest version of the plugin. I’m using LR4.

Thank you.

Liana

There’s not much I can do to diagnose your networking issues from afar, but perhaps this FAQ has some ideas. —Jeffrey

— comment by Liana on October 28th, 2013 at 12:42pm JST (5 years ago) comment permalink

Good morning from NC, USA.
Running LR 5.2 on Mac Pro 10.9 using Zenfolio Plugin. I’m experiencing a problem with filters in conjunction with the plugin. Filters such as (Text, Attribute, Metadata at top, Stars/Labels, and/or Collections) will not properly isolate the relevant photos after viewing the uploaded or modified galleries under the plugin. So, for example, I can search for a file name and isolate the file in question. I can also view orders from Zenfolio after importing them as Collections. However, as soon I as click on any published gallery under the Zenfolio plugin, all filter capability stops working. Clicking on a Collection or searching for an image reveals the entire library of images, not what was searched for. If I restart LR everything starts working again until I view the published galleries. Any ideas? Thank you.

That sounds like this known bug. I believe it’s fixed in Lr5.3. —Jeffrey

— comment by Tripp Harrington on November 8th, 2013 at 2:27am JST (5 years ago) comment permalink

Hi Jeffrey. After I grantedd authorisation to your plugin on Facebook I get a string code:
lightroom://info.regex.lightroom.export.facebook2#access_token=blahblaha&expires_in=5150618

But when i paste it into your plugin’s mask I got an error.
I am stuck here. Any clue?
Thanks

Your browser should automatically forward that url to Lightroom… because it’s not, please see this FAQ. —Jeffrey

— comment by Adolfo on November 29th, 2013 at 3:56pm JST (5 years ago) comment permalink

Hi Jeffrey. Greetings from Houston, Texas. Love your work! After the last Flickr plugin update, or around then, “Publish” is acting up on me. Rarely do all images go through as normal. Most times, the first image gets published and is visible on Flickr (although it still remains in the “New Photos To Publish” section), then the Publish stops and I get one of two dialog boxes. One says:

Unexpected HTML reply from Flickr

Server Connection Closed

Server Connection Closed


Description: The server “rw.api.flickr.com” closed the connection before
the transaction was completed.

The other says something about slow server or interference from a security app.

All of this is a new phenomenon, and only for Flickr plugin. Picasa and the rest all work awesome as usual. Tried a few things like downloading the plugin again and copied it over the previous. No result. LR 5.3. Mac 10.7.5.

Thanks for everything!
Mabry

It sounds to me as if Flickr is having issues. Most often I think it’s just general flakiness on their part, but I did see this kind of error once when a photo had a specific kind of caption, as if a bug on their side always croaked trying to process it. It’s probably just general flakiness, but if you notice some pattern in the image data WRT when you get the error, please send a log with details. —Jeffrey

— comment by Mabry Campbell on December 14th, 2013 at 7:44am JST (4 years, 11 months ago) comment permalink

Writing from California.

Regarding the Lightroom-Zenfolio plugin: is the plugin capable of creating sub-galleries as required when exporting pictures in a hierarchy of sub-folders.

I have jpegs already created, these are in a separate catalog. In this catalog I select all pictures in a folder with subfolders, in the export options I say original (since they are all already jpegs) and export to zenfolio, and all the images from all subfolders get exported into one gallery in zenfolio, the, hierarcyh is not duplicated. Is this the expected behavior or am I missing something?

thanks
Karthik

That behavior should be expected if you told the plugin to export to a specific gallery, which it sounds like you did. But see
this post for an example of how to do what you’re looking for. —Jeffrey

— comment by Karthik Rajkumar on December 16th, 2013 at 1:17pm JST (4 years, 11 months ago) comment permalink

Uploading to Zenfolio, getting the “Network error when attempting http://up.zenfolio.com/…/upload.ushx. The connection to the server was terminated abnormally.” I know it’s probably not your software, and that network connection issues are difficult to diagnose, but I was wondering if anyone had ever given you feedback on how they got their problem resolved? If you have, I’d love to know what other people have found out. Thanks.

I’ve heard of this often, and always just assumed it’s been “issues” on their side, but I’ve never gone deeper than that. It could also be issues with your ISP, I suppose. Networking errors like this are notoriously difficult to diagnose. —Jeffrey

— comment by Scott Bird on January 4th, 2014 at 6:28am JST (4 years, 10 months ago) comment permalink

Another photographer from NC, trying to upload photos of Kyoto. (And failing, it seems.) Love the plugin. It’s been a godsend for me, and has worked like a charm until recently.

I’ve been trying to upload to Flickr now for the last 12 hours, on and off, and I keep running into the same problem. (Running 5.3 and latest JFlickr.) It will upload one photo, then the connection just flakes out with a “Bad server response” error. If I try again, it may/may not upload, and sometimes it screws up my photostream, too. (Multiple copies of the same photo.)

I have tried logging in/out, reloading the plugin, restarting the program, rebooting, etc., with zero luck. Any suggestions as to what to try next? (Smugmug, maybe? 😀 )

If the problem is not your your side (e.g. meddlesome “security” apps), your account is probably assigned to a bad server in their farm. Hopefully they’d notice it sooner than later. —Jeffrey

— comment by Rich Fowler on January 18th, 2014 at 11:29pm JST (4 years, 10 months ago) comment permalink

Jeffrey,

Greetings from Malawi!

Last night I uploaded a few photos to Flickr via the Uploadr. I wanted to upload a larger image size, and at the time I thought it would be easier to just do it that way than to change the settings in the Publishing Manager. (Silly me.)

This morning I associated the uploaded files via your “Flickr Extras” tool (which is probably my favorite thing about your plugin!) They all linked up just fine. Yay!

But they still show up in the “New Photos to Publish” section. I was expecting to use the “Mark as up-to-date” option to move them to “Published”, but that doesn’t even show up as an option for those photos.

It seems like if I hit “Publish,” the images on Flickr will be overwritten with new copies at the size settings for the plugin. A few of those images are on an external drive that’s offline at the moment, so I’d have to publish them from the Smart Previews – which will be smaller than I wanted.

How do I get Lightroom to accept the images I’ve already uploaded as “Published”?

Thanks!

Check out the “claim” feature. —Jeffrey

— comment by Matt on January 20th, 2014 at 3:55pm JST (4 years, 10 months ago) comment permalink

I have the latest (.243) version of the facebook plugin. I have a graphical watermark specified, but it is not getting applied to the images.

It is the zion album.

Thoughts?
Thanks,
🙂

Do you perhaps have the “Image Format” set to “Original” (which Adobe has inexplicably chosen to mean “Original pixels with new metadata” instead of “image format of the original”)? The plugin has nothing to do with watermarking… Lightroom takes care of that before handing the image to the plugin for upload. —Jeffrey

— comment by Patrick Lynch on February 19th, 2014 at 1:48am JST (4 years, 9 months ago) comment permalink

When uploading to zenfolio through their web uploader, I can average one image every 27 seconds. It seems to take about 47 seconds per uploaded image in lightroom using the plugin. The average image size is 12mb. I wondered if the web uploader was more efficient because it allows for 3 concurrent image uploads, and I don’t know if your plugin uploads multiple images concurrently or not. Is this the reason for the difference in speed?

OSX 10.9.1 Lightroom plugin 20140204.243 Lightroom 5.3

I’d think it’s not the reason… one upload should saturate your network (which one assumes is the bottleneck). If Zenfolio is the bottleneck (possible, but highly unlikely) then multiple uploads may well be faster. Most likely, though, the difference is in what you’re uploading…. perhaps you’ve got Lightroom set to produce higher-jpeg-quality shots, which inflates the byte size very quickly toward the upper end (as described here). Another possibility is that Zenfolio may reserve its fastest processing for its own tools, leaving third-party apps to use lower-priority resources. (I don’t know that they do that, but it’d be a smart move on their part.) —Jeffrey

— comment by MIke on February 25th, 2014 at 1:03pm JST (4 years, 9 months ago) comment permalink

I am trying to get the Zenfolio uploader into LR 5.3 but I get the message, “An error occured while attempting to load this plug in.” and that is all. I have had this plublisher before but it seems to not work now.

See this FAQ. —Jeffrey

— comment by Rick on March 30th, 2014 at 3:18am JST (4 years, 8 months ago) comment permalink

New iPernity user from Canada here.

Just downloaded the latest version and I get this:

**** Error 1

An error occurred while attempting to load this plug-in.
The plug-in is designed for version 4.3 of Lightroom.

Is there any way this plugin can be made work with LR 3.3? I am not going to upgrade LR.

Thanks.

No, sorry, Lr4.3 or later is required. —Jeffrey

— comment by Alveric on March 30th, 2014 at 3:00pm JST (4 years, 8 months ago) comment permalink

At some point between March 29 and April 4, Facebook have changed the URL format for photo albums. Any links previously created which use the facebook ‘album.php’ type URL will fail with “Content Not Found”. They seem to have changed to a /Media/Set/ URL format now.. ALL previously tweeted links to Facebook albums created by the JF Lightroom Plugin now fail… ie: Including tweets created before Facebook made the change.. 🙁

That sucks, but there’s not much I can do about it. The plugin doesn’t compose the URLs… it just passes along the URL that Facebook provides. )-: —Jeffrey

— comment by Jason Sheldon on April 6th, 2014 at 9:02pm JST (4 years, 7 months ago) comment permalink

Hi Jeffrey,

Thank you for this plugin, I used it with LR 3 and now upgraded to LR5.3 and am having some trouble.

When I try to get an authorization code, I get an error message: Firefox doesn’t know how to open this address, because the protocol (lightroom) isn’t associated with any program picasa.

Using windows 7, lightroom 5.3, firefox 29.0

Thanks for your assistance.

Noam

A quick re-install of Lightroom should fix it, as per this FAQ —Jeffrey

— comment by Noam on April 30th, 2014 at 12:49pm JST (4 years, 7 months ago) comment permalink

While a photo has development modification it creates a duplicate on Facebook, is there anyway i can make the plugin overwrite the current image instead of creating a new one?

No, Facebook doesn’t allow it. —Jeffrey

— comment by Tony on May 9th, 2014 at 5:44pm JST (4 years, 6 months ago) comment permalink

I have had a consistent problem for awhile now (a few weeks?) with the export to Flickr plugin. It seems to work OK, mostly, but sometime after it’s done exporting (perhaps while downloading comments?) I get this error message. When I click the (very hard to see) close button, I get the “canceled” notification. The upload seems to go OK though.

    Yahoo will be right back...
    Thank you for your patience.
    Our engineers are working quickly to resolve the issue.
 

Yahoo’s servers have been really iffy for the last half year or so, so much that I gave up on uploading to them. Not much I can do about it, sorry. )-: —Jeffrey

— comment by Stephen Shankland on May 16th, 2014 at 7:31pm JST (4 years, 6 months ago) comment permalink

I have the same problem as Scott Bird, and its a pretty big issue for me. I can’t leave the computer when its uploading cause everytime it stops due to network error I have to go to Zenfolio, see where it left off, and do a new export with the first image.

The plugin can’t fix a bad networking situation, but it does keep track of what has and hadn’t been exported. If you’re using Publish, just hit the [Publish] button again and it’ll pick up from where it left off. If a normal Export, there’s an option to skip things that have already been uploaded. —Jeffrey

— comment by kati powell on May 29th, 2014 at 12:06am JST (4 years, 6 months ago) comment permalink

Having an issue authenticating to facebook. I’ve updated to the most recent plugin on your site and I still get this message:

Firefox doesn’t know how to open this address, because the protocol (lightroom) isn’t associated with any program.

I’ve tried copying and pasting the address to a different browser and essentially get the same message, the address doesn’t exist.

Any advice on what I need to do? Thanks, Trevor~

Please see this FAQ. —Jeffrey

— comment by Trevor Nichols on June 9th, 2014 at 10:11pm JST (4 years, 5 months ago) comment permalink

I am getting an error when uploading to zenfolio that says “Upload failed: Error 50008”

What do I need to do?

b

Don’t know that error; it’s likely from your OS or Zenfolio. Send a log, I guess. —Jeffrey

— comment by Brian on June 10th, 2014 at 8:55am JST (4 years, 5 months ago) comment permalink

Hi Jeffrey I’ve been recommending your LR-Zenfolio plugin to my colleagues. A couple have had issues because they have upgraded from illegal copies of LR and to legit versions of LR CC. In this case the legit version of LR CC won’t accept the plugin. Is there a workaround or fix? Is an unsintall necessary?

No fix yet for this known issue, but I’m holding hope Adobe will get back to me with help. —Jeffrey

— comment by Tim Stiles on June 30th, 2014 at 4:02pm JST (4 years, 5 months ago) comment permalink

Hello from Brasil.
Just upgraged for LR 5.6 and had to register again (thats not a problem, happy to do it) but when hitiing the register Here Button on the Plugin Manager got the folowing Error:

Assert Failed smugmug#288 +531.8: [x608000f74b88] @Registration line 1558:
Assertion failed(!):
[x608000f74b88] @Registration line 1558
[x608000f74b88] @LrPluginInfo line 378

What to do?

Tks a lot!

Sorry about that… I wasn’t properly prepared for Lr5.6. I’ve pushed new versions of the plugins that should work now. —Jeffrey

— comment by Paulo Barbuto on August 1st, 2014 at 7:40am JST (4 years, 3 months ago) comment permalink

When I try to use the PicasaWeb plugin I get “Unrecoverable server error at Google (it returned a normal web page instead the proper API reply)”. This occurs if I try to refresh the folder list. I have tried to re-authenticate and I get the same error. I am using version 20140820.270 of the plugin and I have Lightroom 5.6, 64 bit.

A number of folks have reported this suddenly. I suspect a bad server at Google. Hopefully the problem will just go away sooner than later. —Jeffrey

— comment by Robert Schmidli on August 26th, 2014 at 9:55pm JST (4 years, 3 months ago) comment permalink

Since upgrading to the 5.6 version of the plugin I have noticed it seems to take longer to upload to smugmug. It used to take no more than an hour or so to upload 100 images…now its taking 6 hours+. I am also working with smug to see if it is their problem.

Note…Nothing else on my end has changed and I am not having problems uploading to other sites. My suspicion is the problem is smugmug, but just want to confirm that nothing new in the latest version of the plugin should slow upload speeds.

Thanks Clark

Nothing major has changed with the plugin in how it uploads since Lr4.1, where it became much more efficient. It’s indeed dependent on SmugMug, but also on your system, your network, and every network between you and SmugMug, so slow uploads can be quite the frustrating thing to debug. /-: —Jeffrey

— comment by Clark Kranz on August 31st, 2014 at 10:33pm JST (4 years, 3 months ago) comment permalink

Hi Jeffrey – mind helping me with this:

I know, that Lightroom behaves quirky, when it comes to the republish-feature in your plugins (at least, that’s how I understand some of the comments above).
I am using jflickr, and most of the time, when I open Lightroom, there’s about 3-4 pictures, that jflickr claims needing a republish. Most of these pictures are pictures, that were uploaded just recently or a few weeks ago. But I KNOW, that I have not touched these photos in any way – be it any editing or changes in the tags or metadata.
Do you have any explanation, why they want to be republished?

Because Lightroom is buggy. )-: —Jeffrey

Republish is only triggered, when there are any changes – so I assume, that Lightroom says “there’s a change” even if I have not touched the picture. What change could that be? Just closing and opening Lightroom should not trigger any changes, shouldn’t it 😉

Thanks for your support!
Joerg

— comment by Joerg on September 13th, 2014 at 6:48pm JST (4 years, 2 months ago) comment permalink

Hi Jeffrey….

I updated Lightroom to 5.7 this morning and now I’m getting the dreaded “Gumby” error for the Picasaweb plugin. Is there a fix for this? Thank you!

The Google error has nothing to do with your upgrade… just bad timing. I believe that “Gumby” is one of the back-end systems, and when it’s over capacity, these errors leak out through their servers to Lightroom to the plugin to you. Just keep trying, perhaps after a wait. I get them as well a lot lately. —Jeffrey

— comment by Kris Rowlands on December 7th, 2014 at 10:48pm JST (3 years, 11 months ago) comment permalink

From England.

I have downloaded the latest update and use LR v5.5 on a windows 7 64bit computer. Images are not uploading.

On export each time a message reads “Downloading comments-Retrieving comments on (specified gallery)”

There also appears to be a network error communication problem.

Please advise.

David

You haven’t given much to go on, but if you’ve gotten to the “download comments” step without an error, the image(s) should have been uploaded. Are they in the “Published Photos” section? If so, the thumbnail context menu has an option to visit the photo at the remote site. But if you’re seeing network errors, then of course uploads might not be completed. —Jeffrey

— comment by David Malkin on December 31st, 2014 at 10:50pm JST (3 years, 11 months ago) comment permalink

Jeffery,

I am still having the Gumby issue. I have removed and reinstalled the latest plugin, but it’s storing some information somewhere that I don’t know where to find. I’m thinking it’s in the LR preferences.

When I removed (physically deleted of my hard drive) the plugin and re-downloaded the latest version (as of today) it remembered my Picasa log in info and logged me in.

I have not be able to upload to Picasa since I last commented on here. I think I’m going to try deleting my preferences (ugh) and see if that works. Do you have any thoughts on why this is happening? This has been happening since the LR 5.7 upgrade. I’m now on 5.7.1.

I’m sure the problem is 100% at Google’s side, which makes me feel there’s nothing you can do. However, there could be some scenarios where it’s related to a login session, so there’s some (small) chance that logging out in the plugin, then logging back in might get you attached to a different server, which might solve the problem. No info is stored in the plugin files, so deleting that would make no difference. Some data is stored in your Lr preferences, and some in the catalog, but I don’t think the bug is related to any of it. It’s frustrating. —Jeffrey

— comment by Kris Rowlands on January 11th, 2015 at 8:46pm JST (3 years, 10 months ago) comment permalink

I have the latest version of the Facebook plug in, LR and OS X and I just noticed today when I went to upload to an older album on Facebook that I can’t see it in the plug in even though it is on Facebook. I then noticed in the options I can select how many lines to display in the album scroll box and the max is 20. Has it always been like this and I am just now noticing this for the first time or did something change recently? I have probably about 100 albums on Facebook and I am still active with close to half of them so this isn’t very convenient. Is this a Facebook API or LR limitation?

The 20-line limit in the height of the album-display scroll was my own arbitrary limit. I just arbitrarily raised it to 50. —Jeffrey

— comment by Kevin Holt on January 22nd, 2015 at 11:35pm JST (3 years, 10 months ago) comment permalink

I have the latest version of the Facebook plugin with LR CC 2015. Every time I start LR, I get the message “Lightroom needs to configure your system for the $$$/xxx=jf Facebook plug-in.” I click OK, it prompts me for elevated permissions, and then everything runs fine until I shutdown LR and start it up again, at which point the process repeats. Any ideas how to fix this (on a Win 8.1 64-bit, if that matters)?

I’ve not seen this before except in reports here. I’m guessing (hoping) that a reinstall of Lightroom would fix it. —Jeffrey

— comment by Branislav Slantchev on April 23rd, 2015 at 3:06am JST (3 years, 7 months ago) comment permalink

Just wanted to confirm that a reinstall resolved the $$$/xxx issue.

— comment by Grant on April 23rd, 2015 at 4:19pm JST (3 years, 7 months ago) comment permalink

I’m getting the $$$/xxx issue on both my desktop and laptop. Is the only option a reinstallation of LR. I tried reinstalling and reloading the plug-in but that didn’t help.

The problem is not with the plugin, but with Lightroom’s install. Adobe suggests that you can also run “lightroom.exe -register” as an admin to fix it. —Jeffrey

— comment by Peter McClintock on April 24th, 2015 at 8:19pm JST (3 years, 7 months ago) comment permalink

Yes, a reinstall solved the $$$/xxx issue. Running “lightroom -register” did not.

— comment by Branislav Slantchev on April 25th, 2015 at 2:51am JST (3 years, 7 months ago) comment permalink

Running “lightroom.exe -register” as an admin fixed it for me, though it is critical that you have cmd running as administrator. Without this it doesn’t so anything. All sorted, thank you.

— comment by Peter McClintock on April 25th, 2015 at 4:36pm JST (3 years, 7 months ago) comment permalink

Found this page when I was about to report the “$$$/xxx” issue too. Pleased to report than uninstalling/reinstalling LR6 fixed it for me too (on Windows 8.1 64-bit). Thanks, folks!

p.s. Would REALLY help if this page was sorted with newest items at the top though. Took a lot of scrolling to get to the bottom!

— comment by Mark Whitaker on April 26th, 2015 at 12:34am JST (3 years, 7 months ago) comment permalink

I also found this page while researching a resolution to the “$$$/xxx=jf” Facebook plug-in issue. It was easily resolved by running “lightroom.exe -register” command as suggested earlier.

For Windows users unfamiliar with the Command Prompt here’s the step-by-step solution:
1. Type “Command Prompt” (without the quotes) in the Search box of the Start Menu (accessed by clicking on the Start button).
2. The Command Prompt applet will be shown at the top of the list in the search results; right-click on it and select “Run as Administrator”
3. When the Administrator: Command Prompt windows appears change the directory to the Lightroom folder by typing “cd Program Files\Adobe\Adobe Lightroom” (without the quotation marks)
4. Once in the Lightroom directory type “lightroom.exe -register” (without the quotes) to fix the issue, then close the Command Prompt window.

— comment by James Nelson on April 26th, 2015 at 8:03pm JST (3 years, 7 months ago) comment permalink

Hi,
Is anyone getting a “Error reply from Facebook: (#200) Requires extended permission: ” when trying to publish photos to a business page album on Facebook. This used to work fine but I’ve just upgraded to the latest lightroom CC and have also upgraded to the latest version of the plugin.

The plugin used to work fine before the upgrade.
Any help much appreciated.
Thanks,
Terry

It’s not related to Lightroom… it’s that Facebook changed how they handle app permissions on May 1st. I believe that modern versions of my plugin should work, but you may need to deauthorize the plugin at Facebook (here), then log in via the plugin… —Jeffrey

— comment by Terry MacSweeney on May 1st, 2015 at 7:49am JST (3 years, 6 months ago) comment permalink

Started publishing via personal page, now it won’t publish to my business page, getting error 200. Please help! Error reply from Facebook: (#200) Requires extended permission:

You might need to log out from Facebook in the plugin, then deauthorize the plugin at Facebook (here), then back in the plugin log back in. In theory that should reset permissions…. —Jeffrey

— comment by Josh E on May 1st, 2015 at 3:02pm JST (3 years, 6 months ago) comment permalink

Still getting error 200 after reauthorizing in plugin. Not sure how to logout from Facebook in the plugin, though.

At the top of the Export dialog (File > Export). —Jeffrey

— comment by Charlie Choc on May 2nd, 2015 at 3:46am JST (3 years, 6 months ago) comment permalink

Hi, I have changed nothing but now I cannot publish to Facebook, it errors with “Error reply from Facebook: (#200) Requires extended permission:” I have updated to the latest plugin 20130501.384, I’ve deleted the FB apps for lightroom and then re-enabled them. No success 🙁
Please can you help….

Please see this FAQ —Jeffrey

— comment by Wayne on May 2nd, 2015 at 12:38pm JST (3 years, 6 months ago) comment permalink

Thank you Jeffrey, followed it exactly, but it still doesn’t work 🙁
Still get the same Auth error.

— comment by Wayne on May 2nd, 2015 at 1:49pm JST (3 years, 6 months ago) comment permalink

works with latest version, thanks.

— comment by Charlie Choc on May 3rd, 2015 at 8:38am JST (3 years, 6 months ago) comment permalink

I recently upgraded to LR6. After updating Zenfolio plugin, LR began hanging soon after launch… Running Mac OS 10.10. Removing plugin from LR plug in folder on hard drive seems to have addressed the problem… LR isn’t freezing up anymore. Has anyone heard of this issue?
Thanks.

I haven’t heard of this specific issue, but when I hear of strange things like this, it makes me wonder whether your Lr preferences file has started to go corrupt. —Jeffrey

— comment by Christine on May 12th, 2015 at 11:52am JST (3 years, 6 months ago) comment permalink

I had a similar problem with LR freezing after launch. Not sure if it’s related to the same cause. However, click Help -> Updates in LR6 and make sure it updates to the latest 6.0.1 update (if it’s not already installed.) The update fixed my freezing issue.

— comment by Jim on May 13th, 2015 at 12:55am JST (3 years, 6 months ago) comment permalink

When I use the Picasaweb Plugin for Lightroom to export Albums to Google Photos, it eats up my Google Drive Space. My Photos are 16mp, and if I upload them via the Photos web app in Chrome it doesn’t use up space, because it uses the new free “high quality” 16 mp mode. I can’t find a setting in the plugin. Am I doing something wrong or is it just too early and I have to wait for an update?
By the way, your plugin is awesome!

Thanks, Niklas

I don’t know about any “high quality” mode… Google’s policy here has long been “Photos bigger than 2048×2048 pixels use your storage”, so if you want to use free storage, export with the Long Edge set to 2048. Or use their tools… Google often provides features in their tools that are not available to third-party apps… (for example, you can upload a 1GB video with their tool, but the limit is 1/10th that if done via third-party app). —Jeffrey

— comment by Niklas on June 1st, 2015 at 7:00am JST (3 years, 5 months ago) comment permalink

I’m trying to change the library names in the plugin an get following error message. Edit Gallery Sorry, due to a bug in Lightroom edit-collection properties can’t be edited.
was in touch with Adobe but they refereed the problem to the plugin.
LR 6
Latest Zenfolio update
Win 8.1

If you rename the albums at Zenfolio, you can have the plugin update the collection names to match via the main Publish Services dialog. See the “Zenfolio: Galleries in this Publish Service” section. —Jeffrey

— comment by Werner Bertsch on June 8th, 2015 at 6:52am JST (3 years, 5 months ago) comment permalink

I have had a couple of times where a network issue causes an upload to retry. The retry is successful, however at the end I get a popup that states “Network Error contacting api.zenfolio.com” However it also states in the popup “Task Completed”. The only thing I can press is “cancel”, but that does nothing. In fact from then on I can do nothing as I can not clear the error. In fact I can not even quit Lightroom. My only way out is to force quit the entire application. Am I missing something?

This is an unfortunate side effect of how plugin dialogs seem to work in Lightroom… I go to great lengths to avoid this situation (and I think this is the first report I’ve gotten about it showing up in this plugin), but it sounds like really unlucky timing caught you. I wish Adobe would let these dialogs be dismissed, but until then I’m not sure that I can do much more. )-: —Jeffrey

— comment by Doug Parks on June 9th, 2015 at 6:27am JST (3 years, 5 months ago) comment permalink

dHello. Trying to add some more Facebook associations using the People Support plugin (20150529.10) and getting errors on every attempt. I turned on logging and see the following:


people-support#10 +16.2: [x608000d6a2c8] @PersonFacebookSupport line 27: Fetching [https://graph.facebook.com/?id=xxxxxx]

people-support#10 +18.0: [x608000d6a2c8] @PersonFacebookSupport line 30:
json = "{"error":{"message":"(#803) Cannot query users by their username (xxxxxx)","type":"OAuthException","code":803}}"
queryurl = "https://graph.facebook.com/?id=xxxx"

I wonder if Facebook made some backend changes without telling anyone?!

Thanks! And thank you for all of the amazing plugins you’ve created!
Mike Hall
Austin, TX

Yeah, it looks like they shut down what the plugin was using. Not sure what to do… I’ll dig around again… —Jeffrey

— comment by Mike Hall on June 22nd, 2015 at 2:34am JST (3 years, 5 months ago) comment permalink

Hi I just downloaded the latest version of your Picasaweb plugin, and it gets an error trying to create a new album

Create new album at PicasaWeb aborted: Unexpected HTTP status from Google: 500

Lots of folks are getting these errors… they’re back-end problems at Google. They seem to be letting photos wither in the vine. Nothing we can do but hope they give it more attention. —Jeffrey

— comment by Alex on July 24th, 2015 at 12:31am JST (3 years, 4 months ago) comment permalink

Live in Newburgh, IN and have been using your Zenfolio plugin for several years and love it. Currently running Lightroom cc 2015 on windows 8.1. Lately When publishing new photos I have been receing the following error: “Unexpected http error from Zenfolio”. That is not thr exact wording but something to that effect. Any ideas? Thanks

It’s an issue that they (at least some of Zenfolio’s customer service staff) knows about and they’re working on it. Some of the staff don’t so they’ll send you back to me, but behind the scenes it’s being worked on. —Jeffrey

— comment by Denny Riffert on July 29th, 2015 at 8:42pm JST (3 years, 4 months ago) comment permalink

Hi. I see a modal dialog box with the common error: Network Error contacting up.zenfolio.com
Probably when uploading multiple galleries at a time.
Often this goes away once the connection resumes.

Often it completes with ‘Task completed” but I will see many boxes on the screen which all prevent interaction with Lightroom.
The only way to resolve the problem is to stop the Lightroom Task and restart.

Is this a bug within Lightroom or something your plugin could address?
Thanks for any insight.

It’s probably my plugin’s fault, though I put a lot of work to avoid a bazillion dialogs, it falls apart if you launch multiple exports at the same time (since one export doesn’t know the other has already put up a dialog). This is all compounded by the troubles that Zenfolio’s servers have been having for the last few months. )-: —Jeffrey

— comment by Darren Whittaker on August 3rd, 2015 at 5:30am JST (3 years, 3 months ago) comment permalink

Many thanks. If you ever get round to a fix I would be very happy but I can live with it as I appreciate it’s not a high priority.
For me I use multiple uploads all the time. Yesterday for example I had to upload 1800 images which were in 18 galleries.

— comment by Darren Whittaker on August 3rd, 2015 at 6:14pm JST (3 years, 3 months ago) comment permalink

Hello from Perth, Western Australia: I am trying to publish images to Flickr but as of the last two days I am getting the following error message. However I can use Lightroom’s plugin okay. I have tried refreshing user data and re-authenticating to Flickr to no avail.

Error during export

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.

Aborting export after 7 of 24 images successfully uploaded.

Any suggestions on getting around this would be greatly appreciated.

Thanks
Andrew

It’s one of those things that we just have to wait to clear up. Flickr’s own uploader likely uses Flickr-specific servers (rather than general servers for third-party apps like mine). I’ve spent many hours on this over the years, and find no rhyme nor reason to the errors, which is why I finally gave up and added the “nothing we can do but wait” message. There’s nothing we can do but wait. —Jeffrey

— comment by Andrew Priest on August 11th, 2015 at 10:47pm JST (3 years, 3 months ago) comment permalink

Hi,

I am writing from NY, NY.

Using Windows 7, and Lightroom 5.7

The Picasaweb plugin will not let me create new albums and gives me the following error message “Create new album at PicasaWeb aborted: Unexpected HTTP status from Google: 500.

There is no problem uploading photos to an already existing album.

Thanks

This is likely a temporary glitch at Google, but just to be sure it’s not an error in my plugin, please send a log after you next encounter it. —Jeffrey

— comment by Noam on August 16th, 2015 at 1:29am JST (3 years, 3 months ago) comment permalink

I’m trying to edit the name of a Google Plus album but I’m getting the error “Sorry, due to a bug in Lightroom edit-collection properties can’t be edited.” Can you please tell me if there’s a way around this? I saw your comment up there about Zenfolio but my issue is specifically with Google Photos. Thanks for the help.

The best I can suggest is to rename the album at PicasaWeb, then refresh the list of albums in the plugin. Then remove and re-add it to the publish service. It’s a horrible workaround, but the best that I can come up with )-: —Jeffrey

— comment by Gautama on September 7th, 2015 at 8:05am JST (3 years, 2 months ago) comment permalink

Hi, when published to Flickr with jf-plugin the rights of photos are “public”. In the LR Plugin can managed the rights to “Friends and Familiy”. How can I change the default setting to “Friends and Familiy”
Best regards

There’s a whole section in the Export/Publish dialog for these kinds of things, including where you can set the default. —Jeffrey

— comment by Jokl on September 21st, 2015 at 9:55pm JST (3 years, 2 months ago) comment permalink

Hi,
in my new Google account, when try create new album or upload photo, I get error
“Unexpected HTTP status from Google: 403 Access forbidden”

please tell me what setting in Google account is responsible for this ?

in other accounts all work fine…

As best as I can tell, it’s an error on Google’s side. I don’t know any way around it other than to wait until it goes away as mysteriously as it came. —Jeffrey

— comment by Max on October 4th, 2015 at 7:02pm JST (3 years, 1 month ago) comment permalink

Lightroom Folder Publisher is not performing the delete operation when a folder is no longer in a directory.

When a folder is renamed, it is published but the other folder is there, also. The first folder remains as it was when it was last published. No changes are reflected in the old folder. Metadata updates and photo additions or deletions are only reflected in the new folder.

If you rename a folder in Lightroom and republish all the affected images in the plugin, it should indeed delete the old folder in your target tree, unless some files are left there for other reasons (or unless there’s a bug in the plugin, of course). Lightroom doesn’t consider a change to the folder name or path to be worthy of republish, so you have to explicitly republish anything affected. —Jeffrey

— comment by Justin on October 8th, 2015 at 4:27am JST (3 years, 1 month ago) comment permalink

With the picasaweb plugin, is there a way to use the auto album creation and have it create private albums instead of “those with links” album?

Basically trying to utilize the plugin to upload my history of photos (in their albums) and then use Google Photos’ new conversion option to take advantage of the free space.

The Google API that the plugin uses merely allows the new album to be marked “public” or “private”; apparently, their idea of “private” is “obfuscated”. The URLs are sufficiently long and complex that the chance of someone coming across it without you having sent it is minuscule, but in any case, I guess the answer to your question is “no”, sorry. —Jeffrey

— comment by Linh on November 18th, 2015 at 1:46pm JST (3 years ago) comment permalink

Yet another addition:
Google stopped the ClientLogin and now only accepts the OAuth2.0 method:
https://developers.google.com/identity/protocols/AuthForInstalledApps

My Google-related plugins have always used OAuth2. I think it’s just problems on Google’s side. )-: —Jeffrey

— comment by Jeroen on December 10th, 2015 at 10:23pm JST (2 years, 11 months ago) comment permalink

The reason that people are getting the lightroom needs to modify your system, is that to open links like lightroom:// it needs to be set as an admin. It seems Lightroom is failing to do this for some reason when you press ok.

But essentially running lightroom.exe -register seems to make these work.

— comment by Andy on December 11th, 2015 at 9:35am JST (2 years, 11 months ago) comment permalink

Hi, Thanks for your great Flickr plugin. I have a problem with downloading comments. Although I disabled automatic downloading of comments for individual collections, the plugin downloads the comments every time I publish a new picture. Since I have several hundreds of pictures in the collections, this takes some time. I would be very happy, if there was a fix to this.

Thanks and greetings

Stefan

It’s probably not actually downloading the comments… just going through the motions. Lightroom doesn’t actually have an option to disable the comment stuff, so it always thinks it’s checking for new comments on all photos with every Publish. This seems ridiculously inefficient to me, so I added an option to the plugin whereby it only pretends to check for new comments. This eliminates all the network traffic, but Lightroom still does a lot of back-end shuffling. Every time. A huge waste. Requests to Adobe for some sanity here have gone unfulfilled so far. —Jeffrey

— comment by Stefan Müller on March 14th, 2016 at 3:45am JST (2 years, 8 months ago) comment permalink

Hi Jeffrey Many thanks for the plug in however this appears to have stopped working for me and reports the following

Flickr API returned an error message (function upload, message Photo is temporarily unmodifiable)

any help would be appreciated

Thanks

Terry

It sounds like they were having maintenance or something… I’d just try again later. —Jeffrey

— comment by Terry on March 16th, 2016 at 1:13am JST (2 years, 8 months ago) comment permalink

Hi Jeffery, I am from Columbus, Mississippi. For sometime now and it may be after I upgraded to U-Verse I have not been able to upload pictures from lightroom. I try to refresh the gallery list first then I get a NetworkConnectionLost message. I logged off ,my site and logged back in and then logged of my site via lightroom plug in and now it will not log back in and I get the Networkconnectionlost error again. Any ideas on what the problem might be? Thanks Keith

Please check out this FAQ —Jeffrey

— comment by Keith Burchfield on March 21st, 2016 at 5:41am JST (2 years, 8 months ago) comment permalink

New York here. I downloaded to Google NIK collection yesterday. Only photoshop displays a pop up when it’s launched, showing the NIK tools. But if I click on one an error message shows unable to load this program.

Secondly, nothing shows up in lightroom for the plugins. And if I go to lightrooom plugins manager. It doesn’t alow me to import plugins.

Any ideas? Bad download?

Those are not Lightroom plugins, they’re stand-alone photo tools. You can call out to them from Lightroom by registering them as an “External Editor”. I’m sure a Google search will serve you well here. —Jeffrey

— comment by Kevin Davies on March 27th, 2016 at 11:43am JST (2 years, 8 months ago) comment permalink

When “publishing” from Lightroom 4 to SmugMug, I now get an error that states, “Export operation not performed (due to) photo being over 210 megapixels”. Any idea how to fix? Thanks

That error message doesn’t ring a bell… is that the exact text of the message? I’ve never seen it, but it sounds like you might have run into a Lightroom limit? If it got as far as generating the copy to be uploaded, but it turned out to be bigger than allowed for your SmugMug account, the plugin would tell you but not with a message like that, so I’m left scratching my head. —Jeffrey

— comment by Kim on April 17th, 2016 at 10:52am JST (2 years, 7 months ago) comment permalink

I have been getting the message

error returned by Flickr: photo is temporarily unmodifiable

when I try to re-publish existing photos from Lightroom 6.5.1 (and previously Lightroom 6.4 and 6.5) to Flickr using your plug-in 20160402.384 (and probably earlier versions), Windows 7 Home Premium. I have a Flickr Pro membership.

Earlier in this thread you recommend to try again later, but this has been going on for a month now. And it’s always the same Publish Collections that have the problem, nothing will publish to Flickr; while other Publish Collections work just fine.

The plugin is just passing along the message from Flickr. This kind of error should be, as the message says, temporary, but maybe there’s actually something about that specific photo (“locked” at Flickr??) that persists. The best I can suggest is to ask Flickr about it, or try deleting it and re-uploading it and hope the stuckage doesn’t follow to the new copy. —Jeffrey

— comment by Paige Miller on May 1st, 2016 at 9:13pm JST (2 years, 6 months ago) comment permalink

While using the Zenfolio up loader it stopped after 388 shots all previous ones fine and no error code LR still thinks its publishing but nothing happens left it all night and all day as I was at work so for approx 20 hours it just didnt do anything, I had to cancel the upload and do the rest of the images manually as it then wouldn’t get past “downloading comments” Will re try this again but any ideas why it did this would be most welcome.

When I hear something like this, my best guess is that you have a large video that Lightroom is taking forever to process. —Jeffrey

— comment by Edward Elliott on May 4th, 2016 at 5:28am JST (2 years, 6 months ago) comment permalink

Hello from Indiana. I recently upgraded LR and now when I try to reload the plugin LR gives me an error message. Any thoughts? LR says an “error has occurred and the plugin can’t be loaded at this time”

It’s difficult to guess when you don’t mention the plugin nor the initial error. Please see this FAQ —Jeffrey

— comment by Lisa on May 25th, 2016 at 1:04pm JST (2 years, 6 months ago) comment permalink

Hey Jeff, Happy Memorial Day!

Second attempt on up loading a set of images to Zefolio using your v.20160307.282. Never has this issue before on my MAC running EL CAPITAN in Lightroom CC release 2015.5.1. In both attempts the following error was received. The second attempt was made making sure I had the max file size restricted to 60Mb: “Unexpected HTTP reply from http://up.zenfolio.com/kenndoylephotography/p120552020/upload2.ushx:503

Can you help point me in the right direction so I can clear this up, please?

Kenn

Zenfolio seems to have had some flakiness lately… they’re giving lots of unexpected replies these days. )-: —Jeffrey

— comment by Kenn Doyle on May 29th, 2016 at 9:37pm JST (2 years, 6 months ago) comment permalink

Hi,
I was wondering if the zenfolio plugin for lightroom allowed you to view which photos are selected as favorites by the client? currently i’m trying to manually go thru 2k photos and selecting each one they have chosen.

I don’t think Zenfolio exposes this functionality to third-party apps, but I’ve sent them a note asking about it. —Jeffrey

— comment by Mediha Sandhu on June 4th, 2016 at 4:05am JST (2 years, 5 months ago) comment permalink

I want to sync my photos in Zenfolio to LR. I have done Refresh All Remote Urls. There is an error “Assertion failed: packed” when doing Associates Images Automatically. I can see the folders in Zenfolio appears in Zenfolio Publish Services but not the photos. Please help and thanks in advance.

I am from Hong Kong.

This seems to be a bug in Lightroom… I’ve reached out to Adobe on it. —Jeffrey

— comment by Philip Mui on July 30th, 2016 at 10:52am JST (2 years, 4 months ago) comment permalink

Hi Jeffrey,

Any update on this error? “Assertion failed: packed” I’m getting this too also.

Thanks,
Guy (from Melbourne)

No, sorry, I’ve reached out to Adobe but no reply. )-: —Jeffrey

— comment by Guy on August 10th, 2016 at 2:59pm JST (2 years, 3 months ago) comment permalink

Hi Jeffrey,

I have been using your Export to Flickr combined with Metadata Wrangler plugins through several generations of Lightroom. I find them very useful and well thought out.

Recently I decided I would like to automatically add my nickname, format “first last”, as a keyword tag. I tried using the “Extra keywords to add” option at the bottom of the Special Keyword Processing box to send this to Flickr but either LR didn’t send it or Flickr didn’t recognize it. I tried doing this as both comma separated and space separated data, and with both new uploads and republishing existing images.

Any suggestions,
Tim L.

After confirming it didn’t work, please send a plugin log, along with a note about the exact keyword you were trying to add. —Jeffrey

— comment by Tim L on August 20th, 2016 at 5:26am JST (2 years, 3 months ago) comment permalink

While looking for the setting to create a log, which I thought was at the bottom of the bottom of the settings dialog, I noticed a section “Flickr: Metadata Management” with an option to register extra “Tags” which I recognized is what Flickr calls keywords. That setting does exactly what I want. Previously, I tried “Extra keywords to add” in the “Special Keyword Processing” box of the “Metadata Wrangler” section, which does not work. I’m not sure of the difference, if any, between keywords and tags but the settings now work as expected. Sorry to have bothered you.

Thanks,
Tim L.

Oh, hah, I didn’t make the connection about the differing plugins. Yeah, the Flickr plugin wouldn’t pick up what you wrote into the exported copy with Metadata Wrangler, and Flickr won’t either since the Flickr plugin is explicitly sending the list of tags, and the Flickr plugin doesn’t know anything about what the Metadata Wrangler plugin is doing. What you’re doing now is indeed the right way to go about it. —Jeffrey

— comment by Tim L on August 20th, 2016 at 10:00pm JST (2 years, 3 months ago) comment permalink

Hi,
when uploading videos with picasaweb and viewing them in google photos they show up with the import timestamp, instead of the capture time. is that a known issue? I found no way to change that.. any idea?

thanks,
Herbert

I hadn’t noticed this before, but yeah, it looks like Google is now ignoring the capture date. The plugin is certainly sending it. As they move away from PicasaWeb, it seems they’re further lowing their already-low value of photography. They haven’t reached Facebook-level lows, but it looks like that’s where they’re headed. —Jeffrey

— comment by Herbert Poul on August 22nd, 2016 at 4:18pm JST (2 years, 3 months ago) comment permalink

Lightroom 6.6.1

On launching Lightroom I get this message “Lightroom needs to configure your system for the jf Facebook plug-in”
This message occurs after configuring and successfully using the plug-in to upload to Facebook.

Please see this FAQ —Jeffrey

— comment by Peter on September 3rd, 2016 at 6:34am JST (2 years, 2 months ago) comment permalink

Over the last three days, I began getting this error for the first time: “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.” It now occurs every time I try to upload.

I gather you’ve tried to debut this with no great success, but it’s become really a big problem for me — the export process has nearly stopped for the last three days. Once I got three photos through some how, but now it’s back to zero uploaded each time. I’m on MacOS 10.12 Sierra release candidate, but which perhaps is a factor, but it worked fine for a long time earlier on Sierra betas.

I recently wiped the OS and did a clean install, which unfortunately broke the catalog sync for all my exported files (my fault for not using the correct process of restoring from a backup). The plugin successfully scoured the Flickr archive and re-linked, but for reasons not entirely clear I had to re-upload them as a result. I got about 13,500 of 14,000 photos done, but now it’s hung.

Happy to send you a log if that helps.

I’m writing from San Carlos, CA, but formerly Paris, France, and Old Windsor, UK.

The problem is almost certainly on their side, so I doubt there’s anything you can do. )-: —Jeffrey

— comment by Stephen Shankland on September 11th, 2016 at 4:13am JST (2 years, 2 months ago) comment permalink

Hi Jeffrey,

I’ll answer all of your Flickr questions like “Flickr’s own uploader likely uses Flickr-specific servers (rather than general servers for third-party apps like mine).” if you send me an email. The answer to that one is: no difference, same APIs and servers 🙂

“Photo is temporarily unmodifiable” – maintenance, very rare, wait a couple of minutes.

“Filetype was not recognised” – corrupted JPG or file greater than 200mb (or not a image file at all.)

Cheers,
Eric

I’ve most often seen the “Filetype was not recognised” error when I know that the proper bytes have been fully sent (watching with Wireshark). I’ve imagined that the image is getting truncated while being processed at Flickr, but that’s just a guess. —Jeffrey

— comment by Eric Willis on September 13th, 2016 at 10:09am JST (2 years, 2 months ago) comment permalink

Hi Jeffery,

Trying to set up your Google Drive plugin with LR 5.7. I have successfully installed the plug in and I can successfully log in to Google Drive. I fill in everything I can but I can’t save the setup. The message says to “Make a selection in the Google Drive: Folders in the publish service section.” The trouble is that I can’t find a way to create any publish collections until the plugin has been set up and I can’t set up the plugin until I create at least one collection. Obviously I am missing something.

Please help.

I guess it’s not very intuitive when you don’t have any folders, sorry. Just make a folder within the Google Drive folder on your system, or in your Google account via the web. Then “refresh list” in the “Folders in this publish service” section. —Jeffrey

— comment by Bill Jensen on October 23rd, 2016 at 10:29pm JST (2 years ago) comment permalink

Hi Jeffery,

Greeting from Switzerland. I’ve been using your plugins for years – many thanks for your efforts!

I’m having a problem with the jf Flickr plugin. If completely publish a collection and then view a photo from the collection in the “Published Photos” section it gets marked to be republish without me changing anything. No editing, or keyword changes, just viewing. Slowly all the published photos migrate to the “Modified Photos to Re-Publish” section. It seems like when lightroom renders the preview they get marked to be republished.

I’ve disabled all other plugins and unticked all the “Metadata that Triggers a Republish” options in the plugin, but it still happens.

That along with the flickr server unrealibility means I’ve not been able to upload anything new for ages. I always have to republish each full collection and flickr usual fails part way through, meaning it never gets to the new ones.

Thanks,
Matt

Please see this FAQ. —Jeffrey

— comment by Matt on October 27th, 2016 at 3:10am JST (2 years ago) comment permalink

using Smug-mug plugin I keep getting errors after a few photos upload it sometimes now takes me 3 -5 retries to get my photos uploaded per vault, is there something I can try to fix this issue Ive been reading comments but i dont see many issues with smugmug plugin listed here. thanks

The best I can guess is that your Internet connection is spotty, or SmugMug is having “issues”. I see this kind of report often, and usually it seems to “fix itself”, which tells me it’s likely an issue at SmugMug, the user’s ISP, or somewhere in between. Just keep trying, I suppose, and hope for the best. —Jeffrey

— comment by Jo on November 22nd, 2016 at 10:20am JST (2 years ago) comment permalink

Hi Jeffrey, I’m from Holland and am using your plugin for picasaweb. It worked fine untill now (previously I had Lightroom 5, now 6CC and that transition worked also). Now I have downloaded your latest plugin because of google’s change (…3) and installed it, but the section of making an album is grayed out. Below the page it says that I am not logged in? probably something simple, but I couldn’t find it in the faq and common issues.
Hope to hearing from you soon,

Pieter Heres

See the top section of the dialog… you should be able to re-login there. —Jeffrey

— comment by pieter heres on December 4th, 2016 at 8:15pm JST (1 year, 11 months ago) comment permalink

Lightroom CC 2015.7
macOS 10.12.1
JF Zenfolio plugin 0.1.0.28

I’m uploading images to Zenfolio, and I’m getting these error messages after a couple of images have uploaded:

Unexpected HTTP reply from http://api.zenfolio.com/api/1.8/zfapi.asmx: Server was unable to process request. —&> Could not find file ‘C:\Users\zenfolio\AppData\Local\Temp\akgxzlzk.dll’.

Another example:

Unexpected HTTP reply from http://api.zenfolio.com/api/1.8/zfapi.asmx: Server was unable to process request. —> Could not find file ‘C:\Users\zenfolio\AppData\Local\Temp\ygifgdvt.dll’.

It looks like the image that appears to fail to upload is uploaded successfully on Zenfolio side, so each attempt to restart the upload creates a duplicate in ZF.

Are these errors coming from Zenfolio?

Yes, they seem to be having “issues”. —Jeffrey

— comment by Robert on December 6th, 2016 at 5:16pm JST (1 year, 11 months ago) comment permalink

Hi, Jeffrey. I’m having problems with your Lightroom Zenfolio plugin. I keep getting an error message when attempting to publish to a gallery that I created on Zenfolio using your plugin. (I have the latest version.)

It will publish a few photos and then return an error message. This is the last one from the zenfolio-log.txt file. They all seem to be similar, but not the same file that “could not be found.”

Unexpected HTTP reply from http://api.zenfolio.com/api/1.8/zfapi.asmx: Server was unable to process request. —> Could not find file ‘C:\Users\zenfolio\AppData\Local\Temp\jrjsmuhb.dll’.”
e3–TrapContextErrors = “initial TrapContextErrors called from:
[DCB6E118] @Debug line 1038

TRAP() = “called from:
[17E15AA8] @Export line 2471
[17E15AA8] @Debug line 1336

zenfolio#290 +1230.1: [902FDC28] @Debug line 988: Debug:1287: Unexpected HTTP reply from http://api.zenfolio.com/api/1.8/zfapi.asmx: Server was unable to process request. —> Could not find file ‘C:\Users\zenfolio\AppData\Local\Temp\jrjsmuhb.dll’.
about to dump LrDialogs.message() tracebackmessage:
[902FDC28] @Debug line 991
.

I have clients that are waiting to review their proofs, and it is taking my forever to upload a collection.

Thanks for your help!

Rod

This is Zenfolio having “issues”. This particular problem seems to have just cropped up. I expect they’ll get around
to dealing with it sooner than later. We can report it to them, but I suspect they already know…. —Jeffrey

— comment by Rod Pickett on December 6th, 2016 at 7:35pm JST (1 year, 11 months ago) comment permalink

Hi Jeffrey, i wonder if the plugin takes timezones into account when setting the creation date metadata? the way it is now, my videos end up 1 hour off when i import them somewhere else (mac photos e.g.). i think it expects the metadata time to be universal time.

kind regards, chris

I don’t know what plugin you might be speaking of, but Lightroom is riddled with date-related bugs, including with its handling of videos. These, unfortunately, are built in to Lightroom and a plugin can’t override them. —Jeffrey

— comment by Chris M on December 26th, 2016 at 10:39pm JST (1 year, 11 months ago) comment permalink

Hi, Jeffrey

For some time, I have used the plug in for Google Photos to upload videos. In the past 2 days, I continually get an error that indicates that the size of my video exceeds the 100MB limit (seems to be an old Picasa Web limit). Am I missing some setting that will allow the video uploads?

John

I don’t have a “Google Photos” plugin… only PicasaWeb. Google hasn’t made an API available for “Google Photos”. They do have a 100MB limit for videos uploaded through the third-party API… their own tools allow much larger uploads. Is that what you’re seeing, or are you seeing the error even though your videos are smaller than 100MB? If the latter, please send a log after encountering the error. —Jeffrey

— comment by John Dougherty on December 27th, 2016 at 10:25am JST (1 year, 11 months ago) comment permalink

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 (1 year, 11 months 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 (1 year, 10 months 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 (1 year, 10 months 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 (1 year, 10 months 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 (1 year, 9 months 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 (1 year, 9 months 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 (1 year, 9 months 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 (1 year, 9 months 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 (1 year, 9 months 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 (1 year, 9 months 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 (1 year, 9 months 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 (1 year, 9 months 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 (1 year, 9 months 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 (1 year, 9 months 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 (1 year, 9 months 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 (1 year, 8 months 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 (1 year, 8 months 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 (1 year, 8 months 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 (1 year, 8 months 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 (1 year, 8 months 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 (1 year, 8 months 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 (1 year, 7 months 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 (1 year, 6 months 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 year, 5 months 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 year, 5 months 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 year, 4 months 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 year, 4 months 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 year, 4 months 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 year, 4 months 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 year, 4 months ago) comment permalink

Hi,

I’m experiencing that page posts between a period (a few months) disappear from the Facebook page. I can see them in the list of performing posts, but they are nowhere to be seen on the page.

I’m not totally sure if this “bug” is because of your plugin or not, but this has happened twice, and both times it has happened shortly after using the plugin to upload 4-5000 images in multiple albums created via the plugin.

Running on Lightroom 2015.12 on macOS 10.12.6

I have contacted Facebook about the issue again, but last time they just closed the ticket and said “they are continually working to improve facebook jadajada…”.

Have you seen this issue before?

I have not seen it, no. Since you mention uploading a large number of photos, I wonder whether you’re bumping up against some kind of limit? —Jeffrey

— comment by JK on August 28th, 2017 at 10:21pm JST (1 year, 3 months ago) comment permalink

Hi Jeffrey,

Until recently the Flickr plugin had been working beautifully but after changing the keywords on a number of previously published photos I’m consistently experiencing the following error “Flickr is currently down (error returned by Flickr: Photo is temporarily unmodifiable)”. It looks like it’s the same error as http://regex.info/blog/lightroom-goodies/issues#comment-57039

I have also recently run the “Claim photos for photo stream” task, so I wonder if this could have contributed – prior to this I’d never seen the error.

I have tested deleting a few of the more recent photos from the feed, but no joy, and I’m reluctant to delete any more than I have because I’ll be loosing the attached Flickr history. I’ve updated the plugin to the latest version, refreshed user data and re-authenticated the plugin and the problem is persisting. Do you have any suggestions?

Best,

Tom

Writing from the UK.

I don’t think the Flickr error is related to the “Claim” operation, or anything else in Lightroom. My impression is that it’s a Flickr back-end issue that comes and goes, and other than reporting it to Flickr, the best you can do is just hope it goes away. An unsatisfying answer, I know. —Jeffrey

— comment by Tom on September 14th, 2017 at 6:07pm JST (1 year, 2 months ago) comment permalink

I keep getting this message when I try to export to zen.

Unexpected reply from Zenfolio: their system returned this error that the jf Zenfolio plugin doesn’t know how to handle: “50005: User is not an owner of an object.”

It might be an issue with Zenfolio, or perhaps with this plugin.

Additional information to pass along to Zenfolio support in case you contact them:

Target url: http://api.zenfolio.com/api/1.8/zfapi.asmx
Unix timestamp of call start: 1505432832.2852
Unix timestamp of call end: 1505432833.4348
HTTP Reply Date Field: Thu, 14 Sep 2017 23:47:26 GMT
HTTP Origin Field: WS001

Thanks for any help…

I’m pretty sure that’s an error at Zenfolio. It’ll likely go away on its own; if not, perhaps send them a note (including the information you copied here). —Jeffrey

— comment by Tim on September 15th, 2017 at 8:50am JST (1 year, 2 months ago) comment permalink

Hi!

First of all: Thanks for your great work!

I installed your flickr plugin for Lightroom. Everything works fine, except one thing: When creating a flickr publish collection, the plugin shows “only” about the first 600 groups (in alphabetical order) and the rest of the groups are not shown – the box stays white…

Is that a known issue?

All the best
Götz

Lightroom’s dialog infrastructure doesn’t do well with really long dialogs, which a list of 600 groups would create. I notice the problem especially on Windows. 600 groups is a lot…. I think Lightroom just can’t handle it, at least as I’ve written the plugin. Sorry. )-: —Jeffrey

— comment by Götz on September 19th, 2017 at 2:08am JST (1 year, 2 months ago) comment permalink

Yesterday I noticed 5 or 6 photos on Flickr viewed with ‘camera roll’ were unavailable. I have tried a few times to republish them yesterday and today but I am getting the same message others here have “Flickr is currently down (error returned by Flickr: Photo is temporarily unmodifiable)”

Just now as I tested again to get he exact error message. They were all present and republishing worked so this is an intermittent problem it seems

Yes, it seems to come and go. It’s a problem with Flickr, in their backend systems, I’d guess. —Jeffrey

— comment by Hans Erken on September 27th, 2017 at 10:26am JST (1 year, 2 months ago) comment permalink

Hi Jeffrey, first of all, your software is fantastic. I am in Oakland, CA. For the last couple days I have been trying to upload photos to Zenfolio. I am getting this message:

Networking error when attempting http://up.zenfolio.com/bradleymart/p90741660/upload2.usha. The action must be retried

When I retry, same result. Advise please. Thank you,

Networking errors can be notoriously difficult to pin down. The best I can suggest is in this FAQ, but it’s just standard stuff and not satisfying if you’ve already tried all that. )-: —Jeffrey

— comment by Bradley Mart on October 3rd, 2017 at 3:43am JST (1 year, 1 month ago) comment permalink

Hi, I’m from the UK near London.

I started using your plugin when I wanted to upload to a business page, but the standard plugin wouldn’t allow. It works fine but, doesn’t seem to allow me to publish file names with each image? When I am uploading 100s of images and someone wants to buy one, the Facebook plugin when publishing to my personal page would name each image (as their original file name that came from the camera. With your plugin however, each image is blank, no file name attributed to the image? Obviously, with a file name, the images were easy to identify…
Any ideas?

See the “Facebook: Metadata Management” section of the Export/Publish dialog. There, you have considerable control over what you send to Facebook to use as the caption. —Jeffrey

— comment by Alan Harding on October 5th, 2017 at 6:35am JST (1 year, 1 month ago) comment permalink

Hi Jeff,

Thank you a lot for your publish plugins. I use mostly publish to Zenfolio.
I have a problem after upgrading LR CC to Lightroom Classic (v7). My publish services setup for zenfolio are gone (I had a few for different types of exporting: print (High Quality), previews (Low-Quality) etc.)

Can I get them back? I have upgraded your plugin to newest version and activated it

Thanks in advance for your help
Tomasz

Lightroom should have brought all the publishing services over when upgrading from Lr6 to Lr7… if it didn’t, it’s a huge bug (that I’ve not heard of yet). Perhaps try the upgrade again by trying to open the Lr6 catalog again from Lr7. —Jeffrey

— comment by Tomasz on October 23rd, 2017 at 9:17pm JST (1 year ago) comment permalink

Hey Jeff. I just updated to Lightroom Classic and your Smugmug plugin stopped working. When I click on what remains of the publishing service it tries to open the following URL, but fails http://www.adobe.com/go/lightroom-smugmug

I don’t want to try reinstalling it before I let you know. Im hoping it can be recovered.

Thanks!

It sounds like you were using a very old version of Lightroom’s SmugMug plugin, which they passed on to SmugMug itself many years ago. My plugin precedes (and is unrelated to) both. —Jeffrey

— comment by Keir Briscoe on October 29th, 2017 at 12:14pm JST (1 year ago) comment permalink

why table with “System returned “securityError” when Lightroom attempted to use the Internet: Are you sure that your system date and time are correct?” turns on when I try to transfer my pictures from Lightroom to Zenfolio? …and it doesn’t allow to transfer any pictures. I didn’t change anything recently.
I’m writing from Canada.

— comment by Elijus on November 1st, 2017 at 12:14pm JST (1 year ago) comment permalink

I am trying to upload pictures from Lightroom to Zenfolio and I keep getting System returned “securityerror” when Lightroom attempted to use the internet:are you sure that your system date and time are correct? My system time is correct I have checked it multiple times. I also don’t have any firewalls or anything. I have spent hours on this today. Does anyone know how to resolve this?? I can log on to Zenfolio just fine on the website.

— comment by Ashley Crook on November 2nd, 2017 at 12:17pm JST (1 year ago) comment permalink

Thanks for all your terrific work. We’ve been running smoothly for years but now seem to have a problem with the Zenfolio plugin.

“System returned “securityError” when Lightroom attempted to use the Internet: Are you sure that your system date and time are correct?”

I checked the time, date, and year 3 times. Then I changed both the timezone and the date/time to be “Automatically” kept by the Apple OS. What else can we do?

A smattering of users are getting this. If you’re among them, and this FAQ doesn’t help, please report the exact version of your OS, your browser, and of Lightroom. I don’t know what the problem is, but I think it’s somehow related to SLL security certificates. —Jeffrey

— comment by Tim Harris on November 4th, 2017 at 4:41am JST (1 year ago) comment permalink

I am getting the same error other users have mentioned, I get this message, “System returned “Security Error” when Lightroom attempted to use the Internet” Are you sure that your system date and time are correct?”

I checked time and date and it was all fine, I even reset it. I tried to switch to the Safari browser rather that MOZILLA firefox Nothing helped. I was trying to upload photos to my Zenfolio account from Lightroom 4. I had done a successful upload just two days ago. Please HELP!

Jolene Grabill
Kansas

It turns out that this is an issue with your old version of OSX. Unfortunately, at this point the only recourse is to update the operating system, sorry. Please see this FAQ. —Jeffrey

— comment by Jolene Grabill on November 30th, 2017 at 6:06pm JST (11 months, 15 days ago) comment permalink

System returned “securityError” when Lightroom attempted to use the Internet: Are you sure that your system date and time are correct?

I have used your service for 4 year.. no problem until recently. Are you saying I need to update my macbook? Thanks for your advice. I am super bummed at the moment but hoping to find a fix

Yeah, sorry, as mentioned in the FAQ, Zenfolio just couldn’t continue to support the old insecure protocols. What’s inexplicable is how Apple didn’t support the secure ones until so late. Your browser likely works because the browser itself has the support, but Lightroom apparently relies on the OS for support. It’d be nice if Adobe included the support in Lightroom, but one doubts that they’d bother, since it would benefit so few people. None of that makes you feel any better, I’m sure, sorry. —Jeffrey

— comment by Karrah on December 11th, 2017 at 7:37am JST (11 months, 5 days ago) comment permalink

Hello Jeffery.
I managed to stumble upon you LR > Facebook plugin as I could not get the Native LR one to work. I’m experiencing a small issue which I hope you can help with…

I have my personal Facebook page (Geoff Moore) and then I have a 2nd page for my photography (Geoff Moore Landscape Photography)

Within the settings for your Plugin > Lightroom Publishing Manager > Facebook Tools I have selected (Geoff Moore Landscape Photography)

Within > Facebook: Albums In this Publish Service > I have selected Time Line Photos

The problem I’m encountering is that the image gets publish to the timeline on my personal Facebook page (Geoff Moore) and NOT (Geoff Moore Landscape Photography) and I cant figure out why. Can you assist?

Regards
Geoff

What albums you can and can’t publish too has seemed to be a buggy area for a long time (see this FAQ). Your photo page is accessed via your personal-page credentials, so they’re all mixed as part of one Facebook account, and Facebook should be telling the plugin all the albums you can post to (personal and professional). The “Timeline Photos” album must be from your personal account, but apparently there’s none from your pro page? This is all usually a mystery to me (bugs that I have no control over tend to be that way), but you can try sending the plugin log after, and I’ll take a look. —Jeffrey

— comment by Geoff Moore on February 10th, 2018 at 10:52pm JST (9 months, 5 days ago) comment permalink

Thank you Jeffrey for creating such a great tool!

Getting the below error —

Plug-in error log for plug-in at: C:\Program Files\Adobe\Adobe Lightroom Classic CC\Flickr.lrplugin

**** Error 1

This plug-in’s post-processing task did not finish successfully.
Flickr API returned an error message (function upload, message Filetype was not recognised)

That’s Adobe’s Flickr plugin, not mine. Flickr’s complaining that the copy uploaded couldn’t be recognized as a photo. I doubt this problem is with the pluign… it’s probably a (hopefully-temporary) issue at Flickr. —Jeffrey

— comment by Singh on March 27th, 2018 at 12:13am JST (7 months, 20 days ago) comment permalink

Hello! I’m writing to you from Davis, California.

I’m having a sudden problem with your export from Lightroom to SmugMug plug-in.

After installing your most recent plug-in into the most recent version of Lightroom CC Classic I find that after some number (maybe 5 to 10) of images have been uploaded the uploads no longer work. It’s like your plug-in thinks the files have already been uploaded. I’ve tried uploading to a different gallery but that doesn’t work. I am able to export the image to a hard drive and then use the SmugMug web uploader to add the same image.

I’m using your plug-in 20180305.319 (I wish I could do a copy/paste out of your plug-in to get that) and using Lightroom CC Classic 7.3.1

Thank you for any insight you might provide.

I’ve provided in the Website field above a link to the gallery in which I’m attempting to upload images.

The next time you run into this issue, please send a plugin log, including a note that is explicit about which image you thought should have uploaded where, but didn’t. About the copy/paste idea, that’s great… I’ve added it to the new version that I just released. Just click the version number to copy it to the clipboard. —Jeffrey

— comment by Adam Bridge on May 12th, 2018 at 7:13am JST (6 months, 4 days ago) comment permalink

Hey Jeffrey,
Recently I have had an issue uploading images from LR Classic CC to Zenfolio. They upload with my name as the title of every image instead of the image name given in LR. Even when I check the button to rename using the file name.
Thanks,
Jay

Love the product. It has helped me immensely over the years. Thank you.

The filename used for export is unrelated to the title and caption sent for each photo. Those are set in the “Zenfolio: Metadata Management” section of the Publish/Export dialog. —Jeffrey

— comment by Jay on June 4th, 2018 at 10:52pm JST (5 months, 11 days ago) comment permalink

So sorry to hear Smugmug pulled the rug out from under you. I have submitted a comment to them specifically asking that they respond quickly to you and get this invaluable tool working again. Sheesh!

It’s not fair to say they they “pulled the rug out”…. they did announce it a month ago, and I simply didn’t notice the announcement, which is certainly not their fault. (I didn’t have their developer forum in my newsfeed; I do now.) The bigger issue for me is that they’re pushing developers to go live with a new API that they themselves explicitly call “beta”. I didn’t intend to bother looking at the new API until it left “beta”; why should I trust it if they don’t? I thought it was odd that they left the “beta” label on it all these years, but I suppose that they have their reasons. And anyway, my plugin continued to work fine with their original system so what did I care? So, now I care. We’ll see. They’re good folks over there, so I’m certain things will work out. —Jeffrey

— comment by Bob Powell on June 14th, 2018 at 8:56am JST (5 months, 2 days ago) comment permalink

Bummed about the Smugmug issue but glad to know it’s not just us. Keep us posted! We love your plugins. Cheers.

— comment by Ben on June 15th, 2018 at 7:11am JST (5 months ago) comment permalink

Thanks for the update. Hoping this is resolved soon, thanks for your work.

— comment by Cody Sims on June 17th, 2018 at 2:31am JST (4 months, 29 days ago) comment permalink

Longtime reader, user-of-plugins, and owner of you regex book.

Your plug-ins, particularly the SmugMug one, are a critical part of my workflow, so I will be eagerly awaiting a fix. Thanks for all your great work over the years!

(from NJ)

— comment by Steve Strickland on June 20th, 2018 at 6:34am JST (4 months, 26 days ago) comment permalink

Hi Jeffrey

I too wrote to Smugmug …because your plugin is so much easier than theirs (or anyone elses!). So it’s been a real blow losing it…

This is what they said:
Jeffrey can update his plugin using our new API and everything will work as it was before – or even better since it is a new API – which I guess you already know looking at the above comments. But thought it might help make them more aware of third party developers’ needs!

Really looking forward to a solution.
Cheers
John F

Sigh, I think that they don’t understand the meaning of the word “beta“. They also don’t respond to my questions about the new API. I’m just in a holding pattern until they bother to reply. )-: —Jeffrey

— comment by John F on June 20th, 2018 at 7:35am JST (4 months, 26 days ago) comment permalink

I’m also a longtime user of your Smugmug and Facebook plugins (and a couple others less frequently) on several computers. The breakage has really messed up your workflow and trying out the Smugmug Publish one I really miss yours — that one (as far as I can tell) doesn’t even upload metadata (like date) or preserve the sort order from LR! Big pain. The API change also broke a plugin I use to insert html tags for a gallery worth of images into WordPress, which is really annoying too (anyone know anything that will generate HTML tags for a whole gallery?). But I reached out to SM about yours. The “heroes” pushed it off to the api team who hasn’t replied (mailed them last Friday). Look forward to the restored version and keep up the good work!

Yeah, I’m still waiting to hear back from the API team, too. —Jeffrey

— comment by Andy Gavin on June 21st, 2018 at 2:27am JST (4 months, 25 days ago) comment permalink

Living in the Midwest, Polk County, Iowa or the Des Moines metro area.

I can’t even tell you how long I have been faithful to you using your many Lightroom Goodies! A long time for sure, and Lightroom user since 1 November 2007 0r 2008, and have been using SmugMug since 2009.

This just tears it, in what SmugMug has done to you and the many of us that publish our photography from Lightroom to SmugMug.

Right now I feel that my hands are tied and I am unsure what steps I need to move forward to publish or upload photos to SmugMug. Yesterday was the last straw using your Lightroom Plugin, SmugMug says now it cannot authenticate my login no longer, so no photos are leaving Lightroom to be published to SmugMug.

I will gladly wait for you but I can’t wait to long publishing photos. Seriously I have a couple hundred people looking for their photos on my photography website.

With that said I want to hear or read your two cents worth on how I should publish my photography in the interim while you make your updates in correcting your Lightroom Plugin. I just feel lost right now because SmugMug pulled a fast on you and all of us.

There are other plugins out that that may work because they were written to use the beta API that didn’t exist when I first wrote mine. (And I didn’t update to it when it came out because it was beta and not intended for production use.). Anyway, try other plugins — they won’t interfere with the data in my plugin. Using other plugins will mean that for those photos my plugin won’t learn the relationship between Lightroom photo and SmugMug copy, but that’s perhaps a minor issue, one that in theory can be remedied later via the “File > Plugin Extras > SmugMug Extras > Associate” operation. —Jeffrey

— comment by Verne Wonderlich on June 21st, 2018 at 8:06pm JST (4 months, 24 days ago) comment permalink

Hi Jeffrey,

Has Smugmug started responding to your questions about the new API yet? Is there anyone at Smugmug we should contact to express our frustration on your behalf?

-Ben

I did get some help, yes, but not as helpful as one could hope. Then the contact went on vacation, and I myself had a previously-scheduled trip to Mt. Fuji, so forward progress has been slow. But it’ll pick up again soon…. —Jeffrey

— comment by Ben Brammeier on July 4th, 2018 at 3:05am JST (4 months, 12 days ago) comment permalink

You might want to put a note at the top of your SmugMug page that says the software currently doesn’t work. Finding this page is NOT obvious.

Earlier I wrote a comment about a problem with the error window that the plugin produced that resulted in requiring a force-quit of Lightroom (there was no way to make the box go away – it was modal and there was no cancel or close button)

Thanks for listening.

Good point, I’ve added something to the top of the plugin page. About the dialog, you should be able to clear it by just pressing the enter key. Unfortunately, Lightroom doesn’t let a plugin know how big something will appear, and despite my having spent considerable effort coming up with heuristics to try to predict what I need to do to keep a dialog smaller than the screen, apparently I’ve not done enough. In particular, it’s difficult with retina displays that have a different actual-pixel-dimension from an apparent-pixel-dimension. Until Adobe adds hooks to help a plugin here (or until I get smarter), I’m afraid we’re stuck )-: —Jeffrey

— comment by Adam Bridge on July 4th, 2018 at 7:40am JST (4 months, 12 days ago) comment permalink

Metadata Wrangler not working. “Could not load the post-processing filter from this plug-in.” in the Export dialog. Version 20180701.163. Lightroom Classic CC 7.4. Any ideas?

Normally this comes from having deleted the plugin files on disk (and if so, just download, unzip, and move them into place, or put them somewhere on your system where you want them to live and re-point the plugin manager at them), but if it’s the first time it could be a bad unzip… try using a different tool to unzip, or a different browser to download. —Jeffrey

— comment by Doug Kaye on July 9th, 2018 at 12:46am JST (4 months, 7 days ago) comment permalink

On another topic besides the Smugmug plugin, there was a note inside Lightroom today (I think from the Facebook publisher plugin) that FB was going to discontinue “uploads” from desktop applications (I think Aug 1, or Sep 1, can’t remember). Is this going to affect your FB plugin? I hope not, because that’s also part of my regular workflow (and great). Manually uploading images is a pain, and since I have everything in LR it’s super easy to do.

Yes, my plugin (and all of them) will cease to work from Aug 2. I was able to get high-ups at Adobe in touch with high-ups at Facebook, looking for some kind of reprieve, but I guess nothing came of it. )-: —Jeffrey

— comment by Andy Gavin on July 10th, 2018 at 3:12am JST (4 months, 6 days ago) comment permalink

Hi Jeffrey
What is the latest with the SmugMug plugin for Lightroom? I have been without it for over a month now and the publish process native to Lightroom is nowhere near as functional. I’m really struggling without yours working.
Is there anything we can do as SmugMug registered users to try to expedite your queries to them?
Have you any news?
Thanks and kindest Regards
Mike
(Registered plugin user)

(July 12, 2018) They’re now actively working with me to help me move forward. I hope for a plugin in a week or so. —Jeffrey

— comment by Mike on July 11th, 2018 at 9:08pm JST (4 months, 4 days ago) comment permalink

Great news that the SmugMug plugin “upgrade” is underway, but that is another huge bummer about the FB one. And they are unlikely to be very flexible. I used their API professionally for a while and they were loath to do much of anything for any 3rd parties once they had set their mind on policies. But it’s really retarded and annoying. Clearly users want to upload albums into their system and clearly it’s VERY convenient to do it directly from LR if you are a serious photographer who uses it (and I don’t know many who don’t). What, are they going to make us dump them to a temp directory and then upload them one at a time manually or something? It’ll just make me stop posting more than 1 off photos to FB!

— comment by Andy Gavin on July 13th, 2018 at 8:56am JST (4 months, 3 days ago) comment permalink

Hi,

After installing your google drive plugin, LR keeps popping up a dialog saying that “Lightroom needs to configure your system for the jf google drive plug-in.” It tells me this upon LR startup, and whenever I mess with the plug-in manager. Also, twitter and order prints plugins aren’t showing up after installation, but i wonder if that’s a side effect of the google drive issue (they were installed after the google drive plugin).

Any help greatly appreciated. Thanks… (writing while traveling through malaysia)

Please see this FAQ. —Jeffrey

— comment by Alex on July 13th, 2018 at 10:01am JST (4 months, 3 days ago) comment permalink

Trying out the beta, can’t find auto-destinations. Are they going away?

I’ll have to look at adding those back in once the dust settles. A bunch of fringe things like that got put off, sorry. —Jeffrey

— comment by Cody Sims on July 30th, 2018 at 3:50am JST (3 months, 17 days ago) comment permalink

Awesome to have it back in business! Uploading as we speak. I assume “create folder” is on the cleanup list? That would be much appreciated as syncing my 10000 folders (after manually creating one) takes some time 🙂 But already a huge win over the Smugmug publisher.

Yes, “create folder” and “update metadata” are on the todo list once things settle down. —Jeffrey

— comment by Andew Gavin on July 31st, 2018 at 8:32am JST (3 months, 16 days ago) comment permalink

In the process of re-installing Lightroom so the new SmugMug plugin will work I noticed the Facebook export plugin is gone from your page. Scrolling through some of the comments above I see Facebook has decided to block uploads from desktop devices.

First, what a kick in the teeth. But thank you so much for getting SmugMug back up and running. You’re the best.

Second, the FB plugin still works when exporting to our business page. We posted a few hundred photos this past Sunday at a trade show. I just reinstalled the last version of your Facebook plugin I had previously downloaded, re-authenticated to Facebook, and uploaded to an album on my business page with no problems. It wouldn’t work when exporting to an album on my personal account though.

Are they allowing exports to business pages? Is this a weird fluke?

I figure that shoe is going to drop and we should start working a manual FB upload into our workflow now but… one can hope FB pulled it’s head out of it’s ass, right?

-Ben

I expect the shoe to drop. The tens of thousands of folks that use my plugin are one or two orders of magnitude too few to be worth their attention. )-: —Jeffrey

— comment by Ben on August 9th, 2018 at 3:15am JST (3 months, 7 days ago) comment permalink

Jeffry, I note that the new plug-in apparently no longer has the Associate function in the SmugMug Extras, is that one of the fringe features which will be reimplemented? I’ve got hundreds of SmugMug photos which have lost their association into my Lightroom catalog. My current work around is to use the SmugMug Lightroom plug-in, but I’ve used yours for years and prefer it. Thank you. – Michael

Yes, I expect that will come back, though the “Associate” feature has always been dicey, since there’s sometimes simply not enough information to make a correct guess. )-: —Jeffrey

— comment by Michael Heathman on August 13th, 2018 at 7:19am JST (3 months, 3 days ago) comment permalink

Hi Jeffrey –
Trying out the new Smugmug plugin. I don’t see the option in the Settings window anymore to allow the creation of a new gallery. Is that a known issue or am I missing some new setting?

That feature will come back eventually, once the dust settles on the recent big changes. —Jeffrey

— comment by Bob Powell on August 20th, 2018 at 9:51am JST (2 months, 27 days ago) comment permalink

Is the Flickr plugin currently working? It’s failing unconditionally for me with “Corrupt Reply from Flickr” (and dialog boxes with HTML error pages saying nothing more useful than “request failed” — the 500 page). I tried reauthenticating but that fails the same way.

Flickr is currently having issues with their API servers. They’re aware; I suspect it’ll be fixed soon. —Jeffrey

— comment by Ken Fox on September 10th, 2018 at 8:36am JST (2 months, 6 days ago) comment permalink

Upgraded to current version of the LR Flickr publisher plug-in and now unable to up load any images – plug-in aborts with message about corrupt response from Flickr. First image is actually added to photostream but without putting it in the album instructed or any pre determined groups. Kept retrying as part of the message sting indicated a Flickr response suggesting engineers working on it, so ended up with 11 duplicated images when I rechecked this morning.

I wonder if its something to do with me still on LR6 (version 6.12). Using Firefox as web browser (latest version)

Is there anyway of going back a release of the plug-in to check this?

Steve

It’s a known issue at Flickr… they’re having ‘issues’. I expect them to fix it quickly. —Jeffrey

— comment by Steve Chasey on September 10th, 2018 at 3:50pm JST (2 months, 5 days ago) comment permalink

Unexpected HTML Reply from flickr after putting in authentication code
Says 400 Bad Request

I’m guessing FLickr? They’re having “issues”. —Jeffrey

— comment by Daniel Lee on September 11th, 2018 at 4:46pm JST (2 months, 4 days ago) comment permalink

Jeffrey – re my post of 10 Sept – now 3 days on and no change. No sure it’s a pure Flickr issue as they ought to have fixed by now……

Steve

I reached out to Flickr, but no response yet. —Jeffrey

— comment by Steve Chasey on September 13th, 2018 at 5:00pm JST (2 months, 2 days ago) comment permalink

Hi,
Why the Flickr plugin integrated with Lightroom is working and not your plugin ?

Best regards
Eric

It should be working now (with the latest release of my plugin). The underlying problem was my fault, but it was compounded by Flickr responding with a misleading error message. Instead of a data-API reply informing me of my mistaken data, they replied with a web page saying that they were experiencing technical difficulties. Because I took them at their word on that, it took a while before I actually noticed that the mistake was mine. —Jeffrey

— comment by Eric LEGIGAN on September 16th, 2018 at 12:32am JST (2 months ago) comment permalink

Hi Jeffrey

I too was having problems with flickr (new LR catalogue, connecting to a flickr account for the first time). I was running 20180906.401. I’ve now updated to 20180917.402 and I can now log in successfully. Thanks for your efforts!

Paul – London, UK

— comment by Paul Walmsley on September 19th, 2018 at 4:38am JST (1 month, 27 days ago) comment permalink

Hi Jeffrey, any ETA on when the update metadata at smug mug will be back? I really miss this one…
Thanks as always for stellar tools!

SmugMug more or less stopped answering my emails a month or so ago, leaving a big metadata-related bug (on their side, I think) unaddressed. I’m in a holding pattern until I hear from them. I suppose they’re busy. /-: —Jeffrey

— comment by Kwai Lam on October 4th, 2018 at 2:51am JST (1 month, 12 days ago) comment permalink

Hi Jeffery,

i have a problem with LR 7 (7.50, german) and the metadatawrangler plugin. I think up to LR version 6.x it works fine. Now it’s stealing the focus from the preset if it’s part of the preset.
I checked es more than once. If i activate a preset with this plugin included then after a short moment the preset lost the focus. It doesn’t matter if the plugin is enabled or not.

At least the last three version include 20181004.167 doesn’t work.

Thanks
joerg

I don’t think it’s something specific to this plugin…. I did some tests and found that Lightroom randomly took focus away from the preset name, regardless of what preset I tested and what plugins the preset did or did not have. I could find no pattern. I never noticed this issue before and now that I do it doesn’t really bother me, but YMMV. In any case, it’s a Lightroom thing. —Jeffrey

— comment by josch on October 7th, 2018 at 2:47am JST (1 month, 9 days ago) comment permalink

Hi Jeff,
The new Lightroom 8 disables your amazing Google drive plugin. My whole operation is now slowed to a snail’s pace without it. Will be able to issue an update? Happy to pay you again…
DL

All the plugins were updated within one minute of Lr8 being announced (I’d been preparing all week), so using the most recent version should be fine in Lr8. If not, please send a screenshot of the plugin manager…. —Jeffrey

— comment by david levine on October 16th, 2018 at 10:49pm JST (4 weeks, 2 days ago) comment permalink

Jeffrey- I’ve been using the Zenfolio plugin for years and am generally happy with it. I’m noticing that I get frequent time-outs in the middle of uploads and that when it happens, Lightroom is frozen until the time-out is resolved. I have a good internet connection. A) is there something I can do to cut down on the connection errors? B) is there a way to prevent the plugin from completely taking over Lightroom during these events so that I can at least keep working while the connection is restoring?

This sounds like a problem deep within Lightroom and/or your OS. I’ve gotten a lot of reports over the years that plugin uploads to Zenfolio are super slow compared to uploading via their browser interface, and that, too, may be something deep inside Lightroom, but since I can’t reproduce the problem, I can only vaguely speculate. I suppose some WireShark logs might help shed some light on it, but networking is not a strong area for me. In any case, the way that the plugin interfaces with Lightroom for the upload is the same code used in my other plugins, none of which garner such consistent “slow upload” complaints, so part of me has to wonder whether the problem isn’t somehow at Zenfolio. I’m just at a loss here. )-: —Jeffrey

— comment by Lee on November 5th, 2018 at 2:11am JST (1 week, 4 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