We appear to be having technical difficulties with commenting. Technicians have been scrambled. But this site is based on the perl language, so the technicians were probably already scrambled.
Actually, I'm thinking it is a problem in the interface between the sql server and the apache server. If you think I'm wrong, go ahead and leave a comment!!!!
HAHAHAHA!!!!!
But seriously, maybe this would be a good evening to get to bed early. I know that works for me, I have a long day planned for tomorrow.
.....
...
see you on Facebook!!!!
- Log in to post comments
More like this
One of my chief joys in life, often to dismay of others, is working with data. Some members of my family (who shall remain nameless) would characterize this fixation as bordering on obsessive, others just call me a "geek" and leave it at that.
I don't care.
Give me a data set and I can play…
Mike Haubrich and I are developing a science oriented podcasting effort. It will be called "Ikonokast" (all the good names, like "The New York Times" and "Apple" were taken). We decided to enhance the podcast with a WordPress based blog site, perhaps with each page representing one podcast, and…
The commenting issues here are seriously driving me nuts. I've just written another letter of complaint on the Seed backchannel, which always seems to mean that it will sink into neglect once again, so I've decided to also post it here, publicly. I hate to air dirty laundry like this because I…
I've been incredibly busy this term, but not so busy I couldn't create more work for myself. Specifically, by writing an opinion piece for Physics World about the FTL neutrino business, that just went live on their web site:
The result quickly turned into one of the most covered physics stories of…
I'm only noticing the issue with Firefox (and Epiphany, also mozilla-based), specifically where Scienceblogs inserts the "Find more posts in: [genre]" block below the post.
Sorry, Greg -- it's got to be in the presentation front end.
Konqueror works like a champ.
Well, somehow the HTML is screwy. And, it wasn't then it was. .... so .... something must have ..... GONE WRONG!!!!!
Aaaaaaaahhhhh!!!!!11!11!!!eleventy!!1!!
It is surely a sign of the end times!
huh. I haven't noticed. That's with Firefox 3 and NoScript, which is not running a whole bunch of scripts; it is set to allow only scienceblogs.com.
I've only seen the issue on certain pages. This page, for instance, displays just fine. The previous post, Watergate Plumbers, stops the post display after the block I mentioned above.
I found it! The span tag for that block, <span class="channelLinks"> isn't closed.
Any post that is included in the channel links is messed up.
Good going, Dan! I've passed that information on to the fixers!
And if Sb would like to put me on remote staff, just let me know.
I think they should!
I've got experience with Perl, PHP, (X)HTML, CSS, JavaScript, etc., but I don't do Windows unless absolutely necessary, and that's rarely necessary as far as I'm concerned. ;)
Are the broken posts going to get fixed or are they gone forever?
I have not heard any details yet. I assume everything will be restored and fixed eventually. I'll post any news when I get it.
The posts (and their comments) are still there. They are quite visible and usable in browsers such as IE, Konquerer, Safari, etc.
Mozilla-based browsers, such as Firefox and Epiphany will not display the pages correctly because of an unclosed HTML tag (The
<span…tag that I mentioned above is the culprit I suspect.)The browsers in the first group are more "forgiving" of the way certain HTML is presented to them. Mozilla's engine, however, is less forgiving, depending on the way that the HTML is presented.
Posts which are not included in specific "channels" (Politics, Biology, etc. as listed on the main page) are not affected.
And it looks like they got it fixed while I was posting! Thanks, Sb team, for keeping things on track for us.
I am now informed, just a few moments ago, that the site is fixed. If anyone sees any problems, try refreshing your browser. If the problem persists, let me know.
Dan had in fact identified the problem correctly! Thanks, Dan!
Nice job Dan! You win the internets!