codeman38

And found the cause of it. It’s the Bad Behavior plugin.

Edit: Or not; I spoke too soon. Now I’ve got all the plugins deactivated and it’s still showing the error. I’m confused…

Edit #2: Ah, apparently this may be an issue with my hosting provider’s configuration, judging from this bug? I hadn’t encountered this with the older version, and it doesn’t affect anything on the non-admin side, which is rather odd.

Edit #3: Indeed, not an issue with 0.9.1.3; admin interface shows up fine there. This only happens with 0.9.2.1.

Aha, some further clues. Disabling some other plugins caused the following error to appear:

PHP Fatal error: Cannot run code from this file in conjunction with non encoded files in [...]/wp-content/plugins/w3-total-cache/inc/mime/cssjs.php on line 231

Deleting advanced-cache.php fixes it– but it keeps regenerating it every time I go to the settings page, causing it to 500 again.

One thing that really threw me… am I the only one who thinks that it’s more intuitive to go to Manage – Media Library to add media to the library, rather than doing it via the posting page? This would particularly make sense if there are media you’re planning to use in multiple posts. I don’t see why it’d hurt to have the option in *both* places…

Thirding the suggestion to have “add media” available on the Manage – Media Library page. Maybe I’m just weird in how I think, but that seemed like a more intuitive place to have it than on the posting page. Why not have it in both places, so people with either worldview will be able to find it?

(And yes, I know, it’s no longer beta. Still, surprises me that this was kept this way in the final version.)

I’ve made a diff file from the 2004-08-10 version of functions-formatting.php to fix some of the more annoying bugs I’ve encountered. One of them is a matter of taste (I think two hyphens should be turned into an em-dash and not an en-dash), but the other two are major annoyances for those who prefer to use single quotes and place punctuation outside of the quotation marks.
https://zone38.net/blog/functions-formatting.diff
For those who might be using a different version, the lines that were changed should be obvious, but the deletion may not be; it’s for the line that texturizes an apostrophe followed by a lowercase s.
The combined fixes will prevent typographical travesties like this one:
a€?This code’, thought the Anglophile programmer, a€?seems very broken indeed.a€? ??

I’ve done some hacks to improve the ‘texturizing’ of previewed comments, fix the problems with quotation marks in user names and URLs, and solve at least some of the layout problems, among other things. Here’s the updated source code:
https://zone38.net/blog/wp-comment-review.phps
Feel free to include the changes in your own distribution, LaughingLizard.