Comments on: Does WordPress 2.5.1 suck?

By: Harry Eves

Harry Eves — Tue, 21 Apr 2009 10:10:22 +0000

Doesn’t like IIS does it. Out of the box, straight in. Runs like a dead slug and takes minutes to load. No templates being used, no plugins, just lousy performance (more 404’s ect.) Never mind, I’ll just use something decent from MS :0)

By: Stefan Mischook

Stefan Mischook — Fri, 06 Jun 2008 06:06:38 +0000

Mayooresan,

I had the same problem with the new image uploader. I was able to get it to work by updating my htaccess file.

And yes, you are right: the huge WordPress community is a HUGE reason to go with WordPress … lot’s of support.

Stefan

By: Mayooresan

Mayooresan — Fri, 06 Jun 2008 06:01:34 +0000

yeah.. agree with you! I had hell lot of problem with image uploader.. later I switched to non-flash uploader.

but what ever the problem.. you can find solutions online.. thats the beauty of wordpress! 🙂

By: Stefan Mischook

Stefan Mischook — Thu, 05 Jun 2008 16:00:18 +0000

Hi Mark,

I appreciate the offer of help, but things seemed to have resolve themselves!?

Check it out:

After doing the installs of different releases of WordPress (from 2.3.1 to 2.5.1) I found that they all ran really, really slow.

… Strange since my original WP install was working fine throughout this process.

Anyway, so I left it alone (planning to take it down later) and proceeded to install WordPress 2.5.1 on my dedicated server with the idea of using a sub-domain to create the virtual connection between the root site (killersites.com) and this new WordPress install.

Note: I tend to prefer sub-directories to sub-domains because sub-domains can confuse some people and sub-domains can ‘confuse’ some search engines.

Anyway ..

Then later that day, I decided to check the hanging WordPress installation and to my surprise … it was working fine. So, there you have it … it just works now.

Conclusion:

Given that all new installations of WordPress, regardless of release, was acting up, I now am thinking there was something wrong/wonky on the server end of things and not necessarily WordPress itself.

… But I just don’t know.

Stefan

By: Mark

Mark — Thu, 05 Jun 2008 00:59:37 +0000

Are you sure it is not a plugin causing the slowdown? Sounds like you have the bug hunting well under control, but you can contact me directly if you believe that I can be of any help.

By: Stefan Mischook

Stefan Mischook — Wed, 04 Jun 2008 19:42:28 +0000

I haven’t tried yet.

Stefan

By: Pádraic Brady

Pádraic Brady — Wed, 04 Jun 2008 18:22:28 +0000

Any chance of isolating the slow down using XDebug? If it’s something specific creating a massive slowdown, XDebug would find capture it in a cachegrind output.

By: Stefan Mischook

Stefan Mischook — Wed, 04 Jun 2008 17:57:42 +0000

“You should never alter a live site that is working until you know that the changed code will work properly for you.”

True. In this case. I was not altering a live site, just adding a new sub section.

“And wait… You find a bug in the code and all the sudden the entire application sucks?”

I was not meaning to convey that. I like WordPress. But the problems do persist.

🙁

Stefan

By: Joseph Crawford

Joseph Crawford — Wed, 04 Jun 2008 17:44:58 +0000

And wait… You find a bug in the code and all the sudden the entire application sucks?

By: Joseph Crawford

Joseph Crawford — Wed, 04 Jun 2008 17:43:05 +0000

I personally did not encounter these issues, however if you are not setting up another sub-domain for migrating your site you need to rethink your web development practices. You should never alter a live site that is working until you know that the changed code will work properly for you.

I always setup beta.domain.com and install the latest WP for testing before I take it live.