.NET and Open Source: better together

RTur.net

  • Join Us on Facebook!
  • Follow Us on Twitter!
  • LinkedIn
  • Subcribe to Our RSS Feed

Spam counter control

pbw-2 I’ve been playing a lot with Commentor and Waegis lately and got a little tired of having to get to admin page through extensions panel. I wanted a one-click shortcut from the front page. Great laziness usually leads to a lot of work – for me it resulted in spam counter user control. It is complimentary to Commentor and is distributed as part of this extension. To use it, download latest (version 1.2) and then add control to your theme of choice. One caviar here is that for visitors clicking on Commentor link inside spam counter will load post about this extension, while for admin it will load Commentor’s admin control panel. This way, you don’t have to go to settings/commentor/edit – it’ll save you whole two clicks! :) More...

Commentor - new extension for BlogEngine

commentor-1 Commentor is a new BlogEngine extension that should make your life a little easier when you have problem with spam comments. At first, I simply wanted to try existing extension to filter spam. My intention was to use anti-spam service as automated moderator and workflow for the task supposed to be pretty simple and look somewhat like this: More...

Writing extensions for BlogEngine 1.4 (part 4)

ex_5-4

Default admin interface for extensions in BlogEngine works fine in most cases and very easy to use. But sometimes you just got to get creative, right? That means, you want no limits. Obviously, some of simplicity will be lost – but still it is surprisingly easy to get along using plug-and-play BlogEngine architecture. Lets say, we ran into nice DHTML color picker and want to use it in the admin page for our extension. We want admin page look like this picture – it should allow us to enter a word, size and color. This values will be saved in the extension manager, so we don’t have to deal with databases or file system – usual BE stuff. And when you click “Color picker” button, nice color picker will show up and you can visually select value for a color. More...

Writing extensions for BlogEngine 1.4 (part 3)

Lets say we want to write an extension to track user activities on our site. Blogger should be able to set basic settings, for example choose to track  posts, pages or both. Then every time user requests post or page, we increment corresponding counter by one. Look at the picture above. Its clear that we need two sets of settings: one for post/page options and another to list user activity.

ext14-3-1

More...

Writing extensions for BlogEngine 1.4 (part 2)

In the first part, we wrote simple extension that changes case in the post to lower. Let’s say, we want user to decide show post in the lower or upper case. For this, we need to be able to maintain variable and let blogger change it’s value through admin interface. Normally, you would need to add a data access functionality for extension to handle this kind of operation, create admin form etc. BlogEngine uses Extension Manager to help make job a lot easier. Take a look at the code below. In the constructor, we subscribe to post serving event and then call InitSettings. There we create ExtensionSettings object, which can hold singe value (scalar) or/and table of values. In our case, we want it to hold single scalar value, so we set settings to scalar. We call our variable “Case” and initialize it with default value of “upper”, then call ExtensionManager.InitSettings and pass name of extension and settings object. More...

Writing extensions for BlogEngine 1.4 (part 1)

This is the first part in the series of tutorials about writing extensions for the BlogEngine 1.4. I’ll start with simple “hello world” example and then gradually move to the more advanced techniques. You don’t need to have any previous experience with BE extensions to follow this tutorial. More...

Changes to Extension Manager in BlogEngine 1.4

Preparing for BE 1.4 release, which is coming soon (although exact date not yet set), I started working on documentation for Extension Manager and changes it has compared to previous BE version. This is a short list I came up with. Obviously, I'll have to go into specifics and provide code examples for documentation be useful. This will be on the Wiki as soon as 1.4 released. More...

Documentation for Extension Manager

Developers don't like to write documentation. There is nothing one can do about it. Yet, no matter how many great features you add to the project, no one will use them if they not well documented and easily discoverable. There is no special department for document writers on the open source projects (alas), so man has to do what the man has to do...

It is work in progress, but I promise to put extra effort and catch up on all features I've been doing for BlogEngine before 1.4 will be released some time late spring. I'll maintain documents both on Wiki and this site, in the future Wiki will have documentation on current release and this site will have latest on new features that will be rolled out to the Wiki when new release will become available.

Data Store Release Candidate

For BlogEngine enthusiasts who like live dangerously and always update their sites with latest code from repository, in the latest build Extension Manager set to use generic data store layer instead of doing it's own thing as it did previously. The story behind it is that in the next release we adding Widgets and customizable Themes, and it makes sense to unify data storage for any kind of "extensions" to avoid headaches in the future. For Extension Manager, it means a bit of redesign. Most of it transparent to the users, but some requires your attention. More...

Using multiple settings in Extension Manager

One of the limitations in the Extension Manager is that extension can handle only one settings object. In most cases, for simple extensions, that is enough. But sometimes you need to let blogger maintain multiple set of settings. Common scenario would be when you want to set some parameters and then maintain list of data. For example, in download counter I might want to have settings for kind of files or directories to watch for or ignore, and then I want to save download log into table structure. Currently – can’t do it without custom admin page. More...