smugmug-20090703.108.zip
· Version History
· Update Log via RSS
· Installation instructions
· More Lightroom Goodies
· All-Plugin Update Log via RSS
· 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.
Availability
This plugin is distributed as “donationware”. It is provide for free and is fully functional for the first six weeks, after which it becomes limited to processing at most 10 photos at a time until registered. Registration costs 1 cent; any additional donation you'd like to make in encouragement or thanks is up to you. For details, see my blog post titled Lightroom Plugin Development: Now With Added Encouragement.
( Update Log via RSS )| 20090703.108 | Completely rewrote how the “extra keyword to send...” line is parsed. It could sometimes be a bit wonky, especially when template tokens were used, but hopefully it's more solid now. (Hopefully I didn't just move the bugs around; it's a touchy area of code.) Speaking of the template tokens, I added a bunch more somewhat esoteric things, filling out all the metadata items available to the plugin. Something like “Workflow Job Identifier” might not be all that useful, but if you repurpose a field with my metadata-viewer preset builder plugin, these otherwise esoteric items may prove to be useful. For example, I've relabeled the Job Identifier field as “Blog Url” in my custom view, and can now use the {JobIdentifier} token to refer to it. I redid all the code on squelching joining characters to make more sense (I hope), and included <br> and friends (e.g. <br/>) as special joining characters that should magically do the right thing. I also added a colon as a joining character. I haven't gotten a chance to update the Templates page with these changes, but I will soon. (If you find something that doesn't seem to work, let me know with specific examples.) Tidied up some Mac-related dialog layout problems associated with the "upload anyway" option added in the previous version. Enhanced the one-click upgrade stuff quite a bit, now detecting ahead of time when it will fail because the plugin is installed where Lightroom can't write (if Lightroom can't write to it, it can't update itself). I also added a progress bar, and now download in smaller chunks to avoid 'out of memory' errors on the larger plugins. Do remember that this new functionality becomes available after you upgrade to or past this version, when you then upgrade with it. |
| 20090629.107 | Added an "upload anyway" option for when an image is too large for your SmugMug account level (too large in bytes or pixels). SmugMug lets you upload them, but it'll downsize them quietly if they exceed the limits, and you'll lose the original that you uploaded. (Your master image in Lightroom remains unchanged, of course.) The new option is at the bottom of the #8220;SmugMug: Metadata Management” section of the Export Dialog. If that option is not enabled and an image is too large, a dialog pops up asking whether to cancel the export or skip the image. Now, it also gives you the option to upload anyway. Added still more logging to try to figure out the upload-destination fiasco thing. Fixed that during an upload of a single image, the progress-bar status didn't reflect when the image was being uploaded (it said "rendering..." the whole time). Reflect that SmugVault users can now upload up to 600MB files (it had been 512MB last time I checked.) Added a couple of defensive error checks: if SmugMug returns a "Wrong Format" error because the full image wasn't uploaded, I change the error message to the more understandable “Upload did not complete... is your Internet connection having issues?”. I also try to detect some of the weird error messages that the OS returns when a firewall blocks Lightroom from using the Internet. You'd be shocked to hear how much time I spend telling people "check your firewall and enable an exception for Lightroom...". Hopefully this'll stem that stream. |
| 20090616.106 | Sigh, this upload-destination fiasco is a real pain. Maybe have it nailed down this time. |
| 20090615.105 | Some people are still having images uploaded to the wrong album, and I'm starting to think that it's a case of corrupt Lightroom preferences. I've looked at some logs and it seems to be a case of "this can't possibly happen" happening. I've added something in this version that kills some old information with prejudice.... if this doesn't take care of it, please send a log again (via the "Send to Jeffrey" button in the upper-right of the plugin manager), but I suspect my reply will be to ask you to blast your LR preferences file and start over. |
| 20090614.104 | Sigh, it turns out that a few days ago, Twitter suddenly changed authentication methods in a way that was guaranteed to break every strong-authentication application (such as this plugin). Sigh. This update handles the new authentication style, and includes better error reporting for the next time they pull a stunt like this. |
| 20090611.103 | It turns out, despite SmugMug's old API documentation to the contrary, album quick settings are available to all users, not just Power/Pro, so I've updated the plugin to match that. Also, better error reporting if the plugin wasn't able to contact Twitter during authentication. |
| 20090607.102 | Still trying to figure out why a small subset of users find that their uploads go to the wrong gallery, so in this push have added more debugging toward that end. |
| 20090605.101 | Oops, fixed an "Access to undefined global" error that popped up when trying to clear uploaded-to-SmugMug data via the SmugMug-Extras menu. |
| 20090605.100 | A few things for this 100th update of the Lightroom 2 version of this plugin.... 1) Added a couple of new custom metadata fields, "SmugMug Upload Date", and "Upload Time". The former can be used in the Library Grid Filter to sort/select/filter by the date you uploaded to SmugMug. Because the new custom fields mean a change to the database, the first time you load this new version, Lightroom will pop up a dialog asking "Update catalog for plug-in?" to which you'll want to answer yes ("Update"). Then a progress bar will show up and, if you have a lot of photos in your catalog that had been uploaded to SmugMug, will just sit there for potentially several minutes, looking stuck. Just let it work. For my catalog with 48,000 photos, it took about 5 minutes. I'll add these to my Metadata-Viewer Preset Editor plugin soon, but for those maintaining their own viewer tagsets, these can be found at info.regex.lightroom.export.smugmug2.uploadDate and ....uploadTime. 2)Finally fixed the progress bar during upload. 3)Added a bunch of options to the gallery-creation stuff in the "SmugMug Tools" section of the export dialog. (If you make a variety of gallery types often, you'll probably want to make your own Quick Settings, since they override all the options here and include many other options not yet included here.) I didn't add every gallery option (there are a bazillion of them!) – I just picked the low-hanging fruit– so let me know if I missed some that are important to you. |
| 20090602.99 | Sigh, small bug fix for the new Twitter stuff. |
| 20090602.98 | Well, here's something new: Twitter support. It may be a bit iffy, mostly because I don't use Twitter myself, so perhaps I've missed something about the culture in which it's used, but I've added something that allows you to send a tweet after a successful upload, with a mini template language that allows you to include a photo url or destination-set url in the tweet. The plugin uses Twitter's new strong secure authentication, so you don't even have to tell the plugin your username or password. You authenticate at Twitter and grant the plugin application permission to send tweets on your behalf. A note to fellow developers, who will feel my pain: in order to get this strong-secure authentication support working, I had to code up SHA-1 Secure Hash computation from scratch, in pure Lua... a horrid language, I'll remind you, that has absolutely no bitwise operations, or even integer support. No masks, no bitwise xors, no way to test bits or shift words or any of that stuff. As I coded it, I felt as if I were chiseling NAND gates from rough blocks of silicon. I felt quite the achievement once I got it working, but only then realized that I also need to code up my own HMAC-SHA1 secure signature routine. It's less involved than the original SHA-1 stuff, but again, filled with bytewise xors. Fun stuff, in a very old-school way. This release also contains some extra logging to try to get to the bottom of a problem that a few users have reported, namely, that their uploads don't go into the galleries they specify. |
| 20090521.97 | Sorry, another quick bugfix. It seems an internal change I made to try to get around a bug in Lightroom wasn't quite ready for prime time. Hope it is now. |
| 20090521.96 | Fixed a "loadstring" error some users got. You can now use the scroll wheel with the scrollable lists (such as for the gallery list)... sort of. It works while the mouse is actually hovering over the scroll bar. That's the best I can figure out so far... it's better than nothing if you're a scroll-wheel user. Added some new token filters to the preset templates used for things like extra keywords and image captions: They're listed in the docs, but include new items like UCFirst capitalize first character of the item, or LC to lower-case the entire item. For example, if you want to include the city as an extra tag, but prefer your tags to be all lower case, you might use {City:LC} in the extra-tag dialog. |
| 20090519.95 | Fixed an album-creation bug I introduced in a previous version. |
| 20090518.94 | Somewhere along the way the plugin stopped updating the progress bar as it worked. I've restored it, so now you can see it inch along as the uploads complete. I also included some stuff to communicate with the next version of my Metadata Wrangler plugin help coordinate a canceled export. Unfortunately, if you cancel an export, Lightroom does not tell filters like the Metadata Wrangler, so it blindly continues trying to process images that will not show up. I've added some hooks here to help the next version of the Metadata Wrangler detect a canceled export and not complain. It's imperfect, but I'm hoping it'll help. |
| 20090510.93 | Added a link in the Plugin Manager to the plugin's update-log RSS feed. |
| 20090509.92 | Added items to the title/description presets: ZenfolioUrl, FlickrUrl, and PicasawebUrl. If you have previously uploaded this image to one of those sites with my plugin that uploads to those sites, you can refer to that copy of the image by reference. Using the tag alone, e.g. {ZenfolioUrl}, it becomes the raw url, or nothing if the image wasn't previously uploaded. Using a =text argument inside the tag turns it into a link with the given text, e.g.
See the {ZenfolioUrl=photo at Zenfolio}.
becomes:
See the <a href='...'>photo at Zenfolio</a>.
if the url is known. If the url is not known, the tag is replaced with nothingness,
so you might want to include an "|..." fallback section, such as:
See the {ZenfolioUrl=photo at Zenfolio|"photo at <a href='http://myname.zenfolio.com'>my Zenfolio site</a>"}.
The entire double-quoted part after the "|" is used when what comes before ends up being empty. In this case, that double-quoted part is some text that includes a link to a Zenfolio user's home page (you'd want to put yours, of course). So, if the url isn't known, the entry becomes
See the photo at <a href='http://myname.zenfolio.com'>my Zenfolio site</a>.
|
| 20090508.91 | SmugMug has fixed the bug that I worked around in the previous version, so this undoes that workaround. |
| 20090504.90 | There's a bug in how SmugMug returns data to the plugin, or in my understanding of what's supposed to happen, that causes some accented characters in gallery names to appear as HTML entities. I rewrote how I parse the data they return, and inserted code to work around this issue (manually decoding the entities I know about). Let me know if you run into gallery names (or anything else) that doesn't display properly. |
| 20090429.89 | Fixed a bug that could potentially crashed the plugin while editing caption/title and auto-destination presets. |
| 20090425.88 | Tweaked how the plugin tries to update itself during the one-click upgrade process, to hopefully get things working for those few Windows users that have never had it work. Crossing fingers. We'll see. |
| 20090422.87 | Fixed the caption preset stuff to disallow editing of the built-in caption presets, and added a note to that effect in the preset editor. I also reset the 'None' preset to an empty value, just in case it had gotten edited in a prior version of the plugin. Sorry it took so long to get around to this fix. |
| 20090422.86 | A few minor housekeeping updates: the 'enable enhanced debugging' checkbox in the Plugin Manager now turns on logging of all web traffic. It'll be useful if I ask you to send a log, but you probably want to leave it turned off during general use. I also added an icon to the registration page to reinforce what plugin is being registered. |
| 20090403.85 | Corrected the photo-date related items in the preset templates to properly use the dateTimeOriginal metadata field, rather than the edit-time dateTime field. It now uses the first of the following that it finds with a value: dateTimeOriginal, dateTimeDigitized, and dateTime. This bug was reported to me long ago, but I let it slip through the cracks, sorry. |
| 20090331.84 | Added scroll-one-line arrows to the top and bottom of the scrollbars, to allow fine-grained
control of scrolling very long lists. (I've been programming for almost 30 years, but this
is the first time I've ever built a graphical scrolling system from scratch, so I may
be a bit slow on the uptake at times  )
|
| 20090327.83 | Turns out that there's a bug in Lightroom that causes login names to be rejected if they can't actually fit in the input box that's presented when trying to log into a second account. To get around this bug for the few who run into it, I've made the box as wide as I can... I hope it's sufficient. |
| 20090325.82 | Big UI changes in some areas. I've cobbled together a way to add what appears to be a real scrollbar, so I've replaced the kludgey scrolling solution I had before. It seems to work okay. I also changed the "Token Examples" dialog from paging to use the new scroll stuff. |
| 20090313.81 | It seems that PayPal doesn't give everyone a "Unique Transaction ID" in the registration confirmation mail; some people get a "Receipt Number". So, the registration dialog now accepts that as well. I also removed the "Resolution value to record in metadata" control in the Metadata Management section. That had dated back to a time when the resolution setting was not available in the standard "Image Sizing" section of the export dialog, and I forgot to remove my custom one when the standard setting appeared. It was sort of silly having two controls for the same thing, sorry. The resolution setting is still utterly meaningless unless you use it to actually compute the pixel size of the image (that is, if you have the "resize to" setting to something other than "pixels"). Once the image has been created, it's just a hint about how you intend it to be rendered when printed, but it has exactly zero impact on the quality that can or can't be achieved when printing. |
| 20090310.80 | I've added a popup dialog that appears the first time you install this plugin that explains how to activate it from the Export Dialog. It's currently not very “discoverable” (in UI lingo), and it leaves a lot of people befuddled. I hope this helps to stem the flow of “I can't get it to work” messages I get each day. I've begged Adobe to tweak the UI to make it more clear in the future. |
| 20090305.79 | Fixed a bug that caused the plugin to crash (and stay crashed across Lightroom restarts, even!) when deleting the caption preset that was actually chosen for the caption. |
| 20090303.78 | If there's an error calculating the automatic destination for a photo, now actually reports that error instead of just crashing |
| 20090302.77 | Fixed a bug that could cause the plugin to crash when using the File > Plugin Extras |
| 20090228.76 | Fixed a bug that caused a plugin crash if my server couldn't be reached during registration. |
| 20090225.75 | As per the ongoing discussion on my blog, with this version this plugin moves over to
a "donationware" model, in which the plugin remains free, but registration eventually becomes
required (and an eventual donation hoped for For details, see Lightroom Plugin Development: Now With Added Encouragement. (For info about what drove this decision, see What To Do When a Hobby Becomes Work?) The plugin no longer expires, and correspondingly, I will not pay much attention to reports of bugs that have already been fixed, so please check your version and the version history before submitting bugs or feature requests. There was a lot of internal upheaval in the code, so I expect that some boo-boos my surface. If something breaks for you with this version, please let me know, but until I fix it, feel free to revert to the previous version. One enhancement in this release: I realized that the image caption can actually be HTML, so I now allow for that in the Export dialog. |
| 20090219.74 | Sigh, I need to slow down and test these things better before pushing them out. Sorry, it's been a tumultuous week. This version fixes a few stupid bugs stupidly introduced in the last stupid update. |
| 20090219.73 | Some UI tweaks for the multi-login feature added yesterday. More robust error reporting if an export is attempted without an Internet connection. |
| 20090218.72 | Feature added per request of one of the SmugMug founders: can now easily switch among multiple SmugMug accounts. |
| 20090217.71 | The folks at SmugMug pointed out an error in how I was uploading to their servers that might explain a "bad album id" that a couple of users have reported. Also, some UI tweaks. |
| 20090215.70 | Woohoo!!! Fixed the "badServerResponse" error!!!!
Wow, it was frustrating. A bunch of people kindly sent logs and network traces, and but I couldn't find a clue in them as to the cause of the problem. However, with the help of tech-savvy Alabama-based photographer Kevin King, I was able to isolate and work around the problem. Kevin really went the extra mile here, running network traces, sending me logs and photos and catalogs, running at least a half-dozen debug builds of the plugin and reporting back as I tried different things that might lead to a clue. Eventually one did, and Kevin confirmed a final-fix build, so here we are. For what it's worth, there is a bug in either Lightroom or Windows related to HTTP traffic headers. I've reported it in detail to Adobe. NOTE: The automatic upgrade may have trouble upgrading to or beyond this from a version prior to this, so if it doesn't work for you, please just blast (or rename) the old "jfriedl-smugmug.lrplugin" plugin, and download/unzip/install manually. (I wish Adobe would officially support automatic upgrade, but until then, the works-usually system I've cobbled together will have to do) |
| 20090210.68 | Fixed a bug on my side that on rare occasions resulted in an "invalid session id" error, and another that sometimes resulted in a "wrong format" error. |
| 20090130.67 | SmugMug was suddenly denying my plugin's API key, which (of course) caused all kinds of problems. Making it worse is that I didn't have good error checking, so the reason for the problem wasn't apparent until I dug into it. While adding better error checking, SmugMug suddenly started accepting the API key, so things seem to be working now. This build has more (better?) error checking, and so if the problem happens again, hopefully things will be more clear. One concern, though, is that perhaps I've become too aggressive on checking for error replies from SmugMug (some "errors" really aren't errors, and should be ignored), so let me know if things are not smooth. |
| 20090129.66 | Small housekeeping update for the new locales supported by Lightroom 2.3. Added more info to the debugging log when an export operation begins, to help diagnose any subsequent problems with the export. |
| 20090126.65 | The new scrollable-list stuff didn't deal with ampersands very well... things should be better now. Also added tooltips to the list items so that the full text can be read even if the display is cut short, although ampersands may appear in duplicate (or quadruplicate, depending on the OS)... it just wasn't worth the effort to get ampersands right in the tooltip. |
| 20090126.64 | Fixed a couple of spelling errors. |
| 20090120.63 | Addressed a strange error ("strange error" is a euphemism for "condition I don't fully understand") that could cause a "photohistory: not logged in" error. I think this happened when you got logged out while uploading, but I'm not sure exactly how that could happen. I also added some extra debugging stuff to help clarify whether it's a multi-threading issue. |
| 20090119.62 | Okay, so I spent the entire weekend working on my own scrollable-list control from scratch, because the built-in popup menu is just not very easy to work with when one has a lot of galleries. I didn't have much to work with, and the result is a bit wonky, but it's much more usable when the list is long, so I'm throwing it out there. If you don't have a long list of export destinations, you can revert back to the original via the "configure list appearance" button. With that button you can also change how much of the list is shown at once, to suit your personal preference. |
| 20090116.61 | It turns out that the automatic upgrade stuff doesn't work if the plugin folder has been renamed from its original. That should generally not happen, but it's possible, so the plugin now checks its own location reports the issue to the user if it finds it. |
| 20090115.60 | Added more debugging-log stuff to the 'Upgrade Now' button action, to try to understand why it doesn't work for some people. |
| 20090115.59 | Added a 'click here to change the export destination' note to the masthead image, because some new users are confused how to change export destinations. |
| 20090110.58 | Added a checkbox in the Plugin Manager to turn on enhanced debugging (more stuff in the plugin's debugging log), and added a button in the same place that sends your log to me. Particularly for “the upgrade button doesn't work” and “error while uploading” type issues, this should be useful for debugging. |
| 20090108.57 | I've discovered multiple Lightroom bugs (one on Windows, two on OSX) that caused problems with captions that contained multiple lines and/or non-ASCII data. The plugin now detects captions that will cause platform-specific problems, and gets around the problem by omitting the caption during the initial upload, and then immediately setting it via a different method that actually works. I've also reported the bugs to Adobe. |
| 20081228.56 | My preset dialog (for caption presets) was a bit wonky and didn't update itself when a preset was added. Fixed that. Also, in the export dialog proper, the example text next to the preset dropdown didn't auto-expand as the preset was changed. Fixed that, too. |
| 20081226.55 | The version number had lost its way in life. Setting it straight. 20081224.* -- The "Extras" item in the File menu had stopped working. Works now. 20081223.* -- Bumping back the expiration date. |
| 20081208.52 | Fixed a problem that sometimes caused errors during login/authentication, or after logging out. |
| 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 of this for-Lightroom-2.x version of the plugin. |
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
Any chance of a version that doesn’t expire?
It just seems a little silly having to download a new version every month or so even if it’s running fine. I’m perfectly capable of checking your site if I happen to be having problems, or if I want to check for any updates that are relevant to me (the majority of them aren’t).
It’s annoying enough that I’d be willing to pay for a version without it… in case you’ve had any thoughts in that direction.
If pressing the “update now” button once a month is too onerous a price to pay to use the plugin…. (sigh) —Jeffrey
Of course it’s not - what gave you that idea? I like the plugin, and appreciate your work, but can’t understand why you’d want to force users to upgrade regularly if they don’t need (or want) to.
After installing the new plug-in (20081208.52.zip) for LR2 on my Windows XP computer, I still cannot get it to upgrade. Since this is my first time of upgrading the Export-to-Smugmug plugin, is there a series of steps I can have emailed to me? Imust be overlooking something or there might be a new bug that needs to be eliminated.
Thank you in advance!
Hi,
I am using LR 2.0 and your plug-in for smugmug upload. Great plugin by the way. However, I think there maybe a bug. The File Name box seems to carry on the last known file name for some odd reason.
For example, I had previously some files with Alaska_DSC9999_Date to name the files that I had exported to my harddrive for other use.
I imported some totally new files and when I exported, the “Alaska” tag remained and named my files “Alaska_DSC8888_Newfile info”. Why is this when “Alaska” was not Selected from the Dropdown box under the Template (for naming) shows. That shows just Filename.
Thanx
The filename stuff is completely handled by Lightroom (that section of the export dialog is one of the standard sections). I don’t use much of the filename templates except “Filename”, so I’m not familiar with how other ones might work, but in any case, there’s nothing different about what happens when exporting via a plugin or not, filenamewise… —Jeffrey
I’m currently using your Smugmug plugin and rely on it alot. Thank you for your great contribution to Lightroom. I’m currently running an upgraded version of LR 2.2 and using your Export to Smugmug plug-in version 2008.1208.52. No problems with this. However, I’m thinking about publishing more public entries on Smugmug with another [new] account (probably Pro) and wanted to get your comments about how to manage this. Whould I use two Lightroom catalogs (hope not), two Smugmug accounts (one plugin) etc. I can imagine how the plugin would have to have knowledge of two different accounts (a dropdown to pick from) at Smugmug in order for me to change destinations of exports. Senario: I want to export ALL tagged stuff (like I do today) to my private standard site on Smugmug then, I see that I want to share some pictures on my new Pro site on Smugmug with a subset of or other pictures. Choosing pictures isn’t the issue but having the plugin dual-aware of two accounts would be my biggest concern. Ideas?
Asking here because I didn’t find a better forum for asking this question. This is more of a question than a bug report.
Can you please comment on where the smugmug exporter locates temporary files when the “Export to” option “Temporary folder (will be discarded upon completion)” is selected?
Lightroom 2.1 crashed while uploading a large amount of jpegs via the smugmug exporter 20081204.51. I would like to be extra certain that the temporary files get deleted.
This is the first time lightroom has ever crashed while doing an export to smugmug using your plugin. I don’t know if the crash happened inside the plugin or inside lightroom. I’d be happy to send you the core dump if you email with with instructions for how to locate the core dump. (I’m new-ish to OSX.)
I had queued up three parallel exports to different smugmug folders intending for it to proceed over the next many hours. I noticed that lightroom was constantly pegged around 2 GB in size according to activity monitor. This OSX 10.4.11 system has 3GB of RAM and the hard disk is close to full. I wanted to check my smugmug gallery config so I fired up both firefox and safari. That caused a ton of disk swapping for about 30 seconds before things settled. Then lightroom crashed immediately upon bringing it to the foreground.
On my Mac, the temporary folder is in /var/tmp/folders.503/TemporaryItems/ with a name consisting of a long series of hex digits, like FD16808C-4C12-4D7C-A01F-A2895B5113B8. Lightroom generates all the images as fast as it can, which is likely much faster than they can be uploaded, so it’ll peg the CPU for a while, then the CPU will settle down as all the accumulated images are uploaded over time. As for the crash, you might try upgrading to Lightroom 2.2. It’s free. —Jeffrey
Thanks, Jeffrey. I found and eliminated around 750MB of jpg files from four different sub-folders of that TemporaryItems folder. The time stamps on these sub-folders seem to line up with the times that lightroom crashed on me today while trying to upload through the smugmug plugin.
I’ve also gotten a couple instances of a “wrong format” error that terminates an upload attempt. I’ll try updating to lightroom 2.2 after I get this batch of files onto smugmug.
Jeffery, something is going on with the Smugmug plugin version numbers above it appears to have regressed back to .46 from .52?
Whoops, sorry, not sure how that happened. That’ll make for some confusion. Just pushed a version with a number that’s back on track. —Jeffrey
Jeffrey:
I have V20081208.52 and got the expiration warning notice. I clicked on the Upgrade Now button as I always do, and nothing happened. The new version didn’t download or install. I’m using WinXP Sp3 and LR2 current version. Thanks.
I have loaded your plug-in for Lightroom to export to smugmug. Bet I get the following error:
+1.1: At =(tail call) line -1:
Return header ERROR
——————————-
errorCode = “unknown”
name=”the system cannot find the file specified”
nativeCode=2
Then it aborts the login to smugmug.
I am running LR 2.2 on XP operating system
It seems that the error occurs just after validating smugmug login when it looks for gallery list.
Any help or suggestions on how to correct this problem would be greatly appreciated.
Does smugmug api support metadata updates? I have 1000’s of photos that I just need a keyword or GPS update…
smugmug.images.changeSettings allows you to update geocoding and keywords to the image on SmugMug. I guess it’s possible… Future versions maybe?
Yeah, I’ll be doing a bunch of new development next month. —Jeffrey
Jeffrey,
First of all, I love your plugin. I can’t believe how sophisticated and flexible you’ve made this. Oh, and I remember reading your regex book over 10 years ago.
I’m just adding that I’m seeing the same behavior as JSK in terms of upgrading the plugin with the “Upgrade now” button. It doesn’t appear to do anything when clicked.
Jeffrey,
Your plugins are invaluable!
I am using smugmug-20081228.56 on LR v2.2 on OS X 10.5.6. I am not 100% sure if this is your plugin’s bug or it’s LR… but I notice that when I have two instances of uploading at the same time via your plugin, the memory usage goes up until the system is completely out of memory. With a single instance of the upload, no problem at all. Could this be related to LR or your plugin?
ws
Not sure where the problem might be…. does the memory jump happen when you do two exports to disk? —Jeffrey
I’ve been having the same issues with memory lately when uploading 100’s of photos at a time… out of memory… I’m using a 50d with ~12Mb images now…
I’ve got the Smugmug plugin 1024.38 and it says it’s expired… so I click update and nothing happens… so I uninstalled and tried downloading the 1228.56 you have linked on your page… but when it installed it still says “1024.38 expired please upgrade”
Please help… your plugin is AWESOME… I use it quite often. saves me a lot of time and aggravation
thanks Brandon
The automatic-upgrade stuff I built still doesn’t seem to work for everyone, and until I can figure that out, you indeed have to install manually like you tried. Installing manually should do it, so perhaps give it another try. You can delete the old plugin folder and unzip the new one in its place. Then, reload the plugin in the Plugin Manager, or just restart Lightroom… —Jeffrey
That worked… thanks….. YOU ARE THE MAN!!!!
What a pain! Practically everytime I want to use this plug-in, I have to reinstall it! You should make the update process optional. Some of us are ok with the bugs. The bugs are less of a pain in the rear than having to reinstall the latest greatest version all the time.
It’s funny how in your efforts to make things better for the users, you’re deliberately doing something that causes the most problems!
Damn Jim… you don’t pay for this… and yet your complaining about having to update once a month… the uninstall reinstall takes me about 1-2 mins longer than to click the update button… if you can’t set aside 2 mins a month for something free… you need a vacation.
Jeffrey… Thanks for all you do.
Ver 20081228.56
After upgrading I keep getting this error:
+10785.9: At -(tail call) lin -1:
Return Header ERROR
errorCode = “securityError”
name = “(unknown error)”
nativeCode=12057
an internal error has occured : ?:22419: attempt to index a nil value
I received the following message:
Error response from SmugMug:
wrong format (ByteCount given: 5128933, received: 5128933. MD5Sum given: f5b3873644d3f6d320d6a91d9f93d888, actual: f5b3873644d3f6d320d6a91d9f93d888.)
Aborting upload after 66 of 72 images.
Thanks for all the time you spend on this!
Be seeing you,
Denis
Hi Jeffrey, firstly great plugin saves me oodles of time!
Just to let you know out of 6 or so attempts this morning to upload to smugmug with the latest plugin (i’m on 10.5.5 + lr2.1) only once did i get all the way through upload 25 photos without getting the same error as Denis.
If I can help with any logs or other info please let me know
Cheers, Jason
I love your plugin, thankyou.
I have a feature request: I would like the ability to export to multiple folders on disk in a very similar way to how I upload to multiple albums in Smugmug during a single export.
For example, I think it would be great if I could do each of these scenarios:
1. Select 100 photos to export, then specify that they get exported into subfolders on disk based on the “auto dests” feature of the Smugmug uploader.
2. Select 100 photos, specify that they are exported to /Users/Jamie/Pictures/Photos in subfolders based on a “Folder” metadata attribute that I add, and a subfolder of that folder based on a “SubFolder” metadata attribute. (This could be extended to allow multi-level hierarchies as well)
This could be a useful feature of the Smugmug plugin, as it would be useful to be able to do this while uploading to Smugmug, or as a totally separate plugin–as I would also like to be able to do this just for exporting to disk when not exporting to Smugmug.
Aargh. Perhaps you can update your plugin to help out with my not being able to compute JPG math using XMP instruction sets in my head! I walked away from a largish upload and came back an hour later to find a LR error message had popped up early on: “The exported file size of 12,610,296 bytes is larger than your SmugMug account limit (12,582,912 bytes). Cancel or skip just this image?” OOOhhh…less than 27kb over the limit! The original CR2 is only 10.5MB, but by the time LR adjustments got added, the 100% JPG coughed up like a cat. LR doesn’t give a “skip all and we’ll log ‘em for you so you don’t waste time staring at the screen” option, of course.
Any chance your plug-in could look at the file size after converting to JPG and if larger than the account limit, politely subtract 1 from the JPG quality until it fits??? I hesitate to ask, but could you write a log file of images that were reduced in quality to fit?
Thanks, Mr. Wizard!!!
I’m not sure whether the plugin would even allow that, but even if so, as useful as it would be for the few people who might be helped by it, it’s pretty low on the bang-for-developmenttime-buck scale, so it’s probably not something that will be addressed any time soon, sorry. —Jeffrey
ps - I’m using your 20090110.58 version, with OSX 10.5.5 and LR 2.2 and camera RAW 5.2
Thanks for the great plugin. On my first try, I accidentally uploaded the wrong images. I deleted them in SmugMug, but how do I clear the SmugMug metadata for these images in Lightroom?
Via File > Plugin Extras > SmugMug Extras. I really need to make some docs for these things so that people have one place to go to for a complete overview…. —Jeffrey
smugmug-20090119.62.zip - installs but does not all show up in export dialog to allow for export
Did you follow the instructions? —Jeffrey
Love your work!! I’m using plugin 20090120.63 with LR2 to help set up my new SM account. Plugin worked fine the first few uploads but now the copyright data entered on my photos has shrunk dramatically in font size. Not sure how that happened. First uploads copyright data is plainly visible ons creen in SM. Now it is so small in size it can’t be read. I haven’t changed any settings at all. Any advice please would be greatly appreciated.
The plugin doesn’t have any control over the watermarking, which is really poor. The font size is fixed, so the text appears smaller as the image size gets larger, and vice-versa. Tim Armes’s LR2/Mogrify plugin gives you complete control over watermarking, so you may wish to check it out. —Jeffrey
Smug Mug version 20090129.66.
Hi,
Am new to this uploader. Used an older version 1x before without problem. Just downloaded this and put it where it belongs. I know I’m missing something very basic but when I try to use the uploader I keep getting the message that I can’t export because I’m not logged in. I have LR running, I have Smug Mug running, I am logged into SmugMug and just don’t “get it.”
Thanks
Stephanie
First - Thank you very very very much for this plugin. It has been a lifesaver! I’ve been using it for quite a while with no issues - until tonight. All of a sudden, no galleries populate the ‘Upload to your SmugMug Gallery’ section. I updated to 200901129.66 and the issue is still there. I am on LR version 2.2 523352. I checked on my xp64 box and my xp media box and I’m having the same issue on both. I logged into my smugmug account and everything there looks fine.
Thanks again for the plugin and the help!!
Just want to say I had the same problem - also suddenly - as above. And about the same time too. I sent you a log-report. Using LR 2.3 release candidate, re-installed both old plug-in, newest plug-in version and reinstalled RC 2.3. No change at all.
Thanks for your efforts for making our life easier - its now we know what we otherwise would be missing…
As best I can tell, SmugMug had a hiccup that caused it to reject my plugin’s API key, and making it worse, my poor error-checking caused the plugin not to report that to you clearly. The hiccup seems to be over (it’s working for me know, and likely for you, too), but I’ve gone ahead and pushed a new version with better error checking. —Jeffrey
Thank you!!
smugmug-20090130.67
Error uploading pictures:
+283.5:[5D1BDF8] +(tail call) line -1
Return header ERROR
————————————————————
errorCode = “badServerRespons”
name = “the requested header was not found”
nativeCode = 12150
Ps: thank You for this fantastic tool.
I keep getting this error message: bad server resonse when attempting to upload from lightroom to smugmug.
version 2.2 of lightroom
version smugmug-20090130.67.zip of plugin
SmugMug has been having all kinds of hiccups lately, so I assume it’s more of that, but I’ll check it when I get a chance later. In the mean time, send a plugin log if you get a chance and haven’t done it already (I don’t have access to my email at the moment) —Jeffrey
While uploading from LR 2.2 MAC to smugmug, with pluging 20090130.67 several pictures I get very often the error “wrong format”.
If i re-select and upload again non any new error for hundreds of pics….
It’s eally unconfortable!
Anybody has a suggestion/solution?
Hi thanks for all your work here. I get the following error on the export to smugmug plugin, (Picaca Web Albums export works fine for what its worth). Sometimes the first line starts with +0.5: or +0.3: and the hex address changes each time.
+1.0: [58CB490] =(tail call) line -1:
Return header ERROR
——————————————————
errorCode = “unknown”
name = “An error occurred in the secure channel support
”
native Code = 12157
Plugin version smugmug-20090130.67.zip
Lightroom Version 2.2 523352
Windows XP Service Pack 3
Everything shows up but the upload destination. I can’t see any of my smugmug folders or create news ones. Thanks for any help you might offer……..Dave
SmugMug (or my plugin, or Lightroom, or something ) has been having network issues of late. SmugMug is actively looking into it. But this one smells more like a firewall / security issue with your computer, but that’s just a hunch. I’ve never seen that error message. PicasaWeb and SmugMug use different kinds of uploads, so it’s possible (although not too likely) that your security settings allows one but disallows the other. I’m not an expert on this stuff, so the best I can do at this point is to ask you to look into your security settings carefully, or try disabling antivirus stuff, or whatnot, and see whether that helps. —Jeffrey
smugmug-20090130.67
I’ve been getting the following for more than a week now uploading to smugmub… Am I the only one?
LR2.2/Vista
Error uploading pictures:
+283.5:[5D1BDF8] +(tail call) line -1
Return header ERROR
————————————————————
errorCode = “badServerRespons”
name = “the requested header was not found”
nativeCode = 12150
Same as Dan Pancamo above, just with LR2.3
FYI regarding
name = “An error occurred in the secure channel support”
native Code = 12157
http://regex.info/blog/lightroom-goodies/smugmug#comment-34170
Jeffrey, your hunch was correct. I am using K9 web filtering software. I added smugmug.com to the “sites to never block list” and it fixed the problem. Works Great. Thanks!!!!!!
I just wanted to thank you for all your hard work - the Smugmug plug in saves me lots of time, has helped me post pictures much more rapidly. Thanks for fixing the update bug, I was just able to update by clicking the update button - first time that has worked. No other issues, I am enjoying using your plug in!
Thanks Dave ovard.
Hope the problem be solved soon.
I saw this post before, but the only firewall I have is Windows Firewall. I turned it off, and I also turned off all the Internet Explorer security settings (I know it has nothing to do with it, but I just wanted to make sure…), and the problem is still there.
I really miss this great tool
I have exactly the same error as Dan from above. I’d LOVE to have this plugin working again as it promotes my inherent laziness. I’ve tried uploading with and without my virus scanner and firewall turned off with the same result. Is there anything that I’m just doing wrong?
smugmug-20090130.67
I’ve been getting the following for more than a week now uploading to smugmub… Am I the only one?
LR2.2/Vista
Error uploading pictures:
+283.5:[5D1BDF8] +(tail call) line -1
Return header ERROR
————————————————————
errorCode = “badServerRespons”
name = “the requested header was not found”
nativeCode = 12150
Hi there,
I am getting an “Internal Plugin Error: SmugMug login aborted”
“Couldn’t get gallery list from SmugMug: Unexpected error response #3 from SmugMug(”invalid session”)”
I just received the 20090130.67 “Export to SmugMug” update this morning.
I am running Lightroom 2.2 on Mac OS 10.4.11
Thank you for your good work.
If you get it again, could you send the plugin log? There’s a button to do so in the top-right section of the Plugin Manager. —Jeffrey
Thanks! Now with the last update (20090215.70) it works again!
What a wonderful plug-in!
Works fine here to, THANK YOU
20090215.70
So far so good - thanks!
Hi Jeffrey, great plugin. I noticed that my keywords with special characters (ı, ğ, ö, ü, İ, ş, ç, etc.) are omitted from the word on export. So “yöre” becomes “yre”. I checked your known issues page and didn’t see that listed. I was wondering if special character omission is expected behaviour?
Thanks.
Smugmug plugin - 20090215.70
ooops gettign the error messages again
Hey Jeffrey,
I am still getting an:
Error response from SmugMug:
system error (invalid album id)
Aborting export after 0 of 1 images successfully
uploaded
I have the debugging log if you need it.
Any thoughts?
Just downloaded the newest plug-in…and LOVE the new folder selection! My wife uses my Smugmug pro account for her online business and has almost 400 galleries just for that. Finding my more recreational galleries was always a chore with the old popup list and the arrows. This is so much better. Thanks as always.
aah turns out smugmug doesn’t support the special characters
Where are the auto-destinations stored? I’m trying to move my upload exports to smugmug to another PC, and have everything working except the ones that use auto-destinations.
In the Lightroom preferences file. —Jeffrey
Just as an FYI since I’ve seen others with the issue here.
It looks like Lightroom 2.2 has an export memory leak. Depending on RAM if you export more than 100 pictures you’ll get a “Not enough memory” error and the export will die. The only way to clear it is to restart Lightroom.
Lightroom 2.3 RC fixes this, per the release notes:
A memory leak could cause Lightroom to crash while attempting to process files with local adjustments.
Unfortunately 2.3 is not officially released yet, but it seems stable. For download see:
http://labs.adobe.com/wiki/index.php/Lightroom_2.3
At first I admit I thought it might be an issue with Jeffrey’s plugin, but then I found info that led me to the solution.
Hi!
I wonder what the plugin does to the Lightroom catalog.. I just want to be sure that it does something simple that is unlikely to corrupt the database in the future.. Corruptions could possibly be hard to revert as the catalog grows and backups from the times before using the plugin becomes more and more obsolete..
Thanks for all your efforts! it seems to be a great plugin.
Cheers,
Marcus
The plugin doesn’t do anything directly to the catalog… the plugin works only through the approved Adobe API when accessing or writing the catalog. —Jeffrey
smugmug-20090305.79
light room 2.2 523352
windows vista
I had a complaint about uploading an image to smugmug that was too large for my account. Its my understanding that there is no size limit of images to be uploaded.
Other than that I love the plugin.
Clark
I believe SmugMug has a size limit (in bytes, not pixels). If they don’t, please ask them to tell me. —Jeffrey
SM does have size limits but they’re pretty generous :
http://www.smugmug.com/help/upload-photos
When trying to upload i am getting no response from smugmug error after after uploading part of my gallery. I just upgraded to lightroom 2.3 and i am using version 20090305.79 of the plugin. it doesn’t look quite normal in the plugin manager, but i have tried redownloading multiple times.
Perhaps SmugMug is having system maintenance now? If it persists, please send a log (via the button in the upper-right of the Plugin Manager). —Jeffrey
I have Lightroom 2.2 64bit and camera raw 5.2. I am attempting to upload to smug mug. I installed according to instructions
Plugin shows correctly installed and working, however I can not find it in the export menu. My Lr2 is upto date and I have tried several ways to install this to include restarting after importing the plugin, and closing light room starting it back up etc.
Any Suggestions?
Thanks
Adobe hid it pretty well. See < a href='http://regex.info/blog/lightroom-goodies/plugin-installation#using'>this image in the instructions. —Jeffrey
LR 2.3; GPS ver 20090302.77; received “Error response from SmugMug:
wrong format (ByteCount given: 6116320, received: 6116320. MD5Sum given: 88f564470b62a5d8bb096c0670e244b1, actual: 88f564470b62a5d8bb096c0670e244b1.) Aborting export after 82 of 140 images successfully uploaded”
I’m embarrassed to say that I got this error once before, but I can’t remember what you suggested to do!
Thanks,
Denis
Well, you shouldn’t be embarrassed… that’s a pretty unfriendly error message, sorry. I didn’t spend much time on making it more readable because it’s pretty darn rare…. it seems that SmugMug somehow feels that the upload was corrupted, although the points they report in the error show no problems. I can’t really speculate what the problem might have been, but I bet if you retry it will be okay. Chalk this one up to “cosmic glitch”, I guess. /-: —Jeffrey
Checking this out, I’m from Los Angeles California
In the old Smugmug plugin for 1.X the File naming option could be used in the caption box. So I could set for the sequence number and the number series would show in the caption.
Here’s an example of this http://pa-iki-i.smugmug.com/gallery/5999650_uG4YY
I don’t see an option for that in the tokens.
I don’t recall that any of my plugins have ever done anything with a sequence number, but it shouldn’t be too hard to add something that allows you to access the final number in the generated filename, so I’ll see what I can do… —Jeffrey
Jeffrey
I meant that I could use the generated filename in place of the of the caption, title headline. You could set the priority. So I could create a custom name sequence in the Filenaming option and put that in the smugmug caption.
Plugin for SmugMug version 0313.81 I check “add copyright watermark” However, when I upload full size images, the watermark is so tiny on images displayed at SmugMug (up to XLarge) they are practically invisible. If I upload 1024*768 the watermark is normal size and legible. However, uploading small images defeats one of my main reasons for selecting SmugMug (full size uploads). Is there a way I can have both — fullsize upload AND visible copyright watermark on displayed images? Thanks RandyHI (The “HI” stands for “Hawaii” where I live — Kihei, Maui to be precise)
The watermarking (or the lackthereof, as the case may be) is part of Lightroom. For useful watermarking, you might consider Tim Armes’ LR2/Mogrify plugin. —Jeffrey
This is an excellent plug-in I have been using (in New Zealand) for many months now. However, just recently you have changed the destination gallery selection tool from a horizontal to a vertical slider. This has been a retrograde step for me, as I can no longer select a particular gallery of interest as the window is too small and the tool jumps past this gallery. Can you please revert to the horizontal slider which worked well. The new one is too fiddly!
Have you tried configuring the display size to be longer (say, 15-20 lines)? If you have a lot of galleries, you’d want to do that…. —Jeffrey
Okay, just pushed version .84 that adds arrows at the top/bottom of the scrollbar that scroll when clicked. That should help a lot, I’d think…. —Jeffrey
I went ahead and deleted the file. Then, I download the “same” file. Now, I have the slider. Everything is working great.
Bob from “Kali-forr-na” the land of the terminator
Been using the latest plugin smugmug-20090331.84.zip recently but noticed that now when ever I load up Lightroom 2 I get the following:
An error occurred while reading the schema for the plugin “SmugMug”. The plug-in will be disabled.
Some of the messages that come from it are couldn’t read the metadata spec for this plugin
access to undefined global: _cm
access to undefined global: _pi
Sorry forgot to add the OS and version of Lightroom last time.
OSX 10.5.6
LR 2.3
Using the latest plugin smugmug-20090331.84.zip recently but noticed that now when ever I load up Lightroom 2 I get the following:
An error occurred while reading the schema for the plugin “SmugMug”. The plug-in will be disabled.
Some of the messages that come from it are couldn’t read the metadata spec for this plugin
access to undefined global: _cm
access to undefined global: _pi
If you’re seeing this after a Lightroom restart, it’s probably because you have a bad install. I guess you’ll have to install from scratch. Sorry for the hassles. —Jeffrey
Jeffrey - Still receiving the same error messages with the new .85 update there’s a total of 15 errors. Not sure if the plugin as of 2.3 gets copied into a folder that Lightroom can reference each time.
I’m not sure if this requires a reinstall of Lightroom or if I’m possibly looking in the wrong spot for the corrupted plugin that Lightroom is using?
Also not sure if it matters that the plugin is downloaded to the desktop vs a special folder on the hard drive.
Thank you for all your help and a wonderful set of plugins!!!
When you install a plugin in Lightroom, you’re not copying anything… just telling Lightroom “hey, use this folder as a plugin”, so you should put the unzipped folder where you want it to stay before installing it into Lightroom. Perhaps “llink” or “register” would have been better words for Adobe to choose. You can see the path to a registered plugin in the 2nd-from-the-bottom section on the right side of the plugin manager. It should reference a folder whose name ends with “.lrplugin”, and inside should be a bunch of .lua files, some images, and some sub folders…. —Jeffrey
So I’ve redownloaded the plugin using 2 different browsers, completely reinstalled Lightroom 2.2, tried 2.3, fixed permissions and still the same errors pop up:
Plug-in error log for plug-in at: /Users/tjames/Downloads/smugmug-jfriedl.lrplugin
**** Error 1
An error occurred while attempting to run one of the plug-in’s scripts.
?:0: attempt to concatenate a nil value
**** Error 2
An error occurred while attempting to run one of the plug-in’s scripts.
Access to undefined global: _pi
**** Error 3
An error occurred while attempting to start the plugin.
?:0: attempt to concatenate a nil value
not sure what it all means..
It really looks like an install problem…. no one else is reporting these problems. Could you send me (via email) a screenshot of the plugin manager with all sections visible, and a screenshot of the contents of the plugin folder with all details (filename, size, etc.) visible? The folder screenshot should show info about files named “Info.lua”, “Init.lua”, and more. —Jeffrey
Hi there, I’m using plugin v 20090403.85 and LR2.3. I noticed on an older version that it was possible to select a smugmug Quick Setting - e.g. smugmug default, or something we’d created ourselves in smugmug
This no longer exists and it drives me nuts as I everytime have to set the order the photos are sorted in and also to turn shopping cart off.
Is there a way to bring this feature back please?
Thanks, Jason
The “Quick Setting” applies when creating galleries, which you can do fro the SmugMug Tools section of the export dialog. —Jeffrey
Hi Jeffrey - about your answer to my comment - that’s the problem - I don’t see the Quick Settings list in the SmugMug Tools section of the export dialog! Never have… why is that do you know? Do I need to reinstall?
Thanks, Jason
Sounds like we have a mystery on our hands. Could you send (via email) a screenshot of that part of the Export Dialog? —Jeffrey
Hi Jeffrey, actually i just solved it right now
i went into File Plugin Extras and in the SmugMug export settings I cleared out the v1.x uploader settings or prefs
Now it’s back
If anyone else comes up with this problem you’ll know where to point them too now - maybe they had v1.x before too….
Thanks, Jason
I’m glad it’s fixed, but that’s very odd that it was fixed that way…. there’s no relation between the two plugins as far as Lightroom is concerned, and as such, I have to go through some hoops to enable that “clear out” command. I can’t imagine how it could have mattered, but like I said, I’m glad it’s fixed.
—Jeffrey
Hi there,
Sorry - just a quick question which I’m sure is my stupidity, but I’m a bit stumped right now …
I just downloaded version 20090403.85 to try for uploading to SM. Looks fantastic so far, except for one problem:
In LR I use a hierarchy of keywords, eg friends containing a list of names etc. But no matter which combination of the plugin options I seem to choose, only the parent keyword is getting uploaded to SM.
So if I have “paul” inside “friends” the only keyword that gets to SM is “friends” and not “paul”
What I’d like is to have both, or minimally the lowest level tag.
Again - sorry this is probably my stupidity and/or ignorance, but I’ve been playing for a few hours trying to get it to work.
Apart from that looks great - thanks!
Richard
In Lightroom’s library module, right-click on a keyword in the Keyword List and select “Edit Keyword Tag”, then ensure that “include on export” is checked. —Jeffrey
Hi Jeffrey,
thanks for your reply to check that the tag I have is set to be included on export - it was.
I then played around with moving the tag around, checking what other tags did etc. I now am lost.
I have one tag - labelled “me” - that refuses to export to smugmug. It’s set to export, but it doesn’t. It was in a hierarchy under “people”. I moved it to be a top level tag - doesn’t export. I moved it into another hierarchy - doesn’t export. I removed it from the photos, quit, added again - doesn’t export.
I tried adding other tags from the “people” hierarchy to the same photos - they do export without a problem. I tried other tags in other hierarchies - again not a problem.
So it seems I just have a problem with this one tag - “me”!
Do you know if SM has an issue with a tag labelled “me”? (or lightroom???)
Is there any log files that your plugin or LR produce that I could look at to try and see what’s going on?
After doing an export, you can check the log file referenced in the upper-right of the Plugin Manager, although it’s not necessarily easy to understand. There’s a “send to Jeffrey” button you can use to send it to me. Is your LR catalog perhaps brought over from LR1. There was a bug in LR2.0 that caused issues with exportability for keywords brought over as part of a conversion from a LR1 catalog. I don’t have a link handy at the moment, but you should be able to find it at Adobe… —Jeffrey
Thanks Jeffrey,
I tracked it down to a problem on SM. The tags were all be passed correctly, but it looks like SM has a bug/problem/limitation where it won’t display a tag “me”.
I changed “me” to “rjm” and it all works …I’ll follow up with SM later.
Thanks again for all your help
Richard
Jeffrey thanks for the working and maintaining this plugin. It really helps me with my workflow.
I have a question however - how do I make a search query for state of “Uploaded to Smugmug” metadata field generated by your plugin? Often I need to re-export to different source the same set of photos I uploaded to smugmug. Any hints how to achieve that (aside from tagging them manually on every export) would be appreciated!
In the Library Filter (which toggles on and off in Grid mode with “/”), simply pick “Uploaded to SmugMug” in the Metadata dropdown, and choose “Yes”. You can also make a Smart Collection that does the same. —Jeffrey
thanks!
Same question as Greg Aug 2008 but it wasn’t answered. It appears in plug in managerbut not export windows. I’m on a mac with Lightroom 2. Perhaps I’m not enabling it in the Plug-In Manager correctly, when I click on it it says fully functional so I just clicked done thats all. What do I need to do to make it show up above the medatata section as you showed in the export folder or on the lower left under plug-in exchange? I haven’t donated yet but will donate at least $10 if I can get this program to work. Thanks so so much,
Pam
I figured it out (you had it on your site but I didn’t understand that you had to switch to smugmug in the masthead above first instead of Files on Disk. Looks like a few people didn’t get this. Wow! Great program
hooray you fixed the scroll for galleries - thanks Jeffrey!:D
My plug-in has no “quick setting” option….
Thanks, Giulio
Check the “SmugMug: Tools” section, it’s there as part of the gallery-creation options. —Jeffrey
When I create a gallery via the plugin, the gallery doesn’t show up in the list unless I close and re-open the plugin 2-3 times. Am I doing something wrong? I’m sorry if this is a known issue, but didn’t see it on the ‘known issues’ list.
Thanks!
Ross
It should appear in the list right away, so if it’s not, something’s wrong. In testing, could you start Lightroom, create a gallery, wait for a bit (say, 30 seconds) and confirm that it didn’t show up, then enter the Plugin Manger and use the “send log to Jeffrey” button to send me a log. Normally, it’ll appear right away (one or two seconds), and it should scroll into view automatically if it otherwise wouldn’t appear in the list as scrolled. When you send the log, please make a note along the lines of “added category XXX, but it didn’t appear in the list”.
Then, exit the Plugin Manager and reenter the Export Dialog. If it’s still not in that list, please send the log again (”still not there”). Thanks. —Jeffrey
Boston, MA here….
WinXP
LR: 2.3 - 539407
Plugin: 2009429.89
Problem #1 - Can’t Authenticate. The plugin seems to be trying the an old SM nickname. Eventhough, I enter the current SM nickname, the authentication times out. During the waiting for retry period, I cancel the operation the plugin is showing the old SM nickname, not the one I am trying to use. It appears that my old SM nickname is cached somewhere within the plugin. I have uninstalled the plugin, and then shut down LR, and then reinstalled the plugin and same problem. (perhaps I need to reboot?)
Problem #2 - Can’t register the plugin. I have used PayPal to donate and have a transaction ID. When I try to register, it tells me that your server is not available.
Thanks for any/all help you can provide.
-Steven
About the SM nickname issue, after a login attempt, could you send a copy of the plugin log (via the “Send to Jeffrey” button in the upper-right section of the Plugin Manager)? I was out of town for a few days, and had one other report of “can’t register, sever not available” earlier, but I see some other registrations have come in, so perhaps it was a temporary network glitch that’s since corrected itself. Sorry for the hassles. —Jeffrey
Thanks for that new update, one of my clients name is with an ‘umlaut’ and now it’s showing up correctly in the plug-in.
All seems to be working now… nothing changed on my end except I am connected via wire and not wireless….
I am authenticated and donated!
thanks.
-sjf
Sorry but there are no quick settings in my plug-in under gallery creation option
Giulio
Ah, sorry, I forgot…. SmugMug limits quick settings to “Pro” or “Power” users. Does that apply to you? —Jeffrey
I’m getting this error all of a sudden (just started happening):
Error response from SmugMug:
system error (invalid album id)
Aborting export after 0 of 1 images successfully
uploaded
Lots of users are suddenly getting this. I think it’s an issue at SmugMug…. I’ve sent them a note. —
When uploading any images to a Smugmug account I get this error when it tries to send to their server- takes about 10 seconds to get this up after Lightroom starts sending, usually the time to upload one of my files.
“Error response from Smugmug:
system error (invalid album/image id)
Aborting after 1 of xx
Appreciate your help, only happened since I paid for the donateware version, ironic. Thanks for a great tool otherwise.
Spike
SmugMug seems to be having issues…. I’ve reported it, and they’re checking on it. —Jeffrey
re: 20090509.92 and the TEXT in your blog above
I don’t understand a word of it - I hope it doesn’t mean we have to do anything techy???
You can safely ignore it if you like… it’s just added functionality for those who wish to use it. —Jeffrey
Mr. Friedl,
I am a happy and paid user of the great SmugMug app. One SUGGESTION, or perhaps I’m just not seeing the option:
When uploading files to a new gallery, is there any way to ensure they get uploaded in the order they exist in Lightroom? Whenever I upload them, I always need to go into the gallery and reorder them. Just a suggestion for improvement. No urgency at all.
Keep up the great work - I’m sure you’re getting tired of maintaining it day after day, but it’s a great plugin.
Duff
The plugin uploads them in the order you have them displayed in Grid mode (or in the filmstrip in any mode). Do they get scrambled after arrival at SmugMug? —Jeffrey
Yeah, unfortunately they do. In fact, in hindsight, this is probably a Smugmug concern. I think I had the same issue with other uploaders in the past. Just seem to get added in a totally different order to what I’d expect. Lemme check with them and get back to you if it seems like there may be something hinky.
- Duff
The API has a method to forcefully sort a gallery, so I could add something to apply that after each upload. It would force it not to the order uploaded, but to the order selected for the sort (image time, image filename, image caption), so it’s not perfect, but it should be easy to add. —Jeffrey
Version .97 Problem
Hi Jeffrey, when I highlight a bunch of photos and click upload, some of these photos are not uploaded. I have no idea why. When I take an hour and find these unuploaded photo and upload them manually, they upload perfectly. And whats more strange is that the export dialogue says that 0 new photos are available to be updated…it seems that Lightroom doesn’t even detect these missing photos…
Is there a remedy to this? I got a few thousand photos and its a pain to look for those little buggers…
Do you perhaps have something other than “All” selected in the lower half of the “SmugMug: Upload Destination” section of the Export Dialog? —Jeffrey
Hi Jeffery, I had deleted all my photos and tried All to no avail. But after an initial upload, I upload edited photos sometimes using Update and the “delete previous uploaded copy” checkbox
Next time an image doesn’t upload that you think should, go to the Plugin Manager and send a log to me using the “Send to Jeffrey” button in the upper-right section. Include in the notes section what images weren’t included. —Jeffrey
Also Jeffrey, would it be possible to create a “Do this for all following instances” checkbox when you receive a “Image too large for export” or in the export dialogue box? It really would make the uploading process more automated. It’s not the first time I wake up in the morning to see my photos a quarter uploaded and uploading idle due to the popup.
20090521.97 Export to Smugmug plugin
I’m Caroline in Somerset UK.
I have installed the pluging but am unable to connect to SM. I tried sending the report from the plugin manager but that can’r connect either. I have no other problems with connecting.
Hope to get some help here, thanks.
Check your firewall and/or “zone defense” type settings. You may need to set exceptions for Lightroom and/or my server and/or SmugMug. —Jeffrey
Have you seen the new smugmug uploader applet they have on their site? Is waaaay fast. I can get 1.5Mb/sec upload speed with that, almost my full bandwidth.
The reason I point it out is that maybe you could leverage some of his work, and speed up the upload throughput? I do several hundred, sometime over a thousand photos a week…
Here is a thread from the new uploader’s author: http://dgrin.com/showthread.php?t=126990
One would think that uploading on picture would saturate your outbound bandwidth, and so that’s the best you could do. If their uploader is doing that, it doesn’t surprise me, but if LR is not doing that, well, then I’m surprised and I wonder whether the bottleneck is at SmugMug and their new uploader uses a different endpoint? What kind of throughput do you see from LR? The plugin has no control over how the bits are sent… it just tells LR to make the connection. LR, in turn, just uses your OS networking, so if there’s a fundamental difference between what the new uploader can do and what LR does, I’m not sure where to look to address the discrepancy. —Jeffrey
I am currently using 20090602.99
Is there a way in the Image Caption Templates for the upload to insert newlines?
For instance if I want to do something like
{Title}
{Caption}
I can’t seem to find a way to do anything other than {Title}-{Caption} or {Title} : {Caption}
Under the caption preset is a radio button (plain text vs. HTML) and under that is a note about how to enter line breaks… is that note not visible on your version? If not visible, please email a screenshot. —Jeffrey
Hi Jeffrey,
Is there anyway to add a function to the smugmug exporter to automatically skip images if the size is too large for export? Smugmug’s basic and power levels have limits on file size that I occasionally hit with my 50D. I just tried an overnight export of 150 photos but woke this morning to see it had gotten stuck at #29 because it was too large.
An even better option would be to enable size or quality adjustments only if the file size is too large - based on Smugmug’s criteria which you can make easier to remember by just asking the user if they are a basic, power or pro user.
The problem is that the size under limitation here is the generated image file size, which can be determined only after the image has been exported. It’s within the realm of possibility for the plugin to re-render the image to reduce the size, but there are a lot of problems that make the approach non-obvious. For example, the only way the plugin can guarantee the same look for the image (the same crop, same develop adjustments, the same export filters) is to resample down the too-big image to a smaller one (rather than re-generating from the original master, which the plugin can’t do). This means that quality will be lost, and we haven’t even started to reduce the quality in purpose in trying to make the resulting image file smaller. Should the plugin reduce the compression quality? The image pixel width/height? What if it’s first guess is not sufficient, or too aggressive? If you’re exporting your images at sizes near the limit in the first place, I’m guessing you’ll not like whatever compromises the plugin would make to try to get it right. So for the moment, I punt.
Also, a more complicated request would be to allow for multiple exports using the plugin. For example, I have separate galleries for my son and daughter but have to upload to one then the other or to an empty gallery and then move images within Smugmug. It would be great to set two processes to run (sequentially) and have the images (even the same ones if both are in it) posted to the correct gallery.
I don’t quite understand the request. You can select some images and export to one destination, then immediately select the others and invoke a second export. They’ll run in parallel, each to their own destination. Export Presets make it even easier. Is that what you’re asking about? —Jeffrey
Thanks for a great plugin,
E
Using LR2 with plugin version 20090602.99 on a Macbook
I am feeling pretty stupid right now. I did find the button with the hints about 5 minutes after I posted this. That’s what I get for trying to do stuff like this at 3am.
Thanks for your quick reply and this plug-in.
It’s so easy to get my photos out to SmugMug and my wife loves that I am finally getting my photos out for family and friends to see.
Hello Jeffrey,
I am currently using Star Explorer to upload images to my Smugmug account. I recently acquired LR2 and I am currently reviewing all of the plug-ins. Some of you folks, yourself included have done a fantastic job! Kudos to you. My question, How does your plug-in compare to Star Explorer for uploading, and can they work in conjunction. I also use Mogrify.
Thank you in advance,
Sean in Maryland
I don’t know what Star Explorer is, so I can’t comment about it, but I’m sure they can work in conjunction. I wouldn’t think you’d want to, but I don’t see why you couldn’t. If you’re using Lightroom, I’d think that you’d want to export post-develop versions of the images. —Jeffrey
Hi, Karen from Chicago–
How long does the donation last. I submitted a donation several months ago. Do I have to give one every time you make an update?
As I describe on the registration page, it’s my current intent that registration carries over across upgrades. A few users, for reasons I have not been able to nail down, find that the upgrade process destroys the registration. In that case, just drop me a note with your registration number and I’ll zap it so it’ll be good again. —Jeffrey
Jeff -
It appears thatthe only time I got the wrong directory is when i do a different type of export and then go to do a smugmug export. The gallery list is alphabetical and defaults to the middle of the alphabet. I switch it to most recent first and usually choose one of the top 2 galleries (usually just created them). The 3 times I have tried this in the last week it defaults to the gallery that was highlighted when I first switched to smugmug export. This may be why you are having so much trouble tracking it down. It only happens the first time.
It has happened with 20090605.101 and 20090521.
Let me know if I can be of help.
Love the plugin here in NJ.
I’ve tested every way I can think of and can’t replicate the error, nor have I ever been sent a log that illustrates the error. If you have the latest version of the plugin and experience this bug, please immediately visit the Plugin Manager and send a log (via the “Send to Jeffrey” button), noting what gallery you selected, and where the photos actually ended up. Also, please note the state of the “reload plugin on each export” checkbox in the lower-right of the Plugin Manager. (It should generally be unchecked). The log is wiped each time the plugin loads, so if it gets reloaded before you send the log, I’ll get nothing about the failed export… —Jeffrey
You said in a previous comment that Quick Settings are restricted to power & pro users.. I have a standard tier account and have Quick Settings on the Smugmug web interface but not in the plugin.. so is it only limited on their API?
Turns out that their docs were out of date. I just pushed version .103 to sync with reality. Thanks for the heads up. —Jeffrey
Jeffrey - Thanks as always for developing these plug-ins. It is my principal interface with Smugmug. It is a great tool.
I just updated to the smugmug-jfriedl 2.lrplugin 20090611.103 version and I am running Lightroom 2 on Max OSX 10.5.7.
When I bring up the plug-in, it has added a number of extra hidden characters in my password and obviously will not allow me to log into Smugmug. When I deleted that default profile and started from scratch with the right user name and password, the error “The Login attempt failed…Unexpected response from SmugMug (HTTP Status 0)”
Thanks and let me know if this is an easy fix and I’ll check back periodically.
Steve
The plugin always shows the same number of dots in the hidden password, so as not to provide any clues to the real password. The failed login could have been a temporary glitch with SmugMug or your internet connection. If it persists, please send a log (with the “Send to Jeffrey” button in the upper-right of the Plugin Manager). &mdash:Jeffrey
Jeffrey,
I’m about to start playing around with SmugMug’s “Proof and Retouch” feature. Does the “Replace the most-recent previously-uploaded copy” option in your plugin work with this? That is, if I retouch a photo, should I export it to a file and then upload it to SmugMug via the web site to replace the file, or will SmugMug recognize the change when your plugin sends the new image.
Thanks for all your work on your plugins! I use many and they are all amazing!
Jason
I’m not familiar with this “Proof and Retouch” feature, but the plugin’s “replace” feature should work if any updates on SmugMug’s side retains the same internal image number. Perhaps you could just try it and report back? —Jeffrey
As a follow-up to my previous question on “Proof and Retouch” with the LR plugin: based on an experiment I did by placing an order myself and trying to replace the ordered photo with a retouched photo, it looks like the plugin does indeed handle this! You can retouch whatever photos your customer ordered, then use the “Replace the most-recent previously-uploaded copy” in the plugin, and the customer’s prints will use the new copy.
Thanks!
I have been using your product for a few months and really like it. Recently though, I have been unale to upload to smugmug. I have the latest version of your product (version 20090616.106), and am using Lightroom 2, version 2.4.
When trying to upload, I get the following erros.
When trying to export to SmugMug, I get the following message:
Couldn’t render image: AgNegative: renderToFile:dng_error_file_not_found
That message is followed by the following message:
Unable to Export:
That error is from Lightroom proper (you’d get it even if you were doing a normal export to disk without my plugin). I’d guess you have a corrupt DNG file, but for the exact reason you’ll have to dig a bit. Perhaps check with Adobe…. —Jeffrey
Hi Jeffrey,
is there any way to make destination list of galleries bigger/taller and may be with bigger font ? The export destination is single most used control for me (I set up the rest and hardly ever change them) but it fairly small and really hard to use. Search field there would be also great but may be too hard to do…
pretty please
I can look into the bigger font thing, but you can change the height with the configuration link directly below the list. —Jeffrey