deus62

Giving it one second and last shot. I know it might be a stupid question, but I’m stup.., err, a nOOb in regard to all of this stuff.

@exportforce

So, are you actually working with a broken setup right now or did you kick-start it from the ground up again?

I for one would be interested in hearing when you get it fixed. It might also help others down the road who run into the same/similar problems.

Good luck!

Look around this forum, also at the very top, and find a hundred more posts like yours (usually buried a bit further down).

Sorry, I’m not an expert on these matters (relatively new to WP) , but I would think the database upgrade failed and that’s why you have problems.

I remember that I read somewhere that in the upgrade process, when the strings get corrupted (afaik, serialized data are turned into strings from memory to be stored in the DB), a server can’t convert those data back into a PHP object.

Just a stab in the dark.

Others should be able to help a lot better here, but if nobody else chimes in, this is what I would do:

Try to get your backup data into the DB (hope you have a backup), revert everything back to what it was before, and reinstall WP while making sure the DB upgrade script runs properly.

Beyond that, sorry, I’m far too dumb when it comes around to WP.

Just quickly before I go to bed here.
Have you actually checked anything yourself?
I’m assuming the blog linked in your profile is the one in question.

Most of your links go to non-existent pages or do absolutely nothing.

When I run your page through a validator I get this:

‘ Sorry, I am unable to validate this document because on line 70 it contained one or more bytes that I cannot interpret as utf-8 (in other words, the bytes found are not valid values in the specified Character Encoding). Please check both the content of the file and the character encoding indication.

The error was: utf8 “\xFC” does not map to Unicode ‘

I would think this is not (primarily) a WordPress issue, and I’m usually the one to yell at WordPress first. ??

This is a nice portfolio theme, but far from what you apparently want to do.

Check it out anyways: Sharpfolio

What I’ve learned so far is that WP doesn’t have any bugs.
We users do.
??

I didn’t really fix my issue, as I have found out by now. But since people contacted me and asked me to return …

I simply exchanged the former rss2 link with https://mysite.com/feed/ as auto-detected by Firefox.

Works for me, so I left it because I’m seriously tired of trying to figure out the myriad of issues with WP 2.5 and 2.5.1 (images won’t upload, visual editor has never worked for me, feeds were broken upon update, I’ve had issues with the “save” function (got “stuck” several times), custom fields won’t stick without resorting to tricks, … the list is endless).

WP 2.5 and up has been a nightmare for me and I’m just trying to keep my blog running until either the issues get fixed for good via an update or until the summer when I have time to switch to another “publishing” (yeah, right) software.

Cheers!

And?
It seems to work again?
Can you say what you did to fix it?
Can you set this topic to closed?

Or reupload those feed files from the WordPress distribution (but then you revert to the original file if you made any changes since then).

Look in your wp-includes directory for files starting with “feed-“

feed-rss.php
feed-rss2.php
…

Depending on which one the error is in (can’t see your site right now aside from some MAIN PAGE), fix that file.

Or use MS Live writer. I’ve never used anything like this before (and wasn’t planning on doing so), but a link in another forum plus a load of frustration took me over there. I gave it a try and have absolutely no problems anymore. Once they fix issues with the WP uploader, I’ll can LW again.

Look at the validator and fix the issues first (especially the empty lines before the feed declarations start!):

Validator result

My problem (you commented in the other thread and asked) was a different one that was unrelated to this.

Fixed my issue.