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

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

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.

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.

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

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

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.

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.

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.

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.

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

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!

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

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

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

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

Oups… one more..

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

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.

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?

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

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

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.

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

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

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

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

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.

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

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.

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.

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.

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?

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

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

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

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

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.

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.

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

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

_____ _____ _____ _____ _____ _____ _____ _____ _____
.

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

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

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

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!

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

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.

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.

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.

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

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.

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.

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

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

Thanks!

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

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.

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

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

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

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

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.

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

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

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

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

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?

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

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

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.

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

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)

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

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

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”!

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

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

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?

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

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

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

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

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

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

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

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

-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).

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

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!

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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.

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

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

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

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

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

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.

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!

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

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

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

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!

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

>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)

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

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

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

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

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

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

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

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

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

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

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

> 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.

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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?

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

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

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

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

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

Hi Jeffrey,

Following my prior comment, you posted an updated version of the Flickr plugin, however, it has still not resolved my issue. I have tried reinstalling several times but to no avail… Below are the dumped log entries:


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

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


Anthony Knights

It turns out that the error is embedded in the preferences file, which now can’t even load, so the preferences file has to have any entry with “LoginCache4″ in to removed. If you zip it up and mail it to me, I can do it for you. Or just upgrade to Lr4 and bask in the amazing advances since Lr2 —Jeffrey

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

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!

Hi Jeffrey,

I am Martin from Vienna. I have the problem with the flickr plugin as Anthony from Tokyo:

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::

I removed all “LoginCache4″ entries from the prefs file myself, which works. However next time I am starting LR the error appears again.
I am using LR2 on Win7/64. Flickr plugin is the most recent one (20120406.270) – I updated yesterday from a 2010 version.

I’ve seen this before and I’m not quite sure why it happens, so I’ve got to investigate, but Lr2 is very old so it’s difficult to justify a top spot on the todo list so far. It’d be much easier on me if folks upgraded to Lr3 or Lr4 —Jeffrey

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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