WordPress.org

Ready to get started?Download WordPress

Forums

Latest Tweets Widget
[resolved] [closed] Broken Widget, Showing Serialized Data (3 posts)

  1. takosabi
    Member
    Posted 11 months ago #

    Widget is randomly bombing and displaying serialized data rather than the correct HTML display data.

    HTML being produced:

    <aside id="latest_tweets_widget-2" class="widget widget_latest_tweets_widget">
        <h3>Latest Tweets</h3>
        <div class="latest-tweets">
            a:3:{i:0;s:1077:"
            <p class="tweet-text">Boom! ... It's <a class="twitter-hashtag" href="https://twitter.com/search?q=%23BeyondTangyTangerine&src=hash" target="_blank">#BeyondTangyTangerine</a> time! </p>
        </div>
    </aside>

    Specific Tweet that is breaking the Widget:

    https://twitter.com/youngevity/status/375297443442982912

    After posing another Tweet, the HTML output looks like this:

    <aside id="latest_tweets_widget-2" class="widget widget_latest_tweets_widget">
        <h3>Latest Tweets</h3>
        <div class="latest-tweets">
            a:3:{i:0;s:286:"
            <p class="tweet-text">yikes!!! <a href="http://fb.me/1Ji63Jek5" target="_blank">fb.me/1Ji63Jek5</a></p>
            <p class="tweet-details"><a href="http://twitter.com/youngevity/status/375332486429282304" target="_blank"><time datetime="Wed Sep 04 19:00:12 +0000 2013">2 minutes ago</time></a></p>
            ";i:1;s:1077:"
            <p class="tweet-text">Boom! ... It's <a class="twitter-hashtag" href="https://twitter.com/search?q=%23BeyondTangyTangerine&src=hash" target="_blank">#BeyondTangyTangerine</a> time! </p>
        </div>
    </aside>

    http://wordpress.org/plugins/latest-tweets-widget/

  2. timwhitlock
    Member
    Plugin Author

    Posted 11 months ago #

    I can't reproduce this error, I'm afraid. Including that exact same tweet.

    My plugin uses WordPress's built-in "transient" cache and does no serializing or deserializing of tweet data itself.

    It's possible that WordPress is being it's usual clever self and deciding for you that the serialized string is actually not a serialized string, so not deserializing it. If I could reproduce the error I'd start by debugging the maybe_unserialize function, but I'm afraid I can't. Perhaps someone else on this forum can.

    If you had APC installed, this would be used instead of WordPress caching, so my suggestion would be to install APC if you can.

  3. timwhitlock
    Member
    Plugin Author

    Posted 10 months ago #

    Closing after one month without follow up.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.