Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter wuteng

    (@wuteng)

    Sorry for bothering, it was just a simple calculaton error;
    IF anyone would have problems with this kind of bug go to plugin folder/templates/plain
    and change the following (line 144):
    <?php echo human_time_diff( $aTweet['created_at'], current_time('timestamp') - $sGMTOffset ) . ' ' . __( 'ago', 'fetch-tweets' ); ?>
    into:
    <?php $date = date_create($aTweet['created_at']); echo human_time_diff( /*$aTweet['created_at']*/date_format($date, 'U'), current_time('timestamp') - $sGMTOffset ) . ' ' . __( 'ago', 'fetch-tweets' ); ?>
    And that will solve it. (I have commented out the previous variable just “in case” 😉 )

    Plugin Author miunosoft

    (@miunosoft)

    Thanks for the report.

    It seems the problem that the plugin has with custom queries. The response fetched with a custom query is not sanitized properly.

    I’ve uploaded the development vesion, 2.3.5b05, so you may try that: http://downloads.wp.xz.cn/plugin/fetch-tweets.zip It will not require you to edit the template.

    Thread Starter wuteng

    (@wuteng)

    A ok 🙂 thank you very much 🙂

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

The topic ‘Timestamp error’ is closed to new replies.