Link to home
Start Free TrialLog in
Avatar of rdurban
rdurbanFlag for United States of America

asked on

Upgraded to Wordpress 3.0.5

We upgraded our blog to WordPress 3.0.5 and now the rss feed from the blog is returning an empty set.  When I go to the feed url, it shows the posts.  Does anyone have an idea of what to do to fix it?

Avatar of Jason C. Levine
Jason C. Levine
Flag of United States of America image

Have you tried switching the permalinks back to default, saving it, and checking the feed again?  If they show up there, then reset the permalinks back to your preferred method and they should come back in the feed.
Avatar of rdurban

ASKER

Thanks!  Getting the guys to test this out as soon as possible.
Hi rdurban,

I'm not correct above.  The real answer is that WordPress 3.05 requires a database modification.  Go to:

http://www.your site.com/wp-admin/upgrade.php

And that should fix the missing entries.
Avatar of rdurban

ASKER

Hi Jason,

That didn't fix the error.  The developers tried both solutions and neither one worked.  However, I am not sure that I am explaining myself adequately.

Here is the deal.

There is a blog site and a main site.  The main site is handled by a CMS (ModX) and the Blog is handled by WordPress.  Two different parties of developers that are not connected.  The Main site is supposed to display the top two blog entries.

The rss feed was working perfectly unti the blog developers updated the blog.  Now the CMS developers are saying that it is a blog issue, and the blog developers are saying that it is a CMS issue.  Of course this doesn't help to get it fixed.  

The bottom line is that when we go to the blogurl.com/feed, we see the rss feed and can subscribe to it, however, when the CMS reaches out for blog posts, it is returned an empty set and just displays "nothing found".

ASKER CERTIFIED SOLUTION
Avatar of Jason C. Levine
Jason C. Levine
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of rdurban

ASKER

We don't believe that the structure has changed, however, the only change that was made was to the blog, which could mean that either a bug that was being used was fixed and it broke the feed reader, or a feature was added and it broke the feed reader.  
Avatar of rdurban

ASKER

The final solution was:

the old feed url that we were pulling from was:

http://example.com/feed 

which stopped working.  Now, the trailing slash is added:

http://example.com/feed/ 

and it is working again.

Thanks for your replies, they helped us tremendously.
>> Thanks for your replies, they helped us tremendously.

Really?  I'll take it, but I think I was just guessing here. :)