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

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

Plug-in says the license key is invalid

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

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

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

Support - License Key

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

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,458 replies on “Support FAQ”

Hi, to ensure you don’t inadvertently share all your photos when you upload them, the photos just go into a “private” album. You can then use the Facebook website to share the albums or photos.

I understand that logic (and appreciate that the photos aren’t automatically public) but the photos I uploaded went into a new album, named December 2013 (what I had named the album in LR) which was, according to facebook, automatically set to viewable to my friends (which is my default in my FB settings) — except that they weren’t. Only the photos people were tagged in became viewable, and it didn’t show up in anyone’s newsfeed.

If I had gone to FB and seen that the uploaded album was set to “only me” for access, your explanation would make perfect sense, but I don’t understand how I’m supposed to fix it if it says it’s already set to “friends” but isn’t. I haven’t had this problem uploading from other programs before.

Hi. Version 1.4.9 of Photo Upload now allows you to upload photos to a Facebook “page”. When you authorise the plugin for your Facebook account you will get a list of accounts and pages you can administer. Just choose one from the list.
Thanks.

Purchased Picasa upload noticed that while it does everything correctly as advertised, I do not see the legend under each photo being populated with the file name it was uploaded with. Is it suppose to be like that, because this is painfull to have to go in and write a legend/title under each photo which are part of a batch of 30-50 or more photos.

Hi. The plugin takes the caption from Lightroom. If the photos have a title and/or caption in Lightroom then that will be transferred to Picasa Web. Do your photos have captions in Lightroom?
Thanks.

Hmm – that sounds a pain.
I’ve today released 1.4.7 of Photo Upload. It has an option in the Settings window for using the photo file name as the photo title during the uploading. I think this will help you – could you kindly give it a try and let me know?
Thanks,
Rob

This is going in the right direction, the only issue that this poses, is that the renamed newfilename-1…newfilename-50 which carry this new file name when uploaded in batch do not carry this name but the original file name before renaming ie. P0716543_CS6modified.psd and so forth, I still would have to go in Picasa and change the legend title for each to newfilename-1…newfilename-50.

Thanks for the change and the quick turnaround, it’s appreciated!

PS Jeffrey Friedl (http://regex.info/blog/lightroom-goodies/picasaweb#comment-45515) does this in this manner for his picasaweb export, the only issue with his plugin is that I can’t setup my two google accounts because they are both under the same user name with different user emails (one gets overwritten by the other each time, so I have do do separate logins each time and go through authentication…), this is why I purchased your plugin and also because of the integration with other services I use, such as Google drive, Dropbox, Box.

You’re correct. In my rush I didn’t consider that choosing the exported file name for the photo title would be the sensible choice. I’ll update the plug-in but it will probably be tomorrow now. Will get in touch…

Hi,
The Photo Upload plug-in now allows you to use the generated file name (rather than the original file name) for the photo title. Do you fancy giving version 1.4.8 a go and let me know if this works for you?
Thanks,
Rob

Yes this works super!

Furthermore I have never seen to date a SW developper so responsive and quick in implementing changes.

A big thank you this is a real timesaver.

Hi,

Have been using the full version for Picasa for a while and love it. Upgraded to PhotoUpload tonight with no problems and the Export\Publish works fine except at the very end I get an error with a dialog box stating:

“Unable to Export”
An Internal Error has occurred: Export.lua:373 bad argument #1 to “formatlongdate” (number expected got nil).

I’m not sure what I have that should have a date and doesn’t. Like I said, the albums upload ok.

Thanks,

Joe..

Hi Joe. Thanks for your note. At the end of an export or publish operation, the plugin updates the album with the earliest photo date, if possible. It very much sounds like something has gone wrong while it is trying to do that. There was such a problem a few months ago. Can you confirm what version of the plugin you have?
Thanks, Rob

Rob,

It is version 1.4.5. I checked for updates but it is the latest I am told. This is the first an only Album I used PhotoUpload for. I had used the Previous Picasa Web Upload v1.4.0.1 for probably 15 albums with no issues. I have both loaded currently.

Thanks,

Joe..

Hi Joe,
Think I’ve fixed this one now in Photo Upload 1.4.6. Can you give it a go?
I think the problem was that you were uploading a photo that did not have a “built-in” photo date set for it. I hadn’t tested for that.
Thanks,
Rob

That did it. I I ran the 1.4.6 update and went into Picasa and deleted the same album with the problem last night and then re-exported it out and had no issues.

Thank you!

Quick question if I may:

In the past I usually did a straight export. However, if I were to use the Publishing features (I should read the documentation someday – I know) could I:

1. Remove photos from the album and re-run the publish and have the photos removed the the published album?

2. If I make changes to the photos will they update in place?

Other then that I can’t thank you enough for a great utility and expecially for the fast turnaround.

Thank you,

Joe..

Hi,
Thanks for confirming 1.4.6 fixes the problem you reported. Sorry for the inconvenience.
To answer your questions:
1 and 2, yes.
Lightroom will always want to be the master/owner of the album. So make any changes to the published album in Lightroom and then when you press “Publish” it will sync those changes – adding, removing and updating photos where necessary.
I personally prefer the simplicity of Exporting compared to Publishing.
Thanks,
Rob

Hi Rob,
After a right-click on the “SkyDrive Upload publication service” it’s possible to create an “Album” or a “Folder”.
I don’t see clearly the différences, and, if I’m right, it is not possible to create an Album or Folder within another one ? Right ?
Thanks for answer.
Best rgds.
ryb

Hi,
You are asking about Lightroom specifics.
Lightroom has publish folders, each of which can contain folders and albums, but not photos.
Albums can contain photos, but not folders or albums.
That structure kind of maps to the Flickr stucture, so given that Flickr has been around for longer than most upload services perhaps this explains why Lightroom adopted that hierarchy.
Sadly Lightroom enforces the hierarchy, so all a plug-in can do is to fit in with it.
Hope this makes sense!
Thanks,
Rob

Sorry for disturbing again. I extracted the folder and put it in my plugin folder with my other plugins, namely:

C:\programmes\adobe\Adobe photoshop lightroom lightroom 5.2\Lightroom-plugins\treemirrorexport.lrplugin

Its there, and it shows up in the plugin-manager as activated and running.

But if I want to export, the tree-mirror-export does not show up in the list of publising-services an the left hand menu of lightroom.

What could be wrong?

Thank you

L.F.

Yes, but if I hit export I do not get a choice to use tree Mirror Export. It just exports to the harddisk in the previous destination folder.

It would be helpful to have screenshots in your user instructions.

Thanks L.F.

From the Export dialog select Tree Mirror Export from the “Export To:” at the top of the dialog. I intend to add some screenshots one day… Thanks.

Hi, I have updated to 1.4.5 of Photo Upload and get a problem with the authorization of Google+. I get the code, copy and past it to Photo Upload, the dialog windows of Photo Upload closes and after a second I get the same status: Not Authorized.
I Have tried it several times, with IE, with Crome and I have started LR as admin but still not working.

2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable\serviceFileLicensedStatus
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable\serviceFileLicensedStatus\getServiceLicenseKey
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable\serviceFileLicensedStatus\getServiceLicenseKey – License key Service_GD = ****** Deleted by me **********
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable\serviceFileLicensedStatus\serviceFromFile – Service_GD
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable\serviceFileLicensedStatus – Licensed status = true
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable – Licensed status Service_GD = true
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable\serviceFromFile – Service_GD
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable – Service_PW
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable\serviceFileLicensedStatus
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable\serviceFileLicensedStatus\getServiceLicenseKey
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable\serviceFileLicensedStatus\getServiceLicenseKey – License key Service_PW = ****** Deleted by me ***********
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable\serviceFileLicensedStatus\serviceFromFile – Service_PW
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable\serviceFileLicensedStatus – Licensed status = true
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable – Licensed status Service_PW = true
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable\serviceFromFile – Service_PW
2013-12-02 20:49:15 5.2 1.4.5 .\addLicensedStatusToTable – Service_SD

This is what I did several times. If you are interested I can send you the screen shots step by step. After I have entered the key from the browser (copy/past) into the dialog window of your software and pressed “OK”, I can see “Retrieve account …” and than again: “Not authorized …”.

Hi Rob, why did you delete my reply here ?
I just told you that I’am following the specified process step by step and took some screen shots and it didn’t work. I can show you the screen shots if you want maybe you see what I did wrong. It would be very nice if you try to help me.

What I have tried now:
I deteleted the directory photoupload.lrplugin and took version 1.3.6. No change, the authorization is still not accepted.
I try it again wit the browser Crome insted of IE but same result.
Can I delete something in the registry to start from scratch with the installation of Photo Upload ?

How I solved my problem:
I have deleted the file “Photo Upload.prefs”, add the licence key again and authorized the google+ account and it works.

Hi Peter. I sent you an email a few days ago to see if I could help but for some reason the email bounced and didn’t get through. You used different email addresses when adding comments to this website – the one ending in @gmail.de did not work, but the one ending in @googlemail.com appears to work fine.
Glad you have your problem sorted. Thanks for letting me know how you fixed it!

I just installed LR 5.2 (Creative Cloud) and also upgraded my Photo Upload software to the latest 1.4.5. I still have LR4 sitting on my hard drive.

When I try to export a single photo to Picasa, it gives an error: “some export operations were not performed.” Photo Upload does create the new album in Picasa.

I am trying to upload 1920 pixels on the longest edge and I have plenty of storage space at Google.

I was able to do an export of the photos to my hard drive.

I did a search for this issue on the web and couldn’t find a good solution. Any ideas?

Hi, the latest versions of the Photo Upload (version 1.4.1 and later) and the SkyDrive Upload (version 1.1.1 and later) plugins both support Lightroom 5.3.
I assume you have an older version if you are experiencing problems.
I would recommend using Photo Upload rather than the old SkyDrive Upload plugin if you are investigating these plug-ins just now. The Photo Upload plug-in gets many more updates.
Thanks,
Rob

I have paid November 20 for this plug-in from Ukraine. Till now (November 28) I don’t have any reply from you. Spam box was also checked.
I will thankful for your assistance

You had entered your email address incorrectly at the time you ordered. You entered “@!gmail.com” instead of “@gmail.com”.
I have resent your license keys.
Thanks.

insisto con el pedido de la licencia, me respondieron el mail pero no me enviaron la licencia.
por favor reenviarme la licencia.
muchas gracias

Hi,

I sent you an email yesterday asking you to check your spam/junk email folder which you did not respond to. So perhaps that message also went to your spam/junk folder.
Please reply to my email to confirm you are receiving emails and if necessary I will get your license re-issued.

Thanks,
Rob

Awesome, I’ve been looking for a workflow for this since I started using Lightroom 2. (Amazed that Adobe have not made it possible to use regexp and original file folder as part of name creation on export, thoguh!)

But with your plugin, I have now significantly less work on exporting, every single time!

Hereby donating for this fine plugin! (Urge other users to do the same!)

Hi!

I’ve upgraded Lightroom 4 to Lightroom 5. I had 2000 pictures published on Google+. After importing my catalogue and installing the photoupload plugin, Lightroom wants to publish all 2000 pictures again.

Do i have to re-publish them?

Hi,
I wouldn’t have expected you to need to re-publish them if the pictures have not changed. Lightroom controls whether the photos need re-publishing, not the plug-in.
I assume Lightroom thinks the photos have been changed somehow – perhaps the import of the LR4 catalog applied the “2012 process”?
Sorry I can’t help further.
Rob

I get an error with photo upload (picasa export) (free version) that my lightroom version 5.2.0.922700 is uncompatible with this plug-in
is there a fix?

I apparently made the mistake of buying it and trying to use it in LR 5.2. It seemed to install without problems, but failed to work. What would you recommend?
Regards, Ralph Nash

Hi,
The latest versions of the Picasa Web Upload plugin and the Photo Upload all work with the latest versions of Lightroom (including 5.2).
Please download the appropriate plug-in from this website.
I assume you downloaded the plug-in from the Adobe website. If so please be aware that Adobe do not update the plug-ins on their site very often (ever?) and therefore the plug-ins can get out of date.
Thanks,
Rob

Hi,

I set up a publish service to picasa and my token keeps expiring. It then wants all the pictures to be republished. Any suggestions?

Thanks,

Jon

Ah – you found a bug with automatically refreshing the authentication token after a few hours.
Now fixed in Photo Upload 1.3.5.
Can you confirm that this works for you?
Thanks for highlighting this and sorry for the inconvenience!

Dear Rob,
I’ve discovered your tool today and it seems quite useful. I’m missing one option: To skip existing files. This is handy in a lot of use cases.
Is this feature missing or am I missing something?

Hi,
The Tree Mirror Export plug-in (1.1) now has an option called “Existing Files” that allows you to specify whether to overwrite or skip existing files.
Hope this is what you were after.
Let me know how you get on.
Thanks,
Rob

V 1.3.2 works! I can upload over 20 Mb RAW Images to google. Thank you for the update. I realized the 20 Mb cap was lifted when google said they now support raw images. The changes made to v 1.3.2 now let you upload directly from Lightroom. ….going to spread the good news. Thank you for the excellent plugin and support.

CR2 Raw images, can’t upload to Picasa. I’m using V1.3.1 Is it not supported yet?

“Error uploading to Picasa Web”

Picasa Web did not allow uploading of files greater than 20MB or of RAW files.
However it appears to permit this today (although Google have not documented it) so I’ve updated the Photo Upload plug-in to allow CR2 uploads. Version 1.3.2 is now available. Let me know how you get on?

Hi there,
I am using Lightroom 5.2. While publishing I get the message that the plug-in is incompatible with this version. Will it be supported? If so when?
Thanks for help.

Johannes P.

Thanks for your answer 😉
I already have another: I’m using Lightroom as a part of Adobe CC. Is it possible to use the plugin on two devices or is this license only usable on one device?
Thanks for your fast help.

Johannes P.

Thanks for your fast answer. That’s great. Searched a long time for a plugin like yours. Now I know what I’ll buy next 😉

Johannes P.

Hi There!

I want to upload the RAW files to my google drive. PhotoUpload uploads those files but i think it changes the MIMEType or something else. GoogleDrive cannot display the CR2 file anymore.
If i upload the CR2 file manually it works perfect and i’m able to see thumbnails of my RAW pictures.
Any suggestion?

regards

Hi,
Thanks for highlighting this. Yes, uploading CR2s to Google Drive was not working correctly. I’ve now fixed it and if you’re willing to give it a quick test then let me know. Otherwise I will release a fix in a few days.
Regards,
Rob

By redownloading from your site it did work, btw – the ‘upgrade’ button within LR for your app did not work. Thanks for the help

Thanks for confirming the latest version works for you with Lightroom 5. Regarding the “Upgrade” button – this is a known problem on Windows (not Mac) in the older plug-in version that Adobe have on their website. I wish I could persuade Adobe to update the plug-ins… it would save you and me a lot of wasted/repeated effort.

I’ve just downloaded your Photo upload product and lightroom 5 informs me that it is not supported. Now that I have paid, do you plan to support LR5 and if so when? thanks

Hi Micahel,

The plug-ins do support Lightroom 5.
For Photo Upload, please download the latest version from the website:
http://www.newpproducts.com/?page_id=3306

The version on Adobe’s website is old and from before Lightroom 5 came out. Adobe have ignored my requests to update it at this time (they are historically incredibly slow to update their Lightroom plug-in section).

Thanks,
Rob

I am using Photo Upload 1.1.5.1 for Picasa Web (Google+) … since it’s no secret that Picasa Web is being phased out in favor of Google+, why are my uploaded files directed toward the Picasa Web storage instead of the Google+? I’ve purchased extra space on Google+ and I’d like to use it, and not be hindered by the limitations of Picasa Web. Should I have chosen the Google Drive plugin license? if so, then why is there a Google+ alternative. Hopefully I’ve made this clear enough. I have read most of the posts here, but did not find an answer to my questions. Thank you

Hi,
Picasa Web and Google+ share the same photo space (and therefore the same storage). If you have photos in Picasa Web you can see them in Google+ and vice versa.
Thanks,
Rob

Hi,
Every time when I upload, the plug-in adds the following comment to each photo: OLYMPUS DIGITAL CAMERA. How can I avoid this?
Otherwise the upgraded plug-in works great!
Thanks,
Martin

Hi,

The plug-in combines two bits of info from Lightroom into the “summary/caption” field in Picasa Web.
These two bits are the Title and Caption.
You can see the info under the Metadata section for the photo within Lightroom.
Whatever you have deemed appropriate for this title and caption is uploaded.
I would not expect the title or caption for a photo in Lightroom to have the text “OLYMPUS…”.
I don’t think this will help much… but you are not the only person complaining about how Olympus stick their name into the photo metadata. See this Adobe Lightroom forum page:
http://forums.adobe.com/message/4558600
The forum does give you a way to remove the “OLYMPUS…” for a selection of photos at once. Not perfect I know.

Thanks,
Rob

You are right. I found the phrase “Olympus…” in the metadata. Deleting it from caption solved the issue. Thanks! 🙂

I noticed that someone had kindly given instructions how to make a metadata preset to prevent “Olympus…” being set when you import photos. It is the penultimate post in that link I included. Might be worth doing…

It’s really annoying what the manufacture is doing by adding the company’s name to the caption. Gladly, that can be changed without hassle when importing photos. Thanks for your help and keep your good projects up.

Hello,
“Tree Mirror export” does exactly what I need.

Unfortunately the photos are not automatically added to the Lightroom catalog.
On the hard drive but these are not seen in the catalog automatically.
In the export dialog in Lightroom 3.6 there is a checkmark “Add to this catalog.”
That is missing in the dialogue with “Lightoom 3.6” with “Tree mirror export”.
What can I do?

You are correct. Interestingly, no one has ever asked for the ability to add the export to a Lightroom catalog before so I’ve never noticed it was not possible.
I will add it to my to-do list and let you know when there’s a new version of the plug-in.
Thanks.

I would like to try your product but I can’t even get started.
ie:
1. ‘Create the following folder:’
\Documents\Lightroom Plug-ins
but in Windows a file cannot have the special characters \ /:*? , etc.
2. There are many files in the download. Do you ‘unzip’, then extract all?
Thanks,
Don

Hi,

I honestly think you may need some assistance from somebody else who can help you install the plug-in one to one.
But to answer your questions:
1. This is a guide. The “\” notation means separate folders. So open your Documents folder (sometimes called My Documents) and create a folder called “Lightroom Plug-ins”.
2. “Unzip” and “Extract All” generally mean the same thing. You should extract all the files in the zip file you downloaded into the folder you created above.

Rob

I added photos to my Google+ smart collection. The list of photos to upload, remove, modified and published looks good. But, when I try to publish, it thinks for a little while, then gives me this error:

Can’t update this collection.
An internal error has occurred:
LrPhoto:setPropertyForPlugin: must be called from within a withWriteAccessDo or withPrivateWriteAccessDo block

I’ve tried restarting Lightroom. No luck. Seems like a bug. Any ideas? Thanks.

Hi,

I purchased the Photo Upload plugin yesterday.
Is says you should be able to upload(and update?) photos in existing albums, but I can’t figure out how to do this.
“Upload photos to any existing album of your choice”

Can you let me know how to do this?
Also, when you change a photo already in an album…does the existing photo get updated or does another version of the same photo get uploaded?

Raymond

There is a guide that explains how to upload photos to an existing album:
http://www.newpproducts.com/?page_id=3321
If you have already uploaded a photo to Picasa Web (in your case) then the default settings are for that existing photo to be updated/replaced.
The latest version of the plug-in allows you to specify the rules for when to update your photos so that photos are not always replaced. I don’t think you have the latest version – Adobe are incredibly slow to update the version on their website. You can download the latest here:
http://www.newpproducts.com/?page_id=3306

thx for the quick reply.
I do have the latest version.
I want to use the publish method for updating/adding photos in existing albums.
For example:
I have a smart-album (which adds photos with specific keywords to that album). Then I would like to be able to publish everything in that album to my (already existing) album on Google+

Is that possible or is that just something that cannot be done with this plugin?

Is it possible to target a subfolder, i.e. \Photos\, when uploading to SkyDrive or Google Drive, and if so how? I’ve only been successful in uploading to folders created in the root folder.

Thank you.

Hi. If you use the Export capability then you can upload to any folder, however if you use the Publish capability then you are limited to just albums in the root folder. I am working on adding in the ability to use Publish to upload to a non-root folder. Hang on in there, I should have it soon. Thanks.

Hi. There is no time limit for the Tree Mirror Export plug-in. I’ve not heard of anybody experiencing the problem you describe. Did you try adding the plug-in again?

Yes, I added the plug in again and it worked fine. Just an extra step. Though I find extracting confusing.

How do I authorize this app to access my Google+ business page instead of my personal profile? The upload to Google+ worked great, but I want to post photos to my photo business page instead of my personal page, which is where it seems to authorize by default. Thanks in advance!

Hi,
Google do not provide a public way for Lightroom plug-ins to update G+ “pages”. They allow you to upload to personal profiles but not business pages. As soon as Google make the API public I will look into updating the plug-in. Sorry I don’t have a better answer for you.
Thanks,
Rob

Hi Rob, this is exactly my problem as well. Your uploader works perfectly well with my personal G+ account but I now need to upload to my business page.
Has the API made public in the meantime? Any changes we can have this feature?
Cheers

Google have not made their Pages API public – the situation has not changed since 2012. I’m not sure why they have such protection for their Pages API, but I’ve written to Google asking for permission to use it. I don’t think this plug-in is a big enough player for Gpogle to take notice, but I’ll see if they reply and what they say.
Sorry – wish I had better news.
Thanks.

Hi, Ive used your Skydrive plug in happily for sometime but now Im getting an error message

“Lightroom version 5.0.0.907.681 is incompatible with this plug in”

The plug in manager says it all ok and the authorization is fine.

Any pointers will be gratefully received.

Barry.

Hi,

You’ve upgraded your Lightroom to version 5 🙂
You’ll need a new version of the plug-in. Your current license key will work with the new plug-ins.
You can get a new Sky Drive Upload plug-in here:
http://www.newpproducts.com/?page_id=3172
However if you haven’t used what Lightroom calls published services with the plug-in then I’d recommend upgrading to the newer Photo Upload plug-in:
http://www.newpproducts.com/?page_id=3306
Either way there is no additional cost – your existing license key will work with both options.

Rob

I am testing out Tree Mirror and so far so good when I export to a desktop folder. But, I tried to export the same folders directly to a DVD and it wouldn’t burn. Any advice?

Hi,
Sorry but I don’t think I know how to help you. I have never tested exporting direct to a DVD. Why wouldn’t it burn? Was there an error message?

Hey…SO I bought the liscence for the Plug in for Drive…I never received an email with the key…At least that I can find…

My name is Anthony Giudice and I used paypal…Let me know what else I can do to get my key.

Thanks

Hi, I’ve just replied to your email. Can you reply back to confirm you are getting emails ok? Your license was sent automatically on payment so you should have received it. I can resend it of course, but can you reply to the email I have just sent?
Thanks, Rob

When exporting I can choose a subfolder in dropbox, how can I choose a location when using the publish service? It will only create an album for me at the root level, and I want to publish into an existing subfolder. Just purchased the plugin today, looking forward to using it. I’m using lightroom 5

Hi,

Currently the plug-in only allows published collections to be created at the root. You can use this plug-in with Lightroom’s “Export” feature to create albums elsewhere, but I am aware that this is not ideal for folks that really like creating published collections.
I am working on allowing you to specify a root folder when you first setup the published service. Hopefully I can get this finished soon.

Thanks,
Rob

Great! Looking forward to seeing this added to the publishing area as well. One other suggestion, since your plugin works with several online storage solutions, I’d love it if you’d take a look at adding http://www.copy.com as an option, as they give you 15gb to start with (I think Dropbox only gives you 2gb free). Thanks!

when i try to publish using the plug-in, I got the following error:

Lightroom version 5.0.0.907681 is incompatible with this plug-in

Thanks for the advice – I followed it and installation went smoothly.
However, I am seeing this message –
An internal error has occurred: ServiceManager.lua:366: bad argument #1 to ‘formatLongDate’ (number expected, got string)

Advice?

PS – If this can resolved, I am going to buy the product so that I can place the files into predetermined locations. Thanks!

Apologies – that’s embarrassing. I introduced a bug specific to uploading to Google Drive yesterday. It’s now fixed.
You should be able to use the update button in the plug-in settings to update to Photo Upload 1.1.5.1.
Please let me know if this fixes the issue.
Thanks for reporting it!

Sir –

So, I am considering buying your product but I need a bit of info first – When you Export to Photo Uploader and than to Google Drive from there, are the pictures being exported as Jpeg? Original ARW? Will the edits come along?

Thanks

One way to answer your questions is to try the product. Even if you don’t buy a license you can still use it to upload your photos to a single album.

Google Drive allows you to upload your files in any format that Lightroom supports, e.g. JPG or RAW. If you exported the RAW files then the edits would not go along, of course. But if you exported as JPG or TIFF etc. then, yes, you would get the edits. Each photo upload service is different though, e.g. Picasa Web is more restrictive about the files it allows to be uploaded.

Why not try out the plug-in? You don’t need to purchase a license to see how it works.

Thanks.

Rob, Thanks for your quick reply! I don’t think that I have used the “publish” feature. What would the advantage be of using it over “export”? Since I obtained my license some time ago, I doubt that I can locate the original number, can I find it in my existing version, or would you need to send it to me again?

Thanks again.

Peter

Publishing causes Lightroom keep a record of what has been uploaded. Exporting is more of a fire and forget activity.

Your existing license key is visible from the Enter License button in Lightroom’s Plugin Manager. Just copy and paste it.

Thanks.

When publishing to Dropbox any whitespaces are replaced by “+” signs, that means “my girl.jpg” is changed to “my+girl.jpg”. Is there any possibility to keep the whitespaces? Thanks.

I have v 1.2.4 of Picasa upload with a full license. Of course it will not work with LR5. Please spell out the steps that I need to take inorder to update. Including continuing to have the full version.

Thank you

You have two choices. Either use a more recent version of the Picasa Web Upload plug-in, or move to the Photo Upload plug-in.
Your Picasa Web Upload license will work in both plug-ins.
If you have not so far used Lightroom’s publish services with your existing plug-in then I would recommend you download the newer Photo Upload plug-in. This new plug-in does everything the Picasa Web Upload plug-in did, and more.

Download Photo Upload here and then follow the link for Installation instructions:
http://www.newpproducts.com/?page_id=3306

If you have used published services and want to keep them, then you will have to download the latest version of Picasa Web Upload from here and then follow the link for Installation instructions:
http://www.newpproducts.com/?page_id=2743

It is easy to get the plug-in working with Lightroom 5, but you do have the above choice.

Hi, I am a licensed user (for Dropbox, Google Drive, and Picasa Web). It was working well. I recently upgraded to Lightroom 5. I tried to publish, but it says “Lightroom version 5.0.0.907681 is incompatible with this plug-in”. I noticed that if I edit settings for the plugin, it says I am using version 1.0.5, and there is a new version 1.0.9.1 available. But if I click the Upgrade button, it says “could not download the new plug-in”. Should I manually download and install the new version? Will I lose my existing Smart Collections?

Thanks for your help.

Hi,
Yes – 1.0.9.1 works with Lightroom 5.
The Upgrade from 1.0.5 to 1.0.9.1 has to be manual I’m afraid.
Please download the new 1.0.9.1 and install it. You will not lose your existing Smart Collections.
Let me know how you get on…
Thanks,
Rob

The folder name in downloaded zip for 1.0.9.1 is slightly different to 1.0.5 (that is why the in-place upgrade does not work).
Just extract that folder alongside your 1.0.5 version.
And in Lightroom’s Plug-in Manager, use the Remove button to remove the old plug-in before using the Add button to add in the new 1.0.9.1 version.
It’s simpler than it sounds!

It worked! It didn’t handle the video files, though (.MOV). It gave an error message saying it couldn’t handle file extension “ but only .JPG and .PNG or something. And it froze up Lightroom for quite a while.

Picasa Web only allows JPGs and MP4s. You should be able to ask Lightroom to convert you MOVs to MP4s during the upload process.
Dropbox and Google Drive do not have such restrictions. Any file can be uploaded to them.
Picasa Web also has a restriction of movies being less than 100MB.
I assume the “freezing” of Lightroom is down to Lightroom preparing the video for export (video files are big), only to find out that Picasa Web does not allow it.

Fooey.
“**** Error 1

An error occurred while attempting to load this plug-in’s portion of the Export dialog.
Export.lua:120: attempt to call field ‘buttonsForPluginSetup’ (a nil value)”

OS X 10.6.8, LR4

I re-downloaded the plug in, reinstalled, and quit/restarted LR to no avail.
Help?

Hi. You should actually download the plugin called Photo Upload from the link at the top of this page. That plugin works in the same way as the Picasa Web Upload one but is the plugin that is now being actively maintained. Give it a go!
Thanks.

Hi, I am trying to upload (to Picasa from Lightroom4 with your new plugin) the same photo 2 times with two different sizes. One main and second icon size. For this to work I must Export and use the rename function the second time. I do File > Export > File Naming > Rename to > custom rename > Image Size > resize, but when I load the second photo it uploads over the first one leaving me with one photo only. How must I do this right. Thank you and I am glad I bought this software!

Hi,
As you noticed, the same photo can only be uploaded to the same folder once. You are actually the first person to ask to upload the same photo into the same folder in two different sizes.
Do you mind if I ask why you have two photos of the different sizes in the same folder? Just so that I understand?

I could add an option to the “Settings” window, not to overwrite existing photos if you have given the new photo a new name. Do you think this would help you?
Thanks,
Rob

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