Known Issues with my Plugins
Jeffrey's Plugins
for Lightroom 2 or Later:
Known Issues with Lightroom 2.0 and/or my plugins...
Updated September 16, 2008 (update #9)
- There seems to be a Lightroom bug when using my plugin with a filter ("export action") like LR/Mogrify, such that an error is reported: “Whoa, file does not exist immediately after waitForRender. Please let Jeffrey know.” I haven't been able to repeat this, but it apparently happens only on fast Windows machines. For now, the "fix" (if you can call it that) is to not use the filter (or to use a Mac).
- Lightroom 2.0 has an issue with exporting keywords. See that link before reporting any keyword-related issues. (Adobe now has a fix)
- On Windows, you can't fully cancel an export that uses a plugin (at least, my plugins). If you try to cancel it, it will appear to cancel, but the generation of images continues in the background. You have to restart Lightroom to fully cancel the export, and more than that, it leaves a temporary folder full of images that you have to delete by yourself. This is a Lightroom 2 bug.
- It seems that you can't have non-ASCII characters in the path leading up to a plugin folder, at least on Windows. If you do, you'll get messages about failing to load files. The workaround at the moment is to place the plugin into a folder whose path has only ASCII. (This is a Lightroom bug that applies to how my plugins load themselves, but likely does not impact other plugins.)
- The author of these plugins (Jeffrey Friedl) doesn't actually use the photo services that his plugins are written for (Flickr, SmugMug, Facebook, etc....). I'm not even sure how I became the export-to-whatever guy, but anyway, because I don't use these services on a day-to-day basis, I have to rely on users for bug reports and feature requests.
To-do List
Things I'm keeping on the radar to implement in my copious free time....
- Deal with Flickr empty title issue.
- Solve this: figure out a way to make large lists of galleries manageable.
- Figure out a way to incorporate into the Lightroom library information about images uploaded outside of the plugin.
- 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.”
- The ability to use tagging to control which Metadata Wrangler preset should be applied.
- Add the ability to turn image metadata into tags/keywords that are uploaded with the image.
- Add tag recognition to the auto-destination template stuff.
- Add more plugins (for other upload services that garner enough interest).
- Write a “run any command” plugin.
- Write a geo-tagging plugin.
- Have a way to re-upload metadata without actually re-exporting the image.
- Support SmugMug gallery-creation quick settings.
- SmugMug: solve this comment: “my list of galleries is growing so large, the plugin export gallery selection page is growing huge! Would it be possible to have a category selection first, and then a second drop down list to select the galleries only from that category.”
- SmugMug: look into this comment: replacing an image doesn't update keywords. I suspect that this is a "feature", but must look at it and perhaps try to find a way around it.
- SmugMug: look into this comment about auto-uploading the source file to SmugValut along with the exported version.
Add the “auto destinations” feature to the Flickr plugin.
(added in 20080904.20)
Leave a comment...
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 when I try oy export to flickr.
+45.9: At line 13463:Assertion failed(!)
Hit OK button to get me over “+100: At line 13463:Assertion failed(!)” and gave up… Had to Force Quit Lightroom.
I think I fixed this as of the 20080814 versions of the plugins. —Jeffrey
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
Hi jeff,
I wrote a comment before.
I’m still having the same problems with the plug. It’s the same as Ed, E. Walker and Keith Rowley.
+1449.3:At line 14006: Assertion Failed(!)
I press (OK) and the first number changes as many times as I press it, had to force quit Lightroom.
I just don’t see the time when I can use the plugin, it will be so useful.
Thank you very much for you job!
I think I fixed this as of the 20080814 versions of the plugins. —Jeffrey
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.
sorry - my previous comment was altered on posting.
smugmug.images.upload should read:
smugmug.images.upload
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.
Can’t export. First message: +17.6: At line 14225:Assertion failed(!).
Then I hit OK button. Second message: Unable to Export: An internal error has occured: ?:12809: assertion failed!
Those first numbers (17.6) changes every time.
LR 2 on mac leopard. Latest version on plugin.
Thanks for working on this!
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
Hi Jeffrey,
I’ve read your comments on this page, and understand how busy you are. I love your Flickr plugin, and am hoping you can help. I am experiencing the same “assertion failed” error that others have reported. I am using plugin version 20080817.11, OSX version 10.5.4, and LR 2.0. The specific numbers in the error message vary between attempts, but a representative error message looks like this: “+8.2: At line 14255:Assertion failed(!)” I can send you the log file if that would be helpful.
I have tried tossing and reinstalling the plugin. I have tried placing the plugin at different locations (currently at username/Library/Application Support/Adobe/Lightroom/Modules). I have tried reloading the plugin using the “reload” button in the plugin manager. I have tried tossing the LR2 prefs. I’ve tried using a different default browser, in case that makes a difference (Safari 3.1.2 and Firefox 3.0). I’ve tried different Flickr accounts. None of this has made a difference, and the failure is 100% consistent.
I would love to get your excellent Flickr export plugin working again! Please let me know if you need any additional information from me, or if there is anything I can do to help.
Thanks,
Ben
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
I seem to be experiencing issues with the Flickr uploader on 2.0 (final).
In the midst of uploading a set of photos, I get the error:
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.
Thanks for taking the time to create these fantastic plugins and sharing them.
I’d like to suggest some further ideas for the flickr plugin:
1. If the develop settings for a photo haven’t changed, but the metadata have (title, caption, keywords/tags, or security setting selected in the export dialog), and if the replace checkbox is selected, then sync the metadata up to the server, without uploading the photo again.
2. Create a new metadata field associated with the plugin in LR that records the security status of the photo on flickr.
3. For the photos selected in LR and sent to the flickr export plugin, add the ability to — instead of uploading/updating the photos — scan those photos on flickr and (a) verify they’re still there (haven’t been deleted on the website) and update the records kept in LR accordingly, (b) sync any comments from flickr down to a new metadata field in LR, (c) sync any changes to the security status made on flickr back down to the LR metadata.
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.
20080817.11 still has the assertion failed error in every case. It no longer locks up lightroom though, click OK and it exits the export.
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, I still get error ‘+130.7: at line 14317: Assertion failed’ in the latest release (
20080827.12).
I hope this will get fixed soon, as this is a most convenient plugin!
Jesse
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.
I’d love to see the next flickr/picasaweb versions, if possible, to include the scene and location metadata as keywords if at all possible - would take a huge amount of time out of my tagging and help remove my location/scene keyword mess which I now use in the iptc panel part
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
Firstly this is an amazing product that is much appreciated!
The only problem I’m having is with the ‘Location’ field, which doesn’t get exported as a Flickr tag. Country, State and City all work without problems, it’s just the Location field that doesn’t work for me. I’ve checked out the Adobe information on keywording issues with Lightroom via the link you provide, but it doesn’t seem to relate to this particular issue with the Location field.
I am using Lightroom v2.0 and version 20080905.21 of your Flickr plugin.
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:
Oops, let me try that again.
First:
Whoa, “/var/folders/46/46AMTf2wFge1I8WC4U2PrU+++TI/-Tmp-/66241122-D86C-4420-9E6F-2D8F265F0FC0/_MG_9200.jpg” does not exist immediately after waitForRender. Please let Jeffrey know.
Then:
Couldn’t open _MG_9200.jpg: /var/folders/46/46AMTf2wFge1I8WC4U2PrU+++TI/-Tmp-/66241122-D86C-4420-9E6F-2D8F265F0FC0/_MG_9200.jpg: No such file or directory
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
Hi again Jeffrey,
Just wanted to follow up…my issues with using your Flickr export and the LR/Mogrify plugin are happening on a Mac. OSX 10.54 on a 2.16GHz Intel Core 2 Duo iMac. Hope that helps.
Peter
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
Jeffrey -
Re: Feature Request
Great work, and thanks for your tremendous effort.
I believe there would be great interest in a Shutterfly plugin for LR 2.0. Shutterfly offers popular photo books and calendars, as well as great quality printing. Some Scott Kelby literature explicitly recommends Shutterfly for its print quality. I think there would be a lot of photographers (including me) interested in a Shutterfly plugin.
Thanks again.
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
Tried downloading your Flickr plugin for Lightroom 2 and I can’t get LR PluginManager to recogize it. In Plugin Manager, when I click on “browse” then click on the “flickr-jfriedl.lrplugin” folder…
I’ll interrupt here to say that at this point, don’t click Open, click Add Plug-in. That folder, itself, is the plugin. —Jeffrey
….and click on OPEN, it shows me the WIN folder, if tell it to OPEN the WIN folder it appears to be empty, and the “no items match your serch” message. What am I doing wrong? I extracted the files. I know this is an operator malfunction, but it appears that Plugin Manager is looking for a lrplugin FILE, and not accepting the lrplugin FOLDER. Thanks.
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
Hi Jeffrey,
Waou very good Flickr export !!
I love it… But, it missing some options to be perfect (for my usage
1. Tokens replace. For example, I want to convert a lens info to an other : 24-70 mm f/2.8 -> AF-S Nikkor 24-70 mm f/2.8G ED, or ¹⁄₃₂₀ sec -> 1/320 sec.
2. Set privacy of my photo in Flickr base on color label, is more graphic in the grip view in Lightroom than tags.
3. Set resolution of the export base on privacy. Example, public photo to 1600×1600 pixels, other full resolution.
4. It will be nice is I can reexport only the tags, not the picture in Flickr (I don’t now if is possible with the Flickr API)
Et voila
Oups… one more..
5. Assigne group to a photo in Flickr based on tags will be fantastic !!!
About the report I just made, here’s another example that just occured
Picture at http://flickr.com/photos/_mll_/2903077576/
Keywords in lightroom: anophèle, light, lumière, mosquito, moustique, mur, n&b, wall
Tags in Flickr: anophèle, mosquito, n&b, lightroom (the latter being auto-added per my settings by your plugin)
So, 5 tags dropped in this case !!!
Are you sure that this is not the dropped-keywords Lightroom bug mentioned earlier on this page? Have you run the fix-it script provided by Adobe? —Jeffrey
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.
Well the problem was actually mine, and is solved now. Sorry about the annoyance, and thanks for your help.
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 love your Metadata Viewer configurater.
Now that I can see the Longitude/Latitude and Altitude Fields, is their anyway that they can be made to be manually edited within Lightroom?
Ina
Sadly, no, Lightroom’s plugin infrastructure doesn’t allow for it (which is, to me, maddeningly frustrating — Lightroom lets a plugin modify all the fields that no one cares about, and does not let the plugin modify the fields people actually care about, like GPS, keywords, etc….). —Jeffrey
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
I get badServerResponse, nativeCode=12152 when exporting to picasaweb very often. actually it usually takes 2-3 retries to export album
I’d guess that your internet connection is having issues. I’ve not had other reports of this kind of error. —Jeffrey
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
hmm.. don’t this this is problem with my connection, this is definitely something related to lightroom because never had problems when exporting from Picasa even right after export from Lightroom failed.
in any case thank you for all your plugins
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.
Got a couple of these error messages:
“An internal error has occurred: ?:15940: attempt to compare string with number”
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
While going insane and pulling out my hair, I figured out what the exact issue is in my last post! Dual displays! I occasionally hook my laptop up to an external LCD monitor when I need accurate colors, and I had left the export dialog and plugin manager on the external monitor.
Most programs will open windows on the primary display if the secondary is disabled, but apparently not lightroom.
Needless to say, this is a LR2 bug, and has nothing to do with your plugin, which I find incredibly useful, so thank you!
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
Hi, Great Plugin thanks for creating it.
I have downloaded the Facebook exporter and i think it’s great. I have recently set up a “business” page in face book and would ideally like to send the pictures there instead of to a gallery on my normal page. I have had a look round your site but cant find any indication that this is possible. Is it possible and if not available yet is it an enhancement you would consider in a future update. Of course if it is already possible could you point me in the right direction to make it happen.
Many thanks
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
The zip file for version smugmug-20081015.33.zip appears to be invalid. I’ve tried downloading and opening on my Windows Vista machine a couple times over the last few weeks and Vista and WinZip are unable to open it. The file size is 141kb when downloaded. Can you check this file?
Thanks alot for writing these plugins!
mike
I found the issue: http://www.flickr.com/help/forum/en-us/83926/
I live in Belgium!
I am having the same probem:
I get badServerResponse, nativeCode=12152 when exporting to picasaweb for large format images (I use to send to PicasaWeb so I can then use Shutterfly to print…would be awesome to add Shutterfly plug-in)
I load 50% sized photos and it works splendifourously.
Great stuff otherwise, thanks!
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 Jeffery,
Just updated Lightroom 2 with the Lighroom 2 Smugmug plugin, I had been using the version 1 plugin before checking for a new one.
Unfortunately I keep getting:
+286.5: At =(tail call) line -1:
Return header ERROR
———————————————-
errorCode = “badServerResponse”
name = ‘The requested header was not found
”
nativeCode = 12150
The number following the “+” changes.
Sometimes the upload works, sometimes it doesn’t.
These are large files I’m uploading, 10-15 meg, but that shouldn’t matter.
Any ideas?
Thanks
Roger
P.S. I do appreciate your time and effort writing and supporting these plugins.
Hi Jeffrey,
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.
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
Could you please tell me where I’m going wrong as I’d love to be able to use this facility?
Manythanks.
Paul
bug report flickr plugin with LR 2.1:
when uploading an image to flickr with more than 40 keywords no keywords at all are displayed on the flickr website although flickr has set the limit to a maximum of 70 keywords. Please note that all keywords are still in the file itself but those keywords do simply not appear anymore on the flickr website except when you click on ‘more properties’ but that’s not the way it should work.
Inserting more than 40 keywords using the website interface of flickr gives no problem.
So I suspect either a problem with the flickr plugin or a hard limitation being set for uploading pictures with the flickr api.
Can you have a look on this bug please?
Thanks
Fabian
It seems to be a Flickr bug… the magic number for me was 26. If I include more tags than that, they’re all ignored. I’ve send a note to Flickr to ask about it…. —Jeffrey
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.
Hello Jeffrey -
I’m getting the same type and syntax of error as Paul on October 31, but using the Facebook plugin. The line numbers the error occurs on are different, but the error syntax is the same.
Mac OSX 10.5.5, Lightroom 2.0. I have LR Mogrify2 installed, as well as the latest Flickr plugin, which works just fine for me.
If my error log would be useful, I’m happy to send over for your review.
Thank you very much for all that you’ve put into these amazing workflow tools, I appreciate them very much.
Steve
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.
Hi Jeffrey,
Good job with the plugin. Small cosmetic change request/bug. I use a 24 hour clock (H:mm:ss, Dutch regional settings). When I do so the plugins reports for example: “ETA: 6.5 hours, tomorrow at 2:15%p”. The %p at the end is not needed I think, at least not for me.
Keep up the good work with the plugins since they really contains good feature and integrate well!
Regards, Ben
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.
I am getting the same issue.
+11.4: At line 15578: ?:16440: attempt to index field ‘?’ (a nil value)
It won’t export to facebook anymore…
Thank you for your wonderful work.
For me to make any sense of the numbers in the error message, I need the exact version number of the plugin. I put this as an annoying flashing red warning on the comment-submission page, but still, sigh, most people still don’t take the 10 seconds required to tell me the version number. If someone doesn’t care enough to spend an extra 10 seconds, I’m not sure I’m going to bother wasting my time trying to address the issue (an issue that may well already be fixed in a subsequent version). —Frustrated
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?
Oh, and if it helps, I’m on Vista SP1, with Lightroom 2.1
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’ve downloaded & installed the flikr plugin but the “Export” button is greyed out and it says “Upload destination not yet set.” However, when I try to enter anything in the upload destination dialogue box, it won’t let me & the drop down box won’t do anything. I’ve tried restarting lightroom but to no avail. Help please.
Fixed in version .46. I’d send this to you directly if you’d include your email when you leave a comment, but you didn’t. —Jeffrey
I’m another one of your fans!!!
I understand “moonlighting” and hobbies, so please consider this as input to what I’m sure is a difficult problem with little time… I kick off one large export (> 300 photos, may be less to repro but I’m not sure). When it is going, I do anything with the plug-in and I get errors which causes the export to fail and abort. This can be launching the plug-in manager or trying to export another gallery (even to the file system, but it won’t let me get there). I have snapshots of the errors if you want them.
Basically, the first dialog info box is +84.3: At line 18317: photohistory: not logged in
Let me know if you need screenshots, more details, etc.
Again, thanks for saving hunderds (thousands) of us endless hours! You da man!
Gary
Oh. My. Goodness.
When I work on the plugins (which is always), I have the “reload plugin on each export” option checked (in the bottom-right “Plugin Author Tools” section of the Plugin Manager). That way, changes I make to the code are loaded right away, and my testing goes much more quickly.
I tried it today with the reload option turned off, and wow, I got the errors you reported. I realize now what the problem is, but an easy fix is not presenting itself to me. Until I can figure it out, please turn on that “reload plugin” option for all my plugins, and it’ll work just fine, and you can have multiple exports running at once.
What’s shocking to me is that this was not reported until now. —Jeffrey
UPDATE: fixed as of versions posted on Nov 11 2008 —Jeffrey
Problem reported yesterday on ver 20081111.37 is still there with 20081111.38 downloaded this morning. Except that the Blank destination field has been replaced with a message.
I was able to restore the plug in by logging out and reauthenticating the Facebook access after a Lightroom restart. So, bottom line, 20081111.38 is working now. I have tested on Vista 32bit and will test on 64 bit later. Cross fingers!
I think this is finally fixed in .40! —Jeffrey
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
Camera make, model, etc…. uploading to Flickr, used version 20081113.46.
info still not showing up.
It’s probably one of your plugin or Flickr settings, but I’m not going to try to debug this via comments. If you want help, leave your email address next time. —Jeffrey
Jeff,
“minimize embedded metadata” was filtering the camera info; once unchecked, the data appeared fine.
Thanks,
Hi! I’m trying to export from LR2 to SmugMug. It seems that around every third photo I get a message saying that the file size is too large, even though it shouldn’t be. I’m exporting 12MP RAW files to full res JPEG. Other files that are the same size upload just fine to SmugMug. The dialog box gives me a choice to continue or stop the export (a total of 35 images). Exporting a single “too big” image also fails to work.
I’m pretty new to both LR2 and SmugMug, so it’s probably just something I’ve overlooked… but maybe you could give me some ideas to try? Thanks for your generosity - I feel fortunate to have come across your site!
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.
Still having authentication issues. This has been going on with every version for the past 45 days or so up to .50 not sure what to do
Oops! Flickr can’t find a valid callback URL.
An external application has requested your login credentials and permission to perform certain actions on your behalf, but has failed to include all the required data.
Wow, I’ve never seen this one. Please send the log (referenced in the upper-right of the Plugin Manager) via email. Also, be sure you don’t have a local firewall blocking Lightroom…. I’ve heard reports of firewalls being an issue lately. —Jeffrey
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.
Thanks Jeffrey - hadn’t spotted the Plugin Extras…
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
Oh, I was referring to LR 2.0’s smugmug plugin
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
_____ _____ _____ _____ _____ _____ _____ _____ _____
.
Hello and your Flickr plugin is a real good work !
I just have a bug (when I change some export parameters) : AgDate.formatDateInUserFormat: %a specifier not yet implemeted
How can I export now to Flickr ? I’ve reinstalled the plugin, but the bug persists..
Thanxs !
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
Thanks for the info, makes total sense when you know more about facebook!
Nice plugin and very helpful. Thanks for sharing, it will make my life easier a lot!