Forget it. Ill just stick to WP 1.5.0 for now. I didnt copy the theme from the other directory, I did a new fresh install and I did not activate any plugin after installing.
ok so you did a new fresh install right – and you’re saying that after a completely fresh install on a clean db that wp was failing to recognise even the default kubrick or classic themes?
if it’s a textile/markdown issue, disable it – there’s probably a way to get this sorted. if it’s because of what’s been brought into 1.5 then it’s a little..odd. And 1.5.1.1 also does this?
Read IanD post above. Thats the problem causing it and I cant stop it.
Actually, it’s a bug with 1.5.0. http://trac.wordpress.org/changeset/2549 and doesn’t have anything to do with entity2NCR.
To keep this from happening, see these possible solutions. The offending line in default-filters is:
add_filter('bloginfo', 'wptexturize');
Unfortunately, removing that filter from bloginfo will effect some other stuff, too. Try it out to see if it breaks everything.
Bug submitted: http://trac.wordpress.org/ticket/1410
mdawaffe – has this been fixed in 1.5.1 and 15.1.1 – just reading from xero’s post and your comment, that it’s from 1.5.0 but it seems to work ok for him in 1.5.0?
The reason it works in 1.5.0 is because of a bug in 1.5.0. The bug was fixed in 1.5.1+, and so his site broke.
I realize that all sounds backward: a bug fix breaking things. The problem is that XeroCool’s url brings to light an unforseen problem which the bug I’ve just submitted discusses. These two bugs (the one fixed in 1.5.1+ and the one I’ve just reported) are related, but distinct.
