Firas

I just got an email from someone who reports having experienced this problem as well. The sad thing is that there is absolutely no way to go back that I can think of, your data is truly screwed. Anyway, googling around takes me to this post from April 06 which reports that doing search & replace should work.

Did you export or import your DB via phpmyadmin? That could have introduced the issue.

Don’t worry about the mysql collation. That’s not the problem.

Yeah, rather strange… I didn’t change the default constants in there (DB_CHARSET was set to utf8 and DB_COLLATE was empty). I’m just not sure to what extent they’re involved in the db upgrade process… and it looks irreversible because the characters in the actual tables are messed up. May have been a combination of factors specific to my installation.

I suppose at this point I’m mostly wondering if there’s something specific to mysql that can ‘fix’ the characters (I tried copying the posts table and changing the copy’s collation of the post_content row from latin1_swedish_ci to utf8_unicode_ci; no dice.)

So yeah, I suspect I should despair at this point. All fairly annoying. You’d think upgrading WP wouldn’t be like getting axed in the forehead. (Et tu, WordPresse?)

Alchemy and WP-Medic were offshoots of the same urge of mine in March-Nov ’05, to make WP way easier to use (this mainly involved cutting FTP & phpmyadmin out of the interaction processes.)

WP-Medic was just a troubleshooting toolkit to avoid logins to phpmyadmin by automating common fixes. It’d probably have a wide user base by now if we’d kept up on development, but I’m inclined to think that most people have one-off concerns when needing a tool like WP-Medic that don’t warrant downloading, unzipping, and uploading yet another addon to their WP install. One may as well just login to cpanel and follow the manual instructions.

Alchemy was a totally different project (automagic updating and mangement for the WP core and extensions).

This sounds seditious, but the reason I need WP-Medic is that I’m seeking to repurpose some of its code for the Habari installer (not that I couldn’t put said code together again from scratch; it’s just time-efficient to reuse an already working implementation of certain things.)

Right now my intention with Alchemy is to code it up for Habari rather than for WP. I’m sure WP 2.2 will have some sort of Alchemy-like process though, whether I personally get around to it or not, and whether it’s in the core or not. Of course Dr Dave was on the scene way before me with WP Plugin Manager, and Zirona’s WP-Manage comes tantalizingly close.

I find it interesting in an abstract sense that so much when it comes to development for WP &c. is just a matter of somebody ‘doing it’ rather than needing a genius to come up with a technological breakthrough. I suppose it’s the same with most things in life.

We only had one release I think. Merci beaucoup!

You have to use a custom page template for that page (https://codex.www.ads-software.com/Pages#Page_Templates)–start with your regular page.php and then remove the tag that calls the comment form.

Get in phpmyadmin and update the ‘home’ and ‘siteurl’ values in your options table.

Ah I see. This changes the ‘blogdescription’ value in the wp options table, like in your RSS feed and stuff. You can try calling that by <?php echo get_option('blogdescription'); ?>. I’m not sure whether that’s the description used in the default Kubrick header? Probably is. You can modify the code to not touch your blogdescription and just output something based on day:

<?php
function daydesc() {
$daydesc['Mon'] = 'Description for Monday';
$daydesc['Tue'] = 'Description for Tuesday';
/* etc: just finish the $daydesc['3-letter-day'] = 'description' info */
echo $daydesc[date('l')];
}
?>

If the plugin contains just that, you can call <?php daydesc(); ?> anywhere in your template.

bubazoo, “it doesn’t work” as in, it doesn’t show up under plugins, you activate it and nothing happens, something else? You filled in the $daydesc array right? This is really trivial, nothing to pull your hair out over.

vkaryl, at your pleasure! I haven’t looked into the widgets thing. They seem a bit scary. I guess I’ll gather the guts to figure out what on earth they are this weekend.

<?php
function daydesc() {
$daydesc['Mon'] = 'Description for Monday';
$daydesc['Tue'] = 'Description for Tuesday';
/* etc: just finish the $daydesc['3-letter-day'] = 'description' info */
if(!get_option('daydesc')) {
add_option('daydesc', date('l'));
update_option('blogdescription', $daydesc[date('l')]);
} else {
$stored_day = get_option('daydesc');
$current_day = date('l');
if($stored_day != $current_day) {
update_option('daydesc', $current_day);
update_option('blogdescription', $daydesc[$current_day]);
}
}
}
add_action('init', 'daydesc')
?>

Don’t even know if it parses actually but look up the plugin headers on the codex, add them above the code, upload, activate and try it out.

INSERT INTO $wpdb->postmeta (meta_key, meta_value, post_id) VALUES(‘syndication_feed_id’, ‘your value’, ‘$post_id'”)

It’s all just mysql more than a WP question.

Your blog is in utf-8 but browsers are defaulting to the ISO-8859-1 character encoding. You should send a content type header with a utf-8 charset.

The function is wp_mail(). The comment notification function is wp_notify_postauthor().

A cursory glance at calls to wp_mail() suggests that nowhere does commentor-given input get into the to, from, subject or other email headers.