Enpä muuten yhtään tiiä mikä se on, otin sen kohteeksi vain noiden heijastusominaisuuksiensa takia. Joku yleinen liiketila kenties?

Hope I didn’t come across as disbelieving you, I was just curious (as always) about your reasoning behind this.

Burning yourself to charcoal sounds pretty nasty. :P Did you not feel intense pain, or did you in fact enjoy the pain? I.e. do you know what made you do it over and over again?

so they’ll wet their pants and then get very very angry when just being hit by pieces of plastic… xD

Okay, I lol’d, though I can all too easily see this being used against me at some point. x)

About physical violence: you sound pretty sure that it would quench your thirst for blood, but do you actually know that? I mean, have you ever experienced it first-hand? I’ve cultivated such desires myself sometimes, but as I’ve never actually encountered brutal violence in my life, let alone used it, it’s impossible for me to say whether what I’ve dreamt of would actually feel the way I’ve fantasized it to feel.

Haven’t read it through myself either, just glanced it and figured there’s a lot of data there. They say some of it isn’t accurate though, or that it misrepresents some issues.

This looks related to a test case I was preparing to demonstrate how flawed the output from wpautop can get inside lists:

<ol>
<li>
foo

bar
</li>
</ol>

renders as:

<ol> 
<li> 
foo</p> 
<p>bar
</li> 
</ol>

whereas I’d expect it to be

<ol> 
<li> 
<p>foo</p> 
<p>bar</p>
</li> 
</ol>

I’m changing the summary to generally cover wpautop’s problems within <li> elements.

Sloth.

Apparently either results.php or head.php (in view/admin/) refers to an image called small.gif by a path that doesn’t work: every time I use Search Regex I get 404 hits for a ’/images/small.gif’, when it should in fact refer to [site root]/wp-content/plugins/search-regex/images/small.gif. Apparently $this->url() precluding the path in the code doesn’t work — maybe $this is out of scope?

Np, @RavanH, glad my contribution turned out so helpful!

Here’s a related link I just came across that you might find interesting: Aselain hiplaajat (in Finnish).

On a hunch, I instead opted to change Upload Url Path (of the main site) to point to where Fileupload Url already was pointing, and lo and behold, now the uploads get url’s with a /files/ base (which I feel is best).

Funnily, despite this same setting on the testing site, the url’s there have the wp-content/uploads base (like I mentioned in the previous comment), as if Upload Url Path didn’t have an effect. There doesn’t seem to be a Fileupload Url setting there — perhaps it’s deprecated? (The testing site runs trunk, whereas the main site runs latest stable.)

(Usually it’s the other way round: something that works in testing won’t work on the production site.)