Page size must be less than or equal to 100

Oh. This is my problem too! Did you find a solution?
I do not. For the time being, I reduced the size of my albums to 100 images.
did not return an error message to me, but did not display images above 100 pieces!

Yes thanks, but I wanna display all the album because when a user use the slid show to watch the pictures, it’s not intuitive anymore. He cant know there are other pictures.
I really wanna find a solution to display all album in one go.

Ty ??

Having the same issue here. As a temporary workaround so at least the album doesn’t break on the page, I enabled the “More” button, which requires that you add “100” in the field above. Agreed that there’s no way to know intuitively that such a click would be required if in slideshow mode, but maybe put some text above the thumbnails / slideshow as a band-aid for now.

Here’s an example from my site:
https://jacobnovick.com/denali/

• This reply was modified 6 years, 2 months ago by jakenovick.

Thanks, this is indeed my fallback solution. But it must be possible to by-pass this limit even in the source code?

All folks on this thread,
Firstly sorry for responding late – I have been holidaying internationally for the past few days and this is the first I have had access to a connected computer since Saturday.

Moving on to the topic, this is something that has been addressed quite a few times on this forum, and my answer is still the same – though it can be done with considerable effort, it is not worth the risk.

The reasoning is simple enough, though. Whenever you use a third-party API (in this case Google) you must adhere to the terms and conditions. Admittedly this is not a documented “term” or “condition”, however it does fall in a gray area, and there is a catch – rate limiting. What is rate limiting? Google Photos puts a cap of 10,000 requests per day while making API calls. A call beyond 10,000 will result in an error. Note that the other providers (Flickr etc.) have no such limit applied.

Why is this important? Essentially the limit of 100 photos per call is a hard limit. There is no way a developer can pass a higher number and expect to get more photos in a single call. But there is a way to make a series of calls and keep fetching photos till you have reached the end. This is something that can be coded – it isn’t trivial, but it can be done. But each of these counts towards your API usage. Every call you make counts towards it.

Now let’s say you have 500-600 photos in each album and are including 5 such albums on a page. To fetch all photos (i.e. “bypass the limit”) for each album you will be making 6 calls per album, all behind the scenes (i.e. without a user clicking on a “More” button). On a page with 5 albums that is 30 calls. This has two potential issues:

1. Your page will get significantly slower since you will increasing communication with an external source five-fold! This is detrimental to me as a plugin developer, even though the speed of my plugin will actually be driven down by an extraneous factor.
2. If your page is visited more than 330 times in a day, the 331st visitor and beyond will get nothing – an error will show up.

While this is only speculation, there might be a lockout or adverse action as well – I had this happen when I was trying to implement a similar feature for Instagram where the limit is even lower (around 30 I believe). As soon as I experimented with my code Instagram locked me out for around 60 minutes because I had made more calls than was permitted in a certain timeframe. Google is not Instagram, so such a thing might not happen with Google.

IMO the option to “Load More” is a very good compromise for multiple reasons, and should be utilized for such requirements.

Another route you might want to consider is to put in a Feature Request for Google to bump up the limit from 100 to 500 – it used to be 500 earlier till Google brought it down to 100 some time in July.

I am marking this as “Not a support question” as there is really nothing for me to resolve here. Please let me know if you feel otherwise.

thank you for your detailed reply, the reasons are fully understandable. I do not consider this limit to be a bad thing as the user would lose more images. but I would like to ask you to make this clear in the description of the plugin, because I did not discover it, and later it was uncomfortable with users! If I notice it at the beginning, I’ll take it back to 100-piece albums in time.

Same for me.
Thank you ??