@JRonertHromas, I just checked your URL and I am getting the error “Widget not whitelisted for this domain” in the javascript console.

Can you check your settings and make sure you added “www.jroberthromas.com” in the domains section of the configuration?

Same answer as above. “Widget not whitelisted for this domain” error. Check your configuration for “alianzauafc.com”.

@realfaustus this domain is currently not responding at all…

Same diagnostic. “Widget not whitelisted for this domain”… Do you have “www.rowthree.com” is your configuration.

There is a timeline creation limit of 100, no theoretical limit per page. In practice, over 8-12 would seem like overkill…

We are planning for widgets creation via API, but I do not have a specific date for that one.

We hear you :slight_smile:

Yes, the old search widget will work for another 6 months. They did have known annoyances, like 150 API requests per hour. We strongly encourage you to migrate to the new embedded timeline, they were designed to scale to millions of requests per day.

That one was easy to answer. Glad to know it works.

It’s almost realtime, but can lag a few minutes (caching).

Not possible currently. It will be a challenge to squeeze it down smaller, but we might try. No warranties.

awesome, it’s working, i didn’t noticed that we need to add both domains, with and without “www.”. Thanks Sylvain!

Off Topic: Is there gonna be a “language option” version?

Tweet embeds have a min-width too. Frustrating but seems part of Twitter’s desire to control display of Tweets and Twitter Cards.

Never mind, i have just read about the LANG attribute :slight_smile: Thanks!!

Hi Paul,

Are you using Chrome to configure the widget? We’ve got a small bug in the settings page at present where the native colour picker in Chrome doesn’t allow you to not set a colour, so it’s defaulting to black. We’ll fix that—obviously—but in the interim if you use Firefox or Safari to edit the widget you should be able to delete the colour and it will then default to the TweetDeck-style blue.

Ben

Hi Paul. That’s only partially the case. I mean, we obviously have a common design of what a Tweet looks like at Twitter, and the new timelines are an implementation of that design, but the widgets do implement two variations already (wide and narrow mode at < 320px width) to try and be more adaptable to the web.

The issue with going thinner than 220px is the amount of line wrapping that occurs around user names, and the legibility of the line length of the Tweet text itself. Making the avatar even smaller only buys a few pixels before they become indiscernible, and removing avatars would compromise the representation of user’s identity (especially in the case of recognising Retweets in the timelines.)

All that said, we’re keeping an eye on how people get on with the constraints as they are, and could revisit it if there’s a common problem. What’s the column width you’re trying to work with?

In this initial implementation the widget will attempt to size its width dynamically based on its container (or, you can put an explicit width=“300” attribute onto the embed code you can set it in advance. The widget can be sized between 220px and 520px (520 being the width of Tweets on twitter.com, 220 being the smallest we could make the design work without illegible line lengths and horrendous username wrapping. See other reply above.)

At present the widget does not dynamically resize if the page size is changed dynamically, but should initialize into an appropriate size in your adaptive layout when the page loads. How would you like it to behave? Are you adapting your page layout using pure CSS, or are there JavaScript events already occurring in your code that you’d like to hook into the widget?

Ben

Here’s the problem on my homepage http://www.sebastienkalonji.thirdwaveband.com

+1 to needing a username parameter generated server-side to have personalized timelines for a few thousand professionals who have profiles on our site.

If “Domains” include dash “-”, “Domains” work un-expect behavior. you can input “foo-bar.com” into Text area of “Domains”, but it has “bar.com” after “save changes”.

Dev team, I sent you some tweets, but I’m unable to get this working with subdomains. Have you tested this with subdomains? Just wondering.

Under the “Domains” section, if I enter topfiveawards.com, it doesn’t show on www.topfiveawards.com or http://wordpress-themes.topfiveawards.com/. If I update it with www.topfiveawards.com, then it shows great on that section, but no subdomains work.

If I try to save a new “domain” as windows-hosting.topfiveawards.com, it ends up saving as hosting.topfiveawards.com, so the dash in subdomain is also not working.

Any chance I can get this fixed? I’ll leave it up for 24 hours so you can see, but after that, I need to remove it. Code added to the right sidebar of every page, when it isn’t working, it just shows a text link.