facebook-20090616.86.zip
· Version History
· Update Log via RSS
· Installation instructions
· More Lightroom Goodies
· All-Plugin Update Log via RSS
· My Photo-Tech Posts
· My Blog
This Export-to-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”. It is provide for free and is fully functional for the first six weeks, after which it becomes limited to processing at most 10 photos at a time until registered. Registration costs 1 cent; any additional donation you'd like to make in encouragement or thanks is up to you. For details, see my blog post titled Lightroom Plugin Development: Now With Added Encouragement.
( Update Log via RSS )| 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='...'&tg;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