Ryan Boren

Rudeseal, does “prevented from accessing” mean you are getting 404s? Did permalinks work for you with 1.5.2? Can you give me Debug Env output?

rogopag, to help me debug, download, install, and activate the Dump Env plugin. Visit a page that is giving a 404. Save the page source for that page. Forward the page source to ryan at boren dot nu. Deactivate the plugin when finished.

Right you are. I think post caching is getting in the way. We need to turn it off somehow when importing. We set a WP_IMPORTING flag when importing. We could check for that in get_post() and not cache if it’s set. I’ll look into it.

rtatum, I can debug this with a little help. Download, install, and activate the Dump Env plugin. Visit the page that is giving a 404. Save the page source for that page. Forward the page source to ryan at boren dot nu. Deactivate the plugin when finished.

<?php
require_once('admin.php');
echo "Approving comments...";
// Approve all comments
$wpdb->query("UPDATE $wpdb->comments SET comment_approved = '1'");
echo "Updating post counts...";
// Populate comment_count field of posts table
$comments = $wpdb->get_results( "SELECT comment_post_ID, COUNT(*) as c FROM $wpdb->comments WHERE comment_approved = '1' GROUP BY comment_post_ID" );
if( is_array( $comments ) ) {
foreach ($comments as $comment) {
$wpdb->query( "UPDATE $wpdb->posts SET comment_count = $comment->c WHERE ID = '$comment->comment_post_ID'" );
}
}
echo "Done.";
?>


Hmmm, I think you hit a little backward incompatibility gotcha. The new code assumes that drafts are saved without timestamps. It has no way of knowing that the old 1.5 draft that has a timestamp isn’t a 2.0 draft moved from publish back to draft. That’s why it doesn’t try to update the timestamp upon publish. I think you’ll have to create new drafts and cut-and-paste content into them from the old ones if you want updated timestamps. Annoying, I know. I’ll see if we can fix this up for the future. I’m not too thrilled with how the timestamp lifecycle is working out.

Okay, wp-login.php isn’t redirecting. If you visit wp-login.php directly, it will ask you to login even if you already are. However, if you visit anywhere in wp-admin/, those pages will recognize your current login. So, you don’t really have to login again, it just looks like you do. This is annoying, however, so here’s a fixed wp-login.php. Copy it over the top of your existing wp-login.php file.

Make sure the “Theme Name:” field in style.css is something unique. Having two themes with the same Theme Name could cause your problem.