Sometimes problems do occur so please get in contact by adding a comment at the bottom of this page and I’ll do my best to try and help. Please remember to use a real email address when you post a comment so that I can get in contact if necessary (your email address will not be visible publicly).

Contents

Latest support news

20 Jul 2018 – Facebook prevents plug-in from being authorised

Facebook, in light of the Cambridge Analytica scandal, have prevented small businesses like this one from connecting to Facebook. The official date for this dropping of support was supposed to be 1 Aug 2018, but they seem to have taken action a little earlier.

Facebook have not responded to any requests for clarification on their policy for preventing small business access. Unfortunately at this time there is nothing else that can be said except that Facebook have prevented the plug-in from being authorised and therefore have prevented the uploading of photos using the plug-in.

This change of policy from Facebook is very much related to the inability to run Lightroom’s built in Facebook plug-in any longer. This is the warning message from Adobe that Lightroom now gives you for their Facebook plug-in:

15 Jun 2018 – 500px no longer supports plug-ins

500px have announced that as of this date they will no longer support plug-ins like Photo Upload to access their site. This is a decision made by 500px and not by the plug-in.

There is no alternative plug-in available for uploading to 500x from Lightroom.

If this decision affects you then please contact 500px directly and mention that you use or rely on the Photo Upload plug-in for Lightroom. I have also contacted 500px.

24 Apr 2018 – Facebook prevents plug-in from creating posts on user timelines

Facebook have announced that on 1 Aug 2018 they are removing the ability for third party applications to create posts on user timelines. Facebook are still allowing posts to be created for Facebook pages.

Specifically, Facebook have prevented applications from being granted a permission called “publish_actions” that allows posts to be created on user timelines.

Update 20 Jul 2018 – Refer to the news on Facebook dated 20 Jul 2018 above.

23 Jan 2018 – Picasa Web uploads fail (“500” error)

The Picasa Web API that 3rd party apps use to upload and manage photos for Google Photos is giving an error when uploading photos. The error from Google simply says “Internal error, try again later”.

Many other people and apps have reported the same errors, for example see this thread (which has nothing to do with this plug-in).

There are no indications from Google that this is either a planned outage or a planned change, so at this time I have to assume that Google will fix the problem sooner than later. I will keep an eye on the situation over the next day or so, but there is nothing else I can do at this time.

Please be aware that that 12 months ago Google made it clear that Picasa Web was being retired and no longer developed. Sadly, Google do not allow 3rd party plug-ins to upload directly to Google Photos (they can only upload to Picasa Web). My suggestion is that it is time to start looking at alternative photo sites if you want to upload directly from Lightroom.

Update 25 Jan 2018 – Google have now fixed the problem and Picasa Web uploads work again.

27 Feb 2017 – SmugMug no longer allows photos to be uploaded to “Private” galleries

SmugMug have prevented photos from being uploaded to galleries that have their visibility set as “Private”.

I don’t know their rationale why and I even asked them why in their support forum, but no reply – https://dgrin.com/discussion/261330/cannot-upload-photos-to-private-galleries-using-v2-api. I’m not sure if SmugMug will fix this or if it is permanent.

You need to change the gallery visibility to “Public” or “Unlisted” then the upload should work.

Update 28 Jun 2017 – this is now fixed in plug-in version 4.5.7.

7 Feb 2017 – Picasa Web changes (e.g. albums cannot be created)

The Picasa Web API that 3rd party apps use to upload and manage photos for Google Photos has been updated by Google to prevent many update operations.

Google have now prevented the Picasa Web service from creating, renaming and deleting albums and from updating or deleting photos. If you are technically minded, please refer to this Google site for more information (see section titled “Mutation support removed”).

You can still upload photos using the latest version of the Photo Upload plug-in, and you can use the Google Photos website to create your albums before or after uploading to them from Lightroom.

Update 6 Sep 2018 – Google have released an official interface to Google Photos and this plug-in has been updated to support this interface. Please refer to the “Google Photos” service added to Photo Upload version 5.0.9.

Google Photos “shared albums”

Please note that Google does not tell the Picasa Web plug-in about any albums you initially create on Google Photos as “shared albums”. To work around this, please initially create albums on Google Photos as regular “albums” and then configure these to be shared albums afterwards.

7 Feb 2017 – Picasa Web uploads fail (“501” error)

The Picasa Web API that 3rd party apps use to upload and manage photos for Google Photos has been updated by Google to prevent many update operations. Older versions of the plug-in will display “501” errors from Google when trying to perform certain tasks like creating albums.

The Photo Upload plug-in has been updated with version 4.1.9 to handle these Google changes with “friendly” error messages. You should update your plug-in to 4.1.9 or later.

Please also refer to the note above on “Google Photos (Picasa Web) no longer allow albums to be created”.

Update 8 Feb 2017 – this is now fixed in Photo Upload version 4.1.9.

27 Jan 2017 – Picasa Web uploads fail (“400” error)

The Picasa Web API that 3rd party apps use to upload photos to Google Photos is reporting a “400” error with the message “Bad request”. This will affect all 3rd party apps that upload pictures using the Picasa Web API to Google Photos. There is a thread on the Google forums that is discussing the problem.

It is not known what causes the problem and when Google will fix the issue. I’d expect them to fix it quite quickly given the number of 3rd party apps that make use of uploading photos in this manner. I’ll track Google’s response – hopefully it will be quick and positive.

Update 28 Jan 2017 – this is now fixed in Photo Upload version 4.1.6. There has been no indication from Google what the problem is, but I’ve found an alternate way to upload the photos which appears to work well.

19 Apr 2016 – Facebook authentication fails

Facebook have mandated a few changes to authentication and old versions of the plug-in will receive a “URL blocked” message from Facebook when authenticating.

Update 19 Apr 2016 – this is now fixed in Photo Upload version 4.1.9.

16 Feb 2016 – Google announce changes to Picasa Web

Google recently announced that they will be making changes to the Picasa Web API that the Photo Upload for Picasa Web plug-in uses.

Google have been unclear about all the implications of these changes to applications such as the Photo Upload plug-in. However they have stated that changes to their API will not be made until 1 May 2016.

Google may keep the old Picasa Web API working, with some small changes or limitations. They may replace the API with a new alternative that the Photo Upload plug-in can use. Or they may do something else such as improve Google Drive integration for Google Photos, or remove third party API access to Google Photos entirely.

Google have noted that they will announce in March 2016 what the changes will be in detail, so until that time it is not possible to comment further on how Google’s plans will affect Photo Upload for Picasa Web.

Every effort will be made to ensure Photo Upload continues being able to upload your photos to Google Photos. When Google share more details of their plans then this news section will be updated with what this means for the Photo Upload plug-in. Until then, I’m afraid we have to be patient…

13 Nov 2015 – Lightroom hangs/freezes when closing

A few people have highlighted that Lightroom can hang/freeze when it is closing. Lightroom must then be force closed to make it quit properly. In some circumstances a window is shown during the hang that shows the Photo Upload plug-in is shutting down.

It appears that this is a problem with Lightroom, not with the Photo Upload plug-in. Please refer to this feedback page on the Lightroom forums:

http://feedback.photoshop.com/photoshop_family/topics/lightroom-2015-2-hangs-on-quit

The advice that seems to work fairly reliably is:

Reset the preferences (holding down SHIFT and ALT and starting Lightroom) and choose YES.

7 Oct 2015 – Zenfolio communication fails

During some scheduled maintenance on 6 or 7 Oct 2015 Zenfolio have changed the way security for internet communication is handled on their servers.

Update 7 Oct 2015 – this is now fixed in plug-in version 3.2.1.

27 Jun 2014 – Flickr authentication fails

Flickr have changed the way authentication is handled on their servers.

Update 30 Jun 2014 – this is now fixed in plug-in version 1.7.9.

Updating the plug-in – always check you have the latest

If you think you have a problem, in particular if you think you’ve found a bug, then please make sure you have the latest version of the plug-in.

Use the Update button in the plug-in’s settings from Lightroom Plug-in Manager to check that you have the latest.

Support - Plug-in Manager - Update

Downloaded plug-in from Adobe’s website and I have a ZXP file…

If you download the plug-in from Adobe’s Add-ons website then you will get a ZXP file. This type of file is intended to be opened by Adobe Creative Cloud (and Adobe Extension Manager.) If you don’t have Adobe Creative Cloud then you cannot do much with the ZXP file.

Adobe’s add-on installation process for Lightroom plug-ins is really quite complicated – and certainly convoluted.

My recommendation for a more straightforward install is to download the plug-in directly from this website. This will be a regular ZIP file rather than a proprietary Adobe ZXP file. And then simply follow the tried and tested installation instructions also on this website.

Lightroom reports “An error occurred while attempting to load this plug-in.

When using Lightroom Plug-in Manager to Add a new plug-in, you may get an error reporting “An error occurred while attempting load this plug-in.“. This error normally means the plug-in folder has not been extracted correctly from the downloaded Zip file.

Support - Plug-in Manager - Incorrect folder

Lightroom expects all plug-ins to have a folder extension of “.lrplugin” or “.lrdevplugin”. When you download a plug-in Zip file from this website, the top-level in the Zip file will be a folder ending in “.lrplugin”, e.g. “photoupload.lrplugin”. You must extract this folder itself, not just the files within it. Once you’ve extracted the plug-in folder from the Zip, you can move it around your computer (e.g. to your Documents folder) but you must not rename the plug-in folder.

Missing plug-in – The “nil” plug-in is not installed

Lightroom indicates that the plug-in is missing or shows the message “The “nil” plug-in is not installed” if it cannot find the plug-in folder on your computer that you used when you added the plug-in to Lightroom.

After using Lightroom’s Plug-in Manager to add the plug-in to Lightroom, you must not remove the plug-in folder. Lightroom needs to load the plug-in from this folder each time it starts.

If you get this message, please re-install the plug-in by following the installation instructions.

Authentication problem – Error authenticating with [service]

Support - Firewall

When trying to authenticate you may get an error such as this:

Photo Upload: Error authenticating with [service]
No authentication information returned from [service].

The common answer to this is that you are running a firewall (e.g. Little Snitch etc.) and have restrictions on the plug-in’s network access.

Consider whether you currently have network problems or are running a restrictive firewall.

Most firewalls identify this plug-in’s network access as coming from “curl” rather than “Lightroom”. Please make sure your firewall permits network access for the “curl” application.

You can use the “Test Connection” window to test whether your internet connection is working for the plug-in. You can find the “Test Connection” window within the “Configuration” window under the plug-in’s Setting section in Lightroom’s Plug-in Manager.

What is the Export Location used for?

Lightroom provides a setting for the plug-in called “Export Location”. This allows you to specify where Lightroom should create the copy of each photo that you are exporting. Lightroom creates a copy for each photo according to your edits and settings. For example, if you’ve cropped your photo and want to export it as a JPEG then this is what the copy will consist of.

I recommend leaving the “Export Location” setting as the default which is “Temporary folder”. This means that the copy of the exported photos will be removed once they have actually been exported.

Lightroom says my computer is out of disk space

Now that online storage is cheap or even free, people want to upload their entire photo collection.

Some people are finding out that when exporting a large number of photos and videos that Lightroom reports that their computer is out of disk space. This problem typically occurs more frequently on systems that have smaller hard disks, e.g. those with 256GB or less SSDs.

At the start of a publish/export process Lightroom starts creating copies of each photo that you are uploading according to the publish/export settings you have specified. Lightroom does this in parallel to the actual uploading being done by the plug-in and does not wait for the plug-in to request each photo copy. Lightroom does not allow the plug-in to dictate when the photo copies are made and when they are deleted.

The out of disk space problem occurs because Lightroom creates all the photo copies at the start of the upload and only deletes the copies when the plug-in has finished uploading the final photo. The photo copies are created in the computer’s temp folder (on a Windows machine this is usually on the same drive as the main Windows installation, e.g. drive C:). You will need enough space in your temp folder (and drive) to allow Lightroom to create publish\export copies of all the photos that you are uploading in one operation. The space used by Lightroom during the upload will be freed up once the upload has finished.

e.g. If each exported photo that is generated by Lightroom is 5MB in size, and you are exporting 1,000 photos then you will need 5GB of free space in the temp folder on your computer.

Note: A work around for this Lightroom problem is to use the plug-in’s “Generate exports one at a time” setting.

For reference, here is how you can find out where your system temporary folder is that Lightroom will be using for the temporary files during an export/publish:

Win:

  • Open Command Prompt
  • Type:
echo %temp%

Mac:

  • Open Terminal
  • Type:
echo $TMPDIR

Location information not being uploading

Various online services (e.g. Picasa Web) can make use of the photo location information in the photo’s metadata. If the location information is not being uploaded then check that you have enabled location information in Lightroom’s Export/Publishing Manager windows, i.e. you do not have “Remove Location Info” checked.

Support - Location Metadata

Old versions of Photo Upload for OneDrive (and the previous SkyDrive Upload) cannot be authenticated

Update your Photo Upload plug-in to a newer version (version 2.3.7 or later).

Microsoft appear to have changed something on their servers which requires an updated Photo Upload plug-in.

Use the Update button for the Photo Upload plug-in in Lightroom’s Plug-in Manager to get the latest version.

Note: If you are still using the old SkyDrive Upload plug-in then please take this opportunity to upgrade to the Photo Upload plug-in (your existing license key will still work).

WordPress self-hosted sites

The Photo Upload plug-in works with blogs hosted on wordpress.com and blogs that are self-hosted.

Authentication is always managed by wordpress.com, so you will need an account on wordpress.com even if you do not have a site hosted there.

  1. Create an account on wordpress.com (if you don’t have one already). This is free, you do not need to create a site on wordpress.com
  2. Install the Jetpack plug-in on your own self-hosted WordPress site (https://en-gb.wordpress.org/plugins/jetpack/)
  3. After the Jetpack plug-in is installed, connect it to your wordpress.com account (https://jetpack.com/support/installing-jetpack/).
  4. Log in to wordpress.com using your wordpress.com account and add your own self-hosted WordPress site (e.g. wordpress.de or personal domain) to your account
  5. In the Photo Upload plug-in in Lightroom, use the Add/Refresh button to authenticate the plug-in with any of the sites registered with your wordpress.com account

For self-hosted sites, you will need the Jetpack WordPress plug-in on your WordPress site. Ensure that you have version 3.1 or later of Jetpack installed. Version 3.0.2 of Jetpack had an error that prevented authentication. This Jetpack error was fixed in 3.1.

The plug-in cannot be authenticated with sites hosted locally at “localhost”. Authentication needs your WordPress site to be registered and accessible by wordpress.com. WordPress does not allow such local sites to be registered.

WordPress blog site selection

WordPress allows you register multiple blogs with your wordpress.com account. You can select from your available sites using the drop down list in your Web brower when authenticating the plug-in with WordPress.

Photo Upload (WordPress) authentication with WordPress

WordPress authentication does not return an authentication code

Sometimes WordPress plug-ins can prevent the Lightroom plug-in from authenticating with your site. These plug-ins prevent you receiving an authentication from WordPress, i.e. the page with the authentication code does not open in your browser.

The problematic WordPress plug-ins tend to be security ones. There are known issues with these WordPress plug-ins, but other security plug-ins are likely to interfere with authentication too:

  • All In One WP Security
  • iThemes Security Pro

If you do not receive an authentication code in your browser please disable the security plug-ins and try the authentication again. You should be able to re-enable the plug-ins after the authentication has successfully taken place.

Plug-in not compatible with your version of Lightroom

E.g. “Lightroom Version 5.3.0.938183 is incompatible with this plugin“.

You have an old version of the plug-in.

If your plug-in has an Update button then use that to update to the latest version.

If your plug-in does not have an Update button or you are having problems using the Update feature then simply download a new version from this website and manually replace your existing plug-in.

If you have the old Picasa Web Upload plug-in then please download the Photo Upload plug-in which now replaces it. Your old Picasa Web Upload license key will work with the new Photo Upload plug-in (for the Picasa Web service).

If you have the old SkyDrive Upload plug-in then please download the Photo Upload plug-in which now replaces it. Your old SkyDrive Upload license key will work with the new Photo Upload plug-in (for the OneDrive service).

If you have the old Tree Mirror Export plug-in then please download the Photo Upload plug-in which now replaces it. Use the Tree Mirror service in the new Photo Upload plug-in.

Lightroom’s Plug-in Manager’s “Remove” button is disabled

It depends where you installed the plug-in as to whether you can use the “Remove” button to remove the plug-in from Lightroom. It is greyed out if you installed to the following locations:

On Windows, either

\Users\%MyUserName%\AppData\Roaming\Adobe\Lightroom\Modules

or

\Program Files\Adobe\Lightroom 5.x\Modules

On Mac,

/Library/Application Support/Adobe/Lightroom/Modules

To remove the plug-in from these locations you have to manually remove the plug-in folder from the appropriate path.

To avoid this potential problem, I recommend installing the plug-in to:

On Windows,

\Documents\Lightroom plug-ins

On Mac,

/Applications

Unreceived license key

If you purchase a license for the full version of the plug-in you will be sent 2 emails. One email will contain your order number and the second email will contain your license key. These emails will be sent to you immediately and automatically by the FastSpring payment service.

The license key email should be sent immediately – but on a few occasions it has taken 6 hours before it has been received.

If you think you should have received an email but have not received it then please first check your email junk or spam folders. The license keys and order receipts are sent by FastSpring – so it may help to search your junk/spam email folders for the name “FastSpring” or “mailer@fastspring.com”.

When a license key email has not been received there are typically two reasons:

  1. A private\corporate email domain is not processing the email correctly (sometimes the license key emails are identified as junk\spam). The most reliable email addresses tend to be from mainstream domains such gmail.com or live.com.
  2. An incorrect email address being entered during the order.

If you think either of the above apply then please contact FastSpring (support@fastspring.com) with your order number.

Unreceived license key (purchased from the Adobe Add-ons website)

If the above tips for finding your license key have not helped, AND you bought the plug-in from the Adobe website (i.e. not via the plug-in or this website) then you will need to contact Adobe for further assistance.

Please note that, as the plug-in developer and not an Adobe employee, I cannot access the payment and licensing systems used by Adobe. Therefore if you have purchased your license key from the Adobe Add-ons website you will need to contact them regarding any unreceived license keys.

Here’s a thread on the Adobe forums that gives the email address to contact that another customer was given.

Lost my license key

If you’ve bought your license from this website and lost your license key then please use the email address on the Contact page to get in touch. Please provide the reference number for your original purchase or the email address that you originally used.

Lost license keys purchased from the Adobe Add-ons website

If you’ve bought the license from the Adobe Add-ons website then you will need to contact them to have your license key sent out again.

Here’s a thread on the Adobe forums that gives the email address to contact that another customer was given.

Plug-in says the license key is invalid

When copying and pasting your license key from your license email into the plug-in, take care that the key is copied as one long list of characters.

Your email system may insert line breaks or spaces into the email, so please be sure that any such line breaks, spaces or other formatting from the email message are not pasted into the plug-in’s license text box.

If your license key is still reported as being invalid after copying and pasting it then please check you have specified the License service correctly in the license key entry window. e.g. If you have purchased a license for Dropbox then please make sure Dropbox is the selected License service in the window.

Support - License Key

A common mistake is trying to enter a Google Drive license key for Google Photos. Please be careful when purchasing licenses and entering the license keys that you have selected Google Drive or Google Photos correctly.

Don’t rename the plug-in folder

The plug-in folder should be named with a “lrplugin” or “lrdevplugin” extension. For example:

photoupload.lrplugin

or

picasawebupload.lrdevplugin

On Mac, if you open (i.e. extract) the downloaded Zip file a second time you will get a folder with the suffix “2”. Lightroom will not be able to read the plug-in from such a named folder. Before opening the Zip file consider removing an existing plug-in folder.

The following will give an error as the folder extension “.lrplugin 2” is not “.lrplugin” as Lightroom expects:

photoupload.lrplugin 2

If you really need two versions of the plug-in on your computer, I recommend having two separate parent folders and keeping the plug-in folder name the same, i.e.:

Windows,

\Documents\Lightroom plug-ins\picasawebupload.lrplugin \Documents\Lightroom plug-ins\V2\picasawebupload.lrplugin

Mac,

/Documents/Lightroom plug-ins/picasawebupload.lrplugin /Documents/Lightroom plug-ins/V2/picasawebupload.lrplugin

Google’s Picasa Web photo size constraints

The Picasa Web plug-in uses Google’s Picasa Web interface to upload photos to Picasa Web and Google Photos.

The Picasa Web interface has a restriction of a maximum photo size of 2048 x 2048 pixels if photos are not to be counted towards your allowance.

Please note that Google currently only provides “unlimited high quality photos” via its own mobile apps and website. Google does not allow any third party applications such as the Photo Upload plug-in to use those constraints.

However, once your photos have been uploaded to Picasa Web or Google Photos, you can then follow these instructions to recover the storage space:

https://support.google.com/photos/answer/6314648

Google Photos - Recover Storage

Old “Picasa Web Upload” plug-in

The old “Picasa Web Upload” plug-in has been replaced by the “Photo Upload” plug-in which allows you to upload to Picasa Web and many other services.

If you have the old Picasa Web Upload plug-in then please note that this is not available for use with the latest versions of Lightroom. Instead please download the latest Photo Upload plug-in from this website. You can use your existing Picasa Web Upload plug-in license key with the Photo Upload plug-in.

Create multiple publish services

If you want to use the Photo Upload plug-in with multiple services (e.g. Picasa Web and Google Drive) then you create additional publish services by right clicking on an additional publish service and choosing “Create new publish service…”. You can then choose a new upload service, account and settings for this additional publish service.

Checking the version of your plug-in

You may need to check which version of a plug-in you are using. You can do this from Lightroom’s Plug-in Manager.

Select the plug-in on the left (e.g. Photo Upload).

The plug-in version number is displayed on the right in both the plug-ins Settings and Status panes (in the example below the version is 1.5.5).

Support - Plug-in Manager

Removing a plug-in

Sometimes you may need to remove your plug-in, perhaps to replace it with a newer version.

Lightroom’s Plug-in Manager allows you to unregister a plug-in from Lightroom using the “Remove” button, but in most cases I recommend actually deleting the plug-in folder from your system. This is particularly important if you are upgrading the plug-in with a new version – always delete the old plug-in folder first so that there is no doubt which version of the plug-in Lightroom will be using.

You can find the installation folder of your plug-in from Lightroom’s Plug-in Manager.

Support - Plug-in Manager - Install folder

To remove the plug-in simply identify the install folder (highlighted in the above Plug-in Manager screenshot). You can then delete it using either Windows Explorer or Mac’s Finder.

You can use Lightroom’s Plug-in Manager’s “Show in Explorer” or “Show in Finder” buttons to go straight to the folder, making it easy to find the plug-in folder on your system.

Saving your log file

In order to try and help identify a problem, I may ask you to send me a plug-in log file from your machine. If I request this, please follow the instructions below:

1. Do the activity that doesn’t appear to be working, e.g. try uploading a photo. This is important so that the problematic behaviour is recorded in the log file.

2. Save your plug-in’s log file. From the “Plug-in Manager” window in Lightroom, select the “Save log” option from the plug-in’s settings section of the window.

3. Email the log file to me. Attach the log file from the place where you saved it into an email and send it to me.

1,410 Replies to “”

  1. Is there any way to keep trace in Lightroom catalog of what photos have been uploaded to Picasa? Or any filters or collections that can do this?

    1. I think if you need to keep track in Lightroom catalogs of the photos you’ve uploaded then you need to use Lightroom’s publish capability in conjunction with Lightroom’s catalogs. If you’ve purchased the full version of this plug-in then I’m more than happy to share with you an in-development version that works with Lightroom’s publish capability. But for most folks, using the publish capabilities and maintaining catalogs is “overkill” and detracts from getting photos onto Picasa Web and Google+ as quickly as possible.

      1. Hi Rob,
        I have just purchased the full version. I would like to try the in-dev version with the publishing option… Please send me.

          1. Hi, I’ve seen this plugin today the first time and purched the full version immediately for to see how it works as publish service. I’ve setted it up, added a smart collection and published it. I’ve seen that the images uploaded didn’t move from ‘New Photos to Publish’ to ‘Published Photos’, all other publish services I know are doing so. After 300 images it crashed (?:0: attempt to index field ‘_agXml’ (a nil value)). After restarting it it uploaded the same images again, now I see them at PicasaWeb twice. When it crashed again and I’ll restart it I’ll see them three times? Are you still working on this plugin?

  2. Hi,
    This is a very nice and usefull plugin but I have a feature request for futur version: to be able to manage multiple Picasa Web accounts (one at a time).
    I have to upload photos on several society accounts
    Thanks

    1. Interesting – another person asked the same question very recently.
      One way to manage multiple accounts is to create separate “user presets” for each account. Have you tried that?
      Most users have just a single Picasa Web account so I’m reluctant to complicate the user interface unless absolutely necessary.

  3. No issues with installation, and super easy to use. Thanks for the great support as well, in addressing and resolving my questions. This has made my LR to Picasa workflow much, much easier than before.

    1. I think the easiest way is to quit Lightroom. Delete the old plugin folder. Then extract the new folder from the latest downloaded zip into the same place.
      Let me know how you get on.

  4. Having trouble installing the plugin on Lightroom 4. First the plugin manager would give me an “error occurred while trying to load the plugin”. So finally I renamed the folder to “treemirrorexport.lrplugin” which is the filename convention it was looking for. Then I do see the plugin on the left side of the manager dialog box with a red circle and the error “installed but not working”. In the Plug-in Author Tools section the error is “the plu-in description script (info.lua) is missing. Any thoughts

    1. Hi. I’ll email you and you may need to send me some screenshots or details of exactly where you installed the plugin. You definitely don’t need to rename the extension as you did. Thanks.

  5. Hi Rob!

    I can not get window with invitation to name an album while exporting several photos to Picasa. Export itself does work. But I have full featured license and it should support creation of albums. How can I resolve this issue?
    Regards, Stefan

    1. Hi Stefan. I sent you an email to the address you gave me. Let me know if you’ve got it and we’ll get this problem fixed.
      Thanks, Rob

    1. Ah – I think you found a bug. You can enter a license key in three ways… If you entered it from the settings at the top of the Export dialog then the license would not be processed. This has now been fixed in the latest version of the plug-in. Thanks for getting in touch.

  6. I have just installed the plugin and it works. I have bought the license and the dialog box for selecting the album don’t appear. It works the same way without the license. What can i do?

    thks

      1. Ah – yep, the album selection window appears during the export after you have finished in the Export window itself.
        Glad you’ve got it working.

  7. Hi I Just purchased a pro version online but never received the email with the licence code – please supply as I need it for an urgent project and I dont want to have to wait for it Thanks

    1. Hi – have (re-)sent you your license. I assume the previous one got lost in your spam or junk email filter as I do have the correct indication of you placing your order successfully.
      Thanks.

    1. Hi, this plug-in is for Exporting (i.e. via the Export button) only. Not for Publishing. I’ve tried to make this as clear as possible on these Web pages.
      Thanks.

  8. I edit a picture. I right click. I select Export with Previous. Each and every time it asks me to what folder I am going to upload. (I have the paid version.) I do not like this. I chose “Export with Previous” and would prefer if the folder to upload was also the same as the previous upload.

    1. Hi. The latest version of the plug-in now has an option to use the last album that was uploaded to. This is as close as I can get to what you ask for because Lightroom does not tell the plug-in that you clicked “Export with Previous” instead of “Export”. Hope it is useful if not 100% what you wanted.

  9. Rob,
    Have installed your plugin on LR4 on my Mac and have registered. I cannot get the google authorisation to work. The browser window opens with an authorisation code which I paste in the dialog box, but when I press OK nothing happens and I return to the unauthorised dialog for the plugin. Please help. I can send screen shots if you wish.

  10. Hi, thanks for a very good plug-in. Works great for my photos however I am unable to upload video from L4 to Picasa using it (Mac running OS 10.6.8) Any idea why?
    Cheers, Simon

    1. Hi, thanks for getting in touch. The plug-in currently works just with photos, as Google has a slightly different API for uploading videos. I’ll try adding in video support shortly and will get in touch via email to see if you are able to perhaps test out an early version?

  11. Hi Rob,
    I installed and authorized the lightroom plug-in, it worked for uploading two albums. I now get an error message “unable to upload photo – error communicating with Picasa Web”
    I tried re-starting lightroom and re-authorizing the plug-in.
    Is there anything else I can try?
    Thanks for the help.

    1. This problem turned out to be due to some of the metadata including a “&” character. The problem should now be fixed in the latest plug-in. Thanks for the help fixing this, Jonathan.

          1. This issue was down to being out of quota from Google Picasa Web. I’ll see if I can improve the reporting of such to make it clearer what the problem is. Thanks.

  12. I downloaded the lightroom plug in for Picasa Web. It shows up in my Lightroom, however, when I try to input my license code it keeps telling me it is incorrect. I cut and pasted from your e-mail several times and it still says it is incorrect. I already have an established picasa web account that I have had for a few years…is this a problem?

    MaryAnn

    1. Hi. Sorry you’ve had problems. I’m aware of your license key but am away from a PC for the next 2 days. I’ll get back to you then. Sorry about the wait but we’ll get you a valid license key. Thanks for your patience.

    2. Think this was a copy & paste issue when taking the license key from an email. I’ve added a note to the FAQ section to highlight that copying the license key from an email has to be done carefully. Glad you have it working now.

  13. Great idea ! too bad It doesn’t work on lightroom 4 (OSX Mountain lion).
    It’s exporting something somewhere but there is nothing in the export folder.

    Thanks for your time 🙂

    1. Could you turn on Output to Log and kindly send me the *.log file from your Documents folder?
      If you give me a valid email address when you post your next comment then I can contact you by email.
      Thanks!

      1. The plug-in should now work on Macs. I had help from another Mac user to fix a problem. Would appreciate if you could try the plug-in and let me know if it now works for you.
        Thanks.

    1. Hi,

      Thanks for the feedback. Interestingly the plug-in is not limited to photos. What do you want to do with exporting videos? Resize them and put them somewhere else?

      Thanks.

        1. Ah – understood. I was missing something with the plug-in. The latest version should now support exporting of videos. Thanks.

  14. Hi,
    I had troubles installing the last 2 versions (1.0.15 and 1.1.1). Probably a question of characters (space or ‘é’ ?) in path name or lengh (D:Fichiers téléchargésWindowsLightroom4Export).
    Every thing got right while installing in another directory : D:PhotosLightroomPlugin
    Thanks for your work.
    Denis

    1. You were correct. There were problems that I could reproduce on my machine when using folders with modified characters like “é”. The latest version of the plug-in should have this fixed now.
      Sorry you had the problem, thanks for reporting it, and I hope it is now fixed.

  15. Love the plug in. Thank you. I see that video will not transfer. Is there any workaround short of just adding it manually later?

    Thanks.

    1. The plugin does not currently upload videos. I will add this to my list of changes to make. Watch this space.
      Thanks for the feedback!

  16. Using LR 3.6 on pc, your presets don’t show up under user presets…?
    All else worked ok.
    Enjoy the OlymPICs.
    Best

    1. Hi, the presets are actually just my personal presets.
      They aren’t needed in order to use the plug-in and are not provided.
      They are simply my favourite export settings.

  17. Help requested. In lightroom 4, I follow all of the steps but when I paste the authorize code into the lightroom dialog box, it does not authorize. Internet connection and firewall are not an issue. Is this an issue with lightroom 4 vs. lightroom 3?

    1. Can you follow the instructions on this page for creating an output log? And send it to me? I’ll drop you an email. Thanks.

    2. This one turned out to be because the Google account had an incomplete Picasa profile before trying to authorise the plug-in. I’ll add something to the FAQ… Thanks.

    1. This plug-in today only supports a single Picasa account at a time.
      If there is significant demand to support multiple accounts then I can add that capability.

  18. Thanks a ton for this!

    I actually have the Picasa software set up to watch several folders on my hard drive and automatically keep them synced to Picasa Web.

    But every once in a while I found myself wishing I could do it straight from Lightroom. I finally thought about it while sitting at the computer with a few minutes to fool around and found your great plugin.

    Everything installed quickly and easily on 64-bit Windows 7 running Lightroom v3.4. Many thanks for your clear and concise instructions. The value of such (and especially plenty of screenshots, like you included) can’t be overstated.

    Thanks again, and have a great 4th!

    1. Hey there. Thanks for getting in touch, really appreciate the positive feedback and glad that you’ve got it all up and running.
      Have a good 4th yourself too. Bizarrely it’s not quite as celebrated here in the UK as it is in the US 😉
      Cheers!

  19. I have the file type set to jpeg but the plugin errors because it can’t upload the .CR2 file which is the camer raw file. I guess it is not converting it to the jpg file before uploading. Thanks for your generosity with this plug in.

    1. Hi Mike.
      I dropped you an email yesterday to see if I could help with this. We should be able to get this working as I export from Canon RAW CR2s without any problem.
      You’d want to check your export settings to ensure that the export is a jpg and the file size is less than 20MB.
      Also, when you say the plug-in errors can you explain what that means? Specifically what is the error?
      Thanks,
      Rob

  20. Rob,

    thanks for this plugin. I did not have the time to test it yet, but I have a suggestion already :-). Please consider it.

    Picasa web-albums does not support hierarchical albums and many people would like to have that support. Many keep their images in hierarchical folders in LR (and your export utility is a great help when exporting herarchies).

    As an option, you could parse the pathname of a folder and create a compound album name for the pictures to be uploaded. E.g. pictures in Private/Vacation/US/2012 –> new album name “Private-Vacation-US-2012”.

    This would allow us (who are interested) to upload entire folder hierarchies with meaningful album names.

    Please consider it for your plug-in.

    Regards, Pete

  21. Does your plugin support titles/captions? I tried exporting a folder, and I have a title for each of the photos, but they didn’t show up in Picasa. Is there some setting I need to change?

    1. The plug-in supports Captions. If the plug-in supported Titles, where should it put the Title? I can’t see an obvious place. Lightroom puts the Caption text into the Picasa photo Caption property (via EXIF).

      1. I used the FB plugin, and it looks at both Title and Caption, and whichever one of them is not empty, uses that for the text below the photo.

        I can switch to using Caption, if I can figure out a way to copy the Title values to Caption in Lightroom.

        1. I’ve updated the plug-in (now v1.0.11) to combine a photo’s title and caption from Lightroom into one caption field for Picasa Web.
          I think this should be good for you, but do please let me know. Thanks.

          1. Thanks, that did the trick.

            If you only fill in the title field, it leaves a trailing comma, but I can live with that.

          2. Looks like the comma was my fault. It only appeared in the one test picture I tried first (naturally).

            Thanks again.

          3. Phew – was scratching my head where a comma might have come from!

            Thanks for confirming the Title and Caption combining has done the trick for you.

  22. File size.

    Is there limitations on jpeg file size ? If so , how to change it,if possible.
    NEF are too big but 100kb jpeg SOOO small for what I need.

    Thank you

  23. Hi!

    Great plug-in, thank you so much. I need to upload pictures to a Google+ PAGE (not personal profile). Do you plan to provide such a plug-in?

    Thanks & greetings, Dietmar

  24. Hi, i installed the plugin but it seems that it does not authorize on the Picas.
    I paste the “key” and OK….status – working.
    When I tried to export a photo there is a messege on ALBUMS:authorize before selecting an album.
    What do I need to do?

  25. Rob,

    I was looking for a Blogger plugin but was equally happy with a Picasa Web one (as you can add photos from a Picasa Web album to Blogger easily).

    My feedback: simple installation process with clear instructions, smooth Export/Upload process and zero issues after first test.

    Well done and thank you!

  26. This seems to work great, I can get it to Authorize in LR4.1 (win), and upload. However, it seems the version that Exports is the original, not the edited photo. Is this a plug-in issue, or a LR issue?

    1. Hmm… I crop a lot of my Canon CR2 photos and they successfully upload as cropped jpgs to Picasa Web without any problem.

      Have you tried exporting your photos to disk? Does that work?
      What edits are not being exported? e.g. If you crop a photo does it upload in cropped form?

      The plug-in just uses the standard Export settings.
      I guess one thing to check is what your settings are under “File Settings” in the “Export…” dialog. I have mine set to “JPEG”, perhaps yours is set to “Original”?

  27. Hi Rob

    Authorise work in Lightroom 4.0 and 4.1RC, but not in the Final 4.1.
    Iam working on a Mac and PWUL 1.0.9.
    Thanks
    Greetings from Vienna

    1. Hi. There is nothing obvious to suggest I’m afraid. I use the final 4.1 and it works fine for me. Sometimes the Google servers have problems but they normally rectify themselves eventually.

      I will contact you so that you can send me your Output log.

  28. I can’t seem to get GPS tags to upload properly to Picasa. I can see the GPS metadata in Lightroom (using v. 3.6) but when exporting, the location data does not show up in Picasa. Is this a functionality that is supposed to work with your plugin, or is it not included? Any way you could include this ability?

    Thank you

    1. You were correct, GPS location data was not being uploaded to Picasa Web.
      I’ve now added this capability in 1.0.9 of the plug-in. Please download the latest version and let me know how you get on. Thanks!

  29. plug-in working fine on LR4.1 Win7 home premium. don’t know if you care, the word authorise has 2 spellings; the other being ‘authorize’ more commonly seen in the U.S.

    1. Heh – British/international spelling of English versus American spelling. I will consider being consistent with Lightroom’s use of English and use AmericaniZed spellings in a future version 🙂

  30. it seems that this download is only for windows, even though it says windows/mac on the lightroom site. i am not seeing the .lrplugin file extension when i download the zip. Can you let me know how to install on a mac?

    1. Hi – based on this I’ve tidied up the Installation guide to give a few more instructions and screenshots.

      Lightroom does specifically ask for a .lrplugin folder but it is more than happy to accept a .lrdevplugin folder.

  31. The plugin works great and all, but I see one issue with my album: the tags from lightroom do not get synced to picasa. My picasa album is completely tagless. Cheers, Steven.

    1. Hmmm – I don’t use tags so they have had no attention from me.
      I will look into this, but can you confirm you mean the entries in Lightroom’s Keyword Tags panel (with Will Export selected)? And you would like each entry to map to a Tag in Picasa Web? Thanks.

    2. Thanks for the tags suggestion and your help. Version 1.0.8 of the plug-in now uploads Lightroom Keywords to Picasa Web as Tags.

      1. Hi
        I have a problem with export images.
        Even though I select Export Metadata “Copyright Only”, the tags are still sent. You can change the plug-in order to export the tags according to what you select an option Metadata?
        by Google Translate 😉

        1. Thanks for the feedback. There is now a newer version (1.1.8) of the plug-in that will look at the metadata export settings and respect them.
          Please try out the latest plug-in and let me know how you get on.

          1. Now keywords export works great. Thanks for the quick reaction.

            I have a new problem with the plug-in. Although we introduce the license key from time to time shows the message “You have free unlicensed version …” and I have to enter the code again. Why is this happening?

          2. Hmmm, I don’t experience that myself unless I play around with User Presets. Each User Preset stores its own copy of the license key so if you click on a User Export that has no license key saved then you will need to enter one again. Are you using User Presets?
            Thanks.

  32. Hi,
    I can’t get this to work – it appears in the plug-in manager, but doesn’t show up in the “publish services” section of LR.
    My environement :
    – Win7 64
    – LR4

    1. Heh – all I can do is point you to the info on this page about what the plug-in does:
      “Upload photos from Lightroom to a Picasa Web album using Lightroom’s Export capability (i.e. not via the Publish capability).”

      It is an Export plug-in, not a Publish plug-in.

  33. Does not work in LR 4 Mac.
    Get an error message with the authentification code:
    Unexpected error
    …ug-insDev picasawebupload.lrdevpluginPicasaWeb.lua:157: attempt to call global ‘error_from_header’ (a nil value)

    1. I think this is now fixed in 1.0.4 of the plug-in. The error arose if no authentication code from Google, or an incorrect one, was entered into the plug-in.

  34. Hi, the first couple of times I tried to install this, Lightroom (4.0) crashed, but third lucky and photos now successfully uploaded to Picasa. Thanks.

    1. Glad it works! No idea why LR4 would crash due to an export plug-in, but pleased everything seems to working good for you now. Thanks for the feedback.

    1. Hi. It should work on a Mac although I don’t have one to test on. There is nothing Windows specific that I am aware of. Will PM you.

      1. Turns out that there was a file name capitalisation inconsistency in the plug-in that only affected Macs. Should be fixed in version 1.0.1.

  35. Hi – looks great but doesn’t install on lightroom 4. Should it work on Lightroom 4? If not is there a plan for a LR4 version?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.