rustindy

My entire index.php:

/* Short and sweet */
$cat = “-22”;
define(‘WP_USE_THEMES’, true);
require(‘./wp-blog-header.php’);

Category number 22 does not show up on my page now.

Nope, it doesn’t. Otherwise “WordPress Classic” and “WordPress Default” wouldn’t work as names since the folders are named “classic” and “default”, respectively. The theme name and directory name are entirely seperate things.

I’ll be honest – I haven’t found a single blog client for my Palm Zire 72 or Ericsson T610 that works 🙁 They either timeout or give errors, and I’ve tried 7 or 8 between the two.

For now, I can’t write blog entries from my phone or PDA, I can just email moblog pics with captions from them.

I use SK on “normal” right now – so far nothing good has been killed, and everything bad 🙂

(stolen from the codex at http://codex.wordpress.org/Combating_Comment_Spam#Spam_Comments_appear_immediately):

DELETE wp_comments FROM wp_comments C LEFT JOIN wp_posts P ON C.comment_post_ID = P.ID WHERE P.ID IS NULL

The above SQL query will delete any comments in your database that aren’t associated with a valid post ID. If you just want to view the comments, replace DELETE wp_comments with SELECT * and run the query. The codex link above also gives info on how to do this through phpMyAdmin.

ed: yup, that’s basically it. when you do that (you can use Notepad if you want), make sure (and double-check) that there are no blank lines before the <?php at the very top, or after the &rt;?> at the very bottom – otherwise evil things can happen.

as for “every plugin in the known universe”, i hardly think that “2” qualifies. spam is a problem for *every* blog program. different blogs have different ways of dealing with it. personally, i *love* the WordPress plugin architecture, since it makes it extremely easy for people with the knowledge to create fantastic anti-spam plugins – like Kitten’s Spaminator and Dr. Dave’s Spam-Karma (you’ll probably need one or the other – both might be overkill).

pericat: does 1.5 prevent comment posting on non-existent posts?

Putting a reminder on the download page letting users know that they *must* run /wp-admin/upgrade.php when installing v1.5 over *any* previous release is a good idea.

Even though I’ve been programming for 22 years, I *still* look at files named readme or installinfo or other such things, just in case there’s something goofy I need to be aware of. Particularly with Windows (my server is a Windows machine), goofy is the rule, not the exception.

If you’re going to skip reading the included documentation, especially files named readme or important or whatever, do *not* complain about it. It would have taken you all of 10 seconds to skim to the “Upgrading” section and see the 4 steps required (if you include “Done!” as a step).

In any case, it seems that people willing to complain about something are not, in general, the same people willing to do something about it. You have definitely done the former, and in the thread at least, started a bit of the latter.

Take a little time to create a userpage on the Codex for yourself (yes, we already know that the Codex software is not particularly well documented – but it’s not all that tricksy either) and start contributing. If you can’t contribute, don’t complain either. Offer constructive suggestions (which you have done as well), and perhaps someone else will do it (the mantra of complainers everywhere).

He already said he didn’t read the directions 😉