The following BlogEngine.Net extensions are part of the Neovolve.BlogEngine.Extensions pack available from CodePlex. Version 1.1 can be downloaded from here.
CatTagLinker
CatTagLinker automatically associates posts and pages with categories and tags based on their title and contents when the entries are created or updated.
In version 1.1, negations can be set by adding a minus sign (-) before a category or tag when saving the entry. If you have a category for "Switch" and are posting an entry that has the word switch in it that is not related to the Switch category, you can enter -switch as a category when saving this entry. The extension will not associate the entry with the switch category.
Snippets
Snippets automatically injects html snippets into blog entries (posts, pages and comments). Each snippet configuration uses search criteria to identify parts of the entries to be replaced with the snippet html.
The settings used to define a snippet are:
- Find text
- Html snippet
- Require brackets
1. Find text
The find text value defines the string that will be used to identify items in blog entries that will be replaced with the html snippet content. The find text values are case insensitive and find whole words. This means that the term ABCD will match abcd, but not abcde.
In the previous version, if you used the find text of "CP" as the search criteria for CodePlex, only references to "CP" would be found. This scenario was inflexible as older blog posts may refer to "CodePlex" rather than the "CP" shortcut. It also didn't cater for the processing of user comments. The general public will be unaware of the snippet extension configuration for the BlogEngine.Net instance and will not know which terms to use to leverage the Snippets extension.
In version 1.1, the find text can express multiple values delimited by either a comma (,) or semicolon (;). Spaces around these delimiters are removed. This allows for a find text value of "CP, CodePlex" to be used to inject an html snippet about CodePlex for either of the representations found in blog entries.
TIP: When using multiple find text values, order the values from most verbose to least verbose. For example, if "[BE], BlogEngine, BlogEngine.Net" is used instead of "[BE], BlogEngine.Net, BlogEngine" and an entry contains the term BlogEngine.Net, then it will be rendered as BlogEngine.Net.Net as BlogEngine will cause a match before BlogEngine.Net.
2. Html snippet
The html snippet is the value that is injected into the entry for each item of text that is found.
3. Require brackets
This is a boolean value that determines whether the Find text values must be surrounded by square brackets ([]). Using brackets as a delimiter around the find text avoids scenarios where the find text (normally an acronym) also represents a word in itself. For example, BE for BlogEngine.Net and VS for Visual Studio need brackets so as to not inappropriately replace be and vs in sentences.
TIP: If the set of find text values has a mixture of terms that require brackets and don't require brackets, you can add the brackets to the individual find text items as appropriate and mark the Requires brackets value as false. A configuration for BlogEngine.Net for example may be to not require brackets, but then define the find text value as "[BE], BlogEngine.Net, BlogEngine".