facebook-20100209.111.zip
· Version History
· Update Log via RSS
· Installation instructions
· “Donationware” Registration Info
· More Lightroom Goodies
· All-Plugin Update Log via RSS
· My Photo-Tech Posts
· My Blog
This Export-to-Facebook plugin is new for Lightroom 2.0 and later, and is not compatible with Lightroom 1.
Note: the Facebook API currently allows only uploading to personal pages, and does not allow uploading photos to business pages, and as such, your business-page galleries will not show up in the Lightroom plugin.
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”. I wrote it and make it available for free — everyone can use it forever, without cost of any kind — but unless registered, its functionality is somewhat reduced after six weeks. Registration costs the minimum 1-cent PayPal fee; any additional donation you'd like to make in encouragement or thanks is optional and completely up to you. For details, see my blog post titled Lightroom Plugin Development: Now With Added Encouragement.
Lightroom 3 — Registrations in Lightroom 2.x will not carry over to Lightroom 3 when it is released, so plan that you'll have to re-register if you upgrade to Lightroom 3. (That's for the real Lightroom 3.... registration is not required in the Lightroom 3 Public Beta, but be warned that plugin support is spotty and plugins may not work well there.)
( Update Log via RSS )| 20100209.111 | Geez, the auto-destination stuff (see the small "add/edit auto destinations" link on the right, immediately under the list of upload destinations) was screwed up in that the check to see whether the destination already existed didn't work, so it would create another (and another...) album with the same name. Fixed.
Changed the semantics of the Places filter (in the tokens understood by the preset templates of my plugins) in two ways: if applied to a string value rather than a number, it works on the first number found in the string. Another is that you can now use something like Places=-1 to round to the 10s, Places=-2 to round to the 100s, etc. |
| 20100208.110 | Hacked in a way to create a gallery on the fly during export... it's now an option in the list of export destinations. Caption presets weren't getting saved across LR restarts in some cases (for definitions of "some" meaning "all", sorry). |
| 20100205.109 | Completely changed how the one-click upgrade applies the newly-downloaded zip file, in the hopes that it'll work for more people. Rather than unzipping over the old copy, it now unzips to a temporary folder, then moves the old folder out of the way and the new folder into place. Prior versions' folders are now maintained (with the version number in the folder) in case you want to revert a version; you may want to clear them out from time to time. Of course, it won't take affect until you try to upgrade after having upgraded to or beyond this version. Caught a few more LR3b issues.
Fixed the {GPSAltitude} template token so that it should now actually work. Oops, the upload date/time custom metadata items were swapped. Doh! With this new version, each catalog will auto-update to correct the issue the first time it's loaded. The format used for the date and time are restricted in LR2 to whatever I've chosen, but the first time you load the plugin in the real LR3 (whenever it comes out), the catalog will update itself again to write the dates/times in your user-customized, localized format. Lots of updates to the Twitter support:
|
| 20100118.108 | Added two new template tokens, {DaysSince} and {PhotoDaysSince}. They're a bit tricky, but could be useful. |
| 20091230.107 | Added a "Repopulate URLs" button to the Plugin Extras dialog, to allow correcting for the bug fixed in v105, and to correct for photos uploaded with old versions of the plugin. |
| 20091230.106 | Turns out that the fix in v104 didn't. Maybe this'll work? |
| 20091230.105 | Sigh, it seems 30,000+ lines of code are getting to be hard to keep track of, and I unintentially removed the exported url from the custom metadata (from the 'At Facebook' item) a few versions back. This should fix it, at least for images uploaded from now. |
| 20091230.104 | Still don't know what causes the "An unknown error occurred" error at Facebook, but I'll have the plugin retry the operation to see whether it gets more lucky the second (or third...) time around. |
| 20091216.103 | Figured out when the "AgExportSession.photoExportSequence is obsolete; use photoIdExportSequence instead" error was coming from. A bug in LR3 beta. I had to disable the export filter for the beta to avoid this. |
| 20091215.102 | Allow changing the font size of list of upload destinations. Those with long names might want to choose a smaller size to allow more text to fit on each row. |
| 20091214.101 | Added the special {NOJOINERS} token to the Template Language understood by my plugins. |
| 20091212.100 | Added the "At Facebook" custom metadata item for the image Url, and in LR3b, enabled the ability to "Go to Published Photo". Fixed an LR3b problem when trying to republish a photo that had seen some changes. Note that because Facebook does not allow a plugin to delete a photo, when you republish, you're really sending a second (or third...) copy of the photo. Photos are clearly not high on Facebook's priority list for enhancing their plugin API... if you'd like them to add more features (so that I can add more features), please request it of them. |
| 20091209.99 | A few small fixes for LR3b. |
| 20091205.98 | Minor internal debugging tweaks. |
| 20091118.97 | Added an {Altitude} item to the templates understood by the plugin. It's the numeric altitude in meters, as opposed to the {GPSAltitude} item which is a description of the altitude along the lines of “32.7 m”. Also updated the Places filter so that it can be used on fields that merely begin with a number. |
| 20091023.96 | A bunch of UI fixes for LR3b, such as fixing the scrollbar and the token-examples dialog. |
| 20091022.95 | Added a first draft of some rudimentary support for Lightroom 3 Beta. See this important note about plugin support in Lightroom 3 Beta and Lightroom 3, including future plans for features and my registration system. |
| 20090918.94 | Previous fix wasn't quite enough... this should do it... |
| 20090918.92 | Some users' Facebook albums weren't showing up in the export-destination list, due to a processing error on my part. Fixed. |
| 20090916.91 | Some UI tweaks earlier in the month had an unintended side effect of breaking the "choose destination at export time" feature. Sorry... fixed! Also, added some prose to make it more clear that the "create album" part of the choose-destination-at-export-time dialog is not part of the export process, but merely a tool placed there for the convenience of those wishing to create a new gallery just prior to exporting. (Sorry to everyone who couldn't contact my server for the last few days... it had "issues", that are now fixed.) |
| 20090910.90 | I'm back from a long trip and starting up the plugin machinery again. In this version you can now include line breaks in your captions, by using <br> in the template. |
| 20090716.89 | Sigh, Twitter engineers treat developers like a bunch of twits. Twitter just made a sudden, unannounced, and undocumented change to how they allow external applications like this plugin to connect to Twitter, breaking every external application out there. If a plugin follows the Twitter documentation, it will not work. I couldn't believe Twitter engineers could be so inexperienced or hostile (which?) the first time they pulled a stunt like this, but again? This is ridiculous... are there kids running the shop over there? If they do this again, I may just yank Twitter support from the plugins... it's not worth the frustration. For the time being, this push should fix things. |
| 20090715.88 | Facebook changed how they return data about an uploaded image, which manifests itself in prior versions of this plugin as "Error uploading image: no photo id". This fixes that. |
| 20090714.87 | Added TIFF and PSD to the list of image formats that Facebook accepts. Most users won't care about this one way or the other, so it still shows up only when specifically requested via the "Display export-dialog sections for size, quality, and sharpening" option in the Facebook: Tools section of export dialog. 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. 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). Added a defensive error check: 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.86 | Sigh, this upload-destination fiasco is a real pain. Maybe have it nailed down this time. |
| 20090615.85 | 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.84 | 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. |
| 20090610.83 | A lot of people have been getting an “unknown error occurred” error from Facebook, and then reporting it to me. It's an error from within Facebook that the plugin is just passing along, so I can't do anything about it. To try to stem the flood of email I get about it, I've added a note saying "it's Facebook's problem; contact them, not me". It's very frustrating. Added a bunch more debugging to try to figure out why some small number of users can't seem to get the export to go to the album they target. May have even fixed the problem. Added a couple of new custom metadata fields, "Facebook 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 Facebook. 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 Facebook, 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.facebook2.uploadDate and ....uploadTime. |
| 20090602.82 | 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. |
| 20090521.81 | 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.80 | Facebook upped the photo-count limit in albums from 60 to 200. Some users have quietly had the higher limit for months, but the plugin could never know who had what, but now that they've pushed this change for all users, the plugin can do the right thing. You can now use the scroll wheel with the scrollable lists (for the album 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 the caption preset: 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. |
| 20090519.79 | Fixed an album-creation bug I introduced in a previous version. |
| 20090518.78 | 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.77 | Fixed a plugin crash that would happen when "select at export time" was chosen for the destination, and the export was launched from an Export Preset. |
| 20090510.76 | Added a link in the Plugin Manager to the plugin's update-log RSS feed. |
| 20090509.75 | Added items to the title/description presets: ZenfolioUrl, SmugMugUrl, 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>.
|
| 20090429.74 | Fixed a bug that could potentially crashed the plugin while editing caption/title presets. |
| 20090425.73 | 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.72 | 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.71 | 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.70 | 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 |
| 20090325.69 | 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. |
| 20090321.68 | Enhanced the "Create album at Facebook" part of the Export Dialog with the ability to set the location, and the visibility (which defaults to "everyone"). |
| 20090313.67 | 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. |
| 20090310.66 | 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.65 | 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.64 | If there's an error calculating the automatic destination for a photo, now actually reports that error instead of just crashing |
| 20090302.63 | Fixed a bug that could cause the plugin to crash when using the File > Plugin Extras |
| 20090228.62 | Fixed a bug that caused a plugin crash if my server couldn't be reached during registration. |
| 20090223.61 | NOTE: you may need to restart Lightroom after installing to this (or a later) version from the previous (or an earlier) version. Please try a restart if you get an error the first time you try to use the plugin. 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. Several fixes and enhancements in this release: It can now track multiple Facebook authorizations, and you can easily switch between and among them. There have been a lot of UI tweaks to make things look more natural (but Lightroom's plugin infrastructure still places great restrictions on what can be done, so it's not like it's smoothly polished yet). It now has more robust error reporting in the face of network problems. The plugin still can not upload to business pages: Facebook simply doesn't allow it. |
| 20090129.60 | 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.59 | 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. |
| 20090119.58 | 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.57 | 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. Add a bit more stuff to make super-duper sure that the export colorspace is sRGB unless the user explicitly changes it. |
| 20090115.56 | Added more debugging-log stuff to the 'Upgrade Now' button action, to try to understand why it doesn't work for some people. |
| 20090115.55 | 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.54 | 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. |
| 20081228.53 | 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. Now properly reports why an export fails (e.g. because the destination album is full). Added the Facebook default application album to the list of destination albums. This album can hold 1,000 images, as opposed to just 60 for user-created albums. In the list of albums, note how many images can be added to each album, and note that the count is incorrect for images with a non-empty pending queue. Refuse to start the export if the destination album is too full to hold all the exported images. Offer the ability to bypass the pending queue completely. |
| 20081224.52 | The "Extras" item in the File menu had stopped working. Works now. |
| 20081223.51 | Bumping back the expiration date. |
| 20081210.50 | Added a checkbox in the Facebook Tools section that enables the export-dialog sections for image size, quality, and sharpening. The vast majority of Facebook users should not need these sections because the plugin defaults to what makes sense for Facebook, but if you really want to get in there yourself, check the box and reload the plugin (or restart Lightroom). |
| 20081208.49 | Fixed a problem that sometimes caused errors during login/authentication, or after logging out. Fixed another problem that allowed you to authenticate only only once during any particular plugin load (which, for most, means once per Lightroom session). That, too, is now fixed. |
| 20081204.48 | 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.47 | The counting of previous uploads (for the All/Update/New of the Upload Destination section) was not working right. |
| 20081125.46 | Another fix for a bug that had disabled plugin presets (for captions, etc.) |
| 20081124.45 | 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.44 | Fixed a plugin crash when using the plugin's built-in preset system. |
| 20081122.43 | Try to better report errors, such as "album full", when an upload fails. No problems from the upheaval recently, so pushing back the expiration a bit. |
| 20081117.42 | Oops, wouldn't let you log in / authenticate if you weren't already. Doh. Fixed. |
| 20081117.41 | 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.40 | Woo-hoo, finally(!) fixed (I think) the logout/login/restart-and-cross-your-fingers problem. |
| 20081114.39 | More debugging info to the log. |
| 20081113.38 | Fixed yet another list-of-upload-destinations bug. There are sure a lot of edge cases here. |
| 20081111.37 | Fixed a crash that happened sometimes when there are not yet any preexisting destinations at Facebook. |
| 20081110.36 | Added a bunch of debugging stuff to help diagnose a problem that I've not been able to reproduced myself. If you get a “ref.value is nil” error dialog, please send me the debug log referenced in the upper-right section of the Plugin Manager. |
| 20081103.35 | 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.34 | Now works properly with the shadow GPS data maintained by my geo-encoding plugin. |
| 20081022.33 | Addressed (and perhaps even fixed) a bug introduced in the previous build. |
| 20081022.32 | Added back the "Metadata" section, which was one that was removed in .30. Sorry for the hassles. |
| 20081021.31 | Small update so that a stuck background version check does not disable the plugin. Added a message in the login area with instructions on how to use the plugin with multiple accounts. 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.30 | Removed a bunch of sections from the export dialog (export image type, size, colorspace, metadata, etc.). When uploading to Facebook, the same selections are always needed, so it makes the presentation simpler to remove the option to change them. |
| 20081011.29 | Removed the "delete previous versions" option, because Facebook doesn't allow an application like this to delete photos. Internal change to the user-agent string that the plugin sends when uploading, to better conform to accepted web standards. |
| 20080924.28 | 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. Moved the items in the "Upload Management" section into the "Upload Destination" section, since they are really quite related. |
| 20080923.27 | Sigh, just realized that the "check for new version" stuff did break in 2.1. Totally my fault, sorry. Fixed. |
| 20080921.26 | 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.25 | 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.24 | Added the ability to use template tokens like {Filename} in the "extra tags" input box. |
| 20080916.23 | 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 (what I thought I fixed in .18). |
| 20080916.22 | 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.21 | Added a few more descriptive tooltips to the example-token dialog |
| 20080914.20 | Oops, fixed a boo-boo introduced in the previous version. |
| 20080914.19 | 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.18 | Fixed tokens "OriginalWidth" and "OriginalHeight" in templates. Fixed the "home page" url. 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.17 | Fixed an "undefined global: DestinationSynopsis" error that could happen when using a preset with a "select at export time" upload-destination setting |
| 20080831.16 | 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.15 | Added a bunch of new items to the template language. |
| 20080829.14 | Oops, left some debugging cruft that results in an "empty" dialog if the logged-in-user has no galleries or the like. Fixed. |
| 20080828.13 | Minor tweaks |
| 20080828.12 | A few more tweaks to report a failed upgrade attempt a bit more clearly |
| 20080828.11 | Whoo-hoo, finally figured out the "assert" problem that some people without albums 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.10 | 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.9 | 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.8 | Fixed infinite cycle of 'assert' messages one might get in odd situations. A few small typographic nits. I'm not sure why the choose-at-time-of-export dialog also includes the selection "choose at time of export" (it shouldn't), but until I can figure it out, I've added a special check to abort the export if a real destination hasn't been selected. |
| 20080812.7 | Fixes (I hope) a "bad argument #1 to '?' (table expected, got nil)" error |
| 20080811.6 | 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.5 | Fixed {State} and {Rating} in preset templates. |
| 20080805.4 | 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.3 | Fixed "Access to undefined global: LrError" error that happens when trying to report a login-related problem. |
| 20080804.2 | Fixed a couple of internal errors related to the "choose destination at time of export" feature |
| 20080729.1 | Initial public release |
)
See the known issues before reporting bugs. Also, when reporting bugs, please include the OS, the version number of Lightroom, and the version number of the plugin. Seriously. I need the full version number or I likely can't do anything but ignore the message.
If I use the export dialogue box – wait for LR to login to Facebook- then click export i get:
Info
At line 12998 popup.
Then to the “choose dest. for image” which doesn’t pull down any album names (it does login in the export dialogue before though.) then clicking export it closes but nothing happens/gets uploaded. Suspect this is due to the New facebook pages?
If I use the File-Export menu in LR 2 I get the same error as doing so for Flickr:
Unable to export:
can’t log in to Facebook: missing credentials
I think I’ve fixed the first and third of the issues you mention, as of version .2. I’m not sure about the middle issue yet. —Jeffrey
AWESOME! thank you!
When I try to upgrade your plugins using LR 2.0, I consistently receive an error message related to unzipping the new archive. Here’s what it says in the log:
Command: “”C:\Documents and Settings\Michael\My Documents\My Pictures\Lightroom\Plugins\facebook.lrplugin\Win\unzip.exe” -o “C:\Documents and Settings\Michael\Local Settings\Temp\facebook.zip” -d “C:\Documents and Settings\Michael\My Documents\My Pictures\Lightroom\Plugins”> “C:\Documents and Settings\Michael\Local Settings\Temp\lr-plugin-unzip-log.txt”"
exit status is 1 (0×00000001)
My hunch is that there is a problem with the command unzip.exe. I don’t see that file in the Win folder within the plugin and it’s not in the original archive I downloaded.
Doh, you’re right! Fixed in .4 —Jeffrey
Thanks for making great plugins!
It’s seams that don’t work with my windows vista and lightroom 2, I have a mistake
Ok, I find the problem. The plugin don’t support my charset. Ex :
Plug-in error log for plug-in at: C:\Users\Michaël Silvestre\Documents\Lightroom\plugin\facebook-jfriedl.lrplugin
I make a test and I must remove “é, ë, è, à, …” and the installation can begin
I don’t understand what you mean… from what did you have to remove those characters? From one of the folder names? —Jeffrey
No error messages except for the original folders not appearing in the list for this plugin, I click export and nothing seems to happen, no photos exported nor arrive at Facebook. Nothing in the log either – anyone else have this problem or is it fine for all except me?
I get the following several times.
Error response from Facebook:
Error uploading image: no photo id.
Any ideas?
I finally think I figured this out… I wasn’t reading Facebook’s error message properly, and so if there was an error such as “your album is full”, you’d get this not-very-helpful error from my plugin. Fixed in version .43 —Jeffrey
Your Facebook plugin is not reading my Facebook photo albums. And when I try to get it to create a new one, it just doesn’t…
So, it’s not working for me. Bummer.
It DID work for me the other day, just fine. But now it’s not reading my albums…
Same problem here. Painful workaround was to logout from plugin, restart lightroom, authenticate again, then it works as normal. Until you start up lightroom again the next time and same thing happens. rinse and repeat. painful but better than exporting, then uploading manually.
This is FANTASTIC! Huge thanks!
The new version worked fine, until I switched over to the NEW Facebook, then it wouldnt detect my albums and wouldnt create any new ones. It also failed to authenticate- I suspect because of the url being parsed through- the new facebook has a changed url. So, until Mr Friedl returns the solution is actually pretty simple-
*in Facebook just select “Back to the old Facebook” on the top right;
* once in there, reauthenticate (hopefully will work)
*you’re in- uploads should work, album creation works
*once you’re done and want the new FB look, just switch it back with the link on the top left in FB.
Love your work JF.
Spike
Man thanks a lot for this great stuff, I had like 15K photos just waiting for something like this, and now with the LR2 64bit it can’t get any better. I connected ok with the plugin and saw the test album I have on facebook and uploaded files correctly. My question is just if it’s possible to upload to the Profile Album? Nothing important, just curiosity and more convenience. Cheers!
The latest version doesn’t seem to be able to create new galleries, or detect any existing ones, making uploading impossible. At least that is what I am getting.
It seems to be working for me, on both counts. Perhaps you could email the log, after trying (and failing) to create an album from within the Export dialog? —Jeffrey
“The latest version doesn’t seem to be able to create new galleries, or detect any existing ones, making uploading impossible. At least that is what I am getting.”
Same here. And this error comes up as well:
Unable to Export:
An internal error has occurred: ?:13130: attempt to index field ‘?’ (a nil value)
Thanks for this plugin! It works great if I only use one Facebook account.
How do I set things up to allow me to publish to a second Facebook account? As soon as I logout, I can’t seem to authenticate myself again. I have been able to clear things if I completely log out and then back in again, then access the 2nd Facebook account.
Anyway to make this a smoother transition?
Thanks,
Steve
Back again after some more experimenting – turns out the trick is to make sure you close the Export to Facebook dialog from within Lightroom after you have logged out of the current Facebook account. As long as I do this, I can easily switch back and forth. Thanks again!
Steve
The Web site listed in the status doesn’t exist. Not a big deal but thought I’d mention it. I love the Flickr uploader so adding in the rest. I don’t suppose fotonomy.com is on your list of sites to work with
Oops, thanks, fixed the home-page url as of .18. Have never heard of fotonomy, sorry. —Jeffrey
Update via the Plug-in Manager aint overwriting the plug-in file.
I’m using Mac Lightroom 2, tried updating from 20080905.17 to .20.
Otherwise , kick ass plugin, helps out alot! Expect a donation for usage!
Anuga has the same issue with me again – I’m on XP. Stuck on picasaweb, flickr and facebook.
your plugin constantly fails to upload doesn’t even give an error message in some case I tried every possible combination it wastes tiem instead of saving it first I was getting a nil value error then I started to get errors when creating an album. I’m using a macbook pro lightroom 2 and so on please tell me what I’m doing wrong?!!!
Sorry to have wasted your time with my crappy plugin. —Jeffrey
Just like to make a public apology to Jeffrey for my insolent comment. His plugins are great I’ve been using them for a while but my computer and me have not been seeing eye to eye and I fear I have taken my software rage (apparently now known condition!) on Jeffrey. Jeffrey I’m so sorry for dissing your valuable and very time consuming work.
My sincerest apologies to yourself and all those who use this site in future I will not post unless I have something constructive or complimentary to say.
However the question still remains is anyone else having the same eexport problems a me? :::
Failed to create album- error message right on the cusp of sending the first image
or
No activity whatsoever upon clicking the continue to export button.
Jamie
I have a problem when adding the plugin in plugin manager. The system error says “error while reading the schema”. In the diagnostic log there are 17 errors.
i.e.:
(1) Version.lua: No such file or directory,
(2) Access to undefined global: async_version_check
(3) Access to undefined global: PREFS,
(4) ?:411: attempt to call field ‘?’ (a nil value)…
I have vista sp1, admin rights, lightroom 2, downloaded and tried to unzip the package with both winzip and winrar and loaded the facebook-jfriedl.lrplugin folder normally.
Any clue? Thanks.
Gee, I don’t know…. that’s really odd. You get this with the latest version (.20)? —Jeffrey
Yup, latest versin, just downloaded from this site.
It has to be something in general because I have same problem with picasa plugin, very similar error report…
Any clue what should I check, change…? Could it have sth. to do with regional settings, characters (I have english Vista, but Slovenian regional settings)?
Thanks.
Ah, that rings a bell…. there’s a bug in 2.0 that makes my plugins not work when they’re installed in a path that has non-ASCII characters (such as a username with an accent in it). Could you try installing in a place whose path is pure ASCII, and giving it another try? —Jeffrey
Awesome tool, but I can’t seem to export multiple pics to facebook…Only 1 at a time. I get the following 2 warnings:
First Warning:
Whoa,
“…” does not exist immediately after waitForRender. Please let Jeffery know.
Second Warning:
Unable to Export:
Couldn’t open DSC_0006.jpg:
C:\Users\AJ\AppData\Local\Temp\50F0F61B-C8E1-4ECD-ADF7-ESFA0D082540\DSC_0006.JPG: No such file or directory
I have mogrify running but also tried it without…I’m running vista ultimate…thanks for your help!
It appears to be a Lightroom bug; I’ve added it to the known issues page. —Jeffrey
Hmmm, I must have something wrong as the exporter is clearly working for other people – but I am no longer seeing my albums. I saw this upon upgrading to 17. I then uninstalled the plug in and added in version 22 – same issue. Just upgraded to 23, no change.
The only option I have is
*** select at export time (useful for export presets) ***
If I carry on regardless, I am prompted for my destination but I still only have the above option. If I try to continue with export from there, it fails – sometimes silently, other times with a (justifiable message) that it aborted due to lack of destination.
I’m still not that good with lightroom – any ideas of what I should look at? The plug-in worked a treat yesterday!
Jap, that works. The plugin path must be a pure ACSII.
Great, thanks Jeffrey!
Well, I tried various things and in case this happens to anyone else, the following sorted it out:
Go to the Export window
Logout of facebook
Remove the plugin
Restart Lightroom
Add in the plug in manually
Authenticate until successful message appears (took two tries)
Now my folders are there again. Clearly something went wrong with the authentication (although it recognised my name and gave the little “looking up albums” bit at the start) but it wasn’t possible to simply log out and back in.
*shrug* Works now, anyway
Great plug in for the casuel facebook user, but what about those of us who have a facebook artist or business page?
I don’t know… what is a “Facebook artist or business page”? I don’t use Facebook. —Jeffrey
Think of a Facebook Page as something like a Facebook profile, only for entities like a business, a band or artist, or a product or even a brand.
http://wiki.developers.facebook.com/index.php/Facebook_Pages
Uh, so what does this have to do with Lightroom and my plugins? —Jeffrey
You offer a plugin for lightroom that uploads photos to a facebook profile. It’s a nice plugin and is useful to facebook users. Facebook also has Facebook pages, it’s like a profile and is controlled by admins (facebook users). Facebook pages have photo gallery’s just like profiles. So, your plugin could easily be modified to do what it does for profiles but for facebook pages.
The link provided in my last post talks a bit about the how to script the calls needed for a page vs a profile. A user who is an admin would log in and then access the page rather then the profile.
The Facebook instructions are pretty opaque, but I think I figured it out. Let me know. —Jeffrey
? Thanks for your help. I disabled the plugin and I am getting further but after a few exports, I get error response from facebook:
Error uploading image: no photo id
Aborting export after X of X images successfully uploaded.
I was exporting 51 pictures.
Thanks
==============
I’m running into the same thing…. where should I send the plugin log?
Woo-hoo, I finally figured this out as of version .43. The real problem behind that message is that your album was full, or some other message from Facebook that I hadn’t been processing properly. —Jeffrey
Sorry i have problem uploading photos…. can’t select a previously created album or create a new album.
Any idea on what I can do? Thanks!
Hin:
This sounds like the same issue as I have. I’ve now streamlined the fix to:
Log out of Facebook
Exit Lightroom
Start up Lightroom
Go to the Facebook plugin and reauthenticate
Then the folders appear.
None of these gymnastics should be required any more, since version .41. Sorry for the hassles! —Jeffrey
First upload worked like a dream.
However on second and all subsequent attempts (whether trying to upload to an existing album or creating a new one) I get the following error message:
Unable to Export:
An internal error has occurred: Access to undefined global: AuthenticatedRequestHeaders
Logging into Facebook it appears the album is created, and one photo is uploaded, but then things grind to a halt.
Any ideas on a fix?
Yikes, thanks for the report. This is my fault, and the problem is in the code that supports the “delete previous versions” code. It turns out that Facebook doesn’t support deleting uploaded photos from an application like this, so I’ve just removed that option in the newly-pushed .29 version. —Jeffrey
Thanks Sylvia!!!! It’s working fine now!!!
Thanks Jeffrey for updating the plug-in as well!
Facebook exporter doesnt seem to work at all for me… i select the pics i want to export, i go to export, select facebook.. fill in things like file name, DPI and i create a new album… hit export, and nothing… what am i doing wrong?
Just updated to the latest version – for some reason, the plugin isn’t allowing me to create any new albums, thus there is no destination for the picture selection to be uploaded to. This happens in the main export window and also on the following pop up window,
I try and create a new album, but the main export window just refreshes (very quickly) and says ‘unable to create new album’ at the bottom.
I’ve tried restarting Lightroom and logging in out of facebook, but no joy.
Anyways, I love your plugins, the flickr one is brilliant, thanks so much for doing all of these essentially for free.
Thanks
I updated to the latest version and I too am having the same issue as fatpete. I can cot create any new albums or export any pictures.
Hi Jeff
firstly thank you very much for the lovelly plug ins just great work…I just updatet the facebook one and miss the watermark tool
would it be possible to add it again ? so that I can upload some pic with my defined watermark as it was possible to do it with the last one ?
regards reto
my facebook:
http://www.facebook.com/profile.php?id=1477166309&ref=profile
Sorry about that… I put it back in .32 —Jeffrey
Thanks a lot, great work
I’m trying to export upload directly from right hand mouse click menu and I get the following.
“An internal error has occurred: ?:15888: attempt to index field ‘?’ (a nil value)”
works fine if I go into the full Export… menu and do the same export, just not from shortcut menu.
Otherwise working great, thanks.
I’m trying to export to Facebook from version 2.1. When I click the Export button to export the photos, this error is immediately raised: “+743.8: At line 15259: ?:16108: attempt to index field ‘?’ (a nil value)”. It then asks for me to create/choose a FB album, which I do, and then it immediately ends the export without doing anything.
FYI – the album is not being created in FB.
The exact settings for my export are below:
– Export Location: Temporary folder
– File Naming: I’m using a custom template = {filename}-1
– Metadata:
o Minimize Embedded Watermark: N
o Write Keywords as Lighroom Hierarchy: N
o Add Copyright Watermark: N
– Facebook Tools: I’m am leaving these fields blank
– Facebook Upload Destination: I’m leaving these at the defaults.
– Facebook Metadata Management:
o Image Caption: I have tried with and with out captions
o Resolution Notation: 300 pixels per inch
I am using the latest version: 20081022.33
I am on a Mac, running OS X 10.5.5
Any help would be greatly appreciated.
Thanks so much!
I have been using this plug-in since LR 2.0 and it is working pretty nice.
However, I’ve got the error similar to “+743.8: At line 15259: ?:16108: attempt to index field ‘?’ (a nil value)” after I’ve upgraded my LR to 2.1. The problem still exist even I upgraded the plug-in version to 20081022.33
I am running LR in Mac OS X 10.5.5.
Thanks so much!
I’m another happy customer of the new plugin on LR2.1.
I’ve been using the Flickr one for ages.
Thank you!
I still have problems with the issue below (previously reported) …. i think it is not resolved yet…. thank you
“If I use the export dialogue box – wait for LR to login to Facebook- then click export i get:
Info
At line 12998 popup.
Then to the “choose dest. for image” which doesn’t pull down any album names (it does login in the export dialogue before though.) then clicking export it closes but nothing happens/gets uploaded. Suspect this is due to the New facebook pages?”
Hi i have used the flickr plugin for ages and its great, have LR2 and and imac but i have the same problems as a lot of people in that i cant see my albums or create an album in FB.
Thank you for the flickr one, and hopefully we can shed some light on the FB issue to help you with it.
Cheers
All this should be fixed, I hope, in .40. —Jeffrey
followed by:
Error response from Facebook:
Error uploading image: no photo id
Aborting export after 0 of 11 images successfully uploaded
Finally fixed in .43 —Jeffrey
Hi Jeffrey, i worked out if i actually login to FB prior to export from my firefox browser it works. If i dont login it doesn’t work even though the plugin works. I dont know if this will help anyone but give it a try,
All this should be fixed, I hope, in .40. —Jeffrey
I uninstalled the plugin.
Logged into Facebook.
Loaded the plugin through the plugin manager
Authenticated
and it works.
Go figure. Hope this helps others.
I finally figured this out… it’s fixed, I hope, in .40. —Jeffrey
like a number of other users above i have been getting this error.
+159.6: At line 15578: ?:16440: attempt to index field ‘?’ (a nil value)
logging out and then reauthenticating the plug in returned function to normal. very odd. can send a log file if this helps?
Hi i dont loaded the latest 11.37 and the export button is grayed out. I cant see what i an not clicking to get this enabled. Its also no showing my albums. Note two versions ago i had this working but only if i logged into FB with my browser first so i am not sure what has happened?
I use OSX thats patched upto the latest version.
I know this seems to be causing troubles but if you can get it stable like the flickr one it will be great so thank you for your work to date.
All this should be fixed, I hope, in .40. —Jeffrey
facebook-20081111.37
I just can’t get your plugin to authenticate. I can press “Visit Facebook” and my browser opens it but pressing “Authenticate…” just does not do nothing. Same with flickr export plugin. Any ideas? (Mac OS X 10.5.5, LR 2.1, 64 bit)
If you could send me the logs (referenced in the upper-right of the Plugin Manager) after a failed authenticate attempt, I’d appreciate it. Do update to the latest versions first (especially Facebook, where I just fixed an authentication issue in .40). Thanks. —Jeffrey
Version 2008111439
Can you take a look at the issue of colorspace selection? The colorspace selection was removed after 20081011.29 and I have been unable to get the plugin to export in sRGB.
Alternatively, is it possible to build a version of 20081011.29 that does not expire?
thanks
All exports via the plugin are sRGB, or should be, so if you’re seeing resulting files that are not sRGB, it’s a bug, or some intervening “Post-Processing Action” (what I call an “export filter”, such as LR2/Mogrify) diddling things along the way. If it’s not the latter, could you send more details about what you’re seeing? —Jeffrey
“Removed a bunch of sections from the export dialog (export image type, size, colorspace, metadata, etc.). When uploading to Facebook, the same selections are always needed, so it makes the presentation simpler to remove the option to change them. ”
So, how do I select a size, colorspace, sharpening, etc.? I used to resize all photos to 604, make sure the colorspace was correct, and apply no shapening. So, how can I do that now?
It’s all done automatically. It makes no sense to upload to Facebook with anything but sRGB, and little sense (I won’t go so far as to say “no sense”) to use anything but normal screen sharpening. The 604-on-a-side maximum also seems to be the standard, so I just have the plugin select these settings rather than the user. A lot of users don’t understand these settings, so taking them out makes things simpler for everyone, at little to no cost for most people. —Jeffrey
Update: as of version .50 you can now enable the sections if you so wish, but they default to being hidden. —Jeffrey
20081114.40 NOW works! so far I havent had to reload plug in!
great thanks.
I have loaded 1117.42 on an iMAC and its working like dream. Thank you for your support and i look forward to the next project you take on.
Cheers
Carl
I’m still getting the message:
Error response from facebook: Error uploading image: no photo id.
I’ve noticed that this primarily occurs in albums with over 60 photos; is anyone else having the same problem?
I’m using Lightroom 2.0, MacOs MacBookPro Version 10.4.11
I’m also getting (sometimes) the problem with “no photo id” with latest release. Trying several times and sometimes, it finally works, sometimes not.
Hmmm, that’s distressing… I thought I had that bug licked. If you could send me (via email) the plugin log the next time it happens, I’d appreciate it. It’s the log referenced in the upper-right section of the Plugin Manager.
Another question I haven’t found a clear answer (any link?): do the plugins (Facebook as well as Picasaweb) support “replacing” photos? I mean -without deleting or adding- a new photo but really replacing an existing one. For instance, I often tune my photos and I’d want to publish their latest release but I’d like not to loose any comment made before. For this kind of photos, it rightly detects changes but publish new release… Maybe it comes from the ability of PicasaWeb or Facebook not providing replacement feature…Obviously, a comment could be made obsolete considering the photo…
Facebook doesn’t allow replacing, and I think that if PicasaWeb did that I would have added that support. Maybe I just never got around to it. I’ll check. —Jeffrey
Anyway, your plugins are awesome and saves me lot of time. Thanks for your work.
Sorry, just read your red alert
Mine is Lightroom 2.1 with Facebook plugin 20081204.48, Windows Vista.
Very nice plugin, unfortunately it stopped working for me a couple of releases ago.
Current Status is:
Version: 20081204.48
Getting the following error (I am logged in via browser):
“At line 22258:
bad state:
At line 22258″
Then the dialog requesting authentication appears. After clicking on “ok” I receive an
“INTERNAL PLUGIN ERROR
attempting login aborted”
followed by
“An internal error occured: ?:22174: assertion failed!”
and the Dialog for choosing an image destination with status “not logged in”.
Well, while trying to track this down, I found and fixed a few bugs that are probably unrelated, but maybe I got lucky and fixed your bug, too. Could you try again with the latest (whatever is latest when you see this) and report back (via email is best) if the problem happens again? Thanks. —Jeffrey
Love the plugin, I use it regularly. Nice work!!
Is it possible to disable output sharpening. I am tuning my sharpening myself, portraits especially come out worse with screen sharpening.
version: facebook-20081208.49
Okay, in .50, which I just pushed, you can check box to enable all the dialog sections that 99.9% of Facebook users don’t need, so you can access them if you’re in the remaining 0.1%. —Jeffrey
Follow up on
http://regex.info/blog/lightroom-goodies/facebook/#comment-30088
Tested with version .50 – looks like its fixed now
thanks!
I’m running version 20081210.50 with LR 2.1 512205 and I keep getting this whilst uploading, just after the first photo:
“Error response from Facebook:
Error uploading image: no photo id”
What to do? Thanks,
Paul
LR 2.2 and PlugIn .51 on Vista.
I recently noticed that my images are resizing to 604 px. Reading above, I see that this decision is made automatically for me, so the settings I had in place went out the window. I had to reinstall all the plugins, and then recheck all my custom output settings. I found the checkbox for advanced users, and set the size to 500 as I want the photos to be, yet the plug in ignores my settings, and sizes everything to 604 anyway.
The tokens to set the date still do so incorrectly… setting the in camera capture date as opposed to the date the photo was actually captured to the card.
I found one stupid thing on Facebook: There is a limit of 60 photos per album ;(((
Anyway, it’s not clear from error message I got from Facebook Export plugin, which says:
Warning
Error response from Facebook:
Error uploading image: no photo id
Aborting export after O of 65 images successfully uploaded
OK
Actually, it should say (if possible) something like: Error uploading file: you have reached maximum of 60 photos per album – cannot upload more.
LR/Facebook plugin latest: 20081224.52
PS: Thanx for a GREAT plugins!!!
Maxim Krušina
Fixed in .53, thanks. —Jeffrey
Jeffrey, on LR2.2 plugin version 20081224.52
I have noticed that whenever I create and preset, in the Facebook: Metadata management, any caption preset that I have set would not stay.
After I created the preset, and LR preset, a reload of LR will leave the Caption preset blank. The preset that I have created, also disappeared and only the default 4 will remain.
Could you look into that, please? It is a good addition to the plugin.
Cheers from Malaysia.
I’ve gotten reports of this before, but have never been able to reproduce the problem on my end. I’ll dig around some more, I guess…. —Jeffrey
Bug on MAC OS 10.5, Lightroom 2.2, plugin exporter for facebook version 20090115.56 – it seems to always export in ProPhoto rather than in sRGB, resulting in the photos turning out seriously washed out. I have tried selecting sRGB in the dialog and it does not make any difference – thoughts?
Matt
I’m using Lightroom 2.0 and Windows Vista 64 bit os. I loaded the Lightroom 2 Facebook plugin 20090116.57. I can get it to load in Lightroom through the plugin manager, but when I click right click on export the plugin doesn’t show up in the list. Any suggestions……….
Thanks for your help.
Is there a way that the option to use a watermark could have a settings dialog? Point size, font, opacity, option to use identity plate, placement location?
The plugin doesn’t have any control over the (really wimpy) built-in watermarking feature, but Tim Armes’s LR2/Mogrify plugin gives you complete control. —Jeffrey
Is there anyway to change the dpi output? It seems to always be 240 and I would like it to be 72.
Thanks. All other functions work perfect.
hi, i downloaded the latest downloaded zip file.. but there´s no*.lr or lrdevplugin files… i think the file is broken or maybe i´m a fool…lol hope your help…
pretty cool blog
thanks
The plugin folder’s name ends with .lrplugin, and it (the folder) is the plugin. —Jeffrey
Jeffrey, would appreciate if you could put in a field to enter the “location”. I think the API allows it since the Java version of Facebook uploadr has it.
Thanks in advance!
Hi Jeffrey, thank you for a number of great plug in, I use for Facebook and Zenfoio – my question – what about FACEBOOK pages… I admin a few and would like to upload photos, but I can only create and see “albums” in my own profile..
Thanks in advance
Lars
Facebook does not allow an external application to add photos to a page, only to a profile. I have no idea why, but they told me that it’s something they would like to fix, but that it won’t be addressed any time soon. —Jeffrey
A quick question for you.
When I install the plugin I’m prompted to either upgrade my catalog or disable the plugin. I hadn’t expected a catalog upgrade to be required. What extra metadata does the facebook plugin add?
“Upgrade” is an unfortunate word choice by Adobe, I think.. it’s just asking whether the plugin can add per-image data to your catalog. The plugin keeps track of whether an image has been uploaded to support the “reupload” and “upload only if not already uploaded” features. —Jeffrey
I love your plugin have no problem paying for it but dont go touting it as “donation” ware when its painfully obvious that it contains a timebomb activation feature. People should NOT be forced to donate in any way so if you want people to contribute then either make it a donation optional “aka donationware” or make it “trialware”
Thank you for finally posting a civil version of your anonymous opinion. I deleted the dozen other versions you spammed me with.
The “timebomb” is “painfully obvious” because I tell the user about it when they download the plugin, when they activate the plugin, and every time they use the plugin. The point is to make it obvious so that no one is surprised. So I’m not surprised that you figured it out.
Any donation a user does or doesn’t wish to give is wholly optional. Those not wishing to donate don’t. It costs 1 cent to register, something that’s very clear up front, something that some people have done, and something that you are free to avail yourself of. That’s the only cost required to defuse the “timebomb”. If that cost is more onerous a burden than you wish to bare, then simply choose to not use the plugin at all, or to use it with the timebomb-restrictions in place. As always, you are free to write your own plugin (and to let others use on whatever terms you decide). —Jeffrey
Your plugin should be advertised as “trialware” to which you have full access to the features for a given amount of time (in this case 6 weeks) before deciding if its worth it for you the user to pay for a serial number. Those wishing to pay the registration fee of $.01 for PayPal really arent donating at all,
and is at its basic level no different then offering the plugin as you do now for free minus the serial number. The donationware model that you’ve adopted is not optional in any sense of the word since you’re forcing people to donate or face having a crippled plugin.
Registration is required. Donation is optional. I’m not sure why you fail to grasp that, but in any case, please feel free to avail yourself of your right to not use it if the “terms” don’t appeal to you. (“Terms”… terms of use… terms of description.. that’s a pun, get it?) —Jeffrey
Jeffrey, I think you missed my last comment. Could you add a function in so we can key in “Location”?
Thanks!
I did miss it, sorry. I just took a look in Facebook’s docs of its minimal photo API, and didn’t see anything about location. Could you point me at an example of what you’re referring to? —Jeffrey
Jeffrey, the application is called FB-Uploader http://code.google.com/p/fb-photo-uploader/
If you look at the first screenshot that is on the site, you can see the text field Name, Description and Location. That’s what I’m looking for, and hopefully it’s a jiffy code for you to implement in the upcoming version of the plugin (:
Thanks!
Doh, okay, I missed that you were talking about albums and not photos, sorry. Just pushed it in version .68. —Jeffrey
Hi Jeffrey, awesome plugin! I just used it for the first time and it was pure joy. I do have one suggestion, however. The modal dialog that shows the available metadata tokens is taller than my 1024×768 screen thus making it impossible for me to see, or click on, any buttons that may be at the bottom. The only decoration I noticed was a title bar that did not have the close/maximize/minimize widgets, so I couldn’t even use those to resize or close the window. I ended up hitting enter and hoping it wouldn’t do something I did not want to do
Everything seemed to work quite well other than that one little glitch. So my suggestion is to keep all modal windows smaller than 1024×768 for those of us still using small laptops. Actually, I would suggest keeping the vertical dimension smaller than about 700px so Mac users don’t have the button(s) covered up by the Dock.
Good points… I’ll take a look. I’ve figured out how to do a scrollable list, so I’ll see whether that’s a better UI…. —Jeffrey
Hey Jeffrey, I noticed that your plugin is compiled, at least to some extent, and I was curious as to how you did that. I noticed there was a comment about looking in the manual, but I must be blind because I couldn’t find it.
I’ve tried compiling my plugin and the hello world plugin to no avail. I tried using Lua 5.0 and 5.1 with the same results:
Info.lua: bad header in pre-compiled chunk.
I assume I’m doing something wrong. Can you point me in the direction of some detailed information on compiling these plugins? I can’t seem to find it on googles.
luac -o out/Info.lua Info.lua with Lua 5.1 should do it. I’ve never seen the “bad header….” error. —Jeffrey
When I post a gallery on facebook, ALL the images show up on the wall in posts (1-3 at a time). That’s pretty embarrassing! What’s wrong there?
I’m afraid that I don’t speak Facebook, so I don’t understand your concern…. could you translate to English? —Jeffrey
What I really wanted to do was include a link to the url to the image if it was uploaded to flickr. That is, facebook’s resolution really blows and I wanted to say “view on flickr” on the bottom of all my facebook uploads. I know you have a {OnlineID} for the flickr plugin, but is there a way to grab this for the facebook plugin. Thank you
That’s a great idea… I added it in version 75. —Jeffrey
@Thomas Geist,
I am having the same problem as well, and I believe it is Facebook’s fault. However, if you refresh your news feed (homepage) you will only see one published story. Other people only view it as once too, so no problem there.
Just wondering if the recently updated Facebook Pages api will enable export to Pages using the plugin (which is fantastic, btw)…
Looking at the FB API I don’t see anything new that might allow photo uploads to FB Pages. Could you email or post a link? —Jeffrey
I’m using Vista, Lightroom 2, and Facebook uploader 20090422.72. Every time I export jpg photos (at 100% quality, low screen sharpening and 604 pixels wide) they come out really grainy. This doesn’t happen to me with your Flickr plugin, just facebook. What am I doing wrong?
Hmm, indeed, sounds odd. Could you upload one photo, then send me the log via the “send to Jeffrey” button in the Plugin Manager. Include in the note you can type there the URL for the image at Facebook, so that I can see the quality for myself,and compare with the export parameters in the log. Thanks. —Jeffrey
Everytime I try to download the update, the two zips (http://regex.info/LightroomPlugins2/releases/facebook-20090429.74.zip and http://regex.info/LightroomPlugins2/releases/facebook.zip) stall out at 326k. I’ve tried even using curl -O to see if I could grab it and no luck. I really hope it’s me and not your server.
I don’t think it’s my server…. I’ve got no other complaints about download problems. Has anything changed with your network connection lately that might have caused this? —Jeffrey
I bought your export plugin for facebook (LR 2) yet it does not want to work. I can’t get it to authenticate…
What am I to do? Any suggestions… I am on a mac, leopard, iMac intel, latest OS…
Send me a note (via the “Send log to Jeffrey” button in the upper right of the Plugin manager, if possible, or if not, by email, with all the details about the problem. By the way, to correct your verbiage, I don’t sell anything, so the word “bought” is not appropriate. You registered, and on top of that, kindly sent a gift, for which I thank you(!) —Jeffrey
Hi Jeffrey, hailing from New York City =)
Great work on the plugins!
I think I found a bug in the Facebook exporter.
environment:
Execution/debug log for Jeffrey’s facebook plugin for Lightroom, version 20090521.81
Lightroom version 2.3.0 build 539407 for Macintosh (Locale: en).
bug:
I enabled the advance user settings, restarted LR. The advanced checkbox is now checked. Changing the size and quality settings seem to have no effect.
test:
Export a file with dimensions 5616 x 3744. Change quality to 85, resize to fit long edge to 600, no enlarge. The log says quality is at 0.75 (I think this is the default) and max dimensions 604×604. The uploaded file has long edge 604.
If this is really a bug it would be great if you could fix it. The work around is rather tedious: export to file, then upload the file to FB. Reason I want to change the jpg quality is there is a noticeable difference on some photos when uploading to FB if the compression is too high.
Also just occurred to me, FB may or may not re-compress the files upon upload if it falls outside some bounds (photo dimension certainly, but maybe filesize as well). Would you be able to add an option to save a copy of the file the plugin uploads somewhere so I can see if FB is indeed recompressing what the plugin is uploading?
Thanks for your time,
mark
FB does recompress the file, so there’s not much you can do. Set the Export Location (2nd section from the top) to something other than a temporary location, and the LR-produced files will be left for your inspection. —Jeffrey
Jeffrey (wow you reply quick!),
I tried exporting the file with the temp file this time with quality=10. The temp file still has dimensions 604 x 403 even with long edge max set to 600, and the file is about 44k and visibly of decent quality.
I tried the same settings with the Flickr exporter for comparison and it produces the expected visibly crappy file from the low quality setting, about 16k, and resized to 600 x 400.
Any idea what’s going on?
mark.
I’ll have to take a look, but it might not be for a few days…. —Jeffrey
Hi Jeffrey,
Hello from San Diego! I was using the facebook exporter (20090521.81) for the last week without a problem since I installed Lightroom 2 (now on 2.3). I just upgraded to 20090602.82 today and now the exporter no longer functions normally. When I click on export, I get an error message typically in the first photo or two as it renders and sends it.
The message states: Error response from Facebook: Error uploading image: An uknown error occurred
In this specific case, it aborted the upload before it basically even got 1 through. Other times, it has put through anywhere from 1-12 photos (more often 0-2 than anything higher).
Any thoughts? Thanks!
Kent
I think the upgrade is coincidental… a lot of people are getting the same error intermittently, including me. Haven’t heard back from FB yet. —Jeffrey
Hi, Jeffrey. Running 20090602.82 with Lightroom 2.3 on Windows XP SP3, afraid I’m getting endless “Error response from Facebook: Error uploading image: An unknown error occurred” also. Just wanted to make sure you know this is common.
Yes, believe me, I know…. I’ve been getting mail on it nonstop for a few days. The plugin is just reporting the error at FB… nothing I can do. I’ve reported it to FB but still no result. If everyone reports it, perhaps they’ll look into it. —Jeffrey
Plugin Facebook-20090610.83. Lightroom 2.3, Windows XPSP3
Jeffrey. I know you say the error that happens with this plugin is caused by Facebook and we should contact them, but when one tries that one just goes through a set of form questions that don’t include Jeffrey’s plug-in. I had the .81 version which worked just fine. My problem is that I had eight photos to upload. I would click export and it would upload one and then error, click export again, it uploads one and then errors, etc. The error says it’s an unknown error so how do I report it to Facebook. Is there some way to download the .81 version again (I assume that .83 overwrote .81 on my computer). ?
My suggestion to contact Facebook is more a reflection of the fact that one shouldn’t contact me because I can’t do anything about it, and not so much a reflection that I think contacting Facebook will actually prove fruitful. /-: .81 is still sitting on my server here, so you’re welcome to give it a try, but I think you’ll find the timing of the error and the upgrade to be coincidental (which, let me tell ou, is really unfortunate for my mailbox and productivity). —Jeffrey
I absolutely love this plug-in. Do you think you will ever add a feature for uploading groups of photos to fan pages?
Facebook’s API – for reasons I don’t understand – allows only uploads to personal pages. I’ll update the plugin the moment they update their API. —Jeffrey
The problem may be fixed. I uploaded eight images without a hitch.
Terry
Indeed, I just tried a big batch and it worked. Let’s cross our fingers…. —Jeffrey
Concur that the Facebook end of things may have gotten fixed: I had no trouble uploading last night. Tried a 1-photo, 8-photo and 12-photo batch and succeeded.
Then I switched to your fabulous Flickr plugin and uploaded 500 to Flickr. Unfortunately, M$oft decided to “auto update” my computer in the middle. Argh! There’s *another* problem you can’t solve (nor should you!
.
-J
Hi Jeffrey, as always I enjoy all of your plugins. They have made life easy when working with Lightroom and my favorite sights.
Not sure if this has ever been requested, or if it has and you’ve already answered — so here goes: Can you implement the image resize function for both the flickr and facebook export plugins? As it is now, I’m exporting photos resized to certain dimensions via files on disk, adding them to the catalog, and then uploading to Facebook and/or Flickr.
It would be a super benefit to do that in one fell swoop. Thanks in advance for your comment!
I’m not quite sure I understand… Lightroom’s standard image-size section of the Export Dialog remains (see the “Image Sizing” section, 5th from the top). As for the Facebook export dialog, the image-size section is removed by default because the plugin automatically sets the size to 604 pixels on the long edge. However, if you really want control of the size for some reason, you can restore the size section vai the checkbox in the “Facebook: Tools” section. —Jeffrey
Feature request..? New plugin request?
I would like to be able to export to facebook and flickr at the sametime, and post flickr links in the facebook photo description, so that I can take advantage of the exposure facebook gives while having the quality of flickr.
You can’t do both at the same time, but if you do Flickr first, you can include a reference to its url in the comment you use for Facebook, via the FlickrUrl template token. —Jeffrey
I don’t know if it is a facebook issue or the plugin, but when I create a new album either via facebook or the plugin, it does not show up in the list. I checked the logs, the returned data from facebook does not list the new album. I tried adding photos other ways and it still works but the album still doesn’t show up. I have 18 albums, the 19th and 20th don’t show up.
Bug at Facebook —Jeffrey
Hi Jeffrey – thanks for these plugins, they are making life much easier to get things shared with family for me!
I see from an older “release note” comment that you have added some plugin metadata fields in the past (i.e. “Added a couple of new custom metadata fields, “Facebook Upload Date”, and “Upload Time”. …”). I wonder if I can suggest another one, “Facebook Album,” which could also be used in a library filter. It would be nice to be able to “replicate” certain albums at will in Lightroom and right now I’m trying to remember to manually set a keyword or a color or something to accomplish this – if the plugin could do it automatically that would be awesome and my apologies if it’s something a user can easily turn on or add – I did a little searching before posting, but not an awful lot.
- Brent in Cary, NC, US
(ps – I own your regexp book too, long before LR was around)
Hi Jeffrey
You have written an awsome plugin dude. Having to export to JPG and then use the FB uploader was soooo tedious… your plug in is now saving me loads and probably plenty of others a lot of time. The same goes for the flickr plug in.
I’d like to know if there is any easy way I can use LR2’s filter feature in the library to filter out photos I’ve already posted into facebook.
Keep up the great work
Cheers
Matthew
In the filter, select Metadata and then Uploaded to Facebook. —Jeffrey
ahhh found out what I was doing wrong… might sound silly to you, but I didn’t know how to add columns in the filters.. I’m a LR n00b and have only been using it a couple of months.
Just trying to organise my catalogue to export before reformating to windows 7
I’ve added it now. many thanks anyway dude and keep up the good work
also love the photography by the way.
Thanks
Matthew
My system default browser is Internet Explorer (I doublechecked) – but when I go to authenticate on Facebook during an export – it opens Firefox. I keep a different user logged on in the Firefox browser than the one I upload photos to. Where is this specified and is it alterable? I didn’t even have Firefox open on my system when I tried it – I had IE open – but it opened facebook in a Firefox window for authentication. Thanks for a great plugin!
It matters what your browser is logged in to only when authenticating (which you generally need do only once… the plugin should remember from then on). As for which browser Lightroom opens, I really think it’s the system default browser, so if it’s opening Firefox, I’d guess you’re mistaken that IE is your system browser. Maybe there are multiple ways browsers try to make themselves the default? I don’t know the details here, so I may very well be wrong. Could you try reinstalling IE anyway, just to be double extra sure? —Jeffrey
Howdy! Love your LR plugins. They’re one of the things that make LR worth using over competing programs. Any chance of a Myspace uploader?
Just as a note on quality. I’ve noticed that by setting the jpeg compression to 100% and leaving the resize at 604 really helps while still cutting down upload time. I assume that facebook blindly recompresses everything, so the higher quality really helps alot. At the default 75 setting, it really hurt to look at the photos.
Jeffrey,
Just had a thought when I was uploading some photos to Facebook today. Could we have an option (unless I’m being stupid and missing it and it’s already there?) to upload to a Facebook album with the same name as the folder name in Lightroom (or I suppose more generically if possible – I think it’s the Zenfolio plugin that I do this for already?).
Cheers,
David
It’s already there. Just like the Zenfolio plugin, see “add/edit auto destinations” link below the list of albums. —Jeffrey
hey Jeffrey.. using your lightroom-export to facebook for about 2-3 months now and just yesterday I donated. I just wanted to share one small detail that has fallen in my attention and somebody might have mentioned before.
When using the script.. I set the img quality to 100 and the ppi to 300.. After when I change the export method in Lightroom, to hard disc… okey. the setting is 100% and everything fine. When I want to export to facebook again.. the image quality is back to 75 and the ppi is set to 72.. is there any somehow setting to set it costantly the same.. even if I change the method in Lightroom?
Thanks man and good luck from Greece, Crete
Mike
PS. I had posted this comment in an other page. Now I saw that I had to post it here
I did see the other comment but neglected, sorry, to mention that it’s now on my list to check when I get back from vacation. —Jeffrey
@Mike
It makes sense to have different values of image quality for exporting to different places. In the first place, the ppi number is really irrelevant, since you usually define a maximum pixel size, but not a size in inches, so ppi doesn’t affect anything. As far as the quality level is concerned, exporting to your disk, you definitely want the highest quality, but exporting to Facebook, doesn’t require it and is best if your quality is somewhat lower to reduce the size of the file and to reduce the possibility of theft. I think that the parameters you mention are appropriate for the tasks you mention.
Hi Jeffrey,
First of all thanks for all the time you’ve spent with this to make our lives easier.
I’m having trouble exporting the metadata text to Facebook. My template is something like:
{Title:UC} – {Caption} – {City | Location | Province | Country} {YYYY}
I would like to change the dashes (-) for line breaks but I cannot find the way. I’ve used and it appears in the caption field at facebook like text: “TITLE Holidays with my friends MEXICO 2009″.
If I edit it directly in Facebook it let me add line breaks with a return key tap.
Thanks,
jmhita
I’ve just pushed .90, in which you can now use <br> to indicate line breaks. —Jeffrey
Writing from the greater Kansas City area. First off, thanks for a great plug-in. I will be directing a Lightroom workshop next spring at our regional Heart of America PPA photography conference. Hopefully I’ll get a few more customers for you there! If there’s anything you’d like me to show, know, promote, etc. at the workshop let me know! ( I plan on showing the facebook plugin, assuming facebook isn’t totally old-hat by then;-)
hoappa_dot_com if you’re interested.
Hi Jeff,
Thanks so much for creating a brilliant program. I’ve noticed that the photo quality of pictures uploaded to facebook using this Lightroom plugin is not as clear as those directly uploaded from facebook. Have you noticed this or tested it out?
Thanks so much for your reply.
Nina
I’ve heard no other complaints…. are you sure your export settings are proper? You can set the export location to be a specific folder (as opposed to a temporary folder) and the image files will be left behind for you to inspect after the upload…. you can then see whether the image is bad to begin with, or whether Facebook did something to it during the upload. If need be, feel free to send a plugin log (via the “Send to Jeffrey” button in the plugin manager) along with an example URL. —Jeffrey
Jeffrey,
I would agree with Nina. Pictures that are uploaded are someone being compressed by Facebook, it’s horrible. I put a {FlickrUrl} in my caption so that people can see a better quality one. I am quite certain this is a Facebook thing.
OTOH, one of my developer friend suggest that Facebook have API to upload to Pages now. You might want to check them out. This will really help a lot for me to update my Fan Page.
http://wiki.developers.facebook.com/index.php/Stream.publish
- Specify target_id with [page_id]
Check for permission (need to request extended permission)
http://wiki.developers.facebook.com/index.php/Users.hasAppPermission
- return exception if no permission
Apologies to you, Jeff. I figured out how to adjust the image quality so now the facebook photos are great. It takes a lot longer to export, but it’s worth it. Again, thanks for the awesome program. What a time saver!
Nina
Is there any way to use this plugin to publish pictures directly to a ‘Page’ on Facebook. I’m not talking about your own personal wall, but a fan page that I administer.
My FB account has the personal side…only allow real friends and family, but also have a public fan page for those that follow our band….and would like to have an easier way to push pics straight to the fan page.
Facebook doesn’t allow it. —Jeffrey
First off this plugin is a lifesaver. I’ve donated a while ago and never looked back
Maybe someone out there can shed some light on this, but I notice that my photos are always darker after exporting to facebook. Has anyone else noticed this and/or know a solution? Nina perhaphs?
Thanks,
Phil
I’m pretty sure that they strip the color profile, so even if you use a color-aware browser, it doesn’t matter…. results become sort of random, which in your case apparently means a bit darker. —Jeffrey
Commenting from Clarksburg, WV
I have installed in Both LR2 & LR3 beta, I noticed there is two way communication in Version 3, Does this also work in Version 2 & how do I use it.
No, the two-way stuff (“Publish”) is new in LR3. It doesn’t work very well yet in the beta…. it’s a beta…. and my plugins have only been updated in places. More support will come when the real LR3 comes out. —Jeffrey
Hi Jeffrey,
i am using your picasa plugin for a while and I am quite happy with this tool. Now I tried you facebook plugin but it is creating an album on my FB with the correct number of pictures. But they are all blank. So no picutre is uploaded.
Any idea?
Kind regards
Stefan
Seems to be a problem with Facebook. Some pictures are displayed some not
Strange
Will you be updating the plugin to take advantage of the new capabilities of Lightroom 3? In particular, I am interested in the way that LR3 syncs comments on the flickr upload of a photo back to the original. That would be great with your facebook plugin.
Yes, they’re slowly getting new stuff for the eventual real LR3 (less for the 3 beta). Facebook will likely little new, though, because Facebook’s photo API is so very limited. It doesn’t even tell the plugin the URL of the photo at FB, so I doubt comments and ratings will make it.—Jeffrey
I think Facebook has API for pages now. Tweetdeck can update Pages status, and I think I saw some API posted on Facebook about photo posting.
I have commented here, maybe you missed it.
http://regex.info/blog/lightroom-goodies/facebook#comment-36784
I did see it and checked it out at the time, and as best I can tell it merely allows you to post a reference to an image that already exists elsewhere on the web. I didn’t see any way to actually send an image. —Jeffrey
Hi Jeffrey,
I am a student who travels between USA and Indonesia on (somewhat regular basis)
Over the past hour, I have been doing some personal experiment on facebook (lousy) photo quality.
Here are some of my notable findings so far, all photos are uploaded using your plugin version 20091118.97 (which so far, over the past few months, have done many awesome wonder for me)…
http://bit.ly/4HTdC1 – photo I have uploaded few weeks back from Pittsburgh, USA
http://bit.ly/7agzmq – photo I have uploaded an hour ago from Jakarta, Indonesia
http://bit.ly/4DExBS – photo I have uploaded few minutes ago from Jakarta, Indonesia… in which I have specifically set the plugin to upload the jpeg with maximum quality
Based on the above three photos, you must have noticed the marked decline in the quality which I suspect is mostly caused by difference in uploading speed (uploading speed from Indonesia is way much slower than in USA for obvious reason).
Now I am wondering if your plugin actually adjust the quality based on uploading speed.
If not… I am afraid I have just found out another facebook hidden algorithm to reduce image quality.
Hope to hear from you soon
- Aditya
The difference between the 2nd and the others looks to be a color-space issue. The plugin should be forcing sRGB on all Facebook uploads. Set the “Export Location” (in the LR export dialog) to a specific folder, then look at the JPG left behind and compare that with what you see on FB. You can inspect the color space on your local copy of the image with something like my online Exif viewer. FB strips and ignores any color-space info, which means sRGB is the best you can do, but if the plugin is somehow sending something else, that’s a bug I need to address…. —Jeffrey
Hi Jeffrey
thank you for the quick reply
here are my findings from another round of upload
#1 – http://img32.imageshack.us/img32/5291/img6981u.jpg – what LR2 default export to folder has produced (around 311kb) – I use this as main control
Embedded color profile: “sRGB”
http://regex.info/exif.cgi?url=http://img32.imageshack.us/img32/5291/img6981u.jpg
#2 – http://img189.imageshack.us/img189/7456/img69812.jpg – what the LR2-FB plugin has produced in my hard disk (around 122kb)
Embedded color profile: “sRGB”
http://regex.info/exif.cgi?dummy=on&url=http://img189.imageshack.us/img189/7456/img69812.jpg+
#3 – http://bit.ly/7F2gry – what picture is shown in facebook from what is uploaded by facebook exporter plugin (around 82kb)
No color profile
http://regex.info/exif.cgi?dummy=on&url=http://bit.ly/7F2gry+
#4 – http://bit.ly/73RWmB – what picture is shown in facebook from pic #2 that I manually upload from facebook web uploader (around 82kb)
No color profile
http://regex.info/exif.cgi?dummy=on&url=http://bit.ly/73RWmB+
it seems based on #4, the problem is on facebook side
what do you think?
Yeah, looks very strange. It’s not only that they’re stripping the color profile, but they’re changing the color data. Very strange. —Jeffrey
Hi,
I’m loving your facebook plug-in for Lightroom (20091216.103), but I’m peeved with facebook stripping the color from my photos. The plug-in outputs correctly, but I believe facebook removes the sRGB color profile on the image when uploading it. My suggestion is to add an option to boost saturation prior to uploading to offset the desaturation. Keep up the great work!
Boosting saturation might be a “fix” for a removed profile on your personal setup, but each person’s computer, graphics card, monitor, and monitor settings are unique, so doing what seems to help on your system may just make it worse for others. Anyway, FB is doing worse than stripping profiles… they’re actually changing the color data. Nothing you can do here but roll a dice…. or contact FB to ask what’s up. —Jeffrey
Hi, I just realized I stupidly wrote all of my notes regarding some degree of success getting some decent colors back in FB photos using the Jeffrey’s latest version of plugin on the wrong page! Here’s a reprint for this comment thread:
Okay, Jeffrey’s right — rolling back to older versions of the plugin did not resolve the latest color problem (I tried 20090918 and 20091023 before returning to 20091216). After that failed miserably, I decided to try uploading files to Facebook with 1208 pixels as the long edge, which essentially forces Facebook to do some kind of compression. Ironically, color production seems a lot better!
This Facebook test album shows some comparisons I did tonight:
* The first photo in each set was uploaded with the LRtoFB plugin at 604 pixels long and 100% jpg quality. (These look dull in my opinion.)
* The second in each set was uploaded with the LRtoFB plugin at 1208 pixels long and 100% jpg quality. (These look much better, especially in the reds, and seem to match my original photos much better.)
Not sure what to definitely conclude, except it looks like that I might be uploading images at 1208 pixels for now, while periodically testing to see if 604 pixel uploads are restored to their former glory.
Hello,
Love the plugins Jeff, keep up the good work
I have updated to Facebook plugin 20091216.103 and noticed that the pictures are no longer resized. I usually resize them to 600 x 400. However the batch I have just uploaded (the 1st since the update) were sent full size.
I don’t seem to find any dialogue to resize them.
Can you shed any light on it please.
Martin
That’s very surprising that they’re not getting resized… could you upload one then send the plugin log (via the “Send to Jeffrey” button in the plugin manager)? —Jeffrey
hello and merry holidays,
as I saw before, Kenneth has mentioned a problem when uploading on Facebook with 604x and 100% quality.. I noticed the same a few days now once I upload one picture per day, daily.
I not only noticed the problem in the quality but also the colors got lighter.
I just tried the 1208x thing that Kenneth said and the colors and quality are back.
I’m not sure what the problem is but there is something wrong.
I noticed the problem with an other way too. By extracting 604x in my hard disc and uploading it manual on the Facebook album myself.
Please check this problem and notify us
thank you.
Seems to be a problem at FB. I’ve got a note in to them, and am awaiting a response. —Jeffrey
I am experiencing a similar colorshift to some of the above listed issues when I upload my images to Facebook. I have tried several different attempts at maintaining the quality of my uploaded photos, but none have worked. I have been using the plugin for months with no major issues, although a minor quality loss, but since I upgraded the plugin, the quality of the Facebook uploaded image is awful. Here is a comparison of the same image loaded to FB as well as Flickr. http://www.flickr.com/photos/lyleuga/4201846883/ . This was a screengrab showing the color/quality issues.
I am running Lightroom 2 version 2.3 . I have Vista Home Premium SP1. The plugin version is 20091216.103 . I did not have this problem before, but I believe it has come up after the most recent upgrade to the plugin.
I am from Atlanta, GA.
The issue hasn’t changed since I noted above that Facebook is having color issues with their photo processing. Each user reporting “me too” to me doesn’t help. Tell Facebook… if enough people report it, maybe they’ll fix it. I’ve reported it, but have yet to even hear back. —Jeffrey
Hi Jeffrey, sorry for all of us troublemakers creating a stir this December for an issue that seems to be a reflection of some code changes in Facebook rather than your great plugin. I do confirm again that a rollback to previous “working” versions of your plugin don’t resolve the issue, and am more convinced that it is something that Facebook is doing. Also, I confirm that uploading to FB at 1208px long through the plugin seems to help retain a lot of the desired color quality.
I suspect a lot of us who are affected don’t know what to say to Facebook nor expect any positive response, since the most obvious response we might expect from FB to our problem is, “Well, stop using the plugin then.” However, I agree that we, the users of this plugin, need to stop putting the blame on the latest version of Jeffrey’s plugin, which seems to have nothing to do with the issue whatsoever.
Maybe what would be helpful to add to this thread are some specific details to consider including in an email to Facebook about what exactly is wrong. For example, are people noticing the same poor color output when uploading directly to Facebook vs. via the plugin? Do different resolutions of uploaded photos seem to affect the outcome?
From Jeffrey, I’d love to get any insights as to how the plugin used to succeed in uploading photos that FB wouldn’t mess with further. (Or at least I hope those details have already been shared with FB.) Presumably, that procedure hasn’t changed much on the plugin side of things, but FB is now converting/re-compressing the image again after upload and before display. The more this community can aid FB to identify the problem, the sooner the issue can be resolved for everyone so we can quit complaining and get back to taking photos and using Jeffrey’s plugin!
The plugin didn’t change how it uploads; Facebook apparently changed their image-processing pipeline, at least for the 3rd-party API that the plugin must use. Tell them “images uploaded with a 3rd-party app used to work, but now have dorked colors. Nothing has changed with the 3rd party app, and others are reporting the same problem. It seems your image-processing pipeline is changing the color data.” —Jeffrey
@Kenneth and @Jeffrey
I just figured out that uploading manually a picture that is exported from Lightroom at 604x @100% has the same results as uploading it through the plug-in.
When uploading the 1600x @100% version manually I seem to get the colors right without a problem.
+ since yesterday I’m getting this error message way to often that says that Facebook has an error and not the plug-in.
That’s interesting… I’ll try some tests tomorrow to see whether having the plugin send 605px images (1px beyond their max) helps. Clearly they have some bugs in their new image pipeline, but this might be a good workaround, at least for the color things. Still can’t help with the FB internal errors, though. —Jeffrey
Experiencing the same issues with washed out colors, but wanted to add the link to the “bug report” for photo issues on Facebook… http://www.facebook.com/help/contact.php?show_form=photos_bug
Thanks!
John
Seattle, WA
Hi there,
I have a problem with Facebook and uploaded images that a small change to your plugin might help. Problem is facebook’s not yours!
Facebook doesn’t process colorspace information correctly – images tagged with sRGB (from your plugin/LR2) get horribly washed out by Facebook. If you strip out the colorspace information all is well.
This image was uploaded with the colorspace “Profilename” blank
http://www.facebook.com/photo.php?pid=4445503&l=6ecec37a0c&id=678239808
This one with “sRGB IEC61966-2.1″ in the profilename:
http://www.facebook.com/photo.php?pid=4445511&l=ae2ca35af6&id=678239808
The blank profilename image was created in Photoshop CS4 with the colorspace checkbox unchecked, if your plugin could mimic this behavior I believe the facebook issue could be worked around.
Cheers
Adrian
I am on using:
OSX: 10.6.2
Lightroom: 2.6
Plugin: facebook-20091216.103.zip
If it’s as simple as that, you might try stripping the color profile on export from LR, with my Metadata Wrangler plugin. I sure hope they fix this soon, though. —Jeffrey
I can verify that uploading an image by stripping the color profile using Jeffrey’s Metadata Wrangler “fixes” the color issue on facebook.
I can also verify that setting the image to 1208px “fixes” the color issue. I’ve provided a screenshot of my examples.
Here is the image: Facebook Color Test
First image – uploaded at 1208px (100% quality) and removed all metadata (including color profile)
Second image – uploaded at 1208px (100% quality) and color profile intact
Third image – uploaded at 604px (100% quality) and color profile intact
Fourth image – uploaded at 604px (100% quality) and removed all metadata (including color profile)
I hope this helps in any way.
Thanks Jeffrey and Paul! Metadata-Wrangler removes the profile name and the images look fine on Facebook!
Great work!
Adrian
I’m using pretty much the latest version of the plugin and love it.
Question: I’d like to pre-populate the caption field for each image I upload with copyright and website. What’s the corresponding field in LR2?
Well, it depends on where you stuffed the data. Check out the “Token Examples” button in the caption-preset dialog… it’ll show the fields/values for the currently selected photo. —Jeffrey
Jeff,
Just installed the Lightroom Plugin for Facebook. I am using a MAC OS 10.5. I was only able to upload 5-7 photos at a time before receiving an error message. This occurred 8-10 times during the upload process. Each time I encountered a Nil Fieild error. This is my first time using a plugin for Lightroom and I am not sure if there was an error on my end. You directions seemed straight forward and I followed them pretty easily. Any thoughts on the upload problem.
Thanks
Bill
“nil field” sounds like an error in the plugin. After you get it the first time, please send a plugin log (via the “send to Jeffrey” button in the plugin manager). Thanks. —Jeffrey
Echoing what others have seen, I found the simplest fix for the color issue that I’ve found is to simply set the export plugin to something other than 604; there was no need to use the metadata wrangler in addition to that (I think I randomly chose 1200). Thanks for a great tool and hopefully facebook will someday fix things.
Hi Jeffrey,
First of all, thanks a lot for this plugin for Facebook. I’m really loving it.
i do have one question though and that is with the jpg compression. When I export to disk, the pictures are nice and sharp and I can set the jpeg quality, but this is not possible when I export to Facebook. The pictures in the facebook gallery seem to be using a pretty high compression. is this in the plugin or it’s just a setting Facebook uses for images sent to the albums there?
Kind Regards
Teddy
Facebook uses heavy compression. FB photos are just for sharing snapshots…. it’s not a place to highlight great work. —Jeffrey
I’m still seeing things slightly different from others. I’ve tried to export from Lightroom at 604, 800, and 1200 pixels, but all still come out desaturated. Same image saved from Photoshop at 600, 604, and 800 pixels and in Adobe RGB, sRGB, and with no profile all look correct. Here is an album of my tests: http://www.facebook.com/album.php?aid=135793&id=593881723&l=97961a56b1
Same file exported from LR to disk at 800 and 604 pixels and then uploaded via Facebook both look OK. So, for me, it is only the images exported from LR directly to FB that desaturate.
version: 20091230.107
Nice Plugin. Would you add a feature to enable choosing the album within facebook to export to as the public facebook plugin for iPhoto does?
Thanks
Is the album list in the “Facebook: Destination” section of the export dialog somehow not sufficient? —Jeffrey
I think that the color problem has been solved. I found out accidentaly when I uploaded on Facebook without the meta-data plug-in at 604x and 100% quality.
Please test and let us know.
Mike,
Hi Jeffrey…a new user from Colorado here…thanks for all your work on these plugins!
We are trying the Lightroom/Facebook plugin, and we are unable to authenticate. It just keeps saying “CannotConnectToHost”, counting down from 10, and repeating, This is 20091230-107 we’re using
Ive double-checked the defult browser (I’ve tried Safari and Forefox), and it just seems there’s no communication going on between the plugin and the browsers
Lightroom is distinct from whatever browser you may or may not have, except that once LR gets enough info from FB, it’ll launch your system browser to view a specific URL. You’re not getting to that point, so the problem is that LR can’t connect to the web. Since your browser apparently can, it’s likely something in your system is preventing it. Check your security settings and apps. Also, do you use a proxy? I don’t think LR can be configured with a proxy, but I’m not sure how that all works. —Jeffrey
Thanks Jeffrey…some overzealous security settings were indeed to blame. My wife can now upload to Facebook, and domestic tranquility returns! I’m assuming in the next 30 days she’ll like it enough that a donation will be on the way!
Jeffrey,
Real quick, I just registered the Facebook plug-in and I was wondering if there is a possibility we will be able to connect to our business pages through the plug-in.
Thank you.
No, sorry, for some reason, Facebook does not allow it. —Jeffrey
Hi
I rly love your plugins and have donatet to a couple of them. I have a feature request. When i export to Facebook and chose to tweet about it can you make the link a bitly link or other url shortener service. I like bit.ly because of the stats I get.
URLs are shorted (with bit.ly) automatically if needed. I figure that users would prefer to see the actual url if the message is short enough that shortening is not required. —Jeffrey
Please, I’m begging you. Please release an update to the Facebook plugin that makes the “unknown error” dialog not modal! http://en.wikipedia.org/wiki/Modal_dialog when Facebook is acting up, it renders Lightroom useless. I just registered this plugin tonight, and will have to stop using it if turns my machine into a uni-tasker. Okay, that’s a little dramatic. I will have to resolve to only use your plugin when I’m completely done with Lightroom. That will have a terrible impact on my workflow.
LR doesn’t offer a plugin anything but modal dialogs, so I’d have to just quietly keep retrying. Would that be useful? —Jeffrey
Hey! I’m really interested in the Facebook exporter and the GPS data import plugins you have developed… but I cannot seem to find the download links on the pages. Am I going blind?
Thanks!
Yeah, sorry, I think you’re going blind. Try using your browser’s “search on this page” function for “download”, and you’ll find it in the upper-right corner of this page. —Jeffrey
Hi Jeffrey,
I enjoy the convenience of this plug-in, but I don’t use it much because of what I am about to explain below, and I hope you can help with this:
I have a Facebook Fan page specifically for my photography that I created via my regular page. I don’t want to upload images to my regular Facebook page, but to my Fan page. Right now I don’t see a way of doing that with the Facebook export plug-in. It goes automatically to my regular page to authenticate and only gives me the option of working with the albums in that page. Any way of being able to chose which page to which I want to upload?
Thank you for your help.
Unfortunately, no, not until FB allows it. They currently don’t, for reasons no one (outside of FB?) knows. —Jeffrey
Hey, Jeff!
Thanks for this plugin! I’ve been using it for about the last year, and it’s approximately awesome.
That said, the last two weeks have been a bit frustrating because it doesn’t seem to be connecting properly to Facebook. I’m not sure if it’s Facebook being dumb or not, but I’ve tried at different times of different days to no avail.
What happens is that when I export a set of photos, a few of them will upload, and then one photo seems to time out and I receive an error message that says, “Error response from Facebook. Error uploading image: incorrect signature”. Then it aborts.
What’s worse is that the few images that did upload before it aborted have weird artifacts that range from bright bands of green/purple pixels to large chunks of gray pixels.
Is there something I’ve done wrong? Or is this a known issue?
I’m using Lightroom Version 2.06 with plugin version 20100118.108.
Thanks again! You’re incredible.
Facebook has been having all kinds of issues since they changed some of their backend piping a month or so ago, but I’ve not heard of any of these you’ve mentioned. Please turn on enhanced debugging (in the plugin manager) and send a log (via the “Send to Jeffrey” button in the Plugin Manager) the next time you get the signature error… —Jeffrey
Hey, Jeffrey! Thanks for the response.
I tried again this morning, and four times in a row the upload aborted. I actually got four different error messages, in this order: “invalid API key”, the “unknown error”, “invalid signature”, and “session key invalid or no longer valid”. I did send over the log file, though it warned me that it was huge (534kb).
Thanks again for the help!
It’s hard to imagine that the plugin is suddenly going wonky like that, so I’ve got to wonder whether they’re having some major issues these days. I know other apps are also giving the “unknown error” problem. I’ll take a look at the log tomorrow, but I’m inclined to think FB is going through a rough patch. —Jeffrey
Win7 Ultimate , LR 2.6 build 632038
Facebook plugin version 20100118.108
updated to your Jan 18 release yesterday and I cannot shake the dreaded “facebook” error. I know FB changed their rendering starting then to allow for different max size. I also read your description that its on the FB end, but I’ve tried 3 different batches at different times.
Nothing else changed and your Flickr plugin still works fine. Thoughts?
The Flickr plugin still works because it’s not Facebook. Lots of different upload apps are getting this “unknown error” error. Don’t think there’s much I can do. —Jeffrey
Nice tool, I’m pleased overall. Thank you for creating it. But I do have two issues I’d like your reply to.
1. Exporting to Facebook works fine, but simultaneously it also exports a second copy to the original folder. How can I prevent this?
2. After exporting to Facebook, when I return to Disk, resolution and size settings have been rest to what I previously exported. i.e., 400×700 at 72dpi as needed for Facebook, but not correct for my typical exporting. Can your plugin allow LR retain my normal settings when I return to normal export actions?
Using the latest 2.x version of LR, btw.
I may not get back to this blog, so please send any reply to my email address (provided), if you can.
Thanks again!
Steve
For 1, choose “temporary folder” in the “Export Location” section of the Export Dialog. For 2, that’s how LR works by default, so I can’t change it. I did make it so that my plugins remember their state, but unfortunately, I can’t control the LR built-in stuff, or other plugins. The best I can recommend is that you crete an export preset that encapsulates your normal disk export and its settings, and click on it in the export dialog as a starting basis. —Jeffrey
I seem to have to reauthenticate to FB fairly frequently. Either every session or every day, or something like that.
Is that usual?
i
(unable to supply version number currently, but its been this way over all versions I’ve used)
It’s unusual… most people need to authenticate once, and that’s it. This could be a sign of a partially corrupt Lightroom preferences file… not sure. If it happens again, please send me the plugin log (via the “Send to Jeffrey” button in the Plugin Manager) and I’ll see what I can figure out. —Jeffrey
Hello, I have a question regarding the plug-in for Facebook and Lightroom. I have my main personal Facebook page, as well as a page for my Photography. Is there anyway I can upload to my Photography page? I see that I can upload to my personal page, however the ability to upload to my linked Photography page would be MOST beneficial. As that was 99% of why I searched for this plug-in.
Thank you!
I just installed the latest version of the Facebook plug-in, 20100208.110 in LR v. 2.6.
Nothing has changed since the last dozen people asked the same question: Facebook does not allow photo-uploading to Pages. I don’t know why. —Jeffrey
Connections from Malaysia to Facebook is screwed up. It happens every now and then that I have to reupload to Facebook.
The problem is, I am using the Auto-Title destination, and I upload many pictures at one go (all diff titles to diff ‘folders’). Whenever the connection gets wonky, upload fails and I had to reupload again, the plug in creates a new folder (doesn’t check if there’s an existing one) and upload it there instead.
Question, can we have an option for the plugin to check for existing ‘folders’ before creating a new one on Facebook? Cheers!
Yikes, it was supposed to be doing that, sorry. Had a typo. Just pushed v111 that fixes it. —Jeffrey