hmm.
Any sort of caching changes occur recently with your site?
I know I have some amount of errors that are supposed to show for admins only. Impossible for me to tell if you’re seeing those.
Is it possible that there are some issues with your API keys for Untappd? Have you checked their status recently?
Definitely seeing them from the user feed API, tested with my own api key pair, so something is not updating the markup or the cache is stuck, is my guess.
I tried it from Postman and it works as expected. I’m not even sure if I have caching.
And both the Flickr and Twitter plugins on that same page are up to date. It’s just Untappd that isn’t.
I do have wp-cache installed, but it’s deactivated and I haven’t ever messed with that at all.
Know how to do any sort of transient management? I know I use the transients API to store data so that I’m not hitting the API on every single page load.
Not very familiar but I can check into it. Looks like that means you store things in my WordPress database?
I did start using Cloudflare in March, but that’s two months before it stopped updating.
Technically yes. Transiets are a WP core thing that store data to the wp_options table, but with an expiration time. It’s meant to be temporary. Beyond that, any debugging that I could offer would require having extended access to the site in question.
So, thanks again for the responses.
After updating several things and not seeing any change, including purging the Cloudfront cache, I decided to change the limit in the plugin settings.
I had it set to limit=3. I bumped that to limit=4 and saved it. Upon refreshing, I now have the latest 4. It does seem like it wasn’t calling out to Untappd and had just cached some call in the past. Any idea why it would do that? I’m now curious if I’ll be stuck with the latest 4 even after my next checkin.
In this case, if it happened once, I have to assume it’d happen again. Hopefully not though.
My best guess is somehow, some part of the setup isn’t clearing out old transient caches. The fact that you changed the amount to show somehow invalidated the cache is odd since we don’t rely on that value at all for caching.
By all means, let me know if it gets stuck again, I’m growing curious what’s going on. Maybe make it a purpose to enjoy one more that you want to check in with. I’ll be toasting from afar.
