Dave Kellam

Sorry for the delay in responding.

The plugin is limited to a maximum of 20 photos, due the limitations of the feed provided by Flickr.

If you still need caching, and an old version of the plugin worked, you can still grab them here: https://www.ads-software.com/plugins/flickr-rss/developers/. Nothing really changed other than fetching the images from an https:// url. It’s possible that your server has some sort of issue grabbing from an https url.

Going to mark this as resolved.

Which version did you have before, and which version did you upgrade to? And are you using caching? There was a bug with the cache in the 5.3 release, fixed in 5.3.1.

Hmm, don’t really know to be honest, was the caching working before. As part of a rewrite, I’ll use built-in WordPress methods for grabbing the files, and not be reliant on system tools.

Easiest solution for now, is probably to turn the cache off and just load the images from Flickr.

I don’t think it’s related to flickrRSS.

Seems sort of odd… maybe someone has told wp-pagenavi not to update? Perhaps it’s worth updating the plugin, maybe someone got in through an error and has been suppressing notices about updates to the plugin.

I would seem that auto-update only plays nice if the plugin’s folder name matches the repository url. I don’t think auto-update existed the last time I released a version of the plugin. My suggestion would be to rename the file to flickr-rss (you may be able to get away with symlinking flickrRSS to flickr-rss).

Sorry, there’s a bug with the cache in the most recent version I released. If you disable the cache setting on the options page, it should start working again. I also should have a fix pushed through later today.

Manx thanks for commenting here, I’ve been swamped this week. Could’ve sworn I pushed a 5.3.1 release after your patch suggestion, but it might have only been to github.

My apologies, it has been awhile since a previous update and I have been working on an update that was more of a complete overhaul. I wanted to make sure a fix got pushed out for Flickr’s SSL update, but didn’t test the cache (as Manx mentioned)… to be honest I didn’t realize people still used the cache, and it was something I had been thinking about stripping out.

Any chance you could drop the code on pastebin? The forum rules don’t let anyone post code.

Sorry about that, it had been years since the last update and I guess my sandbox install didn’t have the debug flag on. I’ll try to get that fixed up in the near future.

It was a check to see if you had an older version of flickrrss installed, and to update the options in the database. In all honesty, I forget if there were other database tweaks between 3.2 and 5.1, it’s been years. Did you get it fixed at all, or just revert to an older version?