smugmug-20081204.51.zip
· Version History
· Installation instructions
· More Lightroom Goodies
· My Photo-Tech Posts
· My Blog
This Export-to-Smugmug plugin has been completely rewritten for Lightroom 2.0 and later, and is not compatible with Lightroom 1.
(See the old plugin page for a version compatible with Lightroom 1.x)
Please see the known issues before reporting bugs. If this is your first look at my export plugins, please see the announcement post for an overview and some important information.
| 20081204.51 | Try to work around a fairly rare Lightroom bug that sometimes causes large exports to fail with the note Whoa, exported image doesn't exist after waitForRender by pausing for a few seconds to see whether the image shows up. If not, then you still get the error and the export fails. |
| 20081127.50 | The counting of previous uploads (for the All/Update/New of the Upload Destination section) was not working right. |
| 20081125.49 | Another fix for a bug that had disabled plugin presets (for captions, etc.) |
| 20081124.48 | Perhaps fixed a problem whereby the "Upgrade Now" button didn't work for some Windows users. We'll see whether it works when those users upgrade from this version to whatever version is next. |
| 20081123.47 | Fixed a plugin crash when using the plugin's built-in preset system. |
| 20081122.46 | No problems from the upheaval recently, so pushing back the expiration a bit. |
| 20081117.45 | Oops, wouldn't let you log in / authenticate if you weren't already. Doh. Fixed. |
| 20081117.44 | No new functionality in this version, but a huge upheaval in the underlying code to repair an unfortunate design choice I made early on in the development that had limiting consequences I'd not foreseen. There are likely bugs introduced in this version, and as such, it has a short expiration date to encourage updates as those bugs are reported and fixed. If you do run into an error, please send (via email) the log referenced in the upper-right of the Plugin Manager. Thanks. |
| 20081114.43 | Fixed a "attempt to compare string with number" bug. |
| 20081113.42 | Fixed yet another list-of-upload-destinations bug. There are sure a lot of edge cases here. |
| 20081111.41 | Fixed a crash that happened sometimes when there are not yet any preexisting destinations at SmugMug. |
| 20081104.40 | Perhaps squelch a spurious error dialog |
| 20081103.39 | I don't know what's causing the slew of networking problems that have been reported, but I've gone ahead and added a retry mechanism. It'll retry operations that failed due to network problems indefinitely, but you can cancel out of the retrys if you like. If the problems are some kind of flakiness on the machine (somehow introduced in LR2.1???) this may allow operations to complete. |
| 20081031.38 | Now works properly with the shadow GPS data maintained by my geoencoding plugin. |
| 20081027.37 | Added some extra debugging code to try to track down some of the asserts that a few users have been getting. |
| 20081024.36 | Added an option to not add Lightroom keywords as metadata when uploading images. This allows you to not send any keywords if you also have them stripped from the image itself, such as when enabling the "Minimize Embedded Metadata" option, or when stripping keywords with my Metadata Wrangler. This applies only to keywords in the Lightroom library that are marked for export; those not marked for export are never sent. (Also related, recall that due to a Lightroom bug, images in a catalog upgraded from Lightroom 1.x with Lightroom 2.0 lost the ability to export keywords until a fix is applied.) |
| 20081022.35 | Addressed (and perhaps even fixed) a bug introduced in the previous build. |
| 20081021.34 | The "replace" functionality now works even when the target image had been deleted at SmugMug. There is a bug with the SmugMug API that was causing this to fail, but despite that bug still existing, I now implement the replace functionality using a different API method that SmugMug added at my request. (If you use the "replace" mechanism, give SmugMug some love for having done this.) Small update so that a stuck background version check does not disable the plugin. Added the ability to put the "select at time of export" item at the top of the destination list, as had been requested a few times. Added some items to the template language that had inexplicably been missing: {HH}, {MIN}, {hh}, {min}, {ss}. |
| 20081015.33 | Internal change to the user-agent string that the plugin sends when uploading, to better conform to web standards. Added back the ability to set the print size via DPI and inches/cm. I think it's more confusing than anything (because it has nothing to do with what size something gets printed at unless you take care to set the printer DPI the same), but someone asked for it and I should really leave it up to the user. The plugin now allows you to use any color space registered on your computer when generating images to upload. I don't think this will be useful for very many people, but perhaps it might be a benefit when combined with some printing services(?) |
| 20080924.32 | I created a "Metadata Management" section in the dialog, and moved some things into that from other sections. Fixed a race condition that sometimes caused the export destination to not appear in the synopsis of a closed "Upload Destination" dialog section. Also fixed an issue whereby doing a "replace" would abort when the image previously uploaded to SmugMug was no longer present at SmugMug. Now, if the image isn't there anymore, the "replace" turns into a simple upload. (A "replace" goes to whatever the gallery the original was in; but a replace that turns into an upload goes to the export's destination gallery.) Occasionally, a "replace" of a image still results in an abort due to a problem that I've reported to SmugMug. Moved the items in the "Upload Management" section into the "Upload Destination" section, since they are really quite related. |
| 20080923.31 | Sigh, just realized that the "check for new version" stuff did break in 2.1. Totally my fault, sorry. Fixed. |
| 20080921.30 | Oops, the ability to use my template tokens in the 'extra keyword/tags' area, that I added last week, didn't actually recompute the tags on a per-image basis, applying the tags computed for the first image to all the others. That's now fixed, and tags are recomputed with each image. |
| 20080920.29 | Enhanced the {Rating} token to allow {Rating=*} to create "*****" through "". You can put most anything instead of the asterisk, so you might consider {Rating=great } to end up with "great great great". Since these forms result in nothing for an unrated photo, you can use the "|" pipe to provide a default "when empty" value, such as "rating": {Rating=*|"unrated"} |
| 20080918.28 | Added the ability to use template tokens like {Filename} in the "extra tags" input box. |
| 20080916.27 | Pushing some untested support for gallery-creation quick settings. I wrote this a few weeks ago, but may never push it if I wait to test it fully, so I'll just push it and let those of you who know SmugMug better test it for me Update an error message to reflect an apparent bug in LR that causes LR to hand off a file to my plugin for upload before the file is actually available. This seems to happen when using LR/Mogrify or other filters. Updated the url shown in the "status" section of the plugin manager |
| 20080916.26 | Finally have the upgrade button working on both Win and Mac. Since I returned home last week, I now have access to both kinds of machine for the first time since LR2 was released. I can sum up the 5 hours I spent wrestling with the unzip code in three word: I hate Windows. Microsoft owes me five hours of my life back. Note that you may have to install this one by hand in order to get the newly working upgrade button... it's the next upgrade that should be easy-as-click. |
| 20080914.25 | Added a few more descriptive tooltips to the example-token dialog |
| 20080914.24 | Oops, fixed a boo-boo introduced in the previous version. |
| 20080914.23 | Remember (again) the upload-destination across exports. It used to work, and I'm not sure when it stopped working, but it must have been really annoying while it was broken, sorry. |
| 20080914.22 | Fixed tokens "OriginalWidth" and "OriginalHeight" in templates. Added a bunch of new template tokens and a new token filter. Added a token-examples button, which brings up a dialog listing all tokens and their value for an example photo (the first photo in the export list). |
| 20080905.21 | Fixed an "undefined global: DestinationSynopsis" error that could happen when using a preset with a "select at export time" upload-destination setting |
| 20080831.20 | Handle a race condition in the upgrade logic that sometimes results in a superfluous "You have version XYZ, but version XYZ is now available" message |
| 20080829.19 | Added a bunch of new items to the template language. |
| 20080829.18 | Oops, left some debugging cruft that results in an "empty" dialog if the logged-in-user has no galleries or the like. Fixed. |
| 20080828.17 | Minor tweaks |
| 20080828.16 | A few more tweaks to report a failed upgrade attempt a bit more clearly |
| 20080828.15 | Whoo-hoo, finally figured out the "assert" problem that some people without galleries were having. When upgrading, ignore a status of “50” (which means “out of disk space”) from the unzip the plugin performs. It seems Windows often reports this status even when there's plenty of disk space left, so until I can understand it better, I'll just ignore that code. |
| 20080827.14 | Fixed the Caption {Filetype} token (was broken for DNGs). Made some Layout tweaks in my preset dialogs. Added titles to the tools sections (were missing on OSX) |
| 20080817.13 | A few cosmetic changes to the auto-destination dialog. |
| 20080816.12 | Sigh, left some debugging stuff in there that prohibited the auto-destination stuff from actually working. Sorry for the version churn. |
| 20080816.11 | I spent tons of time wrestling with the “Auto Destinations” feature, which I'd never really done properly for SmugMug. It seems to work now. Lots of little tweaks as I cleaned things up. Added a bunch of stuff to the Plugin Manager, including a “What's New” button that shows up next to the “Upgrade Now” button when a new version is available. |
| 20080814.10 | Fixed infinite cycle of 'assert' messages one might get in odd situations |
| 20080812.9 | Fixes (I hope) a "bad argument #1 to '?' (table expected, got nil)" error |
| 20080811.8 | Moved and renamed the debugging logs to a temporary folder, and added log Show/Delete buttons to the plugin's custom section of the Plugin Manager. |
| 20080806.7 | Fixed {State} and {Rating} in preset templates. |
| 20080805.6 | Oops, the Windows versions had lost the ability to upgrade themselves. Once this version is installed manually, subsequent versions should be able to upgrade as discussed here. |
| 20080804.5 | Fixed "Access to undefined global: LrError" error that happens when trying to report a login-related problem. |
| 20080804.4 | Fixed a couple of internal errors related to the "choose destination at time of export" feature |
| 20080804.3 | Handle the fact that the upload-size limit for SmugVault users is half a gig.
There were also some changes under the hood related to logins and Lightroom Export presets. These changes shouldn't have any noticeable effect... unless I introduced a bug. We'll see.... |
| 20080804.2 | Should now work with SmugVault. |
| 20080729.1 | Initial public release |
See the known issues before reporting bugs. Also, when reporting bugs, please include the OS, the version number of Lightroom, and the version number of the plugin. Seriously. I need the full version number or I likely can't do anything but ignore the message.
Jeffrey, thanks for all of your efforts over the last several months supporting us with your LR (Smugmug) export plugin. I was plesently surprised today when I upgraded LR to V2 and saw that you had a new plugin which is another step forward.
Also I was pretty proud when I read that you are Ohio born and still have family here. Have a good rest of your vacation here and enjoy this special time with your son. There is no rewind button time goes by fast.
Thank you, Jeffrey!
We are infinitely grateful to you!
I downloaded your 7/29 zip file, but there was no file in it that LightRoom recognized as a plugin. I looked for a file in the zip with lrplugin in it and there was none. Am I missing something?
-wick
The zip contains a folder that you point the Plugin Manager at. See my writeup on install instructions for details. —Jeffrey
Great plugin. I’m only seeing the first keyword added when I upload though - is there a way to get all the keywords to upload. Probably missing something obvious
That’s a Lightroom-wide bug that’s (now) on the known issues page. —Jeffrey
I’ve just activated SmugVault on my account, but the SmugMug plugin still says SmugMug won’t accept CR2-files. Any plans for an update that will support SmugVault?
Fixed in .3 —Jeffrey
Hi - this is a fantasatic plugin which I’ve now installed for Lightroom 2. I used to use the “Run Any Command” piglet in Lightroom 1.4.1 - I can’t see how to execute the same command with this new version of the plug in. I’m probably doing something really silly. Can you help at all please?
Many thanks
I’ve added this to the todo list, but the list is long )-: —Jeffrey
Hi!
I love the metadata field named Uploaded To SmugMug…
How can I add that field to my Metadata Field List .lrtemplate that I created w/ your Metadata Configuration Manager?
Found it after a little digging and luck. Just add to your template:
info.regex.lightroom.export.smugmug2.uploaded
Hope that helps everyone.
You can also replace “uploaded” with “*” to get the whole SmugMug section (a header and the two items). I actually couldn’t get the individual items (”uploaded” and “url”) working on my Mac. I must investigate. —Jeffrey
On Vista, * gives me the Section w/ just the Uploaded field.
Jeffrey, great plugins! I was beginning to use this smugmug plugin and had some success until today when I got this error message:
couldn’t render image: readnegative: dng_error_bad_format
only got the error using this plugin, the flickr and facebook ones as well as exporting to disk seemed fine.
That’s very odd. If you get that again, please report it to Adobe. I recall something similar a while back related to LR 1.4.0 (which was addressed in 1.4.1), but have never seen anything like it in relation to LR2. In any case, it doesn’t smell like something that should be related to my plugins, so I’m surprised you get it with one but not the others…. —Jeffrey
Hi Jeffrey
Plugin works great with LR2 and after having fixed the keyword upgrade issues from LR1 (export disabled). Many thanks!
The only glitch now I found is when I do the following:
- update some keywords locally, e.g. add a few extra keywords. No other editing.
- upload the image again with “replace the most recent previously uploaded version” option enabled
= new keywords are NOT shown on smugmug
Any idea why that could be ?
Many thanks and best regards,
Markus
This is probably a “feature” that I need to try to look into. I’ve added it to my todo list. —Jeffrey
Jeffrey - thank you for sharing your work, sincerely. I am trying to decide between using your plug-in for export to smugmug or buying star*explorer. I don’t think I need all the features of star explorer, but I do like the ability to apply smugmug “Quick settings” when creating an album via my upload tool (star explorer). Do you envision expanding the “create album” functionality to take advantage of this feature of smugmug? Or do you expect to put more development emphasis on the features that are applicable across the various export plug-in’s (e.g. - keywords, title templates, etc)?
Thanks again for sharing the results of your hard work with the rest of us,
peter
I’ve not heard of the Quick Settings feature of SmugMug, so I’ll have to look into it. Development has been generally slow the last few weeks because I’ve been on vacation. (I’ve got a cold at the moment, so there’s no development until I’m over that). —Jeffrey
Jeffrey, I use and love your SmugMug plugin - thanks. I am getting an error message when I attempt to use the “Automatic Destinations” feature.
I’m using a single token {Folder} and I anticipate the plugin will use that to create a new gallery using the Lightroom folder name (I guess in my SmugMug ‘root’ and I can’t specify a category), and then export the photos there. I’m getting error message “Unable to Export: A internal error has occurred: ?16981 attempt to concatenate field ‘?’ (a nil value)”.
The LR folder name is “2001-09-03 - 200sx - Deca with skyline club”
Any suggestions? A bug or finger trouble on my part?
All fixed in .10.
I also second the request made by PeterM above regarding “Quick Settings” these are essentially templates for the gallery customisation settings, allowing you to set things like the privacy and theme settings. You edit the QuickSetting template via the SmugMug web interface, and then use it when uploading photos.
Cheers, Patrick
I’ve got the Quick Settings stuff coded up, but I can’t get it to actually work. I’m waiting to hear back from the SmugMug guys on it… —Jeffrey
> I spent tons of time wrestling with the “Auto Destinations” feature, which I’d never really done properly for SmugMug.
> It seems to work now. Lots of little tweaks as I cleaned things up.
Jeffrey, awesome! Auto-Destinations are working beautifully now, thanks so much for responding so quickly. You even now allow me to specify a category in the token editor - wow!
It would be cheeky of me to ask for QuickSettings too right now I presume
Love the plugin.
It would be awesome if there was an option to automatically upload the CR2 and XMP files to SmugVault when exporting an image, rather than having to export a second time.
Added to my todo list. —Jeffrey
Hi again, two small things I’d like to suggest. When I use token {Filetype}, it works fine with JPEG and RAW giving 3 character filetype, but with DNG it gives “Digital Negative (DNG)”.
Would it be possible to have {Filetype} provide “DNG” as a 3 character string?
Doh, that’s a Lightroom bug. I’ve worked around it as of version .14 of my SmugMug plugin. I’ll report the bug to Adobe.
Second thing, 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.
This would be much appreciated.
I’ll add it to my plugin todo list. —Jeffrey
Hi - Adobe have released a script which fixes the keyword export issue (by setting the export info on every keyword for you). Details at http://kb.adobe.com/selfservice/viewContent.do?externalId=kb405074&sliceId=2
Jeffrey - Thanks a lot for such a great plugin - One question that has come up since testing your plugin in V2 is … Is there an option to just sync your library with SmugMug - Say I delete a picture out of an album of 1500 photos but don’t want to upload the images again - would just like the 1 deleted image from my library to be removed from the SmugMug Gallery … Any Idea? Thanks again.
This is a big problem that I’m not quite ready to tackle. Once my plugin todo list gets a bit smaller, I’ll have to give it some thought. —Jeffrey
wow, jeffrey i am forever grateful.
over the last few months i scanned several thousand negatives of my childhood, and without this plugin i would have spent endless hours figuring out a reliable upload process.
Hi Jeffrey
I installed the latest version for lightroom 2 and I got 14 error messages. I’m on mac 10.4.11. Let me know how I can send you a copy of the log. Small note I put the plug-in manually in it’s place cause it wouldn’t automatically.
First a huge THANKS YOU Jeffrey for all your hard work!
I have looked at the known issues but I might have missed this: I tried cancelling an SM upload as ~I realised I was sending it to the wrong gallery and the ‘cancelling task’ jst hung - well it was still there 5 mins later
Just thought I’d let you know;D
Jeffrey,
Great plugin, much appreciated. I do have 2 suggestions for the next revision.
1. Showing the estimated time of comepltion for the upload is great, but how about the actual upload speed?
2. The ability to create a NEW gallery from within the plugin.
Thanks so much.
#2 is already there (see the “tools” section of the Export Dialog). I could try to calculate the upload speed, but it’s of marginal use, and there’s almost no space in the progress-bar status for it. I already go to great lengths to contort the ETA to get it to fit reasonably in as wide a range of situations as possible; I don’t think the upload speed will fit. —Jeffrey
I have over 100 galleries… Would it be possible to change the “Upload to your smugmug gallery” control from a menu style popup to a scrolling menu popup with a scrollbar? It takes some time to scroll to the bottom of the list…
Keep up the great work!
thanks
dan
Lightroom doesn’t offer me the ability to create a scrollable anything, so it does whatever it does. If SmugMug were to have a hierarchical gallery scheme, I could have the list be hierarchical as well (as I do with the Zenfolio plugin), but given the current limitations, I’m not sure what I can do. I suppose I could create a virtual hierarchy via first letter of the gallery name, or something like that…. —Jeffrey
I love this tool and have come to rely on it any many ways.. my two wishlist items for it though are:
1) Expand Replace/Update Functionality
-I know right now if I upload a batch of 250 photos, and it aborts on 200, it will now that it still has 50 to upload if I have never uploaded. Though if I upload the 250 successfully in a lower resolution just to get the images available and want to go back and upload the full size after its done it doesn’t currently have the ability to keep track of that and I have to keep starting over from the beginning of 250 or manually reposition and reselect my images to upload neglecting the ones that did get replaced.
2) Notifications
-If uploading large batch of photos from my home computer, I would love to know if it aborted or was successfully, or heck even if it reaches certain thresholds like 50% complete. More so total completion though and aborted to know if I need to run home on lunch to restart the upload.
3) Error Handling
-Skip Image and Continue; I would love it if it had an option to continue upload when less than X number of errors; skipping those images that caused errors and then at the end of the upload display the error messages box stating which images were skipped.
-On Timeout, Wait and Continue; If a timeout occurs wait X time then try again Y number of times.
-Error Severity, on X type of errors continue, on Y type of errors halt.
Thanks Again, I hope SmugMug is paying you something for your efforts.. or is there a Donation Page that I am just missing?
Christopher
All fine ideas… if only there were more hours in the day. )-: At least #2 is easy enough to work around: just check SmugMug itself, to see whether the images are up. If not, skip lunch and run home. (SmugMug doesn’t pay me, but has been generous in providing free service. I don’t draw much attention to it, but there is a donation link within Lightroom, in the Plugin Manager.) —Jeffrey
Jeffrey - excellent work! This plugin is saving me so much time and effort. Looking for the donation option now…
Thank you for providing this (what appears to be a) useful tool.
I so far have not been able to get it to work. It is installed. I do have LR 2 installed. It does properly log into SM. But, the resulting upload is nothing more than a single “dot” or no photo at all. SM shows the file name, etc., but it doesn’t look like any actual photo data is being uploaded. I’ve tried this in both my protected and unprotected galleries. Am I doing something wrong? (I’ve tried exporting both a DNG and a JPG.. both have same results).
(I also just did an “export to this folder” option instead of temp. The resulting exported photo that is generated by the plug-in is ALSO just a single pixel type image and not a valid converted or exported file.. so the issue lies locally and not with the upload process) Help!
Are you perhaps telling Lightroom to resize to a 1×1 image? —Jeffrey
I’ve tried to load 20080905.21 on my Vista machine. The machine gives me the message that it is an invalid file. I’ll be using it with Lightroom 2.0.
What would the fix be?
Perhaps try to re-download and re-unzip the plugin. I’ve heard no other problems using these on Vista. —Jeffrey
Is there any way to get the SmugMug plug-in to remember the last gallery uploaded to? I generally upload single files, and after a few hundred, selecting the same gallery over and over is a pain…
Also, does the update function (write over current version) work if the plug-in is not in the default folder?
Excellent plug-in though, your efforts are to be commended!
Doh, that’s annoying. Sorry. Fixed in .24 —Jeffrey
Hi, I just installed the latest version today, and got the following error when registering with lightroom:
Plug-in error log for plug-in at: /Library/Application Support/Adobe/Lightroom/Modules/smugmug-jfriedl.lrplugin
**** Error 1
An error occurred while attempting to load this plug-in.
The plug-in description script (Info.lua) is missing.
Could you please help?
Thanks,
Sean
Perhaps there was a problem when you unzipped the download? Do you see Info.lua inside the plugin folder? (In your example, do you see /Library/Application Support/Adobe/Lightroom/Modules/smugmug-jfriedl.lrplugin/Info.lua?) If not, you might want to re-download and re-unzip. —Jeffrey
The list of categories does not populate in the Lightroom plugin.
It never has in several installs: including LR 1.4 and 2.0
I therefore can not export to SmugMug. (I suppose because it doesn’t know where to send them)
I am able to connect/login to smugmug using the plugin.
It’s just the “In Category” drop down selector does absolutely nothing.
And I have many categories on smugmug and a pro account if that means anything.
I really really need some help, I’m wanting to upload pictures from years past. (a lot)
scott
Jeff,
Not sure how, but you are correct. The “Image Resize” was set to 4 x 4 px on export. Having a “Doah!” moment right not. Thanks again!!!
Unfortunately, when I try to add the latest plugin (v28) to a new LR2 installation, it fails. LR2 tells me that the schema is invalid and that it has to disable the plugin as soon as I add it. The metadata wrangler installed fine, so perhaps something went wrong with today’s change.
Jeffrey,
I have a small bug with your most recent LR2 plug-in 20080918.28 (actually the bug may be in previous versions as well).
I noticed that my focal length metadata was way off in one of my smugmug galleries. For example, instead of reading 64mm, it reads 640000mm. I have confirmed that this only happens when uploading from a .tif file. I tried uploading the same image from the original .CR2, a converted .jpg and a .tif file. Only the uploaded tif file had the wrong focal length. Everything else looks OK.
Thanks for a great plug-in!
Brad
I love this plugin, it has really helped get my pictures put there for friends and family. One request that i would have is that there is a way to have the Auto gallery creation profiles at the top all the time so a person doesn’t have to scroll through all of their galleries before getting to the auto creation profiles. Just a thought…
The SmugMug plugin for Lightroom 1 works perfectly, but after several attempts to use the newest plugin for Lightroom 2 it keeps giving me this error: An internal error has occured. Access to undefined global: file
What do I need to do? I’ve tried cleaning out everything in the folder the plugin resides, then reinstalling. Same result.
Just installed and used the -32 Smugmug plug-in with LR 2.1 (RC1). It worked perfectly. When I started, I was getting an “internal error” message and I thought it was due to 2.1, but found it was because I had -21, which may have “expired”. When I used the LR Plug-in Manager to try to install -32 over -21, it kept installing -21 again, so I deleted -21 and manually downloaded and installed -32 and everything was fine.
Thank you for keeping these up to date
Great plug-in Jeffrey - here’s a feature request:
Export to multiple locations. I find I often want a copy saved to different locations, e.g two folders and one to smugmug (i.e. one a psd, one to print and one to my Smugmug site)
Very time consuming when doing it with more than one file so being able to save apreset that allowed for export to several locations would be cool
thanks
Simon
You can already save to local disk at the same time you upload (see the “Export Location” section of the export dialog), but it’s a different matter to export two different sizes/formats at the same time. I agree that would be killer – I’d use it myself for my own blog, where I always have to upload two sizes of each image – but it’s a fairly weighty feature to add, so it’ll likely be some time. More likely, some future version of LR will allow a preset to be made that encapsulates other presets. Until then, make an export preset for each common situation, then select the files and just invoke the two (or whatever) presets. It’s less convenient than it could be, but not too arduous. —Jeffrey
The latest Lightroom SmugMug plugin 20080924 seems to have a bug. When I am exporting to Smugmug, it also exports to the last disk location that I exported to.
It does this despite your having set the “Export Location” (the 2nd section of the export dialog) to “Temporary folder”??? —Jeffrey
Just to mention also that it hung on one export last night. Uploaded to five galleries last night , including the culprit gallery, one image hung and was still hanging this morning.
I’ve never run into that myself, but it doesn’t surprise me a whole lot… I’ve spent more time on features than on quality error handling, which is understandable, I suppose, while there’s so much low-hanging fruit (feature wise) yet to be plucked…. —Jeffrey
I’ve downloaded SmugMug plugin smugmug-20080924.32.zip multiple times but am unable to extract the files. I keep getting an error message that the file is corrupted.
I’m not sure what to say… over 1,000 people have been able to run that specific version of the plugin. What version of what software are you attempting to unzip with? —Jeffrey
Downloaded again this AM and it worked fine. But I ran into an issue when I uploaded some files to smugmug. I always rename my files in lightroom to something like this OCT1108-001.jpg. I had done this with a batch of files before uploading to smugmug. But on smugmug, the camera-assigned filenames appear, not the ones I changed them too! Any thoughts why this would happen?
Images created for export are named as per the template you chose in the “File Naming” section of the dialog. Are you sure it was set as you wanted (likely to “Filename”)? —Jeffrey
Thanks for the support on the LightRoom Plugin for SmugMug. The question I have is after installing the latest version I get a message that this plugin will expire in nine days. Is this a new feature from your side or Lightroom?
Regards,
Danny
It’s not new… it’s been there from the beginning. It’s explained here. You’ll be able to update to a newer version before it expires. —Jeffrey
Hi jeffrey,
I am getting an “image too large” pop up. SmugMug has eliminated their 12mp limit. If you upload an image larger than 12mp they resize it. This is a new feature so maybe it is not yet incorporated into your plugin. I verified with SmugMug that they were not generating the flag.
Having SmugMug “clip” my uploads eliminates a resize step in my workflow.
Thanks,
Kurt Rodholm
Jeffery,
Sorry for the false alarm. I just noticed that the pic I was trying to upload was CR2 format!! I did have JPG as the upload format but the CR2 source caused the size flag. When I convert to DNG first everything is OK. I normally do this on import so I missed this error.
Thanks for a VERY useful tool.
Kurt Rodholm
Hey Jeff,
this plug-in is a God send!! Thanks so much. However, I dont know how to use the darn thing!! lol..
I managed to install the plug-in into my LR 2.0, but im lost from there on.
Please help me out!! I got loads to upload and hopefully if everything works out, I’m thinking i’ll go pro!!
Regards,
ali
P.S. do email me the steps (baby steps pls.! lol)
Hi,
I am getting this error when trying to export photos to SmugMug:
“+156.5: At =(tail call) line -1:
Return header ERROR
—————————————————————-
errorCode = “timedOut”
name = “timed out”
nativeCode = -1001
_____ _____ _____ _____ _____ _____ _____ _____ _____
.”
I am using Lightroom 2.0 and the latest version of the plugin (20081015.33), using Mac OSX 10.5.5.
Feel free to shoot me an e-mail if you have any questions/comments. Thanks.
Hi Jeffrey,
got this error message again ( I think it’s the same as before)
“An internal error has occurred: ?:15940: attempt to compare string with number”
All I can tell you is that I was uploading to SM again - about 3 uploads in total and one location on disk
Simon
ps- thanks for your reply to my earlier feature request;)
pps
just to say that I have also had one image hang (all night) while uploading to SM - just re read the others posts and it jogged my memory;)
I sent you a message not long ago. I realized that for whatever reason when I try to logon to smugmug from the plugin, it is not finding smugmug. I have the correct info entered. Then I clicked for your blog and it won’t appear either, and both list “application not found” My internet connection is working fine, so it isn’t that the internet is not working right. I’m using windows xp pro and the most current version of your plugin.
It seems like I’m just a tiny bit away from makingi it work. Doesn’t it almost working make you crazy?! Me too! Especially since it is working on my other computer.
My hair may all fall out before I figure this out!
Thanks so much in advance.
Mary
I’m guessing that there’s an issue with how your browser is installed on your system, because Lightroom uses your system libraries and such when it accesses the web, and uses your browser when it wants to bring up a page like my blog. The “application not found” error message hints at this. To test, load a geoencoded file into Lightroom and bring up the metadata panel to show the latitude/longitude, then click on the arrow next to it. It’s supposed to bring up Google Maps at that location, but I suspect you’ll get the same error. (If you don’t have a geoencoded image handy, just grab any image from my blog that has a map link under it… pretty much all images taken outdoors, such as these.)
If you find that indeed, even that doesn’t work, then the issue is unrelated to my plugin specifically. Unfortunately, I’m no expert on XP administration, so I’d suggest reinstalling IE, and if that doesn’t work, soliciting advice from the Lightroom forums at Adobe. —Jeffrey
Hi Jeffrey — thanks for the plug-in! I’m hitting an issue with the most recent version: “Unable to Export: An internal error has occurred: ?:21047?: assertion failed!” Any suggestions on what I should check? Thanks, Radu
Ever since I downloaded the new Lightroom 2.1 and the new plugin version 20081027.37 on windows vista, i have been unable to export to smugmug. I recieve the following error:
+243.9: At =(tail call) line -1:
Return header ERROR
—————————————————–
errorCode = “badServerResponse”
name = “The requested header was not found”
nativeCode = 12150
I had it working perfectly before the new download. Please let me know what i can do.
question regarding the “expiration” of the plugins…
will the old ones continue to work? or MUST we upgrade?
thanks,
niteowlgary
They cease working once they expire, so yeah, you must upgrade if you want to continue to use it. That’s the whole point of the expiration in the first place. —Jeffrey
Hi Jeffrey,
Is there a way to have the plugin automatically update? When I click on the “update now” button, it does nothing, I have to manually download and unzip the new plugin, but a friend says he’s never, ever had to do anything and his continues to work.. we are both using LR2, XP Pro SP2, ?? Is there a setting in windows somewhere that I need to change to allow this auto feature to work?
btw, the new version 20081027.37 took care of the “assertion failed” issue.
thanks,
niteowlgary
You didn’t tell me what version you were unable to “upgrade now” with, but perhaps it was one of the older ones in which that functionality was broken. If it doesn’t work with a modern build the next time you try, please let me know (and please provide full details). —Jeffrey
got the latyestversion - getting more probelms uploading again Jeffrey
Latest is: an internal error has occurred
?:O: attempt to index a nil value
otherwise manages to export to HD no probs
Hi Jeffrey,
Sorry about the missing info:
XP Pro SP2, Smugmug version 20081015.33, 20081027.37 - no previous version has ever automatically upgraded or worked with the Upgrade Now button. I’ve always had to manually download and install.
Metadata Wrangler v20081004.21 when clicking the Upgrade Now, this one works, at least it opens the dialoge for downloading and installing, haven’t done so yet as current plugin doesn’t expire till Nov 29, 2008.
Smugmug - 20081027.37 - Upgrade Now doesn’t work - press upgrade button: nothing happens.
Facebook - v20081015.30 - Upgrade Now doesn’t work(same as Smugmug)
Flickr - v20081015.38 - Upgrade Now doesn’t work(same as Smugmug)
just FYI, I am the IT tech at a small middle school and having to have these laptops brought in and updated is a bit time consuming… I’m hoping you can get this autoupdating fixed, it sure would save me a lot of time.
thanks,
niteowlgary
Lightroom maintains an error log for each plugin, and my plugins maintain their own running log. The former is referenced in the lower-right section of the Plugin Manager, while the latter is referenced in the upper-right section. Could you try invoking an upgrade on one of the ones that doesn’t work, and emailing the logs to me? Hopefully at least one of the logs will exist. jfriedl@yahoo.com —Jeffrey
Hi Jeffrey,
Sent the log files, hope they help.
As I wrote in the email, it seems the “Upgrade Now” button works okay when accessing the Plugin Manager directly from the “File/Plugin Manager..” drop down menu, but does not work when accessing it from the “Export” window and then choosing “Plugin Manager”… I post this here just in case others are having the same issue.
thanks for all you do,
niteowlgary
XP Pro, SP2, latest plugins 20081031.xx
Unfortunately I have to abandon my attempts to use the ‘Export to Smugmug’ Lightroom plugin. I’m using Lightroom 2.1, Windows XP and just can’t get beyond the following error:
+243.9: At =(tail call) line -1:
Return header ERROR
—————————————————–
errorCode = “badServerResponse”
name = “The requested header was not found”
nativeCode = 12150
I see I’m not the only one experiencing this and if anyone has some suggestions I’m all ears.
It sure seems like a slick tool.
Roger
Love the plugin for Smugmug but ever since going to LR2 I have not had any luck getting it to work. I have the latest update, but it always starts the upload and then fails with a weird message with nil in the text.
I have uninstalled and reinstalled. I can’t see where I can select any of my gallaries. The plugin does log me in properly. Any help would be greatly appreciated.
Thanks
20081103.38, lightroom 2.1, 10.5.5 OSX
Error Message:
+348.0: At line 15664: ?:16526: attempt to index field ‘?’ (a nil value)
Hi Jeffrey
Running LR 2.1 and your SmugMug plugin ver 20081103.39 on Leopard.
Over the last month never had an issue, but now I cannot log in. Your plugin states:
“Authenticating credentials at SmugMug …”, and then nothing happens. Network connection is fine and I can log in @ SmugMug via the website. Any idea what’s going on ? Anything to do with the new feature release of SmugMug ? Thx !
One more thing I just noticed: Exporting locally does stall when I enable “Write Keywords as Lightroom Hierarchy”. When I disable it, the photo(s) is/are exported just fine.
My keyword catalog is fine BTW, and it also used to work with SmugMug before. Strange.
If you could “Export as Catalog” one of the images that this happens with, and mail the resulting catalog to me, I’d appreciate it. I can’t reproduce the bug on my end, but perhaps my keywords are not complex enough. —Jeffrey
I have been using LR2 for about 2 months and have a Smugmug account as well. I installed your plug in for uploading and it worked great. I went to do an upload today and got a bunch of error messages stating my version was expired and I needed to install the latest one. I downloaded the file and the install was far from clean or easy, in fact I had to do a bunch of manual file moves. NOT FUN.
Apparently you didn’t update with any of the dozens of new versions over the last two months, for if you had, you’d have gotten new features and lots of bug fixes, including (according to the changelog above) a fix for the automatic update stuff.
Note that the automatic update stuff is not supported by Lightroom… I implemented it all myself, spending great effort to build a plugin that can download a zip file, unzip and install itself, and report back on the status. I did this because yeah, it’s not fun to do it by hand. But I could test only on my system, and there are a lot of different kinds of systems out there, so it took a while to get it right.
Now, when I go to Smugmug to any of my galleries, and attempt to get a link to share, Smugmug locks up. I have to use task manager to close the unresponsive program. You have an issue either with your latest update, or the install process to make it work.
When you say “go to SmugMug”, if you mean in your browser, then any troubles you have are unrelated to the plugin, and perhaps it’s just a matter of coincidentally bad timing. My plugin doesn’t do anything to your browser. What unresponsive program are you killing in the task manager?
As I have to share these galleries, I will have to look elseware for now to conduct business. Let me know if you have a fix or when you address this.
I’m sorry that you’ll have to look elsewhere to conduct your business. Please contact my well-staffed customer-service department for a full refund of the plugin purchase price.
Sigh —Jeffrey
jeffrey - using Plugin 20081111.41 on XP.
with 20081104.40 was getting:
errorCode = “badServerResponse”
name = “The requested header was not found”
nativeCode = 12150
now with 20081104.41 the upload loops endlessly. ran all day while i was at work some 6k attempts, i believe.
Hi Jeffrey
“Authenticating credentials at SmugMug …”, is sorted!
Seems like it was an issue on the side of SmugMug.
Regarding the problematic local export for hierarchical keywords I will indeed send you a file soon.
Thx for the help.
Markus
Markkus, did you have to do something in Smugmug because i am having the same problem authenticating to smugmug
If you’re on Vista and getting networking error (”can’t resolve host”, “can’t connect”, etc.), it’s likely a bug in Lightroom 2.1. I’ve heard a lot of reports of networking issues on Vista and LR2.1. —Jeffrey
When I click the “Edit/Add” button beside the “Image Caption” dropdown box, I get a popup error message (LR v2.1 512205):
+442.5: At line 19086:
bad state:
+442.5: At line 19086
+442.5: At =[C] line -1
Fixed in .47, thanks. —Jeffrey
Love the smugmug plugin - saves me oodles of time. Had good success with every version so far and really appreciate the frequent updates. Can’t thank you enough!
One feature request if I may - instead of a simple “compress by XX%” in ‘file settings,’ how about an option to compress to a given file size? Smugmug has a fixed 25MB-per-file size limit. Sometimes my shoots contain a mix of digital shots and film scans. The film scans require a different amount of compression to get under the size limit, and it’s always a guess to get them as close as possible to avoid over-compressing. At the moment I just let smugmug barf on film scans, then select those in metadata and export again with a different compression.
Just a suggestion. Thanks again!
The quality setting is not a compression percent, but rather, some kind of vague progression between “really rough” and “as good as possible”. Your size-priority suggestion is good, but it’s quite CPU intensive (since it would just have to keep trying until it got a size that was acceptably close to the max limit). For the most part, that’s all out of the plugin’s hands (Lightroom does the rendering and then hands the image off to the plugin). You might ask Tim Armes to add this to his LR2/Mogrify plugin, where it would fit in nicely. —Jeffrey