Categories

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

Contents

Latest support news

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.

Support - Plug-in Manager - Update

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

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

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

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

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

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

Support - Plug-in Manager - Incorrect folder

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

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

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

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

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

Authentication problem – Error authenticating with [service]

Support - Firewall

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

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

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

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

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

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

What is the Export Location used for?

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

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

Lightroom says my computer is out of disk space

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

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

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

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

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

Note: 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.

1,481 replies on “Support FAQ”

This is a useful product. It would be good to have a few additional features:

1. Add a feature to use the folder name as the default album name for export
2. Add a feature to publish directly from a folder imported into ligthroom (not sure if you are limited by lightroom API’s here)

Hi,
Thanks for your comments.
1. This is a great suggestion and should be included in the next release.
2. Sadly Lightroom provides no way for a plug-in to hook into the Import process. Sorry.
Best regards, Rob.

Hi,
Thanks for you suggestion:
“Add a feature to use the folder name as the default album name for export”
This feature has now been added to the plug-in. Please give it a try (version 1.8.2.1. and higher).
Thanks,
Rob

Hi,

how do I upload to subfolder in Google Drive?

The path I sett is: Meine Ablage\Uploads\Pasta e Olio\PANO

The path Photo Upload retrieves is: Meine Ablage\Uploads

Unfortunatelly I can’t upload to \Pasta e Olio\PANO.

What do I have to do?

Rgs
Norbert

Hi Norbert,
During the Export process you can choose your subfolder in the album selection window by pressing the “>” button.
However when I checked just now I found a bug in the new version of the plug-in released today (version 1.8). Are you using version 1.8? If so, I’ve just released a fixed version, 1.8.1. Could you try it?
Thanks,
Rob

I purchased a license for Photo Upload for Facebook earlier today. Unfortunately, my mail server was misbehaving and I appear to have lost the license info. Could it be resent to me?

Hi,
Thanks for the suggestion.
The plug-in now allows you to set the privacy setting for uploaded photos.
You will need version 1.8.
Go to the plug-in settings in Lightroom and use the Update button to get the latest version.
Thanks,
Rob

I’ve been uploading images from Light Room to Flickr with your Plug-in with great success until this afternoon when I’ve run into this problem.

Account Status is “Not Authorised with Flickr”. I follow the instructions but just get the following message poping up ” Photo Upload: Error authenticating with Flickr 95 – SSL is required.

Help would be appreciated.

Hi, find the Update button for the plugin in Lightroom’s Plugin Manager. I released an updated version yesterday.
On Fri Flickr changed their APIs with no apparent warning so it caught the plugin off guard. Should be all fixed now.
Could you kindly report back to confirm it is working?
Thanks!

Hi, that’s quite a hard comment to advise on. I’d suggest following the installation instructions again – maybe you’ll find your existing plug-in by doing that?
Thanks, Rob.

Damn it!

Upload to Flickr worked yesterday from Lightroom 5, today it says “not authorized”. Tried to authorize, get an SSL error.
Upgraded to latest version of the plugin.
Same problem.

I need this to work. Consistently.

Agreed! Flickr have changed their policy overnight to require HTTPS links not HTTP ones. I’ve sent you an email asking if you want to test out a new version of the plug-in prior to some formal testing over the next few days.
Thanks, Rob.

got the trail version and finally got to install and show up in LR 5.5 in plug in manager. However it does not show up in Export drop down menu even after restarting LR.

Worked it out … I was expecting this to work through the drop down menu (as shown on Adobe site) instead of selecting Export menu and then selecting.

Got it to work as trail version. Thanks

Hi,
Thanks for getting in touch.
I think using the plug-in from the Export menu or Export button is the simplest.
The screenshot on Adobe’s website shows the menu for Publish Services.
Regards,
Rob

Hi,
I purchased Picasa plug-in last year, but doesn’t work anymore.
It says “missing link”. I haven’t keep the registration #. Is there a way to retrieve the registration number ?

Thanks.
Yuki

Two questions:

(1) I downloaded the file to test the plug-in for my Picasa account before purchasing the licensed version. When I select Export, I get the following message: “You have the free, unlicensed version of the plug-in. Your photos will be uploaded to the default album (Drop Box). Upgrade to the licensed version to select an existing album or create a new album.” Is it possible to do a test run before paying for the license?

(2) I also have a blog with WordPress. Is it possible to set up the plugin to work for both applications?

Thanks!

Hi,

1) You can only create new albums with the fully licensed version. Otherwise you are limited to uploading to an album called “Drop box”.
2) Yes – the plug-in supports connections to lots of different upload services. You can use the plug-in to connect to WordPress, sure. Lightroom allows you to create “Export presets” – this will give you quick access to Picasa and WordPress setups.

Thanks.

I just downloaded the program and purchased the license. So far, it appears to work great. The instructions were simple to follow. I think this will make organizing my photo albums for upload much easier. Thanks.

I’m getting an HTTP 413 error when trying to upload a relatively large (~200 MB) video to OneDrive. It looks like the transcoding completes and then the resulting file fails before the upload takes place.

It appears that OneDrive currently has an upload limit of 100MB via the APIs that the plug-in has to use:
http://social.msdn.microsoft.com/Forums/en-US/c4aaa90c-dc75-441f-9b30-f5c45e402ac4/limitation-on-api-requestfile-size-limitationresume-upload?forum=onedriveapi
This is not ideal – neither Google Drive nor Dropbox has these limitations. I’d expect OneDrive to change their policy at some point, but I don’t think there is anything the plug-in can do until that time.

Hi,
I have tested this on my self hosted website and it authorises fine.

The installation notes say:
“For self-hosted WordPress sites, please ensure you have the Jetpack plug-in and have enabled JSON API in the settings. You do not need to do this if your site is hosted on wordpress.com.”
Do you have this installed? Only self-hosted sites need it.

I’ve sent you this in an email too – I’m not aware of anybody else have the same problem so hopefully we can get this fixed quickly.
Thanks,
Rob

For self-hosted sites, it appears there is an error introduced in JetPack 3.0.2. The previous version of JetPack works fine, and after reporting this to JetPack I’ve successfully tested a patch for the next version (3.1).
Please be aware that authentication does not work with JetPack 3.0.2!

Feature request: Plug-in Settings, Privacy. Can you look into adding an option for Only you? Only you is the equivalent of Not Shared (no link in Google+).

Also, are you planning to move to Google+ permission terms and a Google+ page opening after export vs. Picasa?

Hi, thanks for the feedback.
For your privacy suggestion, does the existing setting for album privacy work as you request? You can choose new albums for Picasa Web\Google+ to be public or private.
Google will automatically redirect you to the Google+ page when the album opens. You may have disabled this in your browser – there is a cookie called “noRedirect” which you may have unknowingly set to 1 instead of 0 by choosing the redirect option in the web UI. This is a bit technical, I know, but it is the way Google provides for you to change between Picasa Web and Google+ web links.
Google+ is powered by the old Picasa Web APIs. This really limits how applications and plug-ins can communicate with Google+ and is why you see many of the old Picasa Web terms still in use.
Thanks,
Rob

I bought the full license for Box.net, and will probably get the Google Drive one as well, but is there a way to keep folder retention? I just uploaded 2000+ files to Box and walked away. When I checked on it, I saw that the export function literally just threw all of the photos into one folder and called it a day..

Hi,
Ah… keeping part of each photo’s folder hierarchy (it is normally only part of the hierarchy) in the export is high on my to-do list. But it’s not there today as you notice.
You can of course export one folder at a time – but that will not be pleasant for 2,000 photos in different folders.
One alternative that exists, but is not perfect, is to use the Tree Mirror Export plug-in from this site. This allows you to export photos directly into a publish service AND retains the folder hierarchy for each photo. Once you’ve done this using Tree Mirror Export then the next step would be to publish everything, which should be as easy as one click on Publish.
The downside with this last approach is that Lightroom insists on photos being in publish service folders/albums that do not have sub folders. If you try out the plug-in you’ll see the limitation that each photo folder has an extra sub folder called “Album” to work around the Lightroom limitation. You may be able to live with this.
I’ll get thinking about the capability you ask for though in Photo Upload and will get back in touch.
Thanks,
Rob

I use Lightroom 5 and use Photo Upload to put up pictures on Picasa. This has worked really well for a long time up until a couple of weeks ago when I posted a new album. But suddenly today I cannot add a new album and it says “Unknown service does not support creating albums”. I have updated the plug in but it doesn’t seem to help.
Please advise!

Hi There, I’m trying the plug in out at the moment and have managed to get it working with Google but can’t seem to get any joy with WordPress?
It says ‘wordpress can’t create folders’ so I don’t know what to call the folder that I create in the Publish service. The authorising goes okay and it picks up my various blogs just can’t get any further. any thoughts?
Gordon

Hi! WordPress doesn’t really have the concept of folders or albums. If you want to upload to WordPress use the plug-in via the Export feature in Lightroom. I put a very brief summary together to compare what you can do with the different upload services (they are all different) – http://www.newpproducts.com/?page_id=4083.
That should help. Thanks for getting in touch.
Rob

I seem to have lost an album – it is not showing in my Picasa Albums after I uploaded it via photo upload. I do not use and do not want to use G+ for photos but fear it may have got sucked into that vortex somewhere.
I have since gone back to the old picasa web uploader to get them to Picasa.
Still wondering where they went though !!

Not really sure what to say. “Photo Upload” actually does the same as the older “Picasa Web Upload” plug-in, so your photos will be somewhere. I’ll drop you and email and if you’re inclined you can send me you log file and I can see if that helps identify where your photos went!

Can I use Photo Upload to upload to multiple sites? Say if I wanted to have business stuff stored in one place and personal in another.

Yep – you can do that by using the “Add\Refresh” button to add multiple accounts for each upload service. Give it a go – you don’t need to buy a license to try it.

Hi, I’m not sure I understand, sorry. TME uses the export settings you have applied in the Export window. Have you checked your metadata settings? Or perhaps, could you elaborate on what you mean? Thanks.

Hallo,
is it possible to upload to two different e.g. box-accounts with your plugin?
Would be very nice, because I need to upload photos to my business box-account as well as to my personal box-account.

Thanks for your answer.

Hi. The answer is absolutely yes. I use this feature all the time.
You can use the “Add/Refresh” button to add multiple Box accounts to the plugin.
Then you can choose the account you want to upload to using the “Account” drop down list.
I use a Export User Presets to store my most used export configurations.
Thanks.

I love your plugin and have used it successfully to publish to Google+, but am not getting the WordPress publishing to work. Clicking on any of the options, such as ‘create album’ or ‘create folder’ just result in a dialogue box that says ‘WordPress does not support creating albums/folders’. I’ve tried dragging a single image to the Publish menu, but it doesn’t activate anything. What am I missing?

Hi. Thanks for your comment. Each of capabilities the upload services offer are different – and WordPress is the most different. It does not have the concept of folders or albums to keep photos in. They are all uploaded to the Media library. Therefore this limits what the plug-in can offer within Lightroom for WordPress. I put a table together because WordPress was so different – http://www.newpproducts.com/?page_id=4083. For WordPress, you need to upload to it from the Export button/menu.

Dear Sirs, I have a licensed Lightroom on two computers – PC and laptop, in line with license agreement. I have bought PhotoUpload for PC (it is great tool), can I use the same license on my laptop or should I buy another license ?
Best regards – Jacek

Hi. Thanks for the kind words and for getting in touch. For licensing simply follow the licensing for Lightroom. I.e. you’re fine to use the plugin on a PC and a laptop. Thanks.

Is there any way to change the name of the destination folder for the exported images?

For example:

(ORIGINAL FILES)
MAGAZINE PHOTOS
-2014
–04-04-2014 – Magazine Shoot
—originals
—-filename-001.dng

(DESTINATION DIRECTORY)
MAGAZINE PHOTOS
-2014
–04-04-2014 – Magazine Shoot
—TIFFS
—-filename-001.tif

Thanks in advance for your help!

Hi. I don’t think the Tree Mirror Export plugin can do changing the base folder and changing a sub folder (I.e. originals to tiffs). My best suggestion would be to use this plugin to export in tiffs to the new base destination. Then search on the internet for a renaming utility that will rename the originals folder to tiffs as part of a bulk operation. I’ve seen such things for PCs but not tried for Macs.

I bought photo upload. I am trying to export a jpg version of my entire lightroom catalog to dropbox using the publishing service. I want lightroom to give dropbox the images in folders so that there is some kind of structure in dropbox and I dont have to scroll through 3000 images to find the one i want. Is there a way to make photo upload publish to dropbox with the directory structure?

Hi. I think you might need to look at another (free) plug-in from this site called Tree Mirror Export (http://www.newpproducts.com/?page_id=2877).
The docs aren’t quite complete for that plug-in, but it allows you to export the photos to a new location and keep part of the folder hierarchy.
The feature that is not documented is that you can export the folder structure to a publish service. So for you, you can create publish service albums based on your folder hierarchy. Then you would publish the albums to Dropbox. I’ll give it some thought and and see if there is an easier way. Thanks.

Thanks for the response! I did look into that but I’m confused on what it is doing. How would I update the folders? Export all again? Would it re upload ones that didn’t change?
Also it appears that it doesn’t include sub folders 🙁

Thanks thanks 🙂

Well thinking about it some more, you could use the Tree Mirror Export plug-in to do a one off export of your entire photo collection (assuming a common base folder) to a separate folder location and save the photos as jpegs. You could then use the Dropbox PC/Mac interface to copy all those jpeg photos to Dropbox cloud storage?

Right, I can do that with a lot of plugins. But I don’t have a lot of storage space on my macbook so that’s what I liked about ur plugin, how it up loads directly to the cloud.

Thanks Michael

Purchased a new license (former licensee of Picasaweb Upload Plugin) and did not receive an email. I am hung out to dry waiting for this since I upgraded to LR5.

Hi. You should have received your license key. I’ll resend it now. Can you confirm that you’ve got it and perhaps check your junk email? Thanks.

Tried to donate for Tree Export, but PayPal insisted on me giving my county in my address field. The only options were counties in the UK. I live in the US.

Hi, I certainly appreciate you attempting to make a donation. I’m pretty sure there is nothing UK specific about the link. I’ve just tried the link and PayPal asked me to choose my country at the top of the form – I could certainly choose United States. Thanks.

So I bought $45 worth of plug-ins and installed them (perhaps incorrectly). I entered my lic # in each (authorization recognized)
I re-started LR 5.3.
I selected a photo to upload to FB
In plug-in manager, I selected the appropriate plug-in which was in the enabled state
I clicked “Done” NOTHING HAPPENED
Same for rest of the plug-ins

Hi,

First of all, clicking “Done” in Lightroom’s Plug-in Manager does not upload any photos. Lightroom’s Plug-in Manager is simply used to install plug-ins.

Have you authorised the plug-in with each of your online accounts? Follow these instructions:
http://www.newpproducts.com/?page_id=3353

When you’ve authorised the plug-in then follow the instructions on this page.

Thanks.

I purchased the Picasa web upload but did not get the email with license number and instructions. Can you please re-send? Thank you.

I’ve been happy and content with using the picasaweb plugin; that is all I needed. However, a hardware crash forced me to move to a new PC and re-install LR4, which went without a hitch. I thought, aha, good opportunity to put in the new version “Photo Upload 1.5.8” – I still keep the old-email with the license, which is still good, but LR4 balks in working with Photo Upload when it is called upon.
Error: An internal error has occurred: Account.lua:85: attempt to index global ‘NPPUtilities’ (a nil value). So I go back to picasaweb, and every one is happy.
Same error message when I try to authenticate the picasa account.
Hope my experience is useful for some one. I am OK with old picasaweb.

Hi,
Sorry you had a problem with the plug-in. I released the 1.5.8 version of Photo Upload yesterday and accidentally included the error you reported.
The plug-in has now been replaced with 1.5.8.1.
Really sorry – but many thanks for reporting it. It should now be fixed.
Thanks,
Rob

1. The ‘Installation Instructions’ link brings me to an “Instructions for Use” discussion, which assumes the plugin is up and running.

2. I downloaded and extracted all .zip files. My LR 5.3 CC Plugin Manager does not find anything when I try to ‘add’ and navigate to the download folder…

What am I missing?

Hi,
Oops – yes that Installation link wasn’t directing you to the right place. I’ve fixed it now.
Could you try following the proper installation instructions?
I know a lot of people have followed those instructions and I haven’t had any recent feedback saying people were getting stuck, so please let me know if I need to add further help. Adobe do not make installing plug-ins particularly easy so do let me know if I can make my instructions easier to follow.
Thanks,
Rob

Wham, Boom! Success.
That’s all I had to do ~ read your directions and pay attention.
Thanks for fixing that link, I’m up and running just fine.
Your very quick and generous comments in the email to me are greatly appreciated.
Have fun.
mike

Hi,
I think yes, but I am not Facebook expert. When you authorise the plugin against a Facebook user then if you have multiple accounts for pages then they are presented for you to choose from.
The best option for you is to try the plugin for yourself. You don’t need to buy a license to check if the plugin allows you to upload onto a Facebook group page.
Let me know how you get on.
Thanks,
Rob

Hi,
I’ve sent you an email asking for more details.
I can’t reproduce this on my machine (I can upload to SkyDrive just fine), so will need some more details from you.
Thanks.

hallo,
when I try to upload my photo on Picasa, I get this message by LR4:
————-
Please update your plug-in.
This plug-in is not compatible with Lightroom 4.4.0.891433.
Update your plug-in from Lightroom’s Plug-in Manager using either the ‘Update’ button or the ‘Visit Web Site’ button to download a more recent and compatible version.
————
I have downloaded the plug-in today (jan 9th 2014)
txs in advance for your support.

RP

Hi Rob,

I’m guessing your replies timed to start here (9 January 2014 at 2:41 pm) (GMT if it’s my local time) are for me (I don’t see my comment, but that may be me).

But if so, yes, it’s working for me at least to log on to Flickr, which is great, thanks.

There is one little problem though… 😉

I tried uploading to Flickr and was told “Please update your plug-in [I grabbed 1.5.5]. This plug-in is not compatible with Lightroom 3.6.0795620″…

(And according to LR’s update this is the latest LR. Well, the latest 3.x version, at least)

Thanks for such a quick reply earlier, though.

Rob

Can’t upload to google+ (PicassaWeb) any more.
I have version 1.5.5 downloaded from this website and installed.

Error:
Photo Upload: Error uploading to Picasa Web
Please update your plug-in.
This plug-in is not compatible with Lightroom 5.3.0.938183.

I’ve read the FAQ, but I’ve downloaded it from your website already.

Thanks!

Hi,
I can almost certainly guarantee that even though you may have downloaded 1.5.5, you won’t have installed it correctly.
From Lightroom’s Plug-in Manager, choose the Photo Upload plug-in and then look at the Status section.
What version is reported there?
I can promise you I use the plug-in with Lightroom 5.3 with no problems at all.
Thanks.

Hi Gilberto,
Thanks for highlighting the version problem. This is definitely a bug that I introduced today and I can only apologise.
It is now fixed in 1.5.6.
Could you kindly update your plug-in and confirm this?
Thanks,
Rob

Hi there,

Just excitedly grabbed it as I’m still using LR3 and I wanted to use something better than the build in Flickr extension.

But when I try to Add/Refresh a Flickr account I’m told “Photo Upload: Error authenticating with Flickr Could not retrieve authentication URL for Flickr”.

A few other services seem to open a web page in my browser with no problems.

Is there a XML config file that I can update the URL for Flickr (assuming I can find it in the API docs) that I’ve missed (or is it just fixable)?

Thanks
Rob

Hi,
I fixed a bug similar to what you reported in version 1.5.2 of the plug-in two days ago.
Could you check you have the latest version (which currently is 1.5.4)?
Thanks,
Rob

I have just purchased licences for
Dropbox
Flickr
Facebook
Box
However with the exception of Dropbox I am unable to enter the licence number as these three are not listed when it comes to enter the licence number

Regards,

Iain

Hmm – so are you saying you only see the text for the Dropbox service?
What version of the plug-in are you using?
The list of services is taken from all the files in your Photo Upload plug-in folder that begin with “Service_”. The Dropbox service is in a file called “Service_DB” and the Flickr one in a file called “Service_FL”. Do you have a file called “Service_FL” in your plug-in folder?

Issue resolved it was an older version of Photo upload that I downloaded this morning not sure how that happened.

another issue I have is an error when trying to authorise Photo upload messages states “could not retrieve authentication URL for flikr”

Ok – Flickr authorisation should now be fixed in the latest Photo Upload (1.5.5).
Could you kindly confirm once you given it a go?
Thanks!

I have updated the plugin to 1.5.6 and it works for me thank you for prompt support.

Sorry to those of you who had issues with update 1.5.5. which was an update created to resolve my authentication issue to flickr.

Regards,

Iain

Hi!
I have noticed that geotags of photos do not appear in Google + albums. This Function not released in the Photo Upload?

Hi,
I’ve just done a quick test and the photo I uploaded to Google+ does show the location info.
In your Lightroom Export (or Publish) settings, under Metadata, have you ensured “Remove Location Info” is not ticked?
Rob

I did order the Picasa Plugin through your website but haven’t seen an email for hours. Did check Spam filters very seriously.
Payment was done through PayPal. Please let me know how to proceed. Thanks.

You appear to have accidentally entered the wrong email address when purchasing your license. I’ve fixed the typo and you should have by now received your license key.
Thanks,
Rob

Hi,
If you use the Publish capability of Lightroom then you can keep in-sync all changes you make to an album in Lightroom with the album at Google. See these instructions for using the plug-in with Lightroom’s Publish (http://www.newpproducts.com/?page_id=3426).
However if you make changes to the Google album outside of Lightroom then Lightroom and the plug-in will not be informed of those changes.
Rob

It seems that since the update “Upload performance improved by allowing multiple simultaneous uploads” the pictures appear in wrong order in Picasa. Re-ordering in Picasa doesn’t work if the picture was shot within the same second.
Can you confirm that issue? Is there a workaround?

thx and kind regards

Hi,
Hmm. Problem confirmed. Your analysis was correct. Picasa Web relies on the upload order, and when the plug-in was doing multiple uploads at the same time, the resulting order of the uploaded files could not be guaranteed. Multiple uploading is now disabled by default and can be enabled by an option in the Settings window. Get Photo Upload version 1.5.1.
Thanks for spotting and reporting this one!
Rob

Hi,
still it doesn`t work. No Special Warning or Information. Photo Upload tries to authorise and then just fell back to: Not authorized with Picas Web ……
Thanks for the fast reply and have a merry Xmas!
Regardes
Sebastian

Hi,
I’ve sent you an email. There should be nothing preventing you authorising the plug-in against Picasa Web except your network settings, but hopefully you will send me your log file and I can investigate.
Thanks.

Hi,
i`m having problems authorising my Google account in the plugin. I checked the Firewall and tried a few times to authorize. But after copying the Auth code from the browser and clicking OK, Photo Upload still says : Not authorized with Picasa Web – use the aut…..
Can U help? Please.
Thanks
S

I’ve just today added a new version of Photo Upload (v1.5) that tries to give a clearer message if it appears to have network issues (e.g. a firewall is blocking it).
Could you please try the latest version?
Thanks,
Rob

Hi Rob !

My computer was robbed last August, and just now I’m trying to use the photo upload plugin again.
I’m using Windows 8.1, Lightroom 4.4 and Photo Upload 1.4.9.
The install and licensing process worked just fine, but when I try to authorize any service (I’ve the Google Drive or Picasaweb licenses), I go through all steps, I get the auth code from Google, paste it in the Plugin box, but I always get back to the “not authorized” message.
I tried to run LR as administrator, Firefox and Chrome with same results.
Any sugestion ?
Thanks in advance,

Ronald

Hi Ronald,

If the authorisation does not work then it is almost certainly a firewall problem. Can you check into that?
I’ll drop you an email and see if you can also send me your log file.

Thanks,
Rob

Hi Rob !

Thank you very much for your prompt attention to my message.

After receiving your email about the possible firewall problem, I switched to another connection and the Google auth process worked just fine.

Best regards,

Ronald

After using this a couple weeks, I am totally pleased. In the past I edited my photos in Picasa and saved them to web albums. I got a better camera recently and now use Lightroom but I wanted to keep using Picasa web albums ( now Google +, I guess). Photo Upload works great for me, using the Export method. I also found a $4 app (Web Albums for Picasa, or something like that) that organizes and displays my photos beautifully on the iPad and iPhone. The two are a great combination. I recommend them highly.

Leave a Reply to Rob J 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.