RSS feed loading instead of blog page

Moved to Multisite…

Do the amazon severs do any caching there? Or any cloud type distribution?

Not due to the fact that they are in the cloud. This is a production server for other content so we would have seen some aberrant behavior there as well.

Did you also update the htaccess rewrite rules?

Did you also upgrade plugins?

those woudl be the first two places I’d look.

>>Did you also update the htaccess rewrite rules?
Yup

>>Did you also upgrade plugins?
Upgraded or removed

>>those woudl be the first two places I’d look.

Yeah I thought about that, that is why I then did a clean 3.1 install (no legacy files) and imported the blogs. Symptom persisted.

Can you share your whole .htaccess here?

This is from the version that I took from 1.33 > 3.0

1006 # less .htaccess
RewriteEngine On
RewriteBase /

#uploaded files
RewriteRule ^(.*/)?files/$ index.php [L]
#RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]
RewriteRule ^(.*/)?files/(.*) wp-includes/ms-files.php?file=$2 [L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule . – [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

#limit spam
RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .wp-comments-post\.php*
RewriteCond %{HTTP_REFERER} !.*blog.law.cornell.edu.* [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) ^https://%{REMOTE_ADDR}/$ [R=301,L]

========================

This is the one from the new 3.1 install

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ – [L]
RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]

========================

Also perhaps of note is that this is being run from within an apache 2.0 virthost.

This is from the version that I took from 1.33 > 3.0

Where is that one? If it’s a folder up, that may be WHY it’s being a bit odd.

Turn the first one into this:

#limit spam
RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .wp-comments-post\.php*
RewriteCond %{HTTP_REFERER} !.*blog.law.cornell.edu.* [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) ^https://%{REMOTE_ADDR}/$ [R=301,L]

# WordPress Start
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
# WordPress End

(The ‘new’ htaccess rules from 3.1 actually work fine in 3.0, what you had was the old WPMU stuff and while it MOSTLY works, it can cause conflicts, so may as well clean it up even though I doubt it’ll make a difference.)

>>Where is that one? If it’s a folder up, that may be WHY it’s being a bit odd.

It is in the docroot for the virthost. So if the wordpress install is in /blog, that is where the .htaccess is.

I will make the change. I do however have a clean 3.1 install with only the config generated .htaccess rules. The behavior is still there.

I do however have a clean 3.1 install with only the config generated .htaccess rules. The behavior is still there.

but only *after* you imported the old blogs, right?

If so, I’m guessing something in the db somewhere.

but only *after* you imported the old blogs, right?

If so, I’m guessing something in the db somewhere.

Yes I imported a subset of the blogs (some of them were not unused, so only a total of 4 blogs were moved)

Yes, I thought about a mysql issue. However it is behaving properly using the 1.3 install base. And I do not have enough console time in on what the WP data looks like in mysql to notice something amiss. The way I had to do the import was taking it from the upgraded 3.0 and importing it into the 3.1. The 1.33 exported file would not go into a 3.0. But note also that I switched environments at the same time. Moved from an older brick and mortar server to an EC2 instance. So I also thought about a php issue, or even an apache issue that is just somehow incompatible with WP.

What’s this 1.33 install base you’re talking about?

From my initial post:

We have an old 1.33 wordpress mu install that we are trying to update to a current 3.x version and move it out to an Amazon EC2 instance.

So we copied the 1.33 off to the EC2 (replicated the db as well) and then upgraded it. But the old 1.33 is still sitting on the brick and mortar server with it’s database intact, we just move the dns entry around to point to the right host. As of right now, because of the issues with the upgrade, we are currently serving off the old 1.33. The blogs get a moderate about of traffic, but the RSS’s are picked up all over the place and those also exhibit aberrant behavior so I really can’t leave the broken WP serving to the public while I bang on it for any amount of time.

Yea, I was sorta hoping I mis-read that.

How did you upgrade? Did you just jump from 1.33 to 3.1 or did you do a step upgrade?

I would have done 1.33 -> 1.5 -> 2.6 -> 2.9 -> 3.1

As we say in Upgrading WordPress Extended

If plan on upgrading across more than two major releases, please consider upgrading incrementally to avoid potential conflicts. For example, if you plan on upgrading from 2.5 to 3.1, upgrade to 2.7 first, followed by 2.9, and finally 3.1. Older versions of WordPress can be downloaded from the release archive.

No no, worked the steps, right off the docs from the WP site.