I have to say this is rubbish. It doesn’t even look right on my page because it now doesn’t fit into the space allocated for it. All that shows is a link saying “Tweets by @ImagicDesign” in Times NR.
I am not about to redesign my whole web site to accommodate a massively wide frame just so Twitter can advertise at my visitors.
Stupid Twitter. >=o
Heather
Imagic Design * Good Design - No Compromise
email@hidden http://www.imagic-design.co.uk
Twitter @Imagic-Design
T: 01634 864017
If you make a style called .twitter-timeline in the Styles palette (as a Tag-only Style), you can influence how this link will appear.
What I see in the Safari Developer Tools is a 1x1px iframe (presumably the keyhole through which they can bug your visitors) and a script. That script throws an error saying "Widget not whitelisted for domain ‘scruffydogltd.com’. This is likely a Twitter.com setting you need to make, I haven’t tried this method myself, but they are apparently restricting access to this widget to requests from “approved” domains. When you generated the widget, did it ask you for the domain you were going to access it from?
Walter
On Oct 11, 2012, at 10:55 AM, Heather Kavanagh wrote:
On 11 Oct 2012, at 15:37, Paul wrote:
1 - Create the Widget in Twitter
I have to say this is rubbish. It doesn’t even look right on my page because it now doesn’t fit into the space allocated for it. All that shows is a link saying “Tweets by @ImagicDesign” in Times NR.
I am not about to redesign my whole web site to accommodate a massively wide frame just so Twitter can advertise at my visitors.
Stupid Twitter. >=o
Heather
Imagic Design * Good Design - No Compromise
email@hidden http://www.imagic-design.co.uk
Twitter @Imagic-Design
T: 01634 864017
You also have an error in the Plus One script, wherever that is coming from – an unescaped ampersand. Try removing that and see if it improves anything.
This is likely a Twitter.com setting you need to make, I haven’t tried this method myself, but they are apparently restricting access to this widget to requests from “approved” domains. When you generated the widget, did it ask you for the domain you were going to access it from?
Yes, it does. I’ve added my ID web site domain using the format they suggested (sans http://).
The widget creator shows a preview of how the timeline should look. It’s not supposed to just be a hyperlink.
That’s not the issue. The script includes a bare & in a URL context, where it should be encoded as &. Not sure if it’s under your control. Remove the Google script entirely, just to narrow down the Twitter issue to a single set of factors.
Walter
On Oct 11, 2012, at 11:09 AM, spark wrote:
That’s the Google button script, copied straight from the Google site. Wonderful.
I’ll try converting it to plain text before I paste it.
File a bug report with Twitter, and see if they give you any suggestions. My guess here is teething pains. This is all quite new for them and you. Personally, I think it’s all quite icky what they are doing; I realize they have to eat, but they could do something like App.net have, and charge a subscription. Or they could just realize that they are a protocol, not a platform, and look to monetize the protocol the way the browser manufacturers have done (search engine licensing, mostly).
I just refreshed my browser on your test page and your tweets showed up.
It doesn’t seem to work when you preview locally, which means you have no method of assessing the impact of the new formatting until you load it on a server.
Having seen the mess it makes of my web site, I have removed the markup, and added a paragraph complaining about it.
I’m not redesigning my online presence to accommodate Twitter.
Heather
Imagic Design * Good Design - No Compromise
email@hidden http://www.imagic-design.co.uk
Twitter @Imagic-Design
T: 01634 864017
It’s really really bad. No styling options, no way of removing the reply box at the bottom, patchy functionality (there are load of complaints on the Twitter site about it).
And I’m getting 'Tweets by…" flashing up before the thing loads. Which looks crap. it’s very fussy about ‘www’ in the approved domain list too. Best to put both versions in to make sure it works.