Don’t worry, you’re (probably) not a victim of DNS spoofing. As you may have noticed, the site looks a bit different. To celebrate my arrival on a brand-new continent, I’m relaunching this blog with a brand-new, custom, WordPress theme. All of the design work, and the lion’s share of the PHP/CSS work, are courtesy of Monica Joyce. As you might expect, given the nature of this blog, the theme is GPL-licensed and you can download it from her site if you’d like to use it on your own blog.
I’m pretty pleased with the new design, I think it’s very clean and modern-looking without being too gimmicky. It does have some fancyness like transparency, and rounded corners and so forth, so if anyone out there is running into weird glitches (things overlapping, sections disappearing, etc.) I’d appreciate hearing about them. You can leave a comment, or email me. Please include your operating system and browser, too.
When I clicked on an older post (“Observations from the first week in Argentina”) to read the comments, it switched back to the old theme – was that intentional? This one’s opened up fine on the new theme, but there weren’t any pre-existing comments on this post. I’ll see what happens with this one once I’ve saved it.
Looks smart, otherwise!
I’m using Firefox 3.0.7 on WinXP Pro SP 3.
The plot thickens. I tried it on IE 7 and it was the same: the comments links from the old post showed the old theme, as did “More shameless self-promotion”. Trying to add the first comment to an old post used the new theme; the comment I just posted showed on the new theme. More strangely, the existing comment on “¡Bienvenidos a Argentina!” used the new theme. I doubt it’s a caching issue, as I tried it in two browsers, but I guess I could be wrong.
I am actually meant to be hunting my own bugs on a work website right now, so maybe I should shut up and do that. I can look at this tonight, though, if it helps.
It turns out it WAS a caching issue, but not with your local browser cache. I run a wordpress caching plugin that makes static copies of pages that can be served faster, with less server load than dynamically generated pages (on that hypothetical day when I write something really trendy and this site hits the front page of Digg, I’d like it to survive).
I’ve cleared the server-side cache, so all the pages should be showing the new theme now, I hope. Thanks for the bugreport.
White text on a black background has always hurt my eyes, but I do most of my blog reading in google reader anyway, so that’s not a problem for me. A problem you should take care of, though, is that the link color is the same as the body text color, so you don’t know if something is a link unless you hover over it. And I know how you like to slip links in your posts.
Looks cool. I like the background, though I’m quite sure what it is. In FF3/XP there is a slight problem that a good deal of the text seems to turn link-colored when you hover over it, even though it’s not a link. I’ve seen this before and it was caused by anchor tags like <a name=”foo” />, which FF doesn’t seem to handle correctly – changing them to <a name=”foo”></a> fixed it.
Also, where did this site find / how did it know to use my yin-yang avatar? That’s kind of cool.
Also also, there’s no link back to previous posts on the main page.
As we say at my day job: “Sorry, but we could not replicate the issue. Why don’t you try re-installing the software? In the mean time, we have automatically generated a QA ticket so our developers can review the problem.”
shit, we are the developers. nooooo!