snowgoon

As this is the only forum post that comes up for this error, can I presume it won’t be fixed in the main code stream? If so, how can I check?

My blog is currently running at about 85% functionality, and I guess hand fixing all of the instances where this function is called will mean doing the same every time I upgrade from here onwards?

Not good WordPress peeps, not good at all.

cheers akc.

Doesn’t really help though – I also entered the characters as “special characters” but I guess this might be more an RSS issue and the way it handles this stuff.

I’m off to dig through the specs (RSS) to see what they have to say.

Does this apply to post titles as well?

My feed has broken after I posted some gaelic which includes e acute and a acute – which I posted as eacute; and aacute; – the title displays fine but the feed has since borked.

Gave me this error:

XML Parsing Error: undefined entity
Location: https://www.gordonmclean.co.uk/wp/wp-rss2.php
Line Number 82, Column 11:
<title>L&aacute; Fh&eacute;ile P&aacute;draig</title>

I have the same. Maybe someone can confirm but how can blogrolling work but not the internal WP “blogroll” function?

It’s a bit cheeky to send out a couple of hundred emails to ask all my ‘rolled’ sites to ping ping-o-matic – half of them won’t even know what that means.

Isn’t there any way to edit the PHP in WP to pickup updates from another service (or three).

Some way of filtering the referrers would be good – to take out any random search hits from Google for example.
And as long as I can get a unique visits count I’m a happy man.

pete – you don’t actually NEED to have the index.php in the WP directory. I’ve stopped copying in there as I just edit it locally and upload it where my URI expects it to be (root in my case).

You only need index.php in the WP directory if you want to edit it through the WP Admin interface.

Of course I still think this is a bug – but we’ll see what 1.5 brings.

Sorry, no movement on this. Tried to upgrade to a later build. Failed spectacularly.
I’m gonna wait until the official 1.3 is out, and hope the upgrade isn’t too arduous and is well documented.

Seemingly this has been fixed for 1.3 so I guess it’s a case of “hang in there” until 1.3 is released.
I’m trying to get a definitive list of 1.3 fixes but it’s proving tricky!

I’ve logged this as a bug.
https://mosquito.www.ads-software.com/view.php?id=524

macmanx – I know I could use a redirect – that’s not the issue.
The WordPress options page allows you to set the Blog URI to a different location from your WordPress install. If it allows you to do that, then I would expect it to handle the location and editing of the template correctly. It isn’t.
I THINK this is a bug and will check this today.
Ohh and of course, it may be PEBCAK as I’ve only just switched to WordPress (yesterday).
Anyone else got any ideas?