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

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 – Google Photos (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.

If Google release an alternative method to Picasa Web for managing photos on Google Photos then I’ll investigate as soon as I can, but at this time there is no suggestion from Google they’ll provide such a service.

Google Photos “shared albums”

Please note that Google does not tell the 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 – Google Photos (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”.

27 Jan 2017 – Google Photos (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 – the Photo Upload plug-in now works with Picasa Web again, but an update to version 4.1.6 is required. 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. You need to update to Photo Upload version 3.5.7 or later. You can use the Update button within the plug-in to do this.

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/7 Oct Zenfolio have changed the way security for internet communication is handled on their servers. You need to update to Photo Upload version 3.2.1 or later. You can use the Update button within the plug-in to do this.

27 Jun 2014 – Flickr authentication fails

Flickr have changed the way authentication is handled on their servers. You need to update to Photo Upload version 1.7.9 or later. You can use the Update button within the plug-in to do this.

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 loading 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.

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 ones that are self-hosted. Authentication is managed by wordpress.com, so your account on that site needs to include a reference to your self-hosted blog.

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 on sites hosted locally at “localhost”. Authentication needs your site to be registered and accessible by wordpress.com. Therefore the plug-in does not currently work with “localhost” WordPress sites.

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”.

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 Picasa Web (Google Photos). Please be careful when purchasing licenses and entering the license keys that you have selected Google Drive or Picasa Web (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 (Google Photos) photo size constraints

This plug-in uses Google’s Picasa Web interface to upload photos to Picasa Web and Google Photos. At the time of writing, Google do not provide applications like this plug-in direct access to their Google Photos interface, instead the Picasa Web interface must be used.

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.

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.

Support - Plug-in Manager - Save log

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,307 Replies to “”

  1. I am using Photo Upload Tree Mirror Publish features. As of version 4.6.4, everything was working fine, no errors. I was required to update to version 4.6.8 and now I get the following error:

    Photo Upload 4.6.8: Error uploading to Tree Mirror. The Tree Mirror album you have specified to redirect to does not exist on Tree Mirror.

    I can reproduce the problem on another computer as I get the same error. Is this a bug, or am I missing something?

    Thanks.

  2. I have 22k photos uploaded to Flick, which I included tags using Flickr UI, not LR. Is there anyway, I can import those tags back to LR, so I can upload my photos to another service without loosing the tagging?
    Thank you!

  3. Current version 4.6.4 running on Mac OS Sierra (10.12.6) drops ALL exported photos to Picasa Web (Google Photos) as jpg files on my desktop and does not delete them after upload. Yes, they were successfully uploaded, but this is not an expected/desired result.

    1. Hi,
      Please check your Lightroom Export/Publish settings for your Export Location. It is probably set to export to “Desktop”, but you should choose “Temporary folder”. The plug-in recently enabled this Lightroom setting to help people choose where Lightroom creates the temporary copy of the photo during export/publish.
      Regards,
      Rob

  4. Hello,

    after editing an already exitsting foto it should be reexportet. I always get the error:
    Tree Mirror error: ‘Unable to copy photo’. If the same foto is not existant before, it will be copied. Looks as it is not possible to overwrite the exiting file. The module is configured to “alwasy overwrite”, but it does not. Any ideas how to get this working (again)?

    1. Hi,
      You found a bug.
      It should now be fixed in version 4.6.4. Please use the plug-in’s Update button to get the latest version.
      Thanks for raising this issue,
      Rob

    1. The plug-in has now been updated to work with Lightroom 6.12. Please use the plug-in’s Update button to get the latest version.
      Thanks for highlighting this.
      Rob

  5. I’m using Google Photo (Picassa) uploader, updated to the last version (4.6.2)

    When I try to upload a .dng file, I receive this error:
    “Picassa Web error: ‘HTTP/1.1 400 Bad Request, Content-Type image/x-adobe-dng is not a valid media type.’ (1).

    The same file, uploaded manually, works fine.

    1. Hi,
      You found a bug.
      Should now be fixed in version 4.6.3. Please use the plug-in’s Update button to get the latest version.
      Thanks for raising this issue,
      Rob

  6. Bought and installed Photo Upload for Smugmug (via Adobe’s add-on site). And the photo upload shows up just fine in LR’s plugin manager. But as I understand it, Tree Mirror should be part of the “package” – but it does not show up. That’s a bummer, because I was specifically interested in Tree Mirror’s abitliy to … well, mirror folder trees.
    Regards,
    /Steen

  7. I am using the “Photo Upload” sucessfully to publish photos to my personal FB account. Can I also use it to publish to an album on a FB page that I manage (e.g. a “fan” page)? How?

    1. Hi, yes you can upload to FB pages (but not groups). When you go through the account authentication process using the Add/Refresh button in the plugin you will eventually get a list of all FB accounts and pages your FB user can manage.

  8. Hey there! First and foremost: I absolutely love this plug in, and I am so glad I purchased it. 🙂

    However! I have noticed recently that when I upload to Zenfolio (using the export method) to an existing gallery, it keeps the gallery at 24 pictures, removing the oldest photo in the process. Is this currently a known issue?

    1. Hi. You found a bug with the plug-in’s search for existing photos. It had found an existing photo with the same file name as the photo you were uploading, so deleted the old photo first. This behaviour should only take place if you have the setting value being “If names match, delete”.
      Thanks for reporting the problem and confirming the fix (v4.6.2) works.
      Rob

  9. I am successfully using the uploader to publish to a Facebook album under my account. Can I use it to publish to an album on a page I manage? How?

    1. Yes, you can upload photos for Facebook pages. You will need to use Add/Refresh to add a new Facebook account to the plug-in. When you do, this as part of the authentication, the plug-in will offer you a list of pages that you manage and you should choose the desired page.

  10. I’m using Photo upload Picasa web (Google Photos) vs 4.5.2
    In General Setting/Existing photos and video’s one can choose: 1) if names match duplicate 2) if names match skip 3) always duplicate 4) always skip. In an earlier version it was also possible to choose: if names match overwrite. Are there any plans to bring back this possibility? It would save me a lot of trouble when I want to update already uploaded photo’s by a modified one with the same name. Or is there another possibility to overcome this workflow? Any ideas?
    Thanks Gert

  11. How long do you think the google photos plugin will last now that picasaweb is being slowly dismantled?

    Thanks!

    1. Really hard to say. There is no information from Google saying that Picasa Web is due to be dismantled further. With no alternative I’d expect them to leave it up and running as-is for quite a while in its limited form. The sceptical amongst us would say that Google have reduced the functionality of Picasa Web in order to differentiate it from Google Drive for archiving photos and files.
      Rob

  12. My upload library to SmugMug has always been set to PUBLIC, no issues there.
    The plugin V 4.5.6 now gives me the following error:
    “SmugMug error: ‘HTTP/1.1 401 Unauthorized, Unexpected network connection status.’ (1)
    And the name of my file below that was not uploaded.
    In this particular case I was uploading only 1 file.

  13. I am unable to export with Photo Export v. 4.5.6. The program tells me it is enabled and operating, and I am uploading to “photo upload.” But when I click “Export” I am not taken to the page to select a Zenfolio album. Instead, I see only folders on the computer hard drive.

  14. I’m using the Facebook uploader and I’m having an issue. I’m selecting both “Auto-generate Feed Story” and “Create Post” but it’s not showing up in friends’ feeds like a normal post. If I tag someone in a photo, they see it in their feed, but that’s about it. I’ve found that if I edit the post’s text, it helps but that seems like a workaround. Any tips on what I might be doing wrong?

    1. How Facebook shares posts and photos is a bit of a mystery, so you may know as much as me… It does the sharing all by itself, the plug-in merely uploads photos and create the posts.
      However I believe that if you create an empty post (no text) then Facebook does not actually create a post, it just seems to upload the photo.
      The other thing to look at is your Lightroom plug-in app privacy settings (https://www.facebook.com/help/218345114850283?helpref=faq_content). The photo and post privacy permissions are partly determined by what permissions you gave the app when you first registered it with Facebook.
      Rob

      1. Thanks for replying! I sort of figured this was down to FB’s odd internal workings but wanted to ask. App permissions are setup correctly. I’ll just edit the posts manually once they upload from LR I guess, not a huge deal. Thanks again!

  15. Hi Rob,

    I notice that I am getting a (996/1,000) album retrieval message when I upload to Google Photos. Is there a limitation in your upload process or is there a Google Photos limit on the number of albums?

    Thank you,
    Phil

      1. Thanks Rob!

        I will know pretty soon on the 1,000 block situation, 10,000 should get me by for a while.

        My work around to use a “!temp” folder to upload with your album tool is the best workaround for now. I just go into Google Photos !temp, select the new photos, make a “new album” and transfer the files from the !temp file. Not perfect, but avoids hunting and pecking for the new uploaded pix. I then delete the extras from “!temp.”

        Thank you for updating this software!

        Phil

        1. Thanks for sharing your Google Photos workflow. I know quite a few people are trying to work out how best to deal with the restrictions that Google put in place earlier this year. I’m sure your suggestions will help.

  16. Any plans for video support for WordPress? The export dialogue supports it and works to file. It would be great if I could upload videos via a plugin rather than going to the draft post and adding it manually!

    Website below is temporary, awaiting domain changeover to colinbeggphotography.com

    1. Hi,
      Video upload to WordPress has now been added in the latest version (4.5.4).
      Can you update the plug-in to that version and give it a go?
      Videos can now be uploaded to self-hosted WordPress sites. But if you want to upload to wordpress.com sites then, due to a wordpress.com security change this year, you can’t currently do this without following one of these instructions – https://tribulant.com/blog/wordpress/how-to-fix-sorry-this-file-type-is-not-permitted-for-security-reasons/.
      Thanks,
      Rob

  17. Flickr uploading is completely broken for me, and has been for a few days at least. Though it comes and goes.

    For example, new album creation always fails, with the error:

    Photo Upload 4.5.2: Error uploading to Flickr

    Flickr error: ‘HTTP status 0, Unexpected network connection status.
    Please check internet/firewall settings.
    Curl error 52, ‘Empty reply from server
    ’.’

    It sometimes does actually create the album on Flickr, though there’s never anything in it except Photo Upload’s “Icon.png” that it uses as a placeholder for the new albums (and looking back, I have dozens of these scattered throughout my photo stream from the last several months, that I’ve had to now go back and delete manual through Flickr’s site).

    When uploading to existing albums, it only uploads some photos sometimes, and even those that it does, it doesn’t mark them as published anymore in Lightroom. It also doesn’t actually add them to the album on Flickr – they’re just orphans in the photo stream. It reports no errors when this particular error occurs.

  18. I just started using your plugin to upload to Zenfolio after using Jeffrey’s for many years, so I have thousands of photos on Z already and existing galleries. I set up a collection in your plugin using the same settings, and pointed it to the existing gallery on Z, the same photos are shown in my lightroom as zenfolio, but when I Publish, it is duplicating and triplicating the images on Zenfolio. I am using the setting “if names same update”.

    ALSO how do I set it to delete any images online that are NOT in the local lightroom collection? My collections often change due to keyword changes, so I would need any removed from the collection. Please advise asap. thanks.

    1. Hi,
      You found a bug with the “if names match update/delete” setting behaviour. This is now fixed in version 4.5.1 so please use the plug-in’s Update button to get this version.
      Regarding your other question, the plug-in does not allow you to delete photos from the online collection that do not exist in your local Lightroom collection.
      Thanks for raising your first issue.
      Rob

    1. I mean for google photos. If the photo is already in google photos how do I sync just the description? hope that is more clear.

      1. Hi,
        The plug-in does not currently allow you update only the photo metadata. It’s a good suggestion though so I’ll see if I can add such a capability.
        However… as of Feb this year Google Photos (via Picasa Web) no longer allows updating of photos. If the plug-in gets such a feature in the future, then sadly it will not be able to be applied to the Picasa Web service.
        Thanks,
        Rob

  19. Hi,
    Can the plugin support OneDrive for business?
    When clicking on the authentication button there is no option for selecting the one drive buisness account
    Thanks.

    1. Hi,
      No, the plugin does not support OneDrive for Business as that is very different to personal OneDrive and has an authentication that is specific to each customer.
      Microsoft I think said they intend to make the authentication easier in the future, but right now it is not feasible for the plugin to work with OneDrive for Business.
      Thanks,
      Rob

  20. Hi! Love this plugin, but lately my uploads to Flickr have been DOGGED slow. Like, 5-10 minutes per photo. I’m not sure how to best debug this, but have changed no settings in my Lightroom CC or the Publish Service.

    I’ve tested this out with another Flickr publish plugin, and it went pretty quickly, but would prefer to not have to move everything over to a new Publish Plugin — I like yours! 🙂

    Thanks,
    — W

  21. Is there a way to have it upload to multiple services at once? For example my Flickr and 500px accounts at the same time?

  22. Amazon Prime Membership allows unlimited photo storage, but the Photo Upload Lightroom-plugin assumes user must have an unlimited Amazon Drive storage account.

    Is there a way to use the plug-in with Amazon Prime Photos?

    Thank you.

    1. Hi,
      I’m afraid Amazon only provide an interface for Amazon Drive, not for Amazon Prime Photos.
      There is an overlap though between the two. From what I can see, photos uploaded to your Amazon Drive account do not take any of your storage allocation if you have Amazon Prime Photos. Once the photos are in Amazon Drive you can easily use the Amazon web interface to convert a Amazon Drive folder into an Amazon Prime Photos album.
      Rob

  23. I just licensed the Zenfolio feature…thank you!

    I am having trouble with uploading videos (still images work fine). I have tried both .mov and .mp4 videos (both formats are supported by Zenfolio), and the upload errors out with the following message:

    “Zenfolio error: ‘HTTP/1.1 498 Invalid format, This file format is not supported or the file is corrupt.’ (1)” followed by the file name.

    These videos come from two different cameras (iPhone 6 and Canon G15), and I have tried uploading unedited videos as well as videos processed by iMovie 10.x. All error out with the same message.

    However, the videos CAN be uploaded directly to Zenfolio using their web uploader, so I don’t think the videos are actually corrupt.

    Any ideas?

    1. Hi,
      I’m not sure the plug-in has ever been tested with videos for Zenfolio before(!). I’ve made some changes after also seeing the error messages you reported and hopefully all is working now.
      Can you use the plug-in’s Update button to get version 4.3.7 and give it a try?
      Thanks,
      Rob

      1. That seemed to do the trick! Thanks so much for the quick resolution!

        Your chief competitor :), Jeffrey Friedl, has a similar problem with his plugin for Zenfolio. Are you two on sufficiently friendly terms to share the wisdom?

        1. Thanks for letting me know that the update has worked for you.
          Jeffrey and I have worked together recently and I’m sure we will again 🙂
          I do need to contact Zenfolio about video uploads as I think Zenfolio make it very difficult for a plug-in to track videos that have been uploaded. Currently if you use this plug-in to re-upload a photo then the old one will be updated or replaced but re-uploading videos will leave you with duplicates as it is non-trivial to identify the existing video.
          Rob

          1. Yes, I noticed that, too (about what happens when one reuploads videos). I like Zenfolio, and don’t relish spending the time to move my albums elsewhere, but they have some poorly implemented pieces they just won’t spend the time to fix.

  24. Hello,

    since some weeks I get always errors like this one:

    Tree Mirror error: ‘Unable to copy photo: ‘(nil)’’ (1)
    Y:\Bilder\HQ-Vorlagen\2016\2016-10-30 Ompah-Halloweenshow – 2. Show\IMG_4319.CR2

    I havn’t changed anything at my system. Do you have an idea what’s wrong?

    Kindest regards
    Falk

  25. I have had a problem with uploading .mp4 videos from my Samsung Galaxy S6, and recently updated to 4.1.6 and still see the issue. The export completes successfully from within Lightroom/plugin but when trying to view the videos on the Google Photos site I just see a grey image with “Your video will be ready soon” and it never displays. Eventually Google appears to remove the video (since I assume it is deemed “invalid” and times out). I have tried with all video options:
    – Original, unedited (my preferred to avoid having my export have to reprocess the video)
    – H.264
    – DPX
    Manually uploading the same video to Google Photos via their website results in the video being playable immediately.
    Have you seen this issue? I tried searching but found no reference to it.

  26. Hi
    I have just purchased the Google photo plugin (piscas).
    In the existing photos and videos dropdown.
    I have no listing for a photo to be updated.
    This is the main reason i want to use your plugin.

    Dean

    1. Hi,
      If ifp3 give you FTP access then you could try connecting over FTP. The Photo Upload plug-in supports FTP (and SFTP on Windows).
      Using FTP means you’ll need to know your FTP site configuration, so this may be more technical than you want to spend time on.
      You can try the plug-in for free – and if it works well for you then you could buy a license key at that time.
      Thanks,
      Rob

  27. Uploading from Lightroom to Smugmug with Photo Upload version 4.3.4 not working

    Message
    Smugmug ..HTTP/1.1 401 Unauthorized, Message = System error, Status = 5, Method = smugmug.images.upload’ (1)

  28. Hi, FTP upload in Photo Upload executes the upload even if I select Cancel in the “Display settings” dialog. That is when I have selected to show the settings dialog before publish.

    1. Yes, that was actually the intended behaviour. The dialog showed your settings and if you hit cancel then it would ignore any changes you made to the settings. However in this case the bigger context was that your were publishing and cancel at this point makes more sense to cancel the publish operation.
      So I agree and have updated the plug-in with version 4.3.4. Please use the Update button to the latest version.
      Thanks,
      Rob

  29. Hello Rob
    First thank you for your support here.
    Using/have used LR with several publishing plugins like Smugmug Onedrive NexGen Dropbox etx and all with great success. I’m doing something wrong with the upload for Pinterest.
    I believe I have it set up right. It creates the board but sits there w no progress on the upload and after long enough time I close it, go to Pinterest and no images wre uploaded.
    Thoughts?
    Thanks
    Scott

    1. Hi,
      I’m a bit confused by this one. Could you make sure you have the latest plug-in installed – it should now be version 4.3.3. You can use the plug-in’s Update button in the settings for it in Plug-in Manager to get the the latest.
      I’ve had a look and can’t reproduce the “no progress” you have mentioned. I did find a bug that prevented albums being created and I’ve fixed that one, but that doesn’t sound like what you reported so I thought I’d ask you to check you’re on the latest version.
      Please try with the latest 4.3.3 version and let me know how you get on.
      Thanks,
      Rob

  30. Hello,
    is there a way to connect to the Amazon Drive on the amazon.de Web page?
    The default one goes to the US which is quite use less as my Amazon Prime account is in Germany

    1. Hi,
      Amazon have a .com login page for apps. You can still log in using your German account. For example, I have a UK account, not a .com account.
      Regards,
      Rob

  31. Flickr Upload from Lightroom: All went well downloading and authorising with payment key. Everything looks fine in Plugin Manager. However when I hit the “Publish” all that appears on Flickr is a blurry rendering of your logo! HELP!!!

    1. Hi,
      You found a bug in the plug-in which is now fixed in version 4.3.2. If you uploaded just one photo to a new album then a plug-in logo picture would be left in the album until you uploaded a second photo.
      Thanks for reporting this, and confirming the fix works.
      Rob

  32. Do you know if it is still in any way possible to make an album “public”. It used to be possible through the plugin to create an album and set it to public. But somehow google doesn’t want us to share our albums with the world.

    1. Hi,
      The plug-in setting for making an album public was only used when creating albums. Since Google prevented apps from creating plug-in then the option had to be removed.
      You can create albums in the Google Photos web interface and then you can use that interface to share the albums (which seems to be the same as making them public). However please note that there seems to be a weird quirk by Google Photos that albums created as “shared albums” are not visible to apps like this plug-in. You have to create them as regular “albums” and then share them afterwards, from what I can see.
      Rob

      1. Hi All,

        To get around the Google “new album situation,” I created an album name !Work. It is the first album found at the bottom of the plug-in display because “!” is a very low ASCII character.

        I then upload my images to that album and move them to a new photo created in Google Photos. That is sure a messy way to do it, but the best I can think of for now. Ugh.

        Phil

  33. I’ve an issue just with Fotolia:
    Service_FT.lua:963: bad argument #1 to ‘find’ (string expected, got nil)

    It says “an internal error has occured” while retrieving the album list. That just happens with Fotolia, other ftp sites work as a charme.

    1. Yup – sorry, you found a bug.
      Should now be fixed in version 4.2.5. Please use the plug-in’s Update button to get the latest version.
      Thanks for reporting this!
      Rob

      1. Wowww!! Now it works properly 🙂
        Found a bug and solved in less than 24 hrs, what an amazing support!!!
        Thanks a lot guys…
        I’m suggesting your plugin in my stock photography forums with every pill of my heart

  34. Photo Upload for Tumblr stopped working, giving error dialog
    Service_TB.lua:93 – bad argument #1 to ‘gsub’ (string expected, got nil)

    1. Ah, you found a bug.
      Should now be fixed in version 4.2.4. Please use the Update button in the plug-in settings to get the latest version.
      Thanks for reporting this.
      Rob

  35. I updated to the latest version, and it no longer creates a new album, but only has the option to redirect to an existing album for Google Photos. Any ideas?

  36. I am receiving an error as shown below when trying to create an upload to DropBox.

    I am on Version 4.0.8 and see a new version available. The new version will not install. Please advise how to correct both issues.

    Thank you

    Plug-in error log for plug-in at: C:\Lightroom plugins\photoupload.lrplugin

    **** Error 1

    An error occurred while attempting to update the settings for this collection.
    Publish.lua:1428: attempt to call method ‘setCollectionSettings’ (a nil value)

    **** Error 2

    An error occurred while attempting to update the settings for this collection.
    Publish.lua:1621: canceled

    **** Error 3

    An error occurred while attempting to update the settings for this collection.
    Publish.lua:1621: canceled

Leave a Reply

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