Was working fine on local server but not on live server

I have done some more digging and apparently it is do with the songkick-concerts-cache not updating in the database.

When I fist saw it, the content was value was empty so I copied the value from the local db and it the events showed fine.

I then did a test and updated the widget and it has gone back to not working again with the value being:

a:1:{s:115:"https://api.songkick.com/api/3.0/artists/992288/gigography.json?apikey=io09K9l3ebJxmxe2&order=desc&per_page=5&page=1";a:3:{s:6:"events";a:0:{}s:5:"total";N;s:9:"timestamp";i:1371562852;}}

The value on the local db has the above value to start with and a whole lot more after (wouldn’t let me paste on here)

Any idea how to fix this so the songkick-concerts-cache updates properly?

Hi there

Sorry for the late reply, and that you’re having problems!

This is very strange indeed. I tried to reproduce it, but couldn’t.
What’s the shortcode that you’re using?

The value you shared was cached on June 18th (from the timestamp) and should have definitely been refreshed automatically by now.
Can you try to remove that value from your DB?

Also, I’m not sure what you mean here, could you explain it again?
“When I fist saw it, the content was value was empty so I copied the value from the local db and it the events showed fine.”

thanks!

Hi

Thanks for getting back to me.

The shortcode I have been trying is the one you supplied but even through a widget it doesn’t work.

When I first started investigating the database on the live server, the songkick-concerts-cache field was totally empty, I then coppied the data from the localhost’s songkick-concerts-cache and it seemed to work.

I’m not technically minded but it seems that the songkick-concerts-cache field isn’t updating correctly.

After some more digging, I’ve realised that the hosting company is using old versions of mySQL (5.0.77) and phpMyAdmin (2.11.9.5) so not sure if that’s got something to do with it.

hi again!

I released a new version (0.9.4.5) that allows you to bypass the cached API responses. You can try that out and see if that was actually the problem.

Ideally you’d have the cache turned on, so the plugin doesn’t impact your page’s response time. But you can use this setting just to check if that was a problem.

Could you also get the list of errors and warnings from WordPress?

thanks!