Online casino free no deposit bonus philippines,Tq777 login download.Recharge Every day and Get Bonus up-to 50%!

Plugin Author Sayontan Sinha
(@sayontan)

6 years, 2 months ago
Some time on 16th or 17th of January 2019 Google deprecated the Picasa API, resulting in multiple WP plugins breaking.

Some history:
- Google announced in Feb 2016 that it would kill Picasa, PicasaWeb, and the PicasaWeb API …
- … But it did not create / provide a public API for Google Photos for a long, long time.
- Finally in May 2018 Google introduced the API for Google Photos in a “developer preview” mode (i.e. some sort of a beta mode), and it kept the Picasa API alive.
- In July 2018 I added support for Google Photos to Photonic. I did make an observation in the Picasa documentation:
  
  Also note that while Google hasn’t officially announced the date for phasing out the Picasa API, it will be phased out once the Google Photos API is more stable.
- In late September / early October 2018 the Google Photos API moved out from “developer preview” to “Production”.
- In January 2019 the PicasaWeb API was shut down.
Where does this leave you?

For starters, your pages displaying Picasa galleries will show this:

Failed to get data.
Error:
Start tag expected, ‘<‘ not found

Data returned by Google:
The Picasa API is deprecated. See https://developers.google.com/picasa-web/ for more details and the migration guide.

Given that Photonic has already built in the support for Google Photos you should be able to switch to it though. Note that while the switch is easy, it is not a simple “one-click-and-done” operation.

You have to do the following:
1. First, reauthenticate for Google Photos. While some of these steps are already done as a part of your existing Picasa module, you have to specifically enable the id for Google Photos and then reauthenticate.
2. Then, rebuild each of your galleries one by one using Google Photos. Hopefully the “Add / Edit Photonic Gallery” button that you see in your editor (if you are using Gutenberg this is the Photonic block) will help you with this.
As always, please feel free to open a new support ticket if you run into issues.

Viewing 5 replies - 1 through 5 (of 5 total)

nimbus2006
(@nimbus2006)

6 years, 2 months ago
Hello,

I have been working with following URL;
https://aquoid.com/plugins/photonic/google-photos/#steps

Then I got error code 406, or Apache mod_security errors
```
Not Acceptable!
An appropriate representation of the requested resource could not be found on this server. This error was generated by Mod_Security.
```
So next I follow your Google OAuth2 Playground instruction and ut in https://www.googleapis.com/auth/photoslibrary.readonly https://www.googleapis.com/auth/photoslibrary.sharing.

However, I got a new error like this;

400. That’s an error.

Error: invalid_scope

Some requested scopes were invalid. {invalid=[ttps://www.googleapis.com/auth/photoslibrary.readonly, https://www.googleapis.com/auth/photoslibrary.sharing.]}

Could you please help me out?

Megumi
Plugin Author Sayontan Sinha
(@sayontan)

6 years, 2 months ago

You are missing the “h” in the “https” for your first scope ??
nimbus2006
(@nimbus2006)

6 years, 2 months ago
Thanks quick response but same result.
```
400. That’s an error.

Error: invalid_scope

Some requested scopes were invalid. {valid=[https://www.googleapis.com/auth/photoslibrary.readonly], invalid=[https://www.googleapis.com/auth/photoslibrary.sharing.]}
```
What’s wrong?
Plugin Author Sayontan Sinha
(@sayontan)

6 years, 2 months ago

Your error message actually changed, and the first scope is now “valid”.

You have a “.” at the end of the second scope, i.e. you have “sharing.”, but it should be “sharing”

nimbus2006
(@nimbus2006)

6 years, 2 months ago

Got it! Thank you so much!

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Picasa API Deprecated’ is closed to new replies.

Tags