Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • We are experiencing this issue as well and it’s affecting a large chunk of our site. We’ve had to disable the plugin to alleviate the issue for now.

    That wasn’t the problem for me. In controllers/twitter_widget.class line 210 it has the following if(false === ($tweets = get_transient($transName) ) ) : This was always evaluating to false and so the api was never even being called. Can you provide some details in to why this was happening? I’m not familiar with get_transient and the docs don’t shed much light on it.

    Anyway, after commenting out the line and the endif; down on line 262 I got it working again, but I would like some explanation here.

    edit
    As a quick follow up, I debugged the value of $timeto_store as you might ask me what it was set to, but it was set to 4 which means, according to the docs that set_transient should have expired after 4 minutes. I assume the get/set transient functions acts like a cache, and if that’s the case they were never clearing for me. I checked the database table wp_options as well for the backup option and it was there and the autoload columns was set to yes. Not sure if you need that information, but I thought I’d add it just in case.

    I’m having this issue as well. The latest tweets are from 1 week ago. I tried removing the widget and re-adding the api keys. I also tried deactivating and deleting the plugin and reinstalling, but neither of these resolved the issue. The latest tweets were the same, from 1 week ago.

    The only relevant update we did is we did update the core of WordPress to 4.3 in the last few weeks.

Viewing 3 replies - 1 through 3 (of 3 total)