after having received no answer, I’ve decided to make the appropriate changes myself. My modifications are probably more of a quick hack than an elegant solution, but I’d still think I’d
make them available to anyone who’s interested. Those who are can grab my modified version of BlogEngine.NET at
Changes compared to the “plain vanilla” version of BlogEngine.NET 1.4.5:
We ping external ping services using the weblogUpdates.extendedPing method, passing our blog’s base URL along with the blog’s feed URL to the external service.
In the settings, there’s a new text field into which you have to enter your blog’s base URL. This is required for the above to work. It’s mandatory to enter a trailing slash (i.e.
http://www.nightcastle.org/blog/) for stuff to work properly
Changes have been made to the following files:
When done properly, it would probably not be necessary to enter the blog’s base URL in the settings by hand. However, I didn’t have any better idea in the ten minutes I spent making these changes. Utils.BaseUrl
doesn’t really help in my case, does it?
My original idea was to use weblogUpdates.extendedPing, and if that fails because the ping service doesn’t provide it, fall back to weblogUpdates.ping. In the current form, this probably doesn’t work as
I’m not properly interpreting the ping server’s reply, but only falling back to weblogUpdates.ping when the whole first attempt of sending my ping fails. This certainly needs improvement.
Oh, since I only have Microsoft Visual Studio 2008, my BlogEngine.NET version is now a VS2008 project.
I don’t know if this is useful for anybody, but feel free to decide for yourself. I might find the time to do stuff more properly sometime in the future, if “plain vanilla” BlogEngine.NET
doesn’t use weblogUpdates.extendedPing or weblogUpdates.ping until then anyway…
When I have some more time, I’m planning to get more familiar with the inner workings of BlogEngine.NET and develop a “fortune cookie” plugin that will put some random quote / joke / whatever
on each page the engine serves. I’ll announce this stuff here as well once I’m done with it (hopefully still this year…).