Error Message on Picasa While Attempting to Upload to Google Photos - Failed to Download Album List

Sometimes problems do occur so please go in contact by calculation a comment at the lesser of this page and I'll do my best to try and assistance. Delight retrieve to employ a real email address when you post a comment so that I tin can get in contact if necessary (your electronic mail address will not be visible publicly).

Contents

• Latest support news
  • 6 Feb 2022 – Publishing and exporting hangs after i photo
  • xviii Oct 2020 – Pinterest no longer authenticates
  • 6 Sep 2018 – Picasa Spider web retires on fifteen Mar 2019
  • 20 Jul 2018 – Facebook prevents plug-in from being authorised
  • fifteen Jun 2018 – 500px no longer supports plug-ins
  • 24 Apr 2018 – Facebook prevents plug-in from creating posts on user timelines
  • 23 Jan 2018 – Picasa Spider web uploads fail ("500" error)
  • 27 Feb 2017 – SmugMug no longer allows photos to be uploaded to "Private" galleries
  • 7 Feb 2017 – Picasa Spider web changes (eastward.k. albums cannot be created)
  • vii Feb 2017 – Picasa Web uploads fail ("501" error)
  • 27 Jan 2017 – Picasa Web uploads neglect ("400" fault)
  • 19 April 2016 – Facebook authentication fails
  • 16 February 2016 – Google announce changes to Picasa Spider web
  • xiii November 2015 – Lightroom hangs/freezes when closing
  • vii Oct 2015 – Zenfolio communication fails
  • 31 Jul 2014 Sometime "Picasa Web Upload" plug-in replaced by "Photo Upload"
  • 27 Jun 2014 – Flickr authentication fails
• FAQ
  • Updating the plug-in – always bank check you lot have the latest
  • Downloaded plug-in from Adobe's website and I have a ZXP file…
  • Lightroom reports "An error occurred while attempting to load this plug-in."
  • Missing plug-in – The "nil" plug-in is non installed
  • Authentication trouble – Error authenticating with [service]
  • What is the Export Location used for?
  • Lightroom says my computer is out of disk space
  • Location information not being uploading
  • Quondam versions of Photo Upload for OneDrive (and the previous SkyDrive Upload) cannot be authenticated
  • WordPress self-hosted sites
  • WordPress weblog site pick
  • WordPress authentication does non return an authentication code
  • Plug-in non uniform with your version of Lightroom
  • Lightroom's Plug-in Manager'southward "Remove" button is disabled
  • Unreceived license cardinal
    • Unreceived license key (purchased from the Adobe Add-ons website)
  • Lost my license fundamental
    • Lost license keys purchased from the Adobe Add-ons website
  • Plug-in says the license key is invalid
  • Can I rename the plug-in folder?
  • Google'south Picasa Web photograph size constraints
  • Create multiple publish services
  • Checking the version of your plug-in
  • Removing a plug-in
  • Saving your log file

Latest support news

6 February 2022 – Publishing and exporting hangs afterward one photo

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

There seems to be one solution which involves clicking on a different collection when the publish/consign starting time appears to hang. The second solution is simply to re-install Lightroom Archetype eleven.1 instead of 11.2.

Hopefully Adobe will fix this in the side by side update for Lightroom.

eighteen Oct 2020 – Pinterest no longer authenticates

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

Photo Upload uses v1 of the API from Pinterest and has been an approved app by Pinterest since 2015 (information technology went through their approving procedure). Pinterest appear on their developer website erstwhile in early on 2020 that at that place was a new v2 API bachelor.

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

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

Note: Deprecation does non hateful "removed", but I remember in this instance Pinterest actually meant to utilize the word "disabled". The word "deprecation" is used to announce that something will be removed in the future.

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

On 31 Aug 2020 Pinterest sent me this answer: "Unfortunately, this is no ETA when the new apps will exist approved as I take mentioned nosotros are a very pocket-sized team and currently experiencing a large excess of applications. We're working equally fast as nosotros can to review and become back to everyone and also we do non prioritize requests for any users as of now. I promise this clarifies."

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

I've emailed the developer support at Pinterest again and over again over the by vi months.

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

Unfortunately there is nothing more than I tin do to encourage Pinterest to grant Photo Upload admission to the v2 API. Pinterest disabled the v1 API earlier than they said they would (was meant to be 31 October). The whole idea of a deprecation cycle is to give developers time to move to a new fashion of doing things (i.e. v1 to v2) but in this instance they have not processed applications after 6 months! Hopefully you can see that I'chiliad very frustrated by this, I really oasis't worked with a less professional person mainstream system with the Photo Upload plug-in.

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

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

6 Sep 2018 – Picasa Spider web retires on 15 Mar 2019

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

The Photo Upload plug-in now has the Google Photos service bachelor to it (introduced in version v.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 tin can purchase a license key for the Google Photos service in this plug-in from the usual places. Unfortunately, due to the fourth dimension and effort needed to create the new Google Photos support in the plug-in, there is no complimentary transfer or discount when moving from Picasa Web to Google Photos.

At that place are some differences between the new Google Photos interface and the old Picasa Web interface. Near notably you tin now use the plug-in to create albums on Google Photos, but notation that Google but allows you to upload photos to albums created by this plug-in (i.e. you cannot upload to albums that y'all already have on Google Photos).

Facebook, in light of the Cambridge Analytica scandal, have prevented small businesses like this one from connecting to Facebook. The official appointment for this dropping of support was supposed to be 1 Aug 2018, but they seem to take taken activeness a little earlier.

Facebook have not responded to any requests for description on their policy for preventing pocket-sized business access. Unfortunately at this time there is nothing else that tin can be said except that Facebook have prevented the plug-in from being authorised and therefore accept 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 admission their site. This is a decision made past 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 lot and so delight contact 500px straight and mention that y'all employ or rely on the Photo Upload plug-in for Lightroom. I have as well 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 yet allowing posts to exist 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 twenty Jul 2018 – Refer to the news on Facebook dated 20 Jul 2018 above.

23 Jan 2018 – Picasa Spider web uploads fail ("500" error)

The Picasa Web API that 3rd political 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 mistake, try once more later".

Many other people and apps have reported the aforementioned errors, for example run into 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 alter, so at this fourth dimension I have to assume that Google will fix the problem sooner than subsequently. I will keep an center on the situation over the adjacent twenty-four hours or so, but there is zippo else I can practice at this time.

Please exist aware that that 12 months agone Google made it clear that Picasa Web was beingness retired and no longer developed. Sadly, Google practise not allow tertiary party plug-ins to upload straight to Google Photos (they can only upload to Picasa Spider web). My suggestion is that information technology is time to start looking at alternative photo sites if you want to upload direct from Lightroom.

Update 25 January 2018 – Google have now fixed the problem and Picasa Spider web uploads work over again.

27 Feb 2017 – SmugMug no longer allows photos to exist uploaded to "Private" galleries

SmugMug take prevented photos from being uploaded to galleries that have their visibility set equally "Individual".

I don't know their rationale why and I fifty-fifty asked them why in their back up 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 set up this or if information technology is permanent.

You need to alter the gallery visibility to "Public" or "Unlisted" then the upload should work.

Update 28 Jun 2017 – this is now fixed in plug-in version four.5.seven.

vii Feb 2017 – Picasa Web changes (eastward.g. albums cannot be created)

The Picasa Web API that 3rd political party apps use to upload and manage photos for Google Photos has been updated past 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, delight refer to this Google site for more information (see section titled "Mutation support removed").

You can nevertheless upload photos using the latest version of the Photograph Upload plug-in, and y'all can apply the Google Photos website to create your albums before or later on uploading to them from Lightroom.

Update half dozen 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.nine. 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 lot initially create on Google Photos equally "shared albums". To work effectually this, please initially create albums on Google Photos as regular "albums" and and then configure these to be shared albums afterwards.

7 February 2017 – Picasa Spider web uploads fail ("501" error)

The Picasa Web API that tertiary party apps employ 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.one.ix to handle these Google changes with "friendly" mistake letters. You should update your plug-in to 4.1.ix or later.

Please also refer to the note higher up on "Google Photos (Picasa Spider web) no longer let albums to be created".

Update eight Feb 2017 – this is now stock-still in Photo Upload version 4.one.9.

27 Jan 2017 – Picasa Web uploads fail ("400" mistake)

The Picasa Web API that third party apps use to upload photos to Google Photos is reporting a "400" error with the message "Bad request". This will bear on all 3rd party apps that upload pictures using the Picasa Web API to Google Photos. At that place is a thread on the Google forums that is discussing the trouble.

It is not known what causes the trouble and when Google volition set up the issue. I'd expect them to fix it quite quickly given the number of 3rd party apps that brand utilise of uploading photos in this way. I'll runway Google'south response – hopefully it will be quick and positive.

Update 28 Jan 2017 – this is now fixed in Photo Upload version 4.1.six. There has been no indication from Google what the problem is, but I've found an alternating way to upload the photos which appears to work well.

nineteen Apr 2016 – Facebook authentication fails

Facebook take mandated a few changes to authentication and quondam versions of the plug-in volition receive a "URL blocked" message from Facebook when authenticating.

Update xix Apr 2016 – this is now fixed in Photograph Upload version 4.1.ix.

xvi Feb 2016 – Google announce changes to Picasa Web

Google recently announced that they volition be making changes to the Picasa Web API that the Photo Upload for Picasa Spider web plug-in uses.

Google accept been unclear almost all the implications of these changes to applications such as the Photograph Upload plug-in. However they have stated that changes to their API will not exist made until 1 May 2016.

Google may keep the erstwhile 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 utilize. Or they may practice something else such as better Google Drive integration for Google Photos, or remove third political party API admission to Google Photos entirely.

Google have noted that they volition announce in March 2016 what the changes volition be in detail, so until that time it is not possible to comment further on how Google's plans volition bear on Photo Upload for Picasa Web.

Every effort volition be made to ensure Photo Upload continues being able to upload your photos to Google Photos. When Google share more than details of their plans then this news department will be updated with what this means for the Photo Upload plug-in. Until and then, I'1000 afraid we have to be patient…

13 November 2015 – Lightroom hangs/freezes when closing

A few people take highlighted that Lightroom can hang/freeze when it is closing. Lightroom must and so be force closed to brand 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 folio on the Lightroom forums:

http://feedback.photoshop.com/photoshop_family/topics/lightroom-2015-2-hangs-on-quit

The communication that seems to piece of work fairly reliably is:

"Reset the preferences (holding down SHIFT and ALT and starting Lightroom) and cull YES."

vii Oct 2015 – Zenfolio communication fails

During some scheduled maintenance on 6 or 7 October 2015 Zenfolio take changed the style security for internet communication is handled on their servers.

Update vii Oct 2015 – this is now stock-still in plug-in version 3.2.1.

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

The sometime "Picasa Web Upload" plug-in originally launched in 2012 has been replaced by the "Photo Upload" plug-in which allows y'all to upload to Picasa Web and many other services.

The final version of the "Picasa Spider web Upload" plug-in is one.5.8. If you have a version of the erstwhile Picasa Web Upload plug-in and so delight note that it is not possible to use it with Lightroom 7.0 or afterward. Instead delight download the latest Photo Upload plug-in from this website. You tin employ your existing Picasa Spider web Upload plug-in license key with the Photograph 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 ane.vii.ix.

FAQ

Updating the plug-in – always check y'all take the latest

If you think you take a problem, in particular if you retrieve you've institute a bug, so please brand sure you have the latest version of the plug-in.

Use the Update button in the plug-in'south settings from Lightroom Plug-in Manager to bank check that you have the latest.

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

If y'all download the plug-in from Adobe's Add-ons website and so you will go a ZXP file. This type of file is intended to exist opened past Adobe Creative Cloud (and Adobe Extension Manager.) If you don't take Adobe Creative Cloud then you cannot practise much with the ZXP file.

Adobe'due south add together-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 direct from this website. This will be a regular ZIP file rather than a proprietary Adobe ZXP file. And so simply follow the tried and tested installation instructions as well 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 non been extracted correctly from the downloaded Zip file.

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 superlative-level in the Aught file will be a folder ending in ".lrplugin", e.g. "photoupload.lrplugin". Yous must excerpt this folder itself, non simply the files within it. Once you've extracted the plug-in binder from the Naught, you tin move it around your reckoner (east.g. to your Documents folder) but you must non rename the plug-in folder.

Missing plug-in – The "cypher" plug-in is non installed

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

After using Lightroom'south 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 go this message, delight re-install the plug-in past following the installation instructions.

Hallmark trouble – Error authenticating with [service]

When trying to authenticate y'all may get an error such as this:

Photograph Upload: Fault authenticating with [ service ]
No authentication information returned from [ service ].

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

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

Well-nigh firewalls place this plug-in'due south network admission as coming from "curl" rather than "Lightroom". Please brand sure your firewall permits network access for the "curl" application.

You can apply the "Examination Connection" window to test whether your internet connection is working for the plug-in. Yous can find the "Exam Connectedness" window within the "Configuration" window under the plug-in's Setting department in Lightroom's Plug-in Manager.

What is the Consign Location used for?

Lightroom provides a setting for the plug-in called "Consign Location". This allows y'all to specify where Lightroom should create the copy of each photo that yous are exporting. Lightroom creates a copy for each photograph according to your edits and settings. For example, if you've cropped your photo and want to consign it as a JPEG and so this is what the copy volition 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 really been exported.

Lightroom says my calculator is out of deejay space

Now that online storage is cheap or even free, people want to upload their entire photograph 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 than frequently on systems that take smaller difficult disks, e.1000. those with 256GB or less SSDs.

At the start of a publish/export process Lightroom starts creating copies of each photo that yous are uploading co-ordinate to the publish/consign settings y'all have specified. Lightroom does this in parallel to the bodily uploading being washed by the plug-in and does not wait for the plug-in to asking each photo copy. Lightroom does not allow the plug-in to dictate when the photo copies are fabricated and when they are deleted.

The out of disk space problem occurs because Lightroom creates all the photograph copies at the start of the upload and just deletes the copies when the plug-in has finished uploading the terminal photograph. The photo copies are created in the computer's temp folder (on a Windows motorcar this is usually on the same bulldoze equally the main Windows installation, due east.grand. drive C:). You will demand enough infinite in your temp folder (and drive) to allow Lightroom to create publish\export copies of all the photos that yous 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 yous are exporting 1,000 photos so you will need 5GB of free space in the temp folder on your computer.

Note: Work arounds for this Lightroom problem are ane) apply the plug-in's "Generate exports ane at a time" setting or ii) apply the Configuration setting "Temporary folder for exported photos" to override where the temp folder is.

For reference, here is how y'all can find out where your system temporary folder is that Lightroom volition exist using for the temporary files during an export/publish:

Win:

• Open Control Prompt
• Type:

echo %temp%

Mac:

• Open up Terminal
• Blazon:

echo $TMPDIR

Location information not being uploading

Various online services (e.1000. Google Photos) can make utilize of the photo location data in the photo'due south metadata. If the location information is not being uploaded and so bank check that you take enabled location information in Lightroom's Export/Publishing Manager windows, i.due east. you practice not accept "Remove Location Info" checked.

Old versions of Photo Upload for OneDrive (and the previous SkyDrive Upload) cannot exist authenticated

Update your Photo Upload plug-in to a newer version (version 2.3.vii or after).

Microsoft appear to take changed something on their servers which requires an updated Photo Upload plug-in.

Employ the Update push button for the Photo Upload plug-in in Lightroom'due south Plug-in Managing director to become the latest version.

Note: If you are still using the old SkyDrive Upload plug-in and then delight take this opportunity to upgrade to the Photo Upload plug-in (your existing license central will nevertheless work).

WordPress self-hosted sites

The Photograph Upload plug-in works with blogs hosted on wordpress.com and blogs that are cocky-hosted.

Authentication is ever managed past wordpress.com, and then yous volition need an account on wordpress.com fifty-fifty if you practice not have a site hosted there.

1. Create an account on wordpress.com (if you don't have one already). This is free, y'all do not need to create a site on wordpress.com
2. Install the Jetpack plug-in on your ain self-hosted WordPress site (https://en-gb.wordpress.org/plugins/jetpack/)
3. After the Jetpack plug-in is installed, connect information technology to your wordpress.com business relationship (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.chiliad. 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 whatsoever of the sites registered with your wordpress.com business relationship

For self-hosted sites, you will demand the Jetpack WordPress plug-in on your WordPress site. Ensure that you accept version 3.1 or later of Jetpack installed. Version three.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 non allow such local sites to exist registered.

WordPress blog site selection

WordPress allows you register multiple blogs with your wordpress.com account. You tin can select from your available sites using the drop downwards list in your Web brower when authenticating the plug-in with WordPress.

WordPress hallmark does not render an authentication code

Sometimes WordPress plug-ins can forestall the Lightroom plug-in from authenticating with your site. These plug-ins prevent yous receiving an hallmark from WordPress, i.e. the page with the authentication code does non open in your browser.

The problematic WordPress plug-ins tend to be security ones. At that place are known problems with these WordPress plug-ins, but other security plug-ins are likely to interfere with hallmark too:

• All In I WP Security
• iThemes Security Pro

If yous practise not receive an authentication code in your browser please disable the security plug-ins and try the authentication again. You should exist able to re-enable the plug-ins later the authentication has successfully taken identify.

Plug-in not compatible with your version of Lightroom

E.grand. "Lightroom Version 5.3.0.938183 is incompatible with this plugin".

Y'all accept an old version of the plug-in.

If your plug-in has an Update button then employ that to update to the latest version.

If your plug-in does non 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 sometime Picasa Web Upload plug-in then please download the Photograph Upload plug-in which now replaces information technology. Your old Picasa Spider web Upload license key will work with the new Photo Upload plug-in (for the Picasa Web service).

If you have the one-time 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 yous accept the former Tree Mirror Consign plug-in and then please download the Photograph Upload plug-in which now replaces it. Apply the Tree Mirror service in the new Photograph Upload plug-in.

Lightroom's Plug-in Managing director's "Remove" push button is disabled

It depends where you lot installed the plug-in every bit to whether you can apply the "Remove" button to remove the plug-in from Lightroom. It is greyed out if you installed to the post-obit 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 binder from the appropriate path.

To avert this potential problem, I recommend installing the plug-in to:

On Windows,

          \Documents\Lightroom plug-ins        

On Mac,

          /Applications        

Unreceived license key

If yous buy a license for the full version of the plug-in you will be sent two emails. One email will contain your order number and the second e-mail will contain your license key. These emails volition exist sent to you immediately and automatically by the FastSpring payment service.

The license key electronic mail should be sent immediately – but on a few occasions it has taken 6 hours earlier information technology has been received.

If y'all call back you should have received an email but take non received information technology then please first bank check your email junk or spam folders. The license keys and club receipts are sent by FastSpring – so it may help to search your junk/spam e-mail folders for the name "FastSpring" or "mailer@fastspring.com".

When a license primal email has not been received at that place are typically ii reasons:

1. A individual\corporate email domain is not processing the electronic mail correctly (sometimes the license key emails are identified as junk\spam). The virtually reliable electronic mail addresses tend to exist from mainstream domains such gmail.com or live.com.
2. An incorrect electronic mail address existence entered during the lodge.

If you retrieve either of the above apply then delight contact FastSpring (support@fastspring.com) with your order number.

Unreceived license key (purchased from the Adobe Add-ons website)

If the to a higher place tips for finding your license key have not helped, AND y'all bought the plug-in from the Adobe website (i.e. not via the plug-in or this website) so y'all will need to contact Adobe for further assistance.

Please notation 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 primal from the Adobe Add together-ons website yous will need to contact them regarding any unreceived license keys.

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

Lost my license cardinal

If you lot've bought your license from this website and lost your license key then please apply the email accost on the Contact page to arrive touch. Delight provide the reference number for your original buy 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 yous will need to contact them to accept your license cardinal 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 intendance that the key is copied equally ane long list of characters.

Your email system may insert line breaks or spaces into the email, so please be sure that whatsoever such line breaks, spaces or other formatting from the email bulletin are non pasted into the plug-in's license text box.

If your license key is notwithstanding reported as being invalid subsequently copying and pasting it then please cheque yous accept specified the License service correctly in the license key entry window. east.k. If you lot accept purchased a license for Dropbox so please make sure Dropbox is the selected License service in the window.

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

Tin I rename the plug-in binder?

The plug-in folder should be named with a "lrplugin" or "lrdevplugin" extension. For instance:

photoupload.lrplugin

or

picasawebupload.lrdevplugin

On Mac, if you open (i.e. extract) the downloaded Nada file a second fourth dimension you volition get a binder with the suffix "2". Lightroom will not be able to read the plug-in from such a named binder. Earlier opening the Naught file consider removing an existing plug-in folder.

The following will requite an error every bit the binder extension ".lrplugin 2" is not ".lrplugin" as Lightroom expects:

photoupload.lrplugin ii

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 brake of a maximum photo size of 2048 x 2048 pixels if photos are non to be counted towards your allowance.

Please annotation that Google currently only provides "unlimited loftier quality photos" via its ain mobile apps and website. Google does not let whatsoever tertiary political party applications such as the Photo Upload plug-in to use those constraints.

However, in one case your photos accept 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

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 yous create additional publish services by correct clicking on an additional publish service and choosing "Create new publish service…". You can then choose a new upload service, business relationship and settings for this additional publish service.

Checking the version of your plug-in

Y'all may need to check which version of a plug-in y'all are using. You can practice this from Lightroom's Plug-in Director.

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 Condition panes (in the example beneath the version is 1.5.5).

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 y'all to unregister a plug-in from Lightroom using the "Remove" push, simply in almost cases I recommend actually deleting the plug-in binder from your system. This is particularly important if you lot are upgrading the plug-in with a new version – always delete the old plug-in folder first so that there is no incertitude which version of the plug-in Lightroom will be using.

You tin find the installation binder of your plug-in from Lightroom's Plug-in Manager.

To remove the plug-in simply identify the install folder (highlighted in the above Plug-in Director screenshot). You tin can and so delete it using either Windows Explorer or Mac'south Finder.

You can use Lightroom's Plug-in Manager'south "Show in Explorer" or "Show in Finder" buttons to go directly to the binder, making it easy to observe the plug-in binder on your arrangement.

Saving your log file

In order to effort and help identify a problem, I may enquire you to send me a plug-in log file from your machine. If I request this, please follow the instructions below:

1. Exercise the action that doesn't appear to be working, e.yard. attempt 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.

three. Email the log file to me. Attach the log file from the place where you lot saved it into an email and send it to me.

stokesaremin.blogspot.com

Source: http://www.newpproducts.com/lightroom-plug-ins/support-faq/comment-page-9/

Share this post