On encountering a WP Mysql database error without dying

I’m helping my friend Tina move her blogspot blog to a wp installation on her own website and I’d used the category to tag convertor when I was checking through all her posts to see if things were formatted correctly.Well, I’ve used this tool before and noticed that when you do this it removes all those categories and makes them tags.
This threw me off at first but I got over it.
Except I did first assume that this tool would duplicate, not remove. And in this particular caseI didn’t think that posts that once had a certain category assigned to them would be assigned to a read only uncategorized category. In essence un assigning them. Poor little orphans.

By read only I mean Uncategorized was just text and not a linked category when I went to Manage Posts…
So on her blog if you happened to click on a word in her tag cloud that belonged to a post that used to belong to a category that was converted to a tag but hadn’t been assigned a new category upon saving the post,it made a database error and led to a blank page instead of the single post view.
I read her error log and it told me it was a database error. I didn’t understand the error but I did notice that posts that had both tags and a category were fine and if you clicked the title permalink it led to the single post view.
So all I had to do was go through all her posts that had the text-not-linked Uncategorized category and assign those posts a category.
With my keen powers of observation and deduction I managed to resolve a database error that I didn’t understand. And I didn’t die.
Here is the lovely error message:

WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘AND comment_approved = ‘1’ ORDER BY comment_date_gmt DESC LIMIT 10′ at line 1 for query SELECT wp_comments.* FROM wp_comments WHERE comment_post_ID = AND comment_approved = ‘1’ ORDER BY comment_date_gmt DESC LIMIT 10

Purehost Horror continued

I am now in the second day of my IIS disaster with Purehost.
After reading some very frightening reports on the damage an improper 302 can create with googlebots and all search agents, I’m really quite upset.
Purehost techs are supposed to open a support ticket for you when they are not able to fix the issue while they have you on the phone. However, 2 support techs failed to do this and when I got up this morning and checked the site it was still redirecting in a way that will never complete. So I had to call back and explain for the 3rd time what the problem was. Not only that, but the last tech support guy I talked to said I would get a call back from Purehost this morning…no such luck.

Do not ever use Purehost for hosting.
I repeat,do not ever use Purehost to host your website.

They charge as much as other, far more excellent host providers, (mt) comes immediately to mind at this same price point, but give you nothing for this high price.
Basically if you want anything more than static html pages, ie a database or anything served up dynamically, you must pay extra for it.Their god awful site builder program is as old as the hills and churns out crap tables sites. But they seem to be proud of it.

Black marks against Purehost:
No forum. I will say it again: there is NO support forum.You are on your own.
Ancient knowledgebase.This knowledge base is written for it’s Unix platform customers and is really misleading to Windows customers not to mention packed full of links that lead to tutorials that haven’t been updated since 2000.
If you are on Windows you have to pay for databases. Unix customers get them free with their hosting package.
They don’t actually have tech support;the same folks who answer tech questions also answer billing and sales questions. Hit them with any kind of problem and the 1st thing they do is start whiffling about your scripts being wrong. As if.

Reasons to pick Purehost:
You fell in love with Microsoft’s Frontpage back in 1995 and never bothered to learn any other way to build a website.
You love tables based layouts so you will love their Shopsite doodad and Sitebuilder doohickey.
You enjoy having to fight uphill in order to get the simplest thing to work.You love frustration and challenges.
You don’t mind it if they let your website go down for 3 days.

Typography or font-weight,which is the culprit here?

font firefoxfont ie7
These are 2 screenshots of paragraphs, the first image shows arial with font weight set to normal and about 14px in FF,the second in IE 7.

Just to make certain it wasn’t a flaw in the stylesheet I wrote I checked this issue on many other webpages of very well known CSS experts and noticed the same thing happening on their sites. FF shows a light, less dense looking pixel value, IE7 shows a better looking (in my opinion) typeface rendering.
It doesn’t matter if I specify font-weight,normal the difference persists.
So is it my choice of typography or a font-weight bug?
I messed about with a few different font-families and font weights but setting the body base font weight to bold looks too dark and chunky to me.No matter what I’ve tried so far I can’t find a way to make both pages look the same.
Then I found this link on Simplebits Do websites need to look exactly the same in every browser ?
Hmm.

WordPress emergency?

Sounds pretty alarming-there is a new version of WP that fixes a bug that might allow hackers to do something with post drafts and I have eleven of those.If you have WP you saw this the last time you logged in and this isn’t news to you.So why am I writing a post about it? Because I just freaking updated all my client’s sites and most recently my own to v.231. I am too tired to do it now. I don’t really care about my site but I hope nothing happens to my client’s sites.