noelcower

That’s normal. Don’t worry about it — they can’t do anything harmful or see anything a normal reader wouldn’t. All they’ll get is a list of recent posts, comments, and any other data made available to normal subscribers.

I’m using Spam Karma 2 and Akismet side-by-side and haven’t had any problems. However, Bad Behaviour has an unusual tendency to block me and folks I know (nothing bad on their systems, not using spiders, etc.), so I’ve avoided it.

You might as well try and see, as what happens with one blog isn’t necessarily going to happen with another. My trouble with BB, for example, could just be a freak accident and it could work miraculously for you.

Just thought I’d mention that widgets support has been added. However, reading the readme is important if you plan to use widgets. Then again, it’s called a readme for a reason ??

Well, samboll makes a good point about this. Without knowing her personally, we can’t really suggest much other than simply picking something arbitrarily. If anything, I’d say since you seem to know her, you’re the best person for picking a theme. If in doubt, ask your brother what he thinks of themes you select and have him help you find something suitable.

I tried this myself and nothing out of the ordinary is happening. Are you doing anything prior to this code that may be affecting the output? Maybe a plugin you’ve installed that alters it?

Completely possible and pretty easy to do if you don’t mind modifying your theme.

I can’t see the site you’re linking to, but anyways, you can cut out a portion of the post by including a <!–more–> quicktag, or you could optionally choose to manually do this by, for example, including a custom field in the post with a description that is displayed (if present).

The first is the only option that’s present by default in themes (as far as I can tell), but modifying the pages to do that latter of the two would be easy.

Viper is correct, your fears, while understandable, are unnecessary. PHP files are processed by, well, PHP before the output is sent to the client requesting whatever it is. So, basically, people won’t see the source unless you allow them to.

You can sleep easy, for tonight is not the night that people will hack your gibson.

Well, it depends on your host. I’d suggest starting by checking your FTP server for any log directories, and if none are found, then move on to any control panel your host provides you with. If neither are accessible or provide said logs, then e-mail them requesting the server’s error logs for your account.

Hm, anything in the server’s error log?

FireFox: Anything I could have said on this was pretty much said already by spencerp and Kafkaesqui’s link.

moshu: I can, but that’s a different story entirely.

You shouldn’t. However, as a precaution, you should always back up your database and any other relevant files before attempting to upgrade.

There is a database backup plugin (included with WordPress 2 by default) that can help at times, too.

You wouldn’t be able to use query_posts, but you could do something like this to get the IDs of posts with certain tags:

global $tablepost2tag;
$wpdb->get_results( "SELECT post_id FROM $tablepost2tag WHERE tag_id = $tag" );

It’s not much, since I’ve not had to do anything like #2, but it should get you started.

Well, since the original post never got an answer either, I suppose it’s worth answering.

You could add a filter for the_content that would be called before the wptexturize filter. Basically, like this.

Is your other page a WordPress blog? If so, you may be able to just copy relevant information from the database and the theme. Otherwise, you’ll probably have to write a theme to mimic the appearance of the other page.

If it’s another type of blog, you should be able to at least import your old posts if it’s supported by WordPress’s Import feature (under the dashboard). However, that will not copy the visual appearance, it only serves to import posts from another blog.