dbowen

It appears this bug has been fixed in WordPress 3.0.

Thanks.

Yes, it appears the word Lynx, followed by a space, in a comment or a post will generate an error. Any idea why?

In discussions here: https://www.geekrant.org/2010/03/17/weird-bug-2/ … we noted you can use a nbsp as a workaround.

After all that I’ve fixed it — the main problem was incorrect closure of DIVs.

Thanks,
Daniel

Sorry to drag up an old topic, but I’m having problems with this too: loads perfectly in FF, but erratic in IE.

Main page: https://www.ptua.org.au/

Particularly problematic in IE: https://www.ptua.org.au/category/newsletters/

Test page (to remove any chance of menu causing it) still problematic in IE: https://www.ptua.org.au/test.html

I wouldn’t claim I’m a CSS wizard, and it wouldn’t surprise me if I’ve messed something up, but after hours of looking, I can’t see it.

Anybody? TIA.

– Daniel

Bloglines support got back to me, pointing out an error in my feed when checked by feedvalidator.org. Not actually an error, a warning about relative links/images. I didn’t think it would help, but dutifully removed the relative links/images from my last few posts, verified that feedvalidator wasn’t giving warnings, and tried the feed again in Bloglines. No go. Have let Bloglines support know this, will await the next reply.

luvmoose, did your blog ever have an atom.xml? Was it using Blogger or similar before? You could try using .htaccess to redirect /atom.xml to /feed/atom or /?feed=atom

See https://www.javascriptkit.com/howto/htaccess7.shtml for details.

FWIW, I’m getting this same problem on a number of my WP sites, all running 1.5.x. I’ll upgrade to WP2.0 in due course (anybody verified that fixes it?) but the problem appears to have occurred with Bloglines only, in late December.

I have contacted Bloglines support about it, and would suggest anybody else affected do the same.

Thanks gwijayas… I’ll try changing all authors back to level 7, and see if that stops it happening.

I’ve seen this behaviour not just for published posts, but also drafts, which a co-author might write, but get saved with me as the author.

If I were a PHP guru I’d nose around in the code and sort out why it happens. But I’m not, so I won’t!

Sorry: To clarify, I am seeing this issue on standard WP 1.5, not the Multi-User edition.

For what it’s worth, you don’t have to put the whole URL into your image tags. You can for example use /pics/image.jpg (note the leading slash) which will work fine.

I’m seeing this problem come up too. That is, it hasn’t happened to me, but two co-authors on our blog have both seen their posts marked as being mine, and thus disappearing from their drafts. Very confusing. We’re all using different PCs, so it’s not a case of cookies getting confused.

It’s the pinging. Turn it all off. If your other blog installations had used it, they’d be getting hit that quickly too.

Thanks, I’ll check it out.

Ah. This may be what has caused my siteurl to reset itself to:
https://www.geekrant.org/wp-login.php/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/wp-images/smilies/
…I think you can probably spot why this is wrong!
It’s most visible because it can’t see the layout css, but it also breaks the login. What’s strange is that I haven’t seen the same behaviour on other blogs on the same virtual server. Perhaps it’s only triggered by going to the login page, as well as proxying?
I got paranoid and changed my database password, but I’ll try commenting out as above. Thanks.
Daniel

Okay dudes, I’ve nailed it. I’m guessing it’s an obscure PHP bug, but basically if you have a line like this in your .htaccess
AddType application/x-httpd-php .php .html
…then posting does funny things. With upgrading my diary to WordPress, I didn’t need that line anymore anyway, so it’s all happily working now.
Daniel

Okay this appears to be an issue with my server. Chasing it up with administrators.