|Using the old twitter embed code|
In the past, embedding a twitter feed was not straightforward, but was certainly possible. A quick google search would bring up instructions, and allowed us to produce some nice results (see image).
So, I was really delighted to see that just last Friday, Twitter have announced a new way to embed timelines, making it easier to embed a public twitter stream into a webpage. The old embed codes will no longer work from March 2013.
Since I was already working on my Blackboard course for the current year, I thought I'd give it a try.
Step 1: When logged into twitter.com, go to your settings page and select Widgets from the left menu bar.
Step 2: Click Create New, to create and configure a new timeline widget.
Step 3: Choose a timeline source. In my case, I want to search for course related tweets, using the #cel263 tag. I leave everything else at the defaults. The preview is looking good so far!
Step 4: List the domains where this widget will be embedded. I use the domain for this blog, and also the domain for blackboard (which is on a secure server).
Step 5: Click on Create widget. Success, my widget has been created and I just have to copy the embed code!
Step 6: Now, in my Blackboard course, I create a new item and paste the embed code into it. I'm done!
Clicking on the link will open a new page, but produces a Blackboard error message.
It's not particularly elegant!
When I first encountered the problem, I tweeted about it. I've had a couple of replies from other people experiencing the same issue.
Anybody else having problems with new twitter embedded timelines in Blackboard? bit.ly/OmRuEiI also posted on the Official Timeline Questions blog, but to date have seen no reply.
— Sharon Flynn (@sharonlflynn) September 6, 2012
Has anybody figured this out? Please let me know. For the moment, I'm sticking with the old embed code.
21 September 2012: Update
Hooray! The embedded twitter widget is now working for me. The problem, it appears, was with secure sites (https) but a fix has been implemented. Now, what I see when I insert the code is much, much nicer.
31 January 2013: Update
In response to a couple of queries, I didn't implement the fix, I presume Twitter did. The one change I did make in the narrative above is in the list of domains at step 4. This now looks like: