This has been an issue with Flickr for the past couple of months – intermittently there have been cases where their web-service calls come back with 0 responses (not failures, but just empty responses). Unfortunately there is no fix for this, apart from them fixing the reliability issues on their side. I have seen this happen with small as well as large galleries.
FYI, I tried loading each of your 5 pages – they all loaded at the first attempt. So I tried doing reloads of each of them a few times, and 2 of them had 1 failure each. As there are no “errors”, there were no messages on the page; it is just that the response from Flickr itself was blank.
It might be that they are applying “rate limits” in specific scenarios. Their API T&Cs state:
- Limits: Since the Flickr API is quite easy to use, it’s also quite easy to abuse, which threatens all services relying on the Flickr API. To help prevent this, we limit the access to the API per key. If your application stays under 3600 queries per hour across the whole key (which means the aggregate of all the users of your integration), you’ll be fine. If we detect abuse on your key, we will need to expire the key, or turn it off, in order to preserve the Flickr API functionality for others (including us!). We also track usage on other factors as well to ensure no API user abuses the system.
It is conceivable that you might be hitting some sort of “micro limit” somewhere, but that is just a guess.
Thank you for the quick response….
Its very strange, if the page does not load on a desktop browser and you make the window smaller (to mimic mobile) the gallery loads.
That’s interesting. From what I can see, you have some behaviour that is causing the images to come in from the top left side when the pages are loaded – this is probably happening from your theme or a different plugin. It is possible that such behaviour is conflicting with Photonic’s lazy-loading.
You can try to turn off Photonic’s lazy-loading using this option: Photonic → Settings → Flickr → Flickr Settings → Layout processing engine. Set this to use JS instead of CSS. See if that helps.
unfortunately Js did not change the issues.
i checked flickr for call stats to make sure:
Total calls in the last hour: 144 Total calls in the last 24 hours: 1900Calls in the last day Maximum hourly QPS in the last day: 0.12
unfortunately Js did not change the issues.
JS should help you with the scenario where you are resizing your browser to show the images. It wouldn’t help you with core issues at Flickr’s end. I see that you have reverted to the CSS layout, but you might want to try keeping the JS layout for a bit and see if the resizing is required. If you still have the “JS” setting, then check if you have a caching plugin, or some sort of caching enabled. Try flushing the cache, in that case.
Total calls in the last hour: 144 Total calls in the last 24 hours: 1900Calls in the last day Maximum hourly QPS in the last day: 0.12
Thanks for verifying this. So, at least the issue is not due to any type of rate-limiting.
