Added the {KeywordsAll} template tag.

Added code to allow plugin revalidation after having been locked due to a bad Lightroom serial number.

A few users found some photos to always be "stuck" as Modified photos in a Publish collection. I'm still not 100% what might be going on and can't replicate the issue myself, but this version of the plugin tries some things to hopefully alleviate the problem.

The plugin has long remembered your export settings from Photobucket export session to FLickr export session, overriding Lightroom's desire to always bring your recent export settings from non-Photobucket exports. However, I had neglected to update the list of settings for Lightroom 3, so this is now corrected, and so the plugin now also remembers watermarking settings, file-renaming and photo-stacking, and DNG compatibility.

Added a warning that blocks export when the JPEG quality is set needlessly high, referring users to my Analysis of Lightroom JPEG Export Quality Settings. You can bypass the warning if you like, and hide it forever, of course.

This version can be registered in Lightroom 3. It can run in Lightroom 2 or Lightroom 3; it does not work in the Lr3 betas.

It uses my new registration system when run on Lightroom 3, which avoids some of the silly issues of the old one. Please take care to note the details on the registration page: use of this version (or later) of the plugin in Lightroom 3 requires a new registration code, even if you had registered some older version of the plugin.

Lots and lots of changes under the hood.

Added some options to the Twitter <dest options> special code: add simple as an option to have it become just the name without quotes or other adornment; add short to par down the gallery name to just the leaf name. They can be combined, e.g. <dest short simple>.

Added some stuff to the LUA template token: a version of the standard os table (with date, difftime, getenv, es and time), and the standard Lightroom STK tables LrDate, LrPathUtils, and LrStringUtils). Also added a new functions TBL() (returns an empty table), ne(item) (returns true if the item is not empty), and nb(item) (returns true if the item is not blank; " " is blank but not empty, while "" and nil are both blank and empty).

Removed some LR3-related debugging stuff that's showing up now that LR3b2 is out. All plugin-related things should work in LR3b2 except Publish, which will likely change drasticly between now and when LR3 is actually released.

New when running LR3b2 is a new "Snapshots on Export" section, which is basically a built-in version of this new plugin.

Added new tokens to the templates used in my plugins: IfKeyword and IfExportedKeyword are supported for LR2 and later. For LR3b1 and later the very powerful LUA token, and for LR3b2 and later, a bunch of new localized date/time tokens. See the templates page for details.

Title presets weren't getting saved across LR restarts in some cases (for definitions of "some" meaning "all", sorry).

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.

Wholesale changes that attempt to honor the user's locale settings for numeric display (e.g. Europeans writing 3,14156 for pi). I've probably missed some spots, so let me know if you find some.

Added three new tokens to the templates that my plugins use, CameraName, IfGeoencoded, and Keywords. See the templates page for details.

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:

• Better tweet-size estimates in line with recent processing changes at Twitter.
• Added the ability to control whether to send a Twitter tweet with photo keywords.
• Added <title> and <description> tags to the tweet-text template (they use the title/description from the first image exported).
• Added the ability to geotag tweets with a static location, or with the geoencoded location of the first image. A static location can be specified with a latitude, longitude pair, a geohash, or a url from a mapping service like Google, Yahoo, or Bing. On the encoded side, geodata embedded in the image can be used, or the geodata maintained by my geoencoding-support plugin).
• You can now configure the plugin to shorten URLs via your own bit.ly account, in case you want to track click-throughs yourself.
• You can now specify that you want all URLs shortened. The default remains to shorten them only when required to get under the 140-character limit. You might, for example, want to forcefully shorten them all in conjunction with your own bit.ly account, for click-through tracking.

• The plugin now goes to great lengths to report whether a tweet is accepted by Twitter. In their infinite wisdom, the folks at Twitter suddenly decided to start ignoring long tweets instead of truncating them, but (here's the brilliant part) they still report back to the plugin that the tweet was successful. Sigh.

  Furthermore, they might also ignore (yet report as successful) other kinds of tweets, such as those that are a repeat of a "too recent" tweet. Those crafty folks at Twitter implemented these changes more than three months ago, but in a truly cunning move, they still detail the old behavior in their API documentation, making no mention whatsoever about how their service now actually works.

  Only by doing a bunch of extra work can the plugin detect whether a tweet was accepted or ignored. If ignored, there's no way for the plugin to know why, so at this point it merely reports that the tweet didn't go through.

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 gallery" 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.)

I'm back from a long trip and starting up the plugin machinery again. This push fixes the "failed signature" error that Windows users were getting.... it turns out that there's an insidious bug in Lightroom on Windows that silently dorks certain accesses to Photobucket. Wasted hours and hours and hours on this before I ran a network protocol analyzer and realized that Lightroom was being very naughty. Sigh. Should be fixed now.

One other minor update: the HOME album is now at top in the alphabetic list, even though "H" might fall after other album names. "HOME" is not really the name, but a description, so it makes sense to list it first.