LR/Blog – Version 1.20 adds Blogger support

As promised We’ve been working hard on the next version of LR/Blog. Compared to version 1.00 that we blogged about a few days ago, version 1.20 adds support for hosted Blogger blogs and for creating new posts directly from within Lightroom, thanks to a useful templating sytem.

You can read more in the quick guide.

Please keep your ideas and needs coming…

This entry was posted in LR/Blog and tagged . Bookmark the permalink.

34 Responses to LR/Blog – Version 1.20 adds Blogger support

  1. Hi Tim, I’ve been able to test this now, and it works quite nicely with my blog. Thanks for the nice work! The only thing that I notice is that the token {return} seems to have no effect.

    The Picasa Web stuff allows on-the-fly resizing of the image: if the uploaded image is, say, 1600px on the long side, it can be scaled down automatically with a size parameter in the URL. Inserting /s800/ before the filename in the URL would render it to 800px. I’m using it in my blog to show a version with 640px in the post and then open an 800px sized Lightbox when the reader clicks on the photo. I don’t know if this can be added to the plugin. It would allow me to really automate blogging from within Lightroom. :-)

    • Hi,

      Hmm, the return may confuse people, I’m not sure what to do.

      It should add a real return code, so that you can format the HTML. It doesn’t show up on the web page, for that you need to type in a <p>.

      The size parameter should be easy enough to add. I’ll test it out and if there are no problems I’ll add it as an option to the url token (e.g. {url:800}). Sound ok?

  2. Hi, well, the return confuses me then, sure enough. I thought that a return is . :-) But of course I can add that just as well… d’oh! :-)

    Adding the size to the URL parameter as you described it sounds great. The possible sizes are described in the Picasa Web Album API docs, most likely you already know that but anyway:

    • 1.30 adds this feature.


      • Thanks for the update, Tim.

        I seem to be unable to get the {url:640} feature to work. Instead of the image URL, I get an URL with something like “…”. Am I doing something wrong?

        I can’t add a simple linebreak -br- either, because the consistency check of the HTML says that it has to be closed with a -/br- (I don’t know how to add pointy brackets so that they’re actually visible). Is this a mistake from blogger? :-)

        • Hi Alexander,

          For the url ussue, you didn’t read the help page :)

          The syntax is {url[640]}. If you don’t pick a valid number then it’ll pick the nearest one for your. Bear in mind that you should remove the width and height parameters from the HTML that you’re generating….

          For the second problem Google requires strict XHTML, so a tag without a corresponding closing tag isn’t valid. Instead of ‘<br>’ you should use ‘<br />’

  3. Dave Griffin says:

    Hi. I appear to have installed 1.3. First time I have installed it.
    Exporting fails: Plug-in error log for plug-in at: /Users/daveg/Pictures/Lightroom/Plugins/LR2Blog.lrplugin
    **** Error 1
    This plug-in’s post-processing task did not finish successfully.
    Access to undefined global: INF0
    I enabled the debugging file to the desktop, but it is filled with (perhaps) useless information. Just a long sequence of:<- Removed ->F<- Remo….
    (1.3 megabytes worth)
    Credentials check out ok. Exporting to a WordPress 2.7 blog using XML-RPC. Using the temporary directory option. Fails with just image and with a post. The status bar says “Sending (file)…” and then the error occurs.

    FYI. (I’m a former software guy, so feel free to ask for whatever.. Happy to help.)

  4. Deniss says:

    Hi Tim,
    I updated to 1.30 and now get error every time I try to post to WordPress via “WordPress” type of blog option it works with “Metaweblog” option. The error is: “Access to undefined global: INF0″

    p.s. The plugin is great, wish I had option to somehow chain it with pixelpipe plugin, so that I could export to blog and pixelpipe in one move.


  5. “Access to undefined global: INF0″ has now been fixed….


  6. Hi,

    I’m going to update the plug-in – but I have forgotten how to install it. Where can I find info on how to install/upgrade the plug-in now that I have downloadet it.


  7. Toby says:

    Absolutely love the new plugin. This will make my life so much easier. Just wanted to see if you had a suggestion to get the images centered upon insertion
    to my blog. I tried a couple of different html codes like , and even div align=center.
    I am sure it is simple, but can’t figure it out.

    Thanks again for the plugin.

  8. Susan says:

    HI Timothy,

    I am excited about this plugin, but I haven’t had any success getting it to work. First, I am getting an error message “Internal Plugin Error: Could not contact the version-check server.” I am running WordPress 2.7…and did add the two lines to my .htaccess file.


  9. Amber says:

    hey there, loving your mogrify plugin. For some reason, as i have added LR2/Blog to my plug in manager, it says it’s installed and running, but it doesn’t appear in the bottom left of the export window. Did i miss something? Thanks.

    • Yes, the quick guide ;)

      It’s an export plugin it, so you have to choose it from the menu at the top of the export dialog. Click the two arrows in the top right…


      • Amber says:

        Thank you! I wasn’t looking closely enough, and thought it was mogrify. Can i ask another question? As i export to blogger, it says “(403) Photo limit reached” for Picasa albums. But i check picasa’s page, and i’ve only used 7.6% of my total space. It won’t let me export. Has anyone had this problem before? Thanks for your help! I’m looking forward to the successful process of this feature!

        • elizabeth says:

          Amber, Did you get this fixed? This error just appeared for me too! I don’t know how to fix it!!

          • Amber says:

            I didn’t. I tried it with 2 separate blogs i have, and it worked for one but not the other. I can’t seem to find a reason for it. If anyone finds out how to solve this problem, please let me know! It doesn’t work for my photography blog, which is the whole point of using it for me. Thanks! Amber

          • Amber says:

            I came up with a “hack” for it. Since I could post to my other blog, I just added that blog user as an author and logged in using those credentials. So….if you have the same problem, create another blog and add that second blog as a user for the first and you should be good.

          • Jay Pike says:

            Workaround: I just had this happen to me as well. The issue is simple, once the album you are posting to hits 500 images, you get this error.

            To fix it, manually post an image into a new message, which will create a new Picasa album linked to your blog. You don’t have to post the message (I deleted mine).

            Check your Picasa web albums, you should have a new Blogger album with the one image you uploaded from the manual posting.

            Now, retry the export plugin (you may have to cancel and re-click the ‘Export’ button in order for the plugin to login to Blogger and refresh it’s cache of blog information otherwise you’ll get the same error as it tries to post to the old album with 500 images).

            This worked for me as a workaround. You could also update your subscription to add additional space, but the limit of images per album is only raised to 1000, so eventually you will see the same error again.


  10. misschatter says:

    Hi Tim, love this plugin! It was working great, but then last night started uploading all the photos and when done, popped up an error saying “could not create post” and never switched to my browser. I’m not sure if it’s because I updated to 1.3? I’m pretty sure I successfully posted after that without any problems. I tried 3 times (so now I have 25 photos uploaded into my blog 3 times).

    Does it create a temp post file anywhere that I could just copy and paste into the blog post screen?

    • misschatter says:

      Ok, I enabled debugging and when this happens, I just copy/paste the post data into my blog. I found the debug output file doesn’t create if I export to the blog in back-to-back exports. If I export to the filesystem first, then go back and export to the blog it does. So I have a good workaround going. Although, since updating the plugin in the last month, I haven’t had a failure.

  11. misschatter says:

    The only oddity I noticed was that the filenames in WordPress looked like temp filenames and were not the filenames of my images that were supposed to go across.

  12. I have several errors occuring when I try different ways to upload to wordpress. It says Unable to export: An internal error has occured : Invalid at the top level of the document. This is using the XML export option.

  13. Jon Steele says:

    I have been experimenting with this in blogger. Love the plugin. My only question is if there is a way to include a token or HTML that allows for a link to be created to a high resolution version of the image?

    • Hi,

      You’ll need to write the HTML that’ll link to the high definition version and open it in an appropriate fashion. Blogger uses can refer to a lower definition version using the size parameter of the {url} token (e.g. {url[288]}).

  14. Pretty cool post. I just stumbled upon your blog and wanted to say
    that I have really liked reading your blog posts. Anyway
    I’ll be subscribing to your blog and I hope you post again soon!

  15. pesh says:


    THANKS so much for this plugin. I am a user of the LR2/blog and the LR/Mogrify plugins and have donated for both. This has already saved me a good bit of time and has given me hope to update the blog more reliably!

    So here is what I am experiencing. Every time I export, the initial “<" from the comments AND form each image is omitted. I have to go and edit the post. I am using a self hosted WP installation at version 2.8.4 and on version 1.50 of the plugin.

    I appreciate all your work and thank you in advance for helping me with this.

  16. Hi, I am really curious about your plugin.
    So far as I introduced it to me I do not seem to find a missing option which would make your plugin much more usable. My apologies if it is already possible to do but I were unable to find it.
    What about remote hosting, if one is not hosting its content on a system provided by blogspot? Me and most of my friends are using the possibility to host actual content on their own server and just link to hat.

    Thank you for such passion.

  17. what a great site and informative posts, I will add a backlink and bookmark your site. Keep up the good work!

    I’m Out! :)

  18. Simon says:

    Tim, there seem to be issues with LR2/Blog on OS 10.6.2. The plugin seems to hang on load and on export. Colourwheels for about a minute on load and on export. Exporting on a new install works, despite the delays, but exporting with tokens in the content generates this error:

    An internal error has occurred: ./LRLib_Tokens.lua:283: attempt to index upvalue ‘photo’ (a function value)

    Lightroom 2.6
    System Version: Mac OS X 10.6.2 (10C540)
    Model Identifier: MacBookPro2,2
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2.16 GHz
    Memory: 2 GB

  19. Eric says:

    Hello Tim, I’m using your plugin and it does a good job. One thing I hope you will improve : I manage more than one blog, so each time I change the blog I export my images to, I have to enter again the url / username / password. Could it be possible to register more than 1 blog and just have to choose in a list wich one I want to export my images to?