Support

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

11 Feb 2024 – Google Drive folder restrictions

Starting with version 5.9.6, the Photo Upload plug-in no longer lists Google Drive folders that it has not created itself, including shared folders and shared drives. All the upload capabilities still exist, but any folder that has not been created by the plug-in is not visible and cannot be uploaded to.

Google have announced that the Photo Upload plug-in can no longer access any folder or file that the plug-in has not created itself, including shared folders and shared drives. I’ve done my best to try and persuade the Google app verification team that accessing these folders is very useful to people uploading their photos to Google Drive, but Google have not been flexible on enforcing the new restrictions.

29 Jul 2022 – Uploading to Amazon Drive ending on 31 Jan 2023

Amazon have announced that they have deprecated Amazon Drive and are ending it on 31 Dec 2023 and preventing new files being uploading to it on 31 Jan 2023. This plug-in uses Amazon Drive to upload photos such that they can be viewed in Amazon Photos. On the date that Amazon prevents the plug-in uploading files to Amazon Drive this plug-in will no longer support uploading photos to Amazon. Unfortunately Amazon have not provided an alternative approach for apps such as this plug-in. The future approach for uploading photos to Amazon Photos after Jan 2023 is therefore going to be via the Amazon website or Amazon’s own apps.

6 Feb 2022 – Publishing and exporting hangs after one photo

With Lightroom 11.2, Adobe introduced a bug that causes publishing and exporting to hang after one upload. This has been reported here: https://community.adobe.com/t5/lightroom-classic-bugs/p-update-publish-collection-stalls/idi-p/12749232.

There seems to be one solution which involves clicking on a different collection when the publish/export first appears to hang. The second solution is simply to re-install Lightroom Classic 11.1 instead of 11.2.

Hopefully Adobe will fix this in the next update for Lightroom.

Update 12 Apr 2022 – Adobe report they have fixed (in Lightroom Classic 11.3) the hanging when publishing a collection.

18 Oct 2020 – Pinterest no longer authenticates

Photo Upload no longer authenticates with Pinterest and cannot currently be used to upload photos to Pinterest. It seems that Pinterest have disabled the API that the plug-in uses to communicate with Pinterest.

Photo Upload uses v1 of the API from Pinterest and has been an approved app by Pinterest since 2015 (it went through their approval process). Pinterest announced on their developer website sometime in early 2020 that there was a new v2 API available.

On 17 Apr 2020 the Photo Upload plug-in applied to use the v2 API.

On 5 Aug 2020 Pinterest sent me a notification that “the current version of the Pinterest Developer API will be deprecated in three months, on O‌ctober 3‌1, 2‌020.

Note: Deprecation does not mean “removed”, but I think in this instance Pinterest actually meant to use the word “disabled”. The word “deprecation” is used to announce that something will be removed in the future.

Pinterest asked that apps apply for the v2 API. I contacted Pinterest saying that the app had applied for the v2 API back in Apr.

On 31 Aug 2020 Pinterest sent me this reply: “Unfortunately, this is no ETA when the new apps will be approved as I have mentioned we are a very small team and currently experiencing a large backlog of applications. We’re working as fast as we can to review and get back to everyone and also we do not prioritize requests for any users as of now. I hope this clarifies.

On 18 Oct (or perhaps a few days earlier) Pinterest disabled the v1 API and the Photo Upload plug-in stopped working. Clearly this was before the 31 Oct date that they previously announced the API would be “deprecated” on.

I’ve emailed the developer support at Pinterest again and again over the past 6 months.

On 26 Oct I received the latest reply from them: “I can totally sense the trouble you’re experiencing on your end and I apologize for that. However, we’re bounded with limitations on our end. As I mentioned earlier, the requests for the app are getting reviewed by our internal team. I too agree that it has taken a longer time than expected. But please be assured as I’ve forwarded your feedback to our team. And, I’m sure they will look into your concern and get back to you at the earliest.

Unfortunately there is nothing more I can do to encourage Pinterest to grant Photo Upload access to the v2 API. Pinterest disabled the v1 API earlier than they said they would (was meant to be 31 Oct). The whole idea of a deprecation cycle is to give developers time to move to a new way of doing things (i.e. v1 to v2) but in this case they have not processed applications after 6 months! Hopefully you can see that I’m very frustrated by this, I actually haven’t worked with a less professional mainstream organization with the Photo Upload plug-in.

At this stage I’m waiting to hear from Pinterest about whether they will grant the plug-in access to the v2 API. But I’ve been waiting more than 6 months…

Update 17 Nov 2020 – Pinterest finally granted the Photo Upload plug-in access to their latest Pinterest API and the plug-in has been updated to support it.

6 Sep 2018 – Picasa Web retires on 15 Mar 2019

Google have announced that the Picasa Web interface used by the Photo Upload plug-in is retired on 15 Mar 2019. The plug-in stops working with Picasa Web at that time.

The Photo Upload plug-in now has the Google Photos service available to it (introduced in version 5.0.9 in Sep 2018), which uses the new Google Photos interface instead of the old Picasa Web interface.

The Google Photos support in the plug-in has been written from scratch and is quite different to that previously included for Picasa Web. You can purchase a license key for the Google Photos service in this plug-in from the usual places. Unfortunately, due to the time and effort needed to create the new Google Photos support in the plug-in, there is no free transfer or discount when moving from Picasa Web to Google Photos.

There are some differences between the new Google Photos interface and the old Picasa Web interface. Most notably you can now use the plug-in to create albums on Google Photos, but note that Google only allows you to upload photos to albums created by this plug-in (i.e. you cannot upload to albums that you already have on Google Photos).

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 have announced that the old Picasa Web interfaces will be retired in Mar 2019.

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.

31 Jul 2014 Old “Picasa Web Upload” plug-in replaced by “Photo Upload”

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

The final version of the “Picasa Web Upload” plug-in is 1.5.8. If you have a version of the old Picasa Web Upload plug-in then please note that it is not possible to use it with Lightroom 7.0 or later. 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’s Picasa Web service.

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.

FAQ

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.

Update the plug-in from Lightroom Plug-in Manager

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: Work arounds for this Lightroom problem are 1) use the plug-in’s “Generate exports one at a time” setting or 2) use the Configuration setting “Temporary folder for exported photos” to override where the temp folder is.

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. Google Photos) 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.

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.

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.

Can I 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

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.

Comments

1,539 responses to “Support”

  1. Jacques M. Avatar
    Jacques M.

    Hi,
    It takes ages, and eventually freezes LR, to select a directory on my Amazon drive for publishing (28400 directories), 5Tb.
    is there any way not to have Photo Upload to rescan the whole drive and have ONE directory selected for good.
    Thanks.

    1.  Avatar

      Hi,
      Simply turn off the setting “Display full hierarchy in album list”:
      http://www.newpproducts.com/lightroom-plug-ins/photo-upload/settings/#Display_full_hierarchy_in_album_list
      Thanks,
      Rob

  2. Vladimir K Avatar
    Vladimir K

    The 500px uploader misses the original EXIF Lens field which is shown in the LR correctly. On the 500px in the published photos the Lens field is always empty. Please fix the 500px uploader.

    1. Rob J Avatar

      Hi,
      The latest plug-in now uploads the lens information from Lightroom. Please use the Update button to update to version 4.8.0.
      Thanks,
      Rob

      1. Olav Stana Avatar
        Olav Stana

        Rob,

        Upload to OneDrive does not work after your recent updates to 4.8.1.
        Prior version with 4.7.8 was no problem. It connects to OneDrive and verifies account, but gives error message:
        OneDrive does not permit uploading directly to the Root named “One Drive”
        I have paid Licence Key and Full Access.
        os

        1. Rob J Avatar

          You spotted a problem with the plug-in that is now fixed in version 4.8.3.
          Many thanks for your help testing the fix.
          Rob

  3. Andrew Koenig Avatar
    Andrew Koenig

    Facebook uploading fails intermittently on Windows 7. I’ll upload a bunch of images and a few of them will come back with the error:

    Facebook error: ‘HTTP/2 408, Unexpected network connection status (5)’

    where 5 represents the number of photos that failed. It is followed by a list of failing photos.

    If I republish these photos, they usually go through; but then they appear at the end of the album, rather than appearing in the same sequence in which they appeared in Lightroom.

    1. Rob J Avatar

      Hi,
      The plug-in (version 4.7.8) will now automatically retry when it receives a 408 error from the network connection.
      Thanks,
      Rob

  4. Florian Behner Avatar
    Florian Behner

    Hi,
    I’m not sure if my question is related to this plugin or if it is an issue of Lightroom in general.
    I have used a custom file naming scheme for my uploads using the element image number (Bildnummer in german). I was expecting that number to be unique for the photos at least in one collection. My problem now is that when an upload is interrupted due to connection errors and I restart it to upload the remaining photos this number starts at 1 again and overwrites the already uploaded images of my collection. The lightroom help is not giving any hint at the meaning when using publish services. Normally this image number should be unique all across the catalogue but this is only described for the import file naming settings. As I don’t know if the plugin is in charge in passing that numbers to lightroom I’m asking here.

    Best regards,
    Florian

    1. Rob J Avatar

      Hi Florian,
      The plug-in does not manage the file numbering, I’m afraid. This is a Lightroom capability. I did a few searches on Google and found that many people have asked the same question as you. Here’s one thread – https://www.lightroomforums.net/threads/numbering-on-export.28192/.
      I don’t think there’s an easy way to achieve what you need.
      Regards,
      Rob

  5. Bob Carlson Avatar
    Bob Carlson

    I am using Photo Upload for Facebook and Google Photos, and both I’m able to upload photos to. But for “Google Photos” when I create a new collection and upload them, I get an error message a few minutes later saying it cannot find so & so folder on Google Photos, and references version 4.7. After that I close the error window and click on “publish” again, and the photos are successfully uploaded.

    1. Rob J Avatar

      You were just a bit too quick with the publishing, the new collection had not finished being linked to the album on Google Photos before you tried to publish to it. However I’ve looked into this and done some optimisations to the plug-in, so now you can publish as soon as you create your Lightroom collection.
      Thanks for confirming that the update has now worked for you with version 4.7.5.
      Rob

  6. wolfgang Avatar

    I am trying to export a Lightroom Folder Structure (three levels) to a remote FTP location.

    I am positive that I have understood all the settings and set them correctly.

    After hitting “export” I see that at the FTP location folders do arrive, but in no way in the same structure than I had them in LR.

    _test_export
    …one
    ….1
    ….2
    …two

    for example arrive in the destination root folder as

    1
    _test_export
    …one
    …..1
    …..2
    …two
    one

    also files originally in a folder may end up in any other folder.

    most thankful for any input!

    1. Rob J Avatar

      You found a bug with the FTP part of the plug-in. It was not creating new folders correctly and causing the behaviour you experienced.
      This should now be fixed in version 4.7.4.
      Thanks for raising the problem and confirming it is now fixed.
      Rob

  7. Wade Tregaskis Avatar
    Wade Tregaskis

    Using 4.6.6 line breaks in the ‘Caption’ field aren’t preserved in Flickr uploads (they seem to be replaced with spaces, roughly). I’m not sure if this is a regression or if it’s always done this… I only just noticed it.

    1. Rob J Avatar

      The plug-in has always (for a very long time) replaced newlines with spaces for titles and summaries. Some upload services are sensitive to newlines and throw errors if they receive them from the plug-in.
      However I appreciate your comment that Flickr does support newlines. So version 4.7.4 of the plug-in now supports newlines in Flickr titles and summaries and in Picasa Web summaries.
      Thanks for getting in touch.
      Rob

  8. Jenn Avatar
    Jenn

    Do you know if smug mug will create a plug in to work with Lightroom 6.12? I had to upgrade to newer version of Lightroom when I bought the canon 5D mark iv. Thanks!

    1. Rob J Avatar

      Hi. Not quite sure what you mean. The Photo Upload plugin on this site works with SmugMug and the latest Lightroom. I don’t know what SmugMugs plans are for their plugin.
      Rob.

  9. Diego Avatar
    Diego

    Hello, I have pourchased a 500pxlicence for your plugin. I managed to upload a few pics then suddendly I receive the following error message “500px error: ‘HTTP/1.1 422 Unprocessable Entity, Error = An error occured while trying to create a new photo., Status = 422’ (1)”. Cannot load any pic now. I correctly did authentication. I use lso Flickr, Facebook and WordPress and they work. I am running V 4.7. Tia

    1. Rob J Avatar

      This was down to you specifying a keyword for a 500px photo that was more than 255 characters.
      Version 4.7.1 of the plug-in now trims the keywords automatically for 500px so you should not see this error again.
      Thanks for reporting it.
      Rob

  10. Tommy Avatar
    Tommy

    Hi!

    Why is LR become slow and unresponsive when i export .

    i have a powerfull computer so i dont understand why.

    Thank!

    1. Rob J Avatar

      When you export, Lightroom creates temporary copies of all your photos that are to be exported with all your edits applied. It does this at the start of your export in one go. So if you only export 1 photo the computer will only become unresponsive for a few seconds, but if you export hundreds then it may become unresponsive for a long time. This is simply Lightroom’s behaviour, not the behaviour of the plug-in. You may find this setting useful – http://www.newpproducts.com/lightroom-plug-ins/photo-upload/settings/#Generate_exports_one_at_a_time.

  11. Jose Rios Avatar
    Jose Rios

    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.

    1. Rob J Avatar

      Ah you found a bug, apologies. It’s now fixed in version 4.6.9.
      Thanks for reporting this.

  12. Felipe Avatar
    Felipe

    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!

    1. Rob J Avatar

      I can’t think of a way you can download the keywords/tags from Flickr, sorry.

  13. Robert Lawrence Avatar
    Robert Lawrence

    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. Rob J Avatar

      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

  14. Markus Eichhorn Avatar
    Markus Eichhorn

    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. Rob J Avatar

      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

  15. Ralf Avatar
    Ralf

    Amazon Plugin doesn’t work any more with the latest Lightroom version 6.12

    1. Rob J Avatar

      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

  16. Jose-Manuel Anguita Avatar
    Jose-Manuel Anguita

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

      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

  17. Steen Kroyer Avatar
    Steen Kroyer

    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

    1. Rob J Avatar

      Hi. You’re almost there. Tree Mirror is part of the package. Most people want to use Lightroom’s Export for Tree Mirror, see here – http://www.newpproducts.com/lightroom-plug-ins/tree-mirror/using-tree-mirror/.

  18. Frank Fernino Avatar
    Frank Fernino

    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. Rob J Avatar

      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.

  19. Ryan Avatar

    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. Rob J Avatar

      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

  20. Frank Fernino Avatar
    Frank Fernino

    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. Rob J Avatar

      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.

  21. Gert Mooij Avatar
    Gert Mooij

    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

    1. Rob J Avatar

      That option is no longer available. You’re probably aware, I’m sure, but in February 2017 Google changed what could be done via Picasa Web. This included preventing existing photos from being updated or deleted. See these notes – http://www.newpproducts.com/lightroom-plug-ins/support-faq/#7_Feb_2017_8211Google_Photos_Picasa_Webchanges_eg_albums_cannot_be_created.
      Wish I had a better answer for you!
      Regards,
      Rob

  22. Jake Wright Avatar
    Jake Wright

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

    Thanks!

    1. Rob J Avatar

      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

  23.  Avatar
    Rob J

    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.

    1. Rob J Avatar

      Hi – you found a bug, now fixed in version 4.5.7 of the plug-in. Thanks for confirming the fix works.
      Rob

  24. Scott Avatar
    Scott

    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.

    1. Rob J Avatar

      Hi,
      It sounds like you are only pressing Export once – i.e. to open the Export window. With the Export window open, you press Export again to actually do the upload – it is at this point that you choose the album on Zenfolio. See these instructions – http://www.newpproducts.com/lightroom-plug-ins/photo-upload/uploading-photos-export/.
      Thanks,
      Rob

  25. Seth Avatar
    Seth

    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. Rob J Avatar

      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. Seth Avatar
        Seth

        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!

  26. Phil Pasteris Avatar
    Phil Pasteris

    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. Rob J Avatar

      Hi,
      The plug-in tries to receive chunks of 1,000 albums at a time. Hopefully you’ll see 1,001/2,000 or similar in the future.
      I’m not sure if Picasa Web has a fixed limit on albums though. Having a quick search on Google gave this link that seems to indicate Picasa Web has a limit of 10,000 albums.
      http://news.softpedia.com/news/Google-Ups-the-Albums-Limit-in-Picasa-from-1-000-to-10-000-139165.shtml
      Rob

      1. Phil Pasteris Avatar
        Phil Pasteris

        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. Rob J Avatar

          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.

  27.  Avatar

    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. Rob J Avatar

      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

  28. Wade Tregaskis Avatar
    Wade Tregaskis

    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.

  29. Diana thornton Avatar

    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. Rob J Avatar

      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

  30. krista Avatar
    krista

    Is there a way to just sync metadata changes? I would love to be able to sync just descriptions.

    1. krista Avatar
      krista

      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. Rob J Avatar

        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

  31. Adi K Avatar
    Adi K

    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. Rob J Avatar

      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

  32. Will C Avatar
    Will C

    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

  33. alan Avatar
    alan

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

    1. Rob J Avatar

      No, I’m afraid not. Sadly it would also not be trivial to add this in the future.
      Regards,
      Rob

  34. Michael Avatar
    Michael

    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. Rob J Avatar

      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

  35. Robert Camner Avatar
    Robert Camner

    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. Rob J Avatar

      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. Robert Camner Avatar
        Robert Camner

        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. Rob J Avatar

          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. Robert Camner Avatar
            Robert Camner

            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.

  36. Falk Avatar
    Falk

    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

    1. Rob J Avatar

      Hi,
      You found a bug. It’s now fixed in version 4.3.7.
      Many thanks for working with me to confirm the bug is now fixed.
      Rob

  37. Mothra Avatar
    Mothra

    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.

  38. Dean McKay Avatar
    Dean McKay

    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. Rob J Avatar

      Hi,
      Google have sadly prevented 3rd party apps and plug-ins from updating and deleting photos.
      Please see this note – http://www.newpproducts.com/lightroom-plug-ins/support-faq/#7_Feb_2017_8211Google_Photos_Picasa_Webchanges_eg_albums_cannot_be_created
      Thanks,
      Rob

  39. Bobby Avatar

    My web site is hosted by ifp3. reminderphotography.com can i use lightroom or photoupload to upload to my site if so how

    1. Rob J Avatar

      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

  40. Pierre Poirier Avatar
    Pierre Poirier

    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)

    1. Rob J Avatar

      Hi,
      That sounds like you are trying to upload a photo to a “Private” gallery. SmugMug started to prevent this a few weeks back – I don’t know their rationale why (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).
      You need to change the gallery visibility to “Public” or “Unlisted” then the upload should work.
      Thanks,
      Rob

  41. Sten Palmqvist Avatar
    Sten Palmqvist

    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. Rob J Avatar

      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

  42.  Avatar
    Rob J

    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. Rob J Avatar

      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

  43. Mario Lischka Avatar

    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. Rob J Avatar

      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

  44. Brian Pibworth Avatar
    Brian Pibworth

    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. Rob J Avatar

      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

  45. E. Oonk Avatar

    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. Rob J Avatar

      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. Phil Pasteris Avatar
        Phil Pasteris

        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

  46. Petri Helenius Avatar
    Petri Helenius

    How do I get the location and Person tag infos to export to Facebook?

    1. Rob J Avatar

      Hi,
      Facebook does not allow a plug-in to set a photo’s location and person information.
      For example, see this note from Facebook:
      “Facebook strips all location metadata before publishing and resizes images to different dimensions to best support rendering in multiple sizes.”
      https://developers.facebook.com/docs/graph-api/photo-uploads
      Regards,
      Rob

  47. lorenzo codacci Avatar
    lorenzo codacci

    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. Rob J Avatar

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

        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

  48. Colin Begg Avatar
    Colin Begg

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

    1. Rob J Avatar

      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

  49. Kevin Estey Avatar
    Kevin Estey

    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?

  50. Howard Berliner Avatar
    Howard Berliner

    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 to Deivis Cancel 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.