Twitter has made some changes recently. These changes allow you to have more control; select your choices of timeline to display on your blog or website. You can now display User Timeline, Favorites, List and Search. The new, simple and improved widget Configurator makes life easier.
I find that adding Jetpack widget on WordPress a little big confusing at first but once you know where to get the widget ID, turns out it was very simple.
Step One – Create New Widget
You can visit your setting by following this link directly https://twitter.com/settings/widgets/new/user
Step Two – Choose a timeline source
Choose between User timeline, Favorites, List or Search to be displayed on your blog or website. Once done, click “Create Widget”.
Step three – Copy and paste the code and or copy the widget ID
Now, copy the code and paste it into the HTML of your site. For all of us who have installed Jetpack plugin, we need only the widget ID as shown below.
Congratulations! You’re done.
thisBeast.com – Sharing tech tweets you can use daily. follow me on Twitter.
5 responses to “How-To: Add New Twitter Timeline’s Widget On WordPress”
some wp plugins may conflict with twitter widget, if they mess with JS , example – BWP Minify, widget wont load any tweets if script is minified
I just wanted to let you know that I had a Twitter feed as a widget on my blog and it throttled my blog, causing it to crash. Something to consider…
Hi Prof Kenna,
Wow that doesn’t sound very good.
I have been using Twitter widget for a very long time, I haven’t heard of such problem. I am guessing your other widget are conflicting with Twitter widget. Twitter by itself will not take down a blog as far as I concern.
depends on widget implementation, some widgets use javascript to query twitter servers, some work on server side and since twitter limit API requests per hour per IP, seems your widget worked on server-side
Leela, No wonder I have no problem hahaha.
Prof Kenna, Maybe you can give it a try. The method above will probably work for you since Twitter API query from client side instead of server side. Cheers!