Orin

Ah! Very useful. Been looking for this solution for awhile.

Ohhh… there’s an extra filter call being put in somewhere. So WordPress is seeing the entity and processing the & like it’s an uncorrected characted. It’s doing this to be XHTML compliant which is all well and good, just look for that particular filter EditMonkey is adding.

Gimme enough times trying and I’ll eventually hit on it… the variable I was looking for was ‘$paged‘, everyone, ‘$paged‘. All of you who couldn’t answer within the two hour limit — you just failed WordPress challenge.

…Since that’s not possible, as I found out, allow me to rephrase: is there a method to access the current page number?

Sounds like ther plugin is making your charset act odd. Check Options -> Reading to see that it is UTF-8. Then check if the plugin might be changing it, using any filters like wptexturize, etc.

Scott O’Reilly’s Preserve Code Formatting plugin

It sure is possible, check this page in the Codex.

Yeah, check this thread and this plugin for two different approaches.

This is a fairly odd behavior, I agree… let’s see if I can’t help out.

Hmm… well I’m not sure if this has anything to do with the trouble your having, but I’m unable to reach any of the feed files directly. So I’m unable to tell if wp-rss, wp-rss2.php, wp-atom.php, wp-rdf.php or wp-feed.php is any different. Most likely there’s an .htaccess rule (perhaps) — one that prevents direct linking or direct access to anything besides the main index.php. This seems to be the case as I can’t get to /wp-content/themes either.

First thing is to check if any of the mentioned files act differently… you probably have to change that rule. The setting is usually in your host’s Control Panel. Go there, remove the rule, then look at the files.

Yes, what you can do is make an IE specific rule. I use these all the time. The easiest is the ‘star html hack‘:

* html

Insert it before any CSS selectors that should only be used by IE. It’s as simple as that — just choose different values. There are other ways to do it as well…

<!--[if IE]>
<link rel="stylesheet" type="text/css" href="special-needs.css" />
<![endif]-->

That’s the way to include an entire stylesheet for IE only.
Hope that’s helpful.

Yes, it does — fair enough. I’m just a little post-happy for something I think I know how to explain.

(better luck next time…)

From looking at the source it seems your call to *ahem* “die_fucking_ie_die()” seems to be resizing a few page elements for IE’s sake. First thing I would do is troubleshoot that (try changing the values or taking it out entirely).

I would think the simplest way would be to replace everything related to

post_name = '$name'

with

post_ID = '$id'

This should read from your database in the exact same fashion. And you wouldn’t need the filters applied below there since the data is an integer and not text.

Yes, that also would work. The first method would be if you were having all the different posts on the same page, the second on their individual post and category pages.

Yes, there defeinately is. Check out this thread. My method is to define a different CSS class for every category I want affected, but you can go deeper down that rabbit hole if you like.