philor

Though as usual, my first guess would be wrong: it’s actually returning the “Slow down cowboy” error from two comments in less than 15 seconds, although my trunk install doesn’t do that, and does accept two pings, even though I don’t see any change in the code that ought to have fixed it.

Spaces is correct, for 1.5.2 and trunk: commas is either out of date or just not true. The “only the second one” thing is on the receiving end: if you send to two space-separated URLs on two different weblogs, they both go, and if you send to two URLs on the same weblog, you can see from the server logs that both are POSTed, but only one is accepted. My first guess would be duplicate checking that isn’t checking whether it’s to the same post.

Looks like there’s a patch in Scott’s repository from April 19 to have planet output as utf-8, which should solve your problem.

That one with Shellen clearly involved some chemical “persuasion.”

Are you sure you got all the mod_rewrite stuff copied out? That error sounds rather like one I got once by thinking that the few visible lines were all there was. Maybe it’s a version-difference, but looking at some-random-nightly, I’ve got nine rewrite rules, including one for wp-trackback.php.

Even though in practice they are getting closer all the time, in the original design a Trackback ping said “I wrote something about your post that I think your readers would like to see, here’s an excerpt from it to tease them in”, while a Pingback ping said “I linked to you.”
If all blogware writers were reasonable and supported both, your linkdump posts that are just two dozen links without commentary would Pingback, and your thoughtful explanation of why someone’s crazy as a loon would Trackback (and would send a hand-written excerpt, not a cut off in midsentence excerpt of a few words of throat-clearing). But since b2’s children and a few individuals support both, a few individuals support only Pingback, and MT supports only Trackback, you end up needing both to have a chance of getting something through.

The importer sets the password for all created authors to changeme (making it a good idea to do so ;))
RFE: importers should probably either ask for a password to use for all created authors, or set them all to the admin’s password, so she can change them to something different for each author, and tell them what to use to get in and change to their own.

I would guess that it’s not an attempt on WordPress so much as an attempt on whatever they find by searching for “?p=” (one way or another: I couldn’t find a syntax that would work at Google, but there probably is one).
Most hosts like to disable first, and let you ask questions later. I had my honeypot FormMail.cgi shut down for being “a vulnerable version of Matt’s FormMail” once. It’s only if they don’t re-enable it while apologizing for the inconvenience that you might start thinking about a new host. (Or if they take four days before they notice what they claim is an exploit.)
Actually a cute little exploit, though I wonder why they would risk failure whenever short_open_tags is off in php.ini when they could avoid it with just three more characters. Sloppy.

Is one of the extensions TBE? It’s got some serious issues with Javascript in 0.8, and Piro’s just now getting a chance to look at them and start to fix them. You might want to try the test build in this post. (I haven’t, because I’m using this as an excuse to wean myself from TBE, and anyway I’ve got my own broken extension I should be fixing.)

Sorry to keep nagging about the tiniest things, but install.php needs the same fix escaping those same troublesome quotes around the href.

Yeah, I think MDV means the fix for the breakage because of your fix (look at your single quotes around the URL – they end the value), not your fix for the previous breakage.
We need a Tinderbox/Bonsai setup ??

Closer? You’re almost there. You’ve probably got a copy of 1.0.1-miles, right? install-config.php was, er, not quite as perfect as it could be. Easiest thing to do is just skip over it by editing wp-config.php by hand: save a copy of wp-config.sample.php as wp-config.php, and plug in the data that cpanel conveniently provided in the four lines at the top that start “define”, then upload that to your WordPress directory (the one with stuff like wp-atom.php and wp-comments.php, not wp-admin), and jump ahead to wp-admin/install.php

I don’t use cpanel, but a little googling makes it look like you not only have to create the database, and create the user, you then need to stick the two together, er, grant the user permissions on the database. Is it saying that the user has permission to go hog wild on dalekeig_wordpress, or just that both exist?
And yes, the blank page would say that as far as MySQL knows, there aren’t any databases that your user is allowed to see.
I’ve found the same thing about screaming at people who don’t grasp how to behave at a four-way stop: they don’t learn anything, but I feel better ??

“having a little trouble selecting” comes from the ezSQL class thinking it has a good connection to the db, but then failing on the mysql_select_db() call. You might try going in to wp-includes/wp-db.php and removing the @ in both line 32 (the mysql_connect()) and line 58 (the mysql_select_db()) just to see if there’s some useful error message in either one that it’s hiding from you.

Blacklists only stop the people you already know about, not the people you don’t (or the 500 new domains the previous people have registered today). Having a blacklist is better than not, in the “fool me twice” way, but it’s a long way from a final answer. Forced preview does actually work rather nicely, as long as you are among the few who have it, rather than the many who don’t: when I bother to look at my logs, I see a fair number of comments where a spambot simply POSTed to my comment script without bothering to notice that it actually needed to preview, and pick up a hidden form field based on the content of the comment, and then post. It’s easy enough to work around, just rewrite your script to preview, suck out all the form fields, and post again, but like any good Club solution, it’s very nice when you are the only one on the block who has one.
And, whether or not anyone else uses my preview to fix their errors, I do all the time. Highly recommended.