dthought

Update #2: Getting warm.

When /blog/?s=blah is viewed, the db query ($q, bad variable naming guys ?? ) uses Array ( [s] => blah [pagename] => thoughts )

But when /blog/index.php?s=blah is viewed, the db query does not have the pagename.

Hmm… the plot thickens.

I noticed this as well. It appears to be that they’re sending the JS file via Gzip… and IE simply won’t decode it properly. I would presume their Gzip libraries are borked, because IE usually does Gzipped stuff just fine.

Here’s a quick fix:

Open up wp-admin/admin-header.php

Find the lines
<?php if ( $editing && user_can_richedit() ) : ?>
<script type=”text/javascript” src=”../wp-includes/js/tinymce/tiny_mce_gzip.php?ver=20051211″></script>
<?php endif; ?>

Replace with

<?php if ( $editing && user_can_richedit() ) : ?>
<script type=”text/javascript” src=”../wp-includes/js/tinymce/tiny_mce.js”></script>
<?php endif; ?>

Oh, and whilst you’re at it, feel free to go into admin-functions.php and comment out lines 1589 – 1596. Filthy BrowseHippy scum. Snidely suggesting that people change browsers is inappropriate on people’s sites. If WP want to put it on their own site, so be it, but they should not force their propaganda onto others. If you aren’t totally clueless with security patches and randomly accepting plugin downloads, IE is just fine. If you are good at what you do, you write conditionals to work around IE issues… so then everyone can view your work. That’s what it’s all about.

I meant to say retrieve the second time. Took some messing about, but I managed to write a plugin to grab the comment author’s ID so it can be checked against the article poster’s ID.

Messy, but it works. Still, I’d love it if WordPress had a better way of grabbing info. Rather than relying on a thousand and one functions, perhaps having a generic one which you pass the field name to would be a better option.

Like: get_comment_field(‘user_id’); get_comment_field(‘post_id’);

Sure, I can write one easily enough… but it would be a good thing for WordPress to do something like this at the official level because it’d simplify the template calls significantly.

Oh wait… maybe I’ve already answered my own problem by the fact that I didn’t browse the comment structure thoroughly enough. There’s a user_id field nestled in there. Let’s see if it does what I want it to ??

Update: Well, for some unknown reason, WordPress stores the user_id of the logged in user… BUT THERE IS NO BUILT-IN WAY TO ACCESS THIS. You have to hack the comment functions to get it to store this extra info. Naughty WordPress! ??

Any crashes would be due to the nature of the HTML or CSS used. The underlying technology rendering the page – WordPress, MoveableType, TextPattern – is irrelevant.

That said, IE:Mac is a very, very different browser to IE5 on the PC. It’s also very broken when it comes to a lot of rendering (it’s more weirdly buggy and crashes more often than IE on PC which says a lot!).

The best way to fix it would be to carve out the CSS bit by bit until IE:mac behaves. Actually, first try removing the CSS altogether – if it still crashes then there’s something wrong with the underlying HTML.

Then put things back in bit by bit until you find the point at which it breaks.

I wouldn’t criticise the WP team for having troubles with the CSS in IE. It does take a long, long time to learn all the caveats of coding for it. Still, I manage my way around it and if I find a spare moment, I’d be happy to supply fixes (that is, conditional hacks) to make the pages render properly in IE without affecting other browsers.

Sure, it may make the CSS not “perfect”, but it would then render perfectly in IE, Firefox, Safari, Opera or any other generally supported browser. Is that not a good thing?

A great hack – it should be a part of the core of WP – it’s an important feature if you still want to allow anon posters, and not at all hard to implement. Hats off to you, Kafkaesqui ??

(Though I must admit, I would prefer it to throw an error gracefully rather than outright die ??

https://www.positioniseverything.net/explorer/peekaboo.html

I noticed a lot of this issue on the WP admin pages using IE. Surely you have noticed this occurring too?

For example, the Write Page title gets half guillotined – though that might be the guillotine bug itself. Bleh. So many bugs, but at least with a little forethought and some P.I.E. you can avoid most ??