kirilln

Critical security issues and P0 bugs would still be addressed. Sorry, but no time to add features, improve performance, or fix non-critical bugs.

If CacheManager fails to work on your site please request a refund via PayPal. Payment would be refunded with no questions asked.

CacheManager does work on hundreds of sites. There are some installations of WordPress that either use non-standard configurations, have custom settings on hosting accounts, and etc. that could cause CacheManager’s AJAX requests to fail. I am not able to find time to debug each individual installation any longer so will just refund your payment.

Found the issue. Related to WP3.6 jQuery version of tabs widget. Will be fixed in v4.1

Fixed the bug in 4.1. Will publish the update soon

Roman’s issue is fixed and the fix will go out in v4.1

pixeldawg’s issue was different. Also fixed in 4.1

Try going to Settings > Tweet Blender > Advanced tab and disabling use of Search API.

Sometimes tweets from users don’t come up in searches and that should address that case.

This is something specific to your site. If you can provide me FTP acces I can see the logs and try to figure out what it was. Email me to tweetblender AT gmail DOT com

Twitter changed timestamp format so if you had tweets in the archive then you’d see that error. This should be fixed in v4.0.1 which I just released.

Deleting the plugin, as @indigow mentioned, would also work because it clears out old tweets that had the old timestamp format; however, if you’d like to preserve history then upgrading to 4.0.1 is a better way.

@pie123: thanks for the update. I think w3total cache is trying to minify my JS files which are already minified and that’s the root cause of this. I’ll dig more and v3.4.0 should work OK without conflicts

@kromedesign: sorry it took forever but I just looked at your site in FF and do see the recent tweets. As far as import errors, can you send me that CSV? I’d like to see what’s up. I’m at tweetblender AT gmail DOT com

@pie123: what’s the url of your site?

I’ll do some additional testing with W3 total cache before next release.

@kromedesign: what’s the url of the site? W3 Total Cache could definitely have something to do with it but I’d need to look at the site to see what’s up

@Zemcad: Tweet Blender uses the version of jQuery that ships with WP. You’ll see the call to wp_enqueue_script('jquery'); in tweet-blender.php

I’d help you figure this out but would need temp admin access and possibly FTP access. If you can provide that, just email details to tweetblender AT gmail DOT com and I’ll take a look at your theme.

@popbox: not sure I understand your post. When a site crashes, you can just disable the plugin – there is no need to “migrate to a larger server and reconfigure much on the back end”.

YES, WITH CACHING ENABLED, LARGE NUMBER OF SOURCES IN THE WIDGETS, FREQUENT REFRESHES AND HIGH TRAFFIC TO THE SITE YOU WILL HAVE REALLY HIGH SERVER LOAD WHICH COULD LEAD TO A CRASH.

As I wrote above, you can take some measures to decrease the load on the caching system OR simply disable caching under WP Admin > Settings > Tweet Blender > Archive.

Finally, as with any misson-critical site it is a standard practice to use a staging server to evaluate changes to the configuration. So before you install any new plugins I recommend you set that up and use that test site. That would help you avoid downtime.

Bottom line, stop giving users bad advice and get your infrastructure and processes properly configured.

Hello,
checked your site and see 2 javascript errors in your theme that seem to be blocking Tweet Blender execution. You can use FireFox with Firebug to check them out.

Everything else seems to be set up and configured properly.

Found a bug in my code that was related to SEO feature. Unchecked the SEO setting in admin and embeds now work (https://domainfeeds.co.uk/twitter) . Will have the bug fix ready in v3.4.0 this month