I’m going to have a bigger post up this week about my new blog project that I’ve started, but I wanted to describe some bug issues that I’ve found with BlogEngine.NET in the course of running that project.
Yes, I’m using BlogEngine.NET (Community Server didn’t work out for reasons that I will explain later this week; I have a software engineering midterm tomorrow), and it’s been a painless experience for the most part.
However, two quick bugs:
- Enabling Trim Stylesheets Under settings –> Advanced Settings can cause hidden HTTP 500 errors on the behalf of the style sheet renderer at random intervals, causing the blog to appear without any applied CSS. This can be resolved by simply unchecking the option.
- For some reason, portions of the blog’s default copy appears in localized languages other than the one I specified. For instance, in the image below is some German (?) text when it should read “Related Posts” in English.
While the German text is annoying, at least I have a work-around for first issue.
On a related note, BlogEngine.NET performed magnificently under a medium-sized traffic wave this weekend
I had a decent sized traffic wave from a social media source on my other blog project this weekend, approximately 2000 unique visits in the span of 12 hours. I know it’s not exactly a “Digg effect” sized traffic wave, but the wave did hit within a couple of HOURS of BlogEngine.NET’s deployment and there were no hiccups at all for BlogEngine.NET.
This stands in stark contrast with my initial experience with WordPress, which would choke and start vomiting MySQL connection maxout errors under relatively modest traffic loads*. I guess that’s one of the benefits of not using a SQL database in your blogging engine.
After tomorrow’s exam I promise some more updates on my other blogging project, plus some more Facebook development tips and some other .NET-related musings.
*Note: I resolved those maxout problems by using WP-cache, which you can read about on my WordPress hacks for IIS page.
Update: The German letters have disappeared. I wonder why they even showed up in the first place?
![[Post to Twitter]](http://www.marketing-ninja.com/wp-content/plugins/tweet-this/icons/tt-twitter-big4.png){kind=icon}
If you enjoyed this post, make sure you subscribe to my RSS feed!
Comments 6
I’ve actually found WordPress to be pretty rock solid. If you were seeing database errors under load, it’s likely that your host just put you on an overloaded MySql server.
Posted 29 Oct 2007 at 7:01 pm ¶Don’t get me wrong; I love WordPress. It simply had a lot more problems out of the box than BlogEngine.NET has. DiscountASP.NET limits me to 10 open MySQL connections at any given time, which isn’t much. Luckily WP-Cache solved the problem.
Posted 29 Oct 2007 at 7:24 pm ¶Just curious, are you planning on switching this Wordpress Blog to Blogengine?
Posted 30 Oct 2007 at 12:32 am ¶Andreas,
No, I don’t plan on migrating anytime soon, and I’m still not sure when I’m going to upgrade to WordPress 2.3! I feel like I have a good thing going on AjaxNinja with WordPress, but I wanted a different experience with my other blog, thus I went with BlogEngine.NET.
The process of migrating from WordPress to BlogEngine would be really nasty; I’m not sure if I’d be able to get all of the original WordPress URLs to point back to their corresponding units on a BlogEngine.NET deployment, and I really can’t afford to lose all of that Google/Del.icio.us/StumbleUpon traffic on those existing pages.
Posted 30 Oct 2007 at 1:34 pm ¶Hi Aaron,
yes, that’s the same problem I face here. It’s always a kind of a pity to run a PHP blog if you’re an ASP.NET developer, but back then when I started blogging there hasn’t been stuff like BlogEngine and I assume the same situation counts for you.
I’m looking forward to Windows 2008 Server with PHP deeply integrated by Zend and Microsoft, then I can at least move my Wordpress Blog from my Linux Server to my Windows Server without loosing the current URL Rewriting structure..
Posted 31 Oct 2007 at 2:04 am ¶I think writing your own blog engine is a great idea. And the best part is that you don’t have to bother with someone else’s list of required features. You code it to your needs and leave the rest out. Then add more features as you need them.
Posted 25 Jun 2009 at 9:49 pm ¶Trackbacks & Pingbacks 1
[...] Responds very quickly; handles traffic waves very well. [...]
Post a Comment