Comments on: Wordpress’ Biggest Mistake Yet http://www.gospelrhys.co.uk/2007/10/wordpress-biggest-mistake-yet.html 1/6th of the world cannot access it, 5/6th of the world doesn't want to.... Sat, 06 Sep 2008 18:03:34 +0000 http://wordpress.org/?v=2.6 By: Armen http://www.gospelrhys.co.uk/2007/10/wordpress-biggest-mistake-yet.html#comment-33506 Armen Wed, 17 Oct 2007 08:22:55 +0000 http://www.gospelrhys.co.uk/2007/10/wordpress-biggest-mistake-yet.html#comment-33506 So that's what the problem is! I redesigned my site when I moved over to 2.3 and I thought it had something to do with <b>me</b>! Assuming you're right, I agree with you. It was a stupid move. Most of my 'incoming links' are my own! That's the stupidest thing I've seen in a WordPress upgrade since I started using it nearly a year ago. So that’s what the problem is! I redesigned my site when I moved over to 2.3 and I thought it had something to do with me!

Assuming you’re right, I agree with you. It was a stupid move. Most of my ‘incoming links’ are my own! That’s the stupidest thing I’ve seen in a WordPress upgrade since I started using it nearly a year ago.

]]> By: Mike C http://www.gospelrhys.co.uk/2007/10/wordpress-biggest-mistake-yet.html#comment-33503 Mike C Wed, 17 Oct 2007 05:44:29 +0000 http://www.gospelrhys.co.uk/2007/10/wordpress-biggest-mistake-yet.html#comment-33503 You don't like how wordpress change what the link thing goes to? I like it better actually but thats me. You don’t like how wordpress change what the link thing goes to? I like it better actually but thats me.

]]> By: - Spaceman Spiff - http://www.gospelrhys.co.uk/2007/10/wordpress-biggest-mistake-yet.html#comment-33496 - Spaceman Spiff - Tue, 16 Oct 2007 22:40:42 +0000 http://www.gospelrhys.co.uk/2007/10/wordpress-biggest-mistake-yet.html#comment-33496 I upgraded to 2.3 as soon as it was available and it broke my site. I couldn't even log into wordpress, let alone see my site. I eventually went back to 2.2.1 or whatever the previous one was and everything was ok. I think my plugins weren't ready. That was too painful for me to try that again anytime soon. I upgraded to 2.3 as soon as it was available and it broke my site. I couldn’t even log into wordpress, let alone see my site. I eventually went back to 2.2.1 or whatever the previous one was and everything was ok. I think my plugins weren’t ready. That was too painful for me to try that again anytime soon.

]]>