robkm

I take that back. After all this, I believe it was a caching issue. If I remove the above flags, I still see the album. I have been purging and deactivating the cache plugin (that my host must of installed, recently), but that didn’t help. About a half-hour ago I renamed the cache plugin folder, but it still didn’t change anything until I added the protection='none' flag, which I think now was just coincidence. I’m going to create another album with the cache disabled and see what happens.

I just tried access='public,protected,private' and the album still shows, so I guess they both work..lol.

Yea, I fixed it! I was just reading another topic here where you were helping someone to properly implement the shortcode, and I noticed this – (protection=’none’) – in the shortcode. I added that to mine and it is now showing album 285, which is protected!

Thank you for the time you spent trying to help me figure this out, I really do appreciate it!

• This reply was modified 7 years, 9 months ago by robkm.

This is the page (https://bit.ly/2k9y5AH) where the album is embedded, if it helps.

• This reply was modified 7 years, 9 months ago by robkm.

Sorry, no it does not.

Yes, I can confirm the refresh token is saved.

The ID in the API link is the Album ID, which I already have in the shortcode…

[gallery type='picasa' user_id='My ID' kind='photo' album='6384967383312460833']

The way the code is written is, it uses your Refresh Token, then, behind the scenes, it obtains an access token, then uses the access token to retrieve your albums.

That is the way I understood it, but I wasn’t 100% positive.

What happens if you open the API link I provided above in a browser where you haven’t signed in to Google? Does it give you 272 albums or 284?

If I go to the API link not logged in, I get 284 albums, but that is because I used the Event Gallery tool to make those 12 albums public, so they now show and are marked as <rights type='text'>public</rights>.

I just created album 285 and it is not listed at the API link when I’m NOT logged in. When I am logged in, I see it listed but again it says <rights type=’text’>protected</rights>.

Now, from the list of 284, if you fetch the ID of an album (<gphoto:id>) and use that in the shortcode, does your album display?

I was able to get the album ID from the Event Gallery tool, which is what the <gphoto:id> is, so nothing changes on that front.

Thank you for the link. There was about 284 albums. One thing I noticed is the albums that are not showing in the ID finder or on my website when I place the shortcode are marked <rights type='text'>protected</rights> while all the working albums have <rights type='text'>public</rights>

I have no way to manually set newly created albums to public, but I did connect https://www.svenbluege.de/picasa/v1.1/, which had the simple buttons to make albums private, protected and public. However, Google has just changed the API again, so even that doesn’t work anymore. Uuuuugh.

I count 282 albums on G Photos and 272 albums being found. I usually use ctrl + F when using the Album ID Finder, so I know I’m not overlooking the missing albums.

I narrowed it down to Photonic, but all is fixed. I logged on to my server via ftp and changed the name of the plugin’s folder and created a new one. I put Photonic in the new plugin’s folder and still had the issue.

I then deleted Photonic and uploaded a fresh copy and that seemed to do the trick. I have since activated all the other plugins with no issue.

I’m thinking one or more files were corrupt. I’m just glad everything is working again! ??

I would also like to add, after trying Picasa authentication, it works perfectly. So much better than finding the album ids in the way I posted and definitely a better solution!

You betcha. It was the least I could do to help in return for all your hard work and a fabulous plugin. Cheers!

Thanks for the link. I checked out that page and someone mentioned to “Make sure when copy/pasting the client id you don’t include a trailing space.”

It turns out I included a space in front of both the id and the secret. I deleted that white space and all is good now.

Thank you again. Marking as resolved!

I went back to version 1.57 for now. Everything is back to working fine. If I get the time, I may apply that workaround you provided.

Thank you for taking time out of your day to help!

OK I have narrowed it down to a problem with Swipebox. I have tried all the other pre-installed lightboxs and they all work except the aforementioned.