Support FAQ

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

Latest support news

7 Feb 2017 – Google Photos (Picasa Web) no longer allow albums to 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 updated plug-in, and you can use the Google Photos website to create your albums before 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.

Photo Upload: Error authenticating with [service]
No authentication information returned from [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].

Error communicating with [service]: ‘Unexpected...’

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.

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

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.

Plug-in cannot be authenticated

  1. Ensure you have an internet connection and that Lightroom is not being blocked by your firewall.
  2. Set up your online service (i.e. Picasa Web, OneDrive etc.) account and ensure you can access your albums from a Web browser before authenticating the 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 give 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 give 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.

721 thoughts on “Support FAQ”

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

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

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

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

  5. I have a paid license. Authentication with Picasa (Google Photos) went well, BUT when I hit export I do not get the option of a new album and must choose an existing one.

    Thanks
    Mike Mallen
    Santa Barbara, CA

      1. Rob, Mike,

        This is a ill-advised change by Google. Rob now has to redesign or remove the Create Album function *immediately* to ensure his excellent software still works. Sorry Rob, this is NOT fair to you.

        I will get my comments on this change to the Google comments page.

        Phil

  6. Thanks for continuing to support Google Photos, even though they have limited album creation. There is no other service, commercial or otherwise that offers exactly what Google photos does for archival and sharing. I have no problem dealing with manually creating the album on their website. At least you are still able to download and remember a list of available albums. The amount of lost time is negligible once you get used to the workflow.

  7. The recent changes in Google Photo are driving me bananas. Even in the web UI it now seems impossible to create a new empty album … one needs to select at least one image which is already in google photos … makes my workflow with LR useless as I’d like to control it all from within LR with your plugin. I think I am done with it … just got worse and worse after they discontinued Picasa. Any advice? Anyone came to the same conclusion?

    1. I don’t blame the plug-in for Google Foto but the handling is currently a complete mess.

      Just one thing: obviously the problems are known – so you should not offer that plug-in in the moment or clearly describe the problems in your sales pages. As of today I would not buy it again.

      1. Understood. Some people do need to continue uploading to Google Photos, so the plug-in is still very much useful for this purpose. I’ve added a note to the features page to highlight the changes that Google have made and that the plug-in can no longer create albums.
        Rob

  8. Hi Rob

    I have just finished uploading over 50,000 pics and up to now if i deleted a pic in LR6 it would ask me if I wanted to leave or delete pic on service. If I chose remove from service it performed perfectly. Now for some reason I get this message “Photo Upload 4.1.9: Photos not deleted on Tree Mirror” Can you tell me if I’ve done something wrong please. I will send log. Thanks Geoff

  9. Rob –

    I’m impressed. Just uploaded a load of images to Google Photos and got that 501 error. I saved logs, screenshots etc ready to come here and report the bug to you, but you’d already fixed it!

    This change makes using Google Photos a bit impractical, really. Which of the various hosting services would you recommend, based on reliability and ease of use of the upload service? I’m looking for a simple service that will automatically keep a couple of albums in sync (maybe 200 photos in total), and provide easy to use links that I can send to selected people only to view the albums. Just like Picasa/Google used to do!

    Mike

    1. Picasa Web (Google Photos) was the original reason this plug-in was created, so it is a real shame that Google have now made it much less useful and accessible.
      Many folks like Flickr – this is another ageing photo platform but it seems to be fairly reliable. And then there are the newer non-photo specific services like Amazon Cloud Drive, Google Drive, OneDrive and Dropbox which are probably the most robust of the online file services.
      Rob

      1. I’ve been playing with the Dropbox version of your plugin and it seems to fit my purposes – and I have 50Gb of Dropbox space to play with, so that could work well. But I noticed that although the plugin talks about creating Dropbox albums, it doesn’t actually do that – it creates a Dropbox subfolder instead. It’d be quite neat if it could also create Dropbox albums?

  10. Problem: Upload to Google Photos
    Version: 4.1.8
    Message: Photo Upload 4.1.8: Error uploading to Picasa Web … Could not create album “PanoramaEttlingen” … Error reported by Picasa Web: “HTTP Status 501, Insert is no longer supported.
    Photo Upload works with One Drive without problems.

    Klaus

  11. The manual of tree mirror says in Lightroom 6CC I should select the top folder of the tree that I want to export from Lightroom and press “select all” in the menu. All files in all the subfolders should be marked then – but that does not happen: Only the files of top folder level are marked. So how can I export the whole tree?
    It seems to work when I select the top catalogue folder – but then thousands of pictures that I don´t want to export are included…

    1. I can’t actually find the information you are referring to. Can you share a link to the page which tells you to “select all” etc.?
      If your Lightroom folder tree in the Library module is not showing the contents of sub-folders then perhaps you have not turned on the Lightroom option “Show Photos in Subfolders”?

  12. I have a licens for FTP upload. When I try to create a second Upload the first ones account is predefined in the account settings. I do Add a new account but that does not seem to have any effect as the Account status is: “Retrieving account information…” and nothing more happens.
    Site name: myftp
    Site url: ip address
    Port: 22
    Start directory: tried a specific dir name and also empty
    User name/password: I have verified with Filezilla that I can connect.

  13. When i upload in picasa web album i get thismessage: Picasa web error: HTTP: Status 400, HTML; frankly i dont get how i can solve this issue as seems with google photos the problem not with the uploader.
    Any hint i can try?

      1. Hi Rob,

        This is still a bumpy ride with your update, which I really appreciate! I am getting some strange inaccessibly errors separate from the 400 error. I can send you a log file if needed. As a programmer, I know there can be transition issues. I will keep an eye for your updates.

        All is not lost however. I exported all my LR files separately and then upload them to Google Photos as a work around this weekend before I updated your plug-in.

        Keep up the good work!!! You have an excellent product!

  14. Why when I upload to 500px do photos go to Untitled Gallery instead of photos? Is there a place in settings to direct the upload?

    1. Hi,
      If you are using a publish service then you can right click on the album in Lightroom, choose “Edit Album…” and then specify where the album points to on 500px. Or you can create additional albums and do the same.
      Alternatively if you are using export rather than publish then you will get a list of albums to choose from after you’ve clicked the “Export…” button.
      Regards,
      Rob

  15. Wonder if your Facebook publisher can upload to the cover photo (I’m not sure I see all of the features with a trial version)? My thoughts are that it would be useful to have a smart collection in the publisher service that would reference one photo which could be pushed out to Facebook to replace the cover photo on the main page or a created page.

    1. Hi,
      I did some research and it seems that Facebook does not allow any app or plug-in to change the profile picture of a Facebook user account.
      Sorry, your idea sounded great!
      Thanks,
      Rob

  16. Hi ! When I publish to FTP many of the photos are marked as “Changed photos to be published again” and then I have to publish them again. This happens almost every time I publish an Album. Even when I republish all photos in an Album the same problem occurs but not with the same photos so it seems it has nothing to do with the photos themselves.
    I use standard FTP without any encryption.

    1. Hi,
      Assuming you really have not modified the photos in any way then you’ve probably come across a known problem with Lightroom published collections. The Photo Upload plug-in really does not make any changes to a seemingly random set of photos after they’ve been published. As I mentioned in the reply to the previous comment there are multiple discussions about this Lightroom problem you can search for – this is one of them:
      https://feedback.photoshop.com/photoshop_family/topics/modified-to-republish-problem
      I’d suggest keeping the pressure on Adobe to fix this and reporting the problem to them.
      Thanks,
      Rob

      1. I should add that you can use the Lightroom menu item “Mark as Up-To-Date” to move the photos back into the published category without actually publishing them again.
        Rob

        1. Thank You Rob.
          I will surely file an error report to Adobe. I saw there are many users that already did.
          Sten

  17. Hi

    Can you tell me please why photos I’ve just uploaded for the first time suddenly become “Modified Photos to Re-Publish” when no mods have been carried out. This is really frustrating as i am uploading thousands of pictures (not all at once!) and its doubling the time the task is taking.
    Thank You

    1. Hi,
      Assuming you really have not modified the photos in any way then you’ve probably come across a known problem with Lightroom published collections. The Photo Upload plug-in really does not make any changes to a photo after it’s been published. There are multiple discussions about this Lightroom problem you can search for – this is one of them:
      https://feedback.photoshop.com/photoshop_family/topics/modified-to-republish-problem
      I’d suggest keeping the pressure on Adobe to fix this and reporting the problem to them.
      Thanks,
      Rob

  18. When I upload to Google Photos with any video setting (even ‘Original, unedited video’) the videos never viewable. It says ‘Your video will be ready soon’ forever (I have waited for days, and eventually they get automatically removed from the album).

    This is currently making the plugin unusable for posting an album with mixed photos/videos (all of mine).

  19. Hello, this is probably more of a google thing than your plug in, but your plug in requires uploading to an album, but I found that if you publish to an album, all the pictures you select appear….however, if you just go to the “photo’s” area in google which is where you can search and view by date, the photo’s published don’t appear…which is a bummer…

    Perhaps someone can outline their preferred workflow, as here is what I am trying to accomplish.
    1. I currently have my phone set to backup photo’s to my google photo’s automatically (for convenience and quick posting to facebook from my phone for smaller events).
    2. I also download the photo’s from my iPhone to Lightroom to ensure I have the full versions and if I want to do any editing on them.
    3. If it is an important event that I take pictures with my Nikon D4 and/or my iPhone, my thought was I could use this plug-in to upload the photos to google photo’s so all my pictures would be there…so I select the ones I wanted to publish, use the plug in to put them in albums…but…as stated above, this doesn’t work out to well because the photo’s don’t end up in my main photo’s library…just the album.

    So…perhaps my workflow should be…
    1) don’t auto upload photo’s if I know I am going to be shooting with dual cameras.
    2) use plug-in to export my collections to .jpg
    3) use the google uploader (which will upload the photo’s to google photo’s general library)
    4) create my albums in google photo’s instead of lightroom to share with others.

    Would be interested if anyone else has a workflow already figured out….and thanks in advance

  20. Hi Rob, i used the “OneDrive modul of photo plugin with no problems. Thanks for it.
    Now I try (the licensed) “FTP” modul and went crazy.
    – I made all settings like default
    – I filled in all required URLs, accounts, password, etc.
    Exporting a picture leads into the correct creation of the needed path on the target FTP system. (Verified with FileZilla).
    But the picture itself will not be transferred to this new path. (not any transfer) Lightroom shows the bar for exporting the file but no file is available at target http://ftp…Do you have any ideas?

  21. Hi Rob, The Creative Cloud app says “You installed add-on Photo Upload Amazon Cloud Drive”, however I cannot find it anywhere in the LR plugin manager. What am I doing wrong (I restarted LR, still nothing)

  22. Receiving the following internal error, when exporting LR5 pictures to Google Drive:
    Service_GD.lua:772: bad argument #1 to ‘ipairs’ (table expected, got nil)

    Export process stalls out and does not transfer to Google Drive.

    1. I think you’ve found a bug!
      This should now be fixed in version 4.0.9 of the plug-in. Please use the Update button to get the latest version.
      Thanks,
      Rob

  23. Hi, i use the Amazon Drive plug in.
    I use the way “Album”.
    Unfortunately creates the plug in only folders!
    This requires no plugin!

    Can i create a real Album in Amazone Drive?
    Thanks for your answer.

    1. Hi,
      Amazon do not allow apps such as this plug-in to create Amazon Drive “Albums” at this time. Amazon may allow this in the future, but until then the plug-in creates Amazon Drive “Folders” for you.
      Thanks,
      Rob

  24. Sorry, little question again

    I just looked into your google photos plugin. So, google photos has 2 options, as you know.. unlimited till 16mp and limited in original size. How does this work with your plugin? There is nothing to choose. Or does the plugin automatically does what I have selected in my normal google photos account?

  25. Hello there

    I want to buy some of your plugins (def. smugmug).

    But before, I have a little question. I am new to lightroom, just finished my folder structure, tagged photos and so on. Now i want to use your plugin to automatically upload some (not all) folders to e.g. smugmug. So, i mean, if I change a tag or delete photos or add new ones in a specific folder, will lightroom automatically do the changes on the website? Does the publish function do this or do I have to create smart folders first and add the smart folders to your plugin?

    1. Hi,
      If you want Lightroom to automatically track what photos have changed and upload those then you probably need to use Lightroom’s publish services. You would create a publish service and then create albums (inc. smart albums) within the publish service that contain your photos. Lightroom would tell you when photos in that publish service have changed and you can press Lightroom’s “Publish” button to upload the changes.
      Thanks,
      Rob

      1. Thx a lot. I am german and I am not sure if I understood you correctly. Do I have to create albums or smart albums within the publish service? I think I need smart albums just because I use raw and jpg and just want to upload the jpgs.

        Are sites like smugmug capable of using folders? Or do I have to choose every subfolder manually?

        Thx for your quick and nicely answer

        1. Lightroom allows you to have many publish services. e.g. You would create one for the Photo Upload plug-in uploading to SmugMug. You would then need to create albums or smart albums in the publish service. You would add your photos (JPGs or RAWs) to your albums (if you used smart albums you could be cleverer here).
          SmugMug can use folders, but not all services allow folders.

          1. Ok, thats really good. I just tested the official plugin of smugmug, but later I will use yours. But, 2 little questions left and I hope you can answer them.

            1. You said that smugmug can use folders. But how do I do that. I know how to use smart folders, but i meant something like –> Photos\City01\Example1 (2,3,4,5,6… and so on). So that I only need to add City01 and everything in this will be published too (with their different folder names) and isalso shown on smugmug itself like this? Is this possible with your plugin? If I right click on the official plugin, lightroom just allows creating a album, smart-album and folder (what means folder in this case?)

            2. If I create smart folders in which I use the rule, that the album-name must be exactly like the folder-name on my harddrive (and of course jpg only), to ensure that it will be uploaded like it is shown in lightroom, what happens if I have to change the album-name? I tested it and lightroom (cause of the rules) don’t changes it in the publish service. Do i have to manually edit the rule in the smart-album if I change a folder-name on my harddrive?

            I know, much to read and maybe a little bit confusing (I am german 😉

          2. Hi,
            To answer your questions.
            1) I don’t use the official SmugMug plug-in so I can’t really comment on what you can do with it – but what you’re asking is probably not handled by their plug-in. However if you the Photo Upload plug-in then you can create an album that is just in Lightroom and then use the “Export sub-folder hierarchy” setting with a base path of “Photos”. When you publish the photos you will get the folders “City01\Example1” created on SmugMug.
            2) Yes, if you use smart albums with hardcoded folder names in your rules then you will need to manually keep those up to date.
            Thanks,
            Rob

  26. I’ve updated to the latest version and now can’t export and documents. The following error command appears:

    En internal error has occured: ..\common\NPPCurl.lua:386: attempt to index field ‘NPPlogger’ (a nil value)

    Is this just a coincidence?

    1. Ah – many apologies! You found a bug introduced today. It’s now fixed in 4.0.2, can you kindly update to that version?
      Thanks for letting me know!
      Rob

Leave a Reply

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

New P Products