FireMotion

Confirmed here:
– After upgrading to 2.5, /index.php/%postname%/ resulted in “Sorry, no posts matched your criteria.” (whatever theme is used)
– Changing the structure to something else, and then changing it back fixes it.

When comments are deleted through the [spam] button, it is still saved in the database (but flagged with “spam”). Like intracateartist said, Akismet uses that information, but if you don’t use it, and know how to code and use sql, then it might come in handy to analyse the data for your own spam fighting.

Deleting comments with [delete] just deletes them, they are also deleted from the database.

By way of testing, I created the following plugin:

function custom_allow_comment($approved) {
global $comment_author;

if ($comment_author == ”)
die( __(‘Please fill the required fields (name, e-mail).’) );

return $approved;
}
add_filter(‘pre_comment_approved’, ‘custom_allow_comment’);

Notes:
1) $comment_author is initiated in wp-comments-post.php from the $_POST variable, and is trimmed there.
2) If the plugin finds that $comment_author has no content, it dies, so WP doesn’t save anything (not even as spam or for moderation).
3) Even if the POST method is used, I’m assuming wp-comments-post.php is executed (for comments ofcourse, assuming this whole thing is about comments as the database data indicates the bad entries are comments [and not trackbacks or pings]). Unless there is a backdoor.
4) I have no other copies of wp-comments-post.php (under this or other names) that are tied to this particular database.

Regardless of this plugin, I’m still getting anonymous comments. (The setting described in previous posts hasn’t been changed), and they are added in the moderation queue. To my knowledge, none of these comments are added live (moderated). I’m unsure if some of these comments are automatically nuked (aside from this plugin).

I expected this answer, but this is a workaround, not a fix.
Plus, I already explained that these comments aren’t trackbacks (and I double-checked the database: the comment-type isn’t trackback). Unless it’s a bug, ofcourse.

Hmm, it’s a first that I heard of this expression() thing. Anyway, this is not a specific WordPress thing, but html/css/browser issue.

I’m assuming you’re putting the p { something } code in your css file. Try putting it in your template’s header (try putting it in header.php):
<style>
p { your code }
</style>

I hope this helps, and good luck with it.

Actually, I couldn’t find anywhere that “name” was used to identify posts by their post_name/post slug title. So your information is already enough :). The reason for this is that I want to use WP partly as a content manager for (semi-)static pages.

Anyway, thanks rboren!

Here’s what I know.
1) Those archives are actually <i>still being called</i> from the database. The “Proper mod_rewrite rules are in .htaccess file” only translates the urls to make WordPress get it as index.php?p=10 or whatever. No actual files are being written.
That’s all. I don’t know the other two issues.

Having a different location for index.php doesn’t require all that too much coding. But my site has these locations:
/index.php (my index page)
/m_blog.php (my archives page)
/wordpress/ (my wordpress directory)
So with each release, I have to edit at least these files (if I remember correctly):
/wordpress/index.php
/wordpress/wp-comments.php
/wordpress/wp-includes/template-functions.php
And then I include the /wordpress/index.php in my (edited) /index.php and /m_blog.php.
This root directory “feature” that WordPress incorporated from b2 doesn’t make it very flexible.
It’d be more flexible if WordPress allowed this out-of-the box, but it doesn’t. Yet?

As this isn’t a supported feature yet, I always have to edit all the code whenever there’s a new release. Because:
/index.php (my index page)
/m_blog.php (my archives page)
/wordpress/ (my wordpress directory)
So I edit my /index.php and include my edited /wordpress/index.php file, edit some other files with variables… personally, I think it’s a mess how b2 was originally scripted, and how WordPress builds on that.
It’d be more flexible if WordPress allowed this out-of-the box, but it doesn’t. Yet?