kromedesign

Hi Kirilln, the minify settings in w3 total cache didn’t seem to fix the issue … however we went into ‘advanced settings’ and ticked ‘Disable data caching’ to on .. and we now see to have no 500 errors on the page.

I’m not sure how that will affect the performace of the plugin or if it will impact on the cached tweets stored by the additional caching plugin?

Settings set – we’ll give that a little while and check for 500 errors and errors in the server log – fingers crossed, thanks for the heads up!

Ah – we’ll give that a go!

A quick update this end – the plugin did seem to start working, which was great. However we think it may haveconflicted with W3 total cache – causing 500 errors on the server. So – we’ve had to remove it for now ?? .. which stopped the 500 errors – a real shame as it’s a great plugin!!

We’ve also tried saving out the cached tweets to a CSV and loading them into the dev site – but it jsut says all 13 record generated errors. The CSV looks fine in excel …

oh – and thanks for looking ?? !!!

it’s https://www.cloudsoftcorp.com/category/blog/ – we’ve tried taking off W3 cache on their dev site but still seem to be having the issue. I’ve assumed when it says ‘once on load’ in the widget that should be every time the page loads it will try and refresh?

We’re also having issues with tweet blender not loading posts… oddly though it loads them first time around, then the only way it will load them again is if you deactivate the plugin – and activate it again. We were wondering if it might be a caching issue – we’ve bought the tweet caching plugin and have it running alongside W3 Total Cache