blogengine Wiki & Documentation Rss Feed

Updated Wiki: Upgrading to BlogEngine.NET 2.8

rtur — Wed, 29 May 2013 01:48:33 GMT

Upgrading to BlogEngine.NET 2.8

If you are updating from BlogEngine.NET 2.7, there are few changes. The web.config files have changed to reflect DLL updates, but there is no database changes in this release. Most of the instructions below are for those upgrading from 2.7

Recommended Path to Upgrade

The cleanest way to upgrade to v2.8 is to start from a v2.8 installation, and then copy your existing data and settings into v2.8. The upgrade steps follow.

A couple of the steps are related specifically to those who use a database for storage, and a couple are related specifically to those who use the default XML storage (non-database). You can skip the steps that don't pertain to your method of storage.

1. Backup

Make a full backup of your existing BlogEngine installation. This is very important. If anything goes wrong, you can always restore to your backup.

2. Install v2.8

Install v2.8 on your computer, in a new folder.

3. Web.config file (for non-database installations)

It is recommended to use web.config that comes with new installation, and then copy any modifications if needed from your blog's web.config

4. Web.config file (for database installations)

If you will be using a Database for data storage, Web.config files you can use are located in the /setup/ folder. Because of the variety of changes to the web.config files, it is strongly recommended you start from these sample web.config files, and copy your specific connection string into the sample web.config file. For example, for SQL Server, in the /setup/SQLServer folder is a file named SQLServerWeb.Config. For MySQL, the file is /setup/MySQL/MySQLWeb.Config, etc. Copy this file to the blog root, delete the existing Web.config file in the blog root, and then rename this sample config file to Web.config (i.e. rename SQLServerWeb.Config to Web.Config).

At this point, the Web.config file you copied to the blog root and renamed contains a sample DB connection string. The sample DB connection string will look similar to:

connectionString="Data Source=MySQLServer;User ID=user;Password=password;persist security info=False;initial catalog=BlogEngine;"

Replace this sample connection string with the connection string in your existing Web.config file.

If you have any other specific customizations to your existing Web.config file (e.g. appSettings), add those into this Web.config file.

5. Database Upgrade Script (for database installations)

If you are upgrading from BlogEngine.NET 2.7, there are no upgrade scripts to run.

Upgrading from earlier version: If you are using a Database to store your data in, you will need to run the DB upgrade script. Each of the /setup folders has an upgrade script. For SQL Server, it is MSSQLUpgradeFrom2.5to2.6.sql. For MySQL, it is MySQLUpgradeFrom2.5To2.6.sql, etc. Run this script in your existing DB. If you are upgrading from a version prior to 2.5, you will need to first run the upgrade script(s) to get your DB up to v2.5. For example, if you are upgrading from v2.0, you will need to first run the 2.0to2.5 script, and after that, run the 2.5to2.6 script.

6. App_Data folder (for BOTH database and non-database installations)

Delete from BlogEngine.NET 2.8 installation "App_Data" folder all except "/App_Data/Blogs/_New"
Copy your existing blog's App_Data folder content to new v2.8 directory
If you have "App_Data/Blogs/Template" folder in your blog's installation and you not using it as child blog, you should delete it

Note: This step should still be performed even if you are using a database since even with a database, the App_Data folder is still used for storing certain items such as files, images and some other small miscellaneous files.

7. Scripts folder

Move scripts from /Scritps/Header to /Scripts/Auto
Move scripts from /Scripts to /Scripts/Auto

In version 2.7, JavaScripts added to /Scripts folder were automatically added to the end of the page at runtime. Scripts added to the /Scripts/Header were added on top of the page before any HTML load. All these auto-loaded scripts have to be moved to /Scripts/Auto to keep working this way. Main reason for this move due to /Scripts folder been a default install directory for NuGet packages and we want to avoid conflicts and keep common conventions with VS and ASP.NET. Make sure you don't have duplicates in the /Scripts/Auto, all scripts from this folder will be auto-loaded in the alphabetical order. If script depends on the other script, you can rename it to sort properly.

8. Styles folder

Move css styles from /Styles to /Content/Auto
If you have any folders under /Styles, move them to /Content
Delete /Styles folder

Similar to situation with JavaScripts, CSS styles moved to location used by VS/ASP.NEN/NuGet

9. Theme folder, Robots.txt & Other Custom Files

If you have a custom theme, copy your custom theme folder into the v2.8 "themes" folder. Similarly, if you have customized the robots.txt file, or if you have any other custom files/folders, copy those into the v2.8 folder you have been working on.

10. Deploy to Web Server

Because you will have files on your web server that no longer exist (or have been moved) in v2.8, it is best to delete all of the BlogEngine.NET files and folders on your web server, and then upload the new v2.8 files and folders you prepared in the previous steps.

Please make sure you have a backup of everything you will delete (see step 1).

After you have deleted the BlogEngine.NET files/folder off your web server, upload the v2.8 files and folders you prepared in the previous steps.

11. Check App_Data folder Write Permissions

If you deleted the App_Data folder in the previous deployment step, you may need to double check that Write permissions are still set on the new App_Data folder you uploaded. Even if you are using the Database storage option, certain items such as files & images you include in your blog posts are still saved in the App_Data folder. BlogEngine.NET can only save files in the App_Data folder if Write permissions are enabled for the ASP.NET account.

FAQs & Troubleshooting

I followed steps above, but I'm getting JavaScript/CSS errors after upgrade
You might have custom code or extensions/widgets that use script or style references pointing to old locations. You'll have to manually change those references to use /Content instead of /Styles for example. You can use FireBug or alike to identify scripts/styles that not loaded properly.

My Syntax Highlighter stopped working

Syntax Highlighter now is a part of TinyMCE. To add it to your current theme, you'll need to update 2 files (check standard theme to see full example):

// site.master
<head runat="server">
 <link href='<%# Page.ResolveUrl("~/editors/tiny_mce_3_5_8/plugins/syntaxhighlighter/styles/shCore.css") %>' rel="stylesheet" />
 <link href='<%# Page.ResolveUrl("~/editors/tiny_mce_3_5_8/plugins/syntaxhighlighter/styles/shThemeDefault.css") %>' rel="stylesheet" />
 <script type="text/javascript" src="<%# ShRoot %>scripts/XRegExp.js"></script>
 <script type="text/javascript" src="<%# ShRoot %>scripts/shCore.js"></script>
 <script type="text/javascript" src="<%# ShRoot %>scripts/shAutoloader.js"></script>
 <script type="text/javascript" src="<%# ShRoot %>shActivator.js"></script>
</head>

// site.master.cs
protected static string ShRoot = Utils.ApplicationRelativeWebRoot + "editors/tiny_mce_3_5_8/plugins/syntaxhighlighter/";

protected void Page_Load(object sender, EventArgs e)
{
  // needed to make <%# %> binding work in the page header
  Page.Header.DataBind();
}

Trying to upload file with FileManager but getting "Undefined" error
FileManager currently does not work with FireFox web browser due to security restriction on Flash (it also broke BlogEngine.NET 2.7). IE and Chrome have no issues and we are looking into ways to work around this in the future.

Updated Wiki: Upgrading to BlogEngine.NET 2.8

rtur — Tue, 28 May 2013 20:39:44 GMT

Upgrading to BlogEngine.NET 2.8

Recommended Path to Upgrade

The cleanest way to upgrade to v2.8 is to start from a v2.8 installation, and then copy your existing data and settings into v2.8. The upgrade steps follow.

1. Backup

Make a full backup of your existing BlogEngine installation. This is very important. If anything goes wrong, you can always restore to your backup.

2. Install v2.8

Install v2.8 on your computer, in a new folder.

3. Web.config file (for non-database installations)

It is recommended to use web.config that comes with new installation, and then copy any modifications if needed from your blog's web.config

4. Web.config file (for database installations)

At this point, the Web.config file you copied to the blog root and renamed contains a sample DB connection string. The sample DB connection string will look similar to:

connectionString="Data Source=MySQLServer;User ID=user;Password=password;persist security info=False;initial catalog=BlogEngine;"

Replace this sample connection string with the connection string in your existing Web.config file.

If you have any other specific customizations to your existing Web.config file (e.g. appSettings), add those into this Web.config file.

5. Database Upgrade Script (for database installations)

If you are upgrading from BlogEngine.NET 2.7, there are no upgrade scripts to run.

6. App_Data folder (for BOTH database and non-database installations)

Delete from BlogEngine.NET 2.8 installation "App_Data" folder all except "/App_Data/Blogs/_New"
Copy your existing blog's App_Data folder content to new v2.8 directory
If you have "App_Data/Blogs/Template" folder in your blog's installation and you not using it as child blog, you should delete it

7. Scripts folder

Move scripts from /Scritps/Header to /Scripts/Auto
Move scripts from /Scripts to /Scripts/Auto

8. Styles folder

Move css styles from /Styles to /Content/Auto
If you have any folders under /Styles, move them to /Content
Delete /Styles folder

Similar to situation with JavaScripts, CSS styles moved to location used by VS/ASP.NEN/NuGet

9. Theme folder, Robots.txt & Other Custom Files

10. Deploy to Web Server

Please make sure you have a backup of everything you will delete (see step 1).

After you have deleted the BlogEngine.NET files/folder off your web server, upload the v2.8 files and folders you prepared in the previous steps.

11. Check App_Data folder Write Permissions

FAQs & Troubleshooting

I followed steps above, but I'm getting JavaScript/CSS errors after upgrade
You might have custom code or extensions/widgets that use script or style references pointing to old locations. You'll have to manually change those references to use /Content instead of /Styles for example. You can use FireBug or alike to identify scripts/styles that not loaded properly.

My Syntax Highlighter stopped working

Syntax Highlighter now is a part of TinyMCE. To add it to your current theme, you'll need to update 2 files (check standard theme to see full example):

// site.master
<head runat="server">
    <link href='<%# Page.ResolveUrl("~/editors/tiny_mce_3_5_8/plugins/syntaxhighlighter/styles/shCore.css") %>' rel="stylesheet" />
    <link href='<%# Page.ResolveUrl("~/editors/tiny_mce_3_5_8/plugins/syntaxhighlighter/styles/shThemeDefault.css") %>' rel="stylesheet" />
    <script type="text/javascript" src="<%# ShRoot %>scripts/XRegExp.js"></script>
    <script type="text/javascript" src="<%# ShRoot %>scripts/shCore.js"></script>
    <script type="text/javascript" src="<%# ShRoot %>scripts/shAutoloader.js"></script>
    <script type="text/javascript" src="<%# ShRoot %>shActivator.js"></script>
</head>

// site.master.cs
protected static string ShRoot = Utils.ApplicationRelativeWebRoot + "editors/tiny_mce_3_5_8/plugins/syntaxhighlighter/";

protected void Page_Load(object sender, EventArgs e)
{
	// needed to make <%# %> binding work in the page header
	Page.Header.DataBind();
}

Trying to upload file with FileManager but getting "Undefined" error
FileManager currently does not work with FireFox web browser due to security restriction on Flash (it also broke BlogEngine.NET 2.7). IE and Chrome have no issues and we are looking into ways to work around this in the future.

Updated Wiki: Upgrading to BlogEngine.NET 2.8

rtur — Tue, 28 May 2013 20:38:38 GMT

Upgrading to BlogEngine.NET 2.8

Recommended Path to Upgrade

The cleanest way to upgrade to v2.8 is to start from a v2.8 installation, and then copy your existing data and settings into v2.8. The upgrade steps follow.

1. Backup

Make a full backup of your existing BlogEngine installation. This is very important. If anything goes wrong, you can always restore to your backup.

2. Install v2.8

Install v2.8 on your computer, in a new folder.

3. Web.config file (for non-database installations)

It is recommended to use web.config that comes with new installation, and then copy any modifications if needed from your blog's web.config

4. Web.config file (for database installations)

At this point, the Web.config file you copied to the blog root and renamed contains a sample DB connection string. The sample DB connection string will look similar to:

connectionString="Data Source=MySQLServer;User ID=user;Password=password;persist security info=False;initial catalog=BlogEngine;"

Replace this sample connection string with the connection string in your existing Web.config file.

If you have any other specific customizations to your existing Web.config file (e.g. appSettings), add those into this Web.config file.

5. Database Upgrade Script (for database installations)

If you are upgrading from BlogEngine.NET 2.7, there are no upgrade scripts to run.

6. App_Data folder (for BOTH database and non-database installations)

Delete from BlogEngine.NET 2.8 installation "App_Data" folder all except "/App_Data/Blogs/_New"
Copy your existing blog's App_Data folder content to new v2.8 directory
If you have "App_Data/Blogs/Template" folder in your blog's installation and you not using it as child blog, you should delete it

7. Scripts folder

Move scripts from /Scritps/Header to /Scripts/Auto
Move scripts from /Scripts to /Scripts/Auto

8. Styles folder

Move css styles from /Styles to /Content/Auto
If you have any folders under /Styles, move them to /Content
Delete /Styles folder

Similar to situation with JavaScripts, CSS styles moved to location used by VS/ASP.NEN/NuGet

9. Theme folder, Robots.txt & Other Custom Files

10. Deploy to Web Server

Please make sure you have a backup of everything you will delete (see step 1).

After you have deleted the BlogEngine.NET files/folder off your web server, upload the v2.8 files and folders you prepared in the previous steps.

11. Check App_Data folder Write Permissions

FAQs & Troubleshooting

I followed steps above, but I'm getting JavaScript/CSS errors after upgrade
You might have custom code or extensions/widgets that use script or style references pointing to old locations. You'll have to manually change those references to use /Content instead of /Styles for example. You can use FireBug or alike to identify scripts/styles that not loaded properly.

My Syntax Highlighter stopped working

Syntax Highlighter now is a part of TinyMCE. To add it to your current theme, you'll need to update 2 files (check standard theme to see full example):

// site.master
<head runat="server">
    <link href='<%# Page.ResolveUrl("~/editors/tiny_mce_3_5_8/plugins/syntaxhighlighter/styles/shCore.css") %>' rel="stylesheet" />
    <link href='<%# Page.ResolveUrl("~/editors/tiny_mce_3_5_8/plugins/syntaxhighlighter/styles/shThemeDefault.css") %>' rel="stylesheet" />
    <script type="text/javascript" src="<%# ShRoot %>scripts/XRegExp.js"></script>
    <script type="text/javascript" src="<%# ShRoot %>scripts/shCore.js"></script>
    <script type="text/javascript" src="<%# ShRoot %>scripts/shAutoloader.js"></script>
    <script type="text/javascript" src="<%# ShRoot %>shActivator.js"></script>
</head>

// site.master.cs
protected static string ShRoot = Utils.ApplicationRelativeWebRoot + "editors/tiny_mce_3_5_8/plugins/syntaxhighlighter/";

protected void Page_Load(object sender, EventArgs e)
{
	// needed to make <%# %> binding work in the page header
	Page.Header.DataBind();
}

Trying to upload file with FileManager but getting "Undefined" error
FileManager currently does not work with FireFox web browser due to security restriction on Flash (it also broke BlogEngine.NET 2.7). IE and Chrome have no issues and we are looking into ways to work around this in the future.

Updated Wiki: Upgrading to BlogEngine.NET 2.8

rtur — Tue, 28 May 2013 20:28:07 GMT

Upgrading to BlogEngine.NET 2.8

Recommended Path to Upgrade

The cleanest way to upgrade to v2.8 is to start from a v2.8 installation, and then copy your existing data and settings into v2.8. The upgrade steps follow.

1. Backup

Make a full backup of your existing BlogEngine installation. This is very important. If anything goes wrong, you can always restore to your backup.

2. Install v2.8

Install v2.8 on your computer, in a new folder.

3. Web.config file (for non-database installations)

It is recommended to use web.config that comes with new installation, and then copy any modifications if needed from your blog's web.config

4. Web.config file (for database installations)

At this point, the Web.config file you copied to the blog root and renamed contains a sample DB connection string. The sample DB connection string will look similar to:

connectionString="Data Source=MySQLServer;User ID=user;Password=password;persist security info=False;initial catalog=BlogEngine;"

Replace this sample connection string with the connection string in your existing Web.config file.

If you have any other specific customizations to your existing Web.config file (e.g. appSettings), add those into this Web.config file.

5. Database Upgrade Script (for database installations)

If you are upgrading from BlogEngine.NET 2.7, there are no upgrade scripts to run.

6. App_Data folder (for BOTH database and non-database installations)

Delete from BlogEngine.NET 2.8 installation "App_Data" folder all except "/App_Data/Blogs/_New"
Copy your existing blog's App_Data folder content to new v2.8 directory
If you have "App_Data/Blogs/Template" folder in your blog's installation and you not using it as child blog, you should delete it

7. Scripts folder

Move scripts from /Scritps/Header to /Scripts/Auto
Move scripts from /Scripts to /Scripts/Auto

8. Styles folder

Move css styles from /Styles to /Content/Auto
If you have any folders under /Styles, move them to /Content
Delete /Styles folder

Similar to situation with JavaScripts, CSS styles moved to location used by VS/ASP.NEN/NuGet

9. Theme folder, Robots.txt & Other Custom Files

10. Deploy to Web Server

Please make sure you have a backup of everything you will delete (see step 1).

After you have deleted the BlogEngine.NET files/folder off your web server, upload the v2.8 files and folders you prepared in the previous steps.

11. Check App_Data folder Write Permissions

FAQs & Troubleshooting

I followed steps above, but I'm getting JavaScript/CSS errors after upgrade
You might have custom code or extensions/widgets that use script or style references pointing to old locations. You'll have to manually change those references to use /Content instead of /Styles for example. You can use FireBug or alike to identify scripts/styles that not loaded properly.

My Syntax Highlighter stopped working

Syntax Highlighter now is a part of TinyMCE. To add it to your current theme, you'll need to update 2 files:

// site.master
<head runat="server">
    <link href='<%# Page.ResolveUrl("~/editors/tiny_mce_3_5_8/plugins/syntaxhighlighter/styles/shCore.css") %>' rel="stylesheet" />
    <link href='<%# Page.ResolveUrl("~/editors/tiny_mce_3_5_8/plugins/syntaxhighlighter/styles/shThemeDefault.css") %>' rel="stylesheet" />
    <script type="text/javascript" src="<%# ShRoot %>scripts/XRegExp.js"></script>
    <script type="text/javascript" src="<%# ShRoot %>scripts/shCore.js"></script>
    <script type="text/javascript" src="<%# ShRoot %>scripts/shAutoloader.js"></script>
    <script type="text/javascript" src="<%# ShRoot %>shActivator.js"></script>
</head>

// site.master.cs

protected static string ShRoot = Utils.ApplicationRelativeWebRoot + "editors/tiny_mce_3_5_8/plugins/syntaxhighlighter/";

protected void Page_Load(object sender, EventArgs e)
{

	// needed to make <%# %> binding work in the page header
	Page.Header.DataBind();
}

Trying to upload file with FileManager but getting "Undefined" error
FileManager currently does not work with FireFox web browser due to security restriction on Flash (it also broke BlogEngine.NET 2.7). IE and Chrome have no issues and we are looking into ways to work around this in the future.

New Comment on "Installation"

joannarom — Wed, 08 May 2013 19:44:34 GMT

Just installed the new version of BlogEngine...fresh install on Windows 7 profession 64 bit edition running IIS 7 and using IE10. I tried both the web and source versions of the project and get the following javascript error when I try to access the "Settings" pages. "Member Not Found" DOM inspector shows that it is occurring in jquery-1.8.2.min.js line 2 character 32075 and highlights the following line: return d||(d=e.createAttribute(c),a.setAttributeNode(d)),d.value=b+"" The settings pages display fine but each section withing settings displays this javascript error. I also cannot save any changes within settings, BUT I was able to change my password so I do not think its a permissions issue on the app_data folder, but I could be wrong, I just started this today.

New Comment on "SyndicationSetup"

SimpleNick — Wed, 08 May 2013 17:58:31 GMT

> Sitemap generated by blogEngine does not work with feedburner. Feedburner does not like the urlset tag Has this been resolved ?

New Comment on "ChangingThemes"

SimpleNick — Mon, 06 May 2013 16:56:29 GMT

Found it. Its under customize on the tab menu.

Updated Wiki: Installation

rtur — Sat, 20 Apr 2013 19:44:41 GMT

Installation

1 - Installation Overview
2 - Choosing a version for download
3 - Fresh Installation
4 - Upgrading From Previous Version
5 - Troubleshooting
6 - IIS 7

1 - Installation Overview

The BlogEngine.NET installation process is fairly straight forward. The information below will guide you through the process and help you with any issues you encounter.

2 - Choosing a version for download

There are two download options for BlogEngine.NET:

Web Project: This is an ideal option if you want to use BlogEngine.NET right out of the box and don't have plans to create custom controls or extend the software.
Source Code: This is the developer option. If you are interested is seeing how things work or want to add to the functionality, this is your option. Note that although you can look at the source with Visual Studio 2005 Express, you can't rebuild the DLL with it.

Choosing one option over the other doesn't lock you into your decision, but you need to choose a place to start. If you are unsure, just download the web project. You can always download the Source Code later and add your changes in.

3 - Fresh Installation

By fresh installation, we mean that you are creating a new instance (folder with the application) of BlogEngine.NET on your server/hosting space/local pc. If you already have an instance of BlogEngine.NET that you want to upgrade, see the next section. If you already have an instance that you played around with, but you just want to start again, this is the section for you.

Get the web project folder

Now that you have a downloaded zip file, you need to un-zip it. This can be done with a bunch of different utilities and in a bunch of different methods.

If you choose the Web Project download, your newly unzipped folder contains the web project you want to work with. If you download the source code, the web project is buried a little bit. The web project is found under the BlogEngine.NET folder, then the BlogEngine folder.

Load the web project on your web server

Now that you have the web project folder, copy those files and folders out to your web server. This usually involves FTP, but depending on your situation, it might even require a portable storage device (e.g. USB flash drive).

Set folder as a .NET 4.0 application

There isn't much to say about this. If you have direct IIS access, you need to create an application. If you are using a hosted provider, you need to use their control panel to make this happen. It should be a standard option, but if you don't find it, you may need to contact your hosting provider for support. BlogEngine.NET is developed under an "Integrated Mode" application pool. It is recommended your application pool be in Integrated Mode (as opposed to Classic Mode).

Add write permissions for App_Data folder

This is an often forgotten step. If you miss it, you'll notice as soon as you try to make a change. You need to give the application write permissions to the App_Data folder. Again, your hosting provider may have a control panel that allows you to do this. If not, you may need to contact your hosting provider for support.

Setting write permissions could involve up to 3 steps: 1) Using the IIS admin tool or your hosting provider's control panel, set the folder as "Write" capable; 2) If you have direct access to the file system, make sure the account under which the BlogEngine.NET's application pool is running (typically "ASPNET" on XP / 2003 and "Network Service" on Vista / 2008) has write access to the physical folder; 3) After unzipping the web folder, all files have their read-only attribute enabled. Turn that attribute off for the App_Data folder and all files and subfolders.

Navigate to the web page

Ok, now you are ready to navigate to the web site and see how you did. For example, if you installed the web site to your local machine for testing, you would navigate to http://localhost/default.aspx. You can also edit the default document to display to default.aspx using the IIS MMC snap-in. If you do this, you can navigate direcly to http://localhost/ without specifying the page name. If all goes well, you are greeted by the default blog page.

Login and Setup your user name

The last step is to scroll down and find the sign in link on the right side. Click Sign in and then login in the following information.

User Name: admin Password: admin

Once you login, you will see a new menu on the right hand side. Click Users.

Create a new user for yourself. The user name you choose is your display name. See the User Administration page for more information.

Delete the admin account. You don't want everyone who reads this to be able to login to your blog, do you?

Finally, log out, then log back in using the user account you just created for yourself.

4 - Upgrading From Previous Version

Ah, a veteran. You know all the basics so I won't bore you with them. If you do struggle with the basic setup though, don't be afraid to read the Fresh Installation instructions.

4.6 Upgrading to version 1.6

If you're upgrading from an earlier release to version 1.6, there's two important changes to make when upgrading.

Delete the entire "ExtensionManager" sub-folder in the App_Code folder. This code has been moved into the BlogEngine.Core.dll in version 1.6. Not deleting this sub-folder will lead to errors.
For multiple widget zone support, a couple of CSS class names have changed. You may need to update your theme's CSS file. A search and replace should be sufficient.
1. Replace #widgetzone with .widgetzone
2. Replace #widgetselector with .widgetselector
As always, please follow the upgrade guidelines described below.

More details on CSS changes and multiple widget zones in general can be found here.

4.6 Upgrading to version 1.4

Checkout this for specific upgrade instructions from previous versions to version 1.4 of BE

Backup your stuff

It is always a good idea to backup your files before starting an upgrade. It's a general recommendation and if you do it right, we guarantee you won't lose any information.

The main things you'll be interested in saving are the entire contents of your App_Data folder, custom themes you may have, and any custom controls you made. Remember that even if you just made a few slight modification to a theme, you will want to back them up so you can put them into the new installation.

Merging your data with the web project

Depending on when you downloaded your pre-release version of BlogEngine, you may have an incomplete settings.xml file. You will want to open the freshly downloaded settings.xml file from the App_Data folder and compare it to your existing settings.xml file. Any entries in the new one that aren't in your existing one, should be added.

If you have a new theme, go ahead and add your theme folder to the new web project themes folder. There have been a lot of changes to the theme process over the course of the project. It would be recommended that you look over the Theme Creation page and make adjustments to your theme accordingly. You could, of course, just try it and see how it works, but then you'd miss out on the fun of reading our Theme documentation.

If you modified an existing theme, it is best to make the changes in the new version of that theme.

Load it up already

Once you have the needed changes, load up your files, and enjoy the latest release. There is lots of good stuff in it!

5 - Troubleshooting

What are you doing here? There couldn't possibly a problem, could there? Ok, these things happen and this is as good a place as any to look for the solution.

When I navigate to my blog, I get a blank page

Make sure your blog folder is set to an Application.

When I navigate to my blog, I get an error page

Check your .NET version. You need to make sure your blog is set to use version 2.0.

I can't edit/change settings/etc

This is caused by not having the correct write permissions on the App_Data folder.

Note: If you use WebHost4Life, the proper settings should be user Network Service has Full Control.

Security/ Permissions

Set up the App_Data folder so that the ASP.NET service and IIS can both read and write to it. In Vista/IIS7.0 this means that you need to set this access up (from within Windows Explorer) for the group "users", and also for the "NETWORK SERVICE" (you have to add this latter through the advanced security dialogs). Make sure that the files within the App_Data folder are not set to read only.

Rename the application directory?

Noooh, don't do that. If you installed Blog Engine in a directory like /BlogEngine, then install a subsequence version in a different directory, say /BlogEngine.NET, everything will be fun except all the image references in your old posts will point to the first directory, not the second. Maybe you can rename all the entries in all the little XML files and that will fix it; or you may just wimp out and rename the new installation to the same directory name as the old one, which definitely fixes this.

6 - IIS 7

Inherited handler settings

If you're getting an error:

404.3 HTTP Error 404.3 - Not Found;
The page you are requesting cannot be served because of the Multipurpose Internet Mail Extensions (MIME) map policy that is configured on the Web server. The page you requested has a file name extension that is not recognized, and is not allowed.
Error Code: 0x80070032

Then it may be that your "handlers" aren't inherited correctly by the site containing the blog. You can check this by looking in the "handler" set up for the web server itself - it should have lots of entries including aspx. Then check the "handler" set for the App_Data folder... if that's much smaller, then as per this link. http://dunnry.com/blog/IIS7And4043Error.aspx you may need to tweak things to force the App_Data folder to inherit the handlers correctly.

HTTP Error 500.0 - Internal Server Error Integrated .NET mode

You may get an error as above, which suggests that you should run: %systemroot%\system32\inetsrv\APPCMD.EXE migrate config "site_name/BlogEngine" For once the instructions are correct... just open an admin command window, paste the command from your error message in there and run it.

web.config

If you have tried everything else and simply can't get the handlers to populate for your App_Data folder, it may be worth looking for a little file called "web.config" in the root of your site. Deleting this and then reinstalling the blog software fixed that problem for me.

VS 2008 with Cassini Web Server

Try running Visual Studio as Administrator. That seems to fix a lot of the permission errors under cassini.

Updated Wiki: Upgrading to BlogEngine.NET 2.8

rtur — Wed, 17 Apr 2013 21:17:39 GMT

Upgrading to BlogEngine.NET 2.8

Recommended Path to Upgrade

The cleanest way to upgrade to v2.8 is to start from a v2.8 installation, and then copy your existing data and settings into v2.8. The upgrade steps follow.

1. Backup

Make a full backup of your existing BlogEngine installation. This is very important. If anything goes wrong, you can always restore to your backup.

2. Install v2.8

Install v2.8 on your computer, in a new folder.

3. Web.config file (for non-database installations)

It is recommended to use web.config that comes with new installation, and then copy any modifications if needed from your blog's web.config

4. Web.config file (for database installations)

At this point, the Web.config file you copied to the blog root and renamed contains a sample DB connection string. The sample DB connection string will look similar to:

connectionString="Data Source=MySQLServer;User ID=user;Password=password;persist security info=False;initial catalog=BlogEngine;"

Replace this sample connection string with the connection string in your existing Web.config file.

If you have any other specific customizations to your existing Web.config file (e.g. appSettings), add those into this Web.config file.

5. Database Upgrade Script (for database installations)

If you are upgrading from BlogEngine.NET 2.7, there are no upgrade scripts to run.

6. App_Data folder (for BOTH database and non-database installations)

Delete from BlogEngine.NET 2.8 installation "App_Data" folder all except "/App_Data/Blogs/_New"
Copy your existing blog's App_Data folder content to new v2.8 directory
If you have "App_Data/Blogs/Template" folder in your blog's installation and you not using it as child blog, you should delete it

7. Scripts folder

Move scripts from /Scritps/Header to /Scripts/Auto
Move scripts from /Scripts to /Scripts/Auto

8. Styles folder

Move css styles from /Styles to /Content/Auto
If you have any folders under /Styles, move them to /Content
Delete /Styles folder

Similar to situation with JavaScripts, CSS styles moved to location used by VS/ASP.NEN/NuGet

9. Theme folder, Robots.txt & Other Custom Files

10. Deploy to Web Server

Please make sure you have a backup of everything you will delete (see step 1).

After you have deleted the BlogEngine.NET files/folder off your web server, upload the v2.8 files and folders you prepared in the previous steps.

11. Check App_Data folder Write Permissions

FAQs & Troubleshooting

I followed steps above, but I'm getting JavaScript/CSS errors after upgrade
You might have custom code or extensions/widgets that use script or style references pointing to old locations. You'll have to manually change those references to use /Content instead of /Styles for example. You can use FireBug or alike to identify scripts/styles that not loaded properly.
Trying to upload file with FileManager but getting "Undefined" error
FileManager currently does not work with FireFox web browser due to security restriction on Flash (it also broke BlogEngine.NET 2.7). IE and Chrome have no issues and we are looking into ways to work around this in the future.

Updated Wiki: Upgrading to BlogEngine.NET 2.8

rtur — Tue, 16 Apr 2013 21:19:03 GMT

Upgrading to BlogEngine.NET 2.8

Recommended Path to Upgrade

The cleanest way to upgrade to v2.8 is to start from a v2.8 installation, and then copy your existing data and settings into v2.8. The upgrade steps follow.

1. Backup

Make a full backup of your existing BlogEngine installation. This is very important. If anything goes wrong, you can always restore to your backup.

2. Install v2.8

Install v2.8 on your computer, in a new folder.

3. Web.config file (for non-database installations)

It is recommended to use web.config that comes with new installation, and then copy any modifications if needed from your blog's web.config

4. Web.config file (for database installations)

At this point, the Web.config file you copied to the blog root and renamed contains a sample DB connection string. The sample DB connection string will look similar to:

connectionString="Data Source=MySQLServer;User ID=user;Password=password;persist security info=False;initial catalog=BlogEngine;"

Replace this sample connection string with the connection string in your existing Web.config file.

If you have any other specific customizations to your existing Web.config file (e.g. appSettings), add those into this Web.config file.

5. Database Upgrade Script (for database installations)

If you are upgrading from BlogEngine.NET 2.7, there are no upgrade scripts to run.

6. App_Data folder (for BOTH database and non-database installations)

Delete all except "/App_Data/Blogs/_New" from BlogEngine.NET 2.8 installation
Copy your existing blog's App_Data folder content to new v2.8 directory

7. Scripts folder

Move scripts from /Scritps/Header to /Scripts/Auto
Move scripts from /Scripts to /Scripts/Auto

8. Styles folder

Move css styles from /Styles to /Content/Auto
If you have any folders under /Styles, move them to /Content
Delete /Styles folder

Similar to situation with JavaScripts, CSS styles moved to location used by VS/ASP.NEN/NuGet

9. Theme folder, Robots.txt & Other Custom Files

10. Deploy to Web Server

Please make sure you have a backup of everything you will delete (see step 1).

After you have deleted the BlogEngine.NET files/folder off your web server, upload the v2.8 files and folders you prepared in the previous steps.

11. Check App_Data folder Write Permissions

FAQs & Troubleshooting

I followed steps above, but I'm getting JavaScript/CSS errors after upgrade
You might have custom code or extensions/widgets that use script or style references pointing to old locations. You'll have to manually change those references to use /Content instead of /Styles for example. You can use FireBug or alike to identify scripts/styles that not loaded properly.

Updated Wiki: Upgrading to BlogEngine.NET 2.8

rtur — Mon, 15 Apr 2013 15:21:11 GMT

Upgrading to BlogEngine.NET 2.8

Recommended Path to Upgrade

The cleanest way to upgrade to v2.8 is to start from a v2.8 installation, and then copy your existing data and settings into v2.8. The upgrade steps follow.

1. Backup

Make a full backup of your existing BlogEngine installation. This is very important. If anything goes wrong, you can always restore to your backup.

2. Install v2.8

Install v2.8 on your computer, in a new folder.

3. Web.config file (for non-database installations)

If you are upgrading from BlogEngine.NET 2.6, there are no changes to the web.config files.

Upgrading from BlogEngine.NET 2.5 or earlier: As noted above, because of the changes to the web.config files, it is strongly recommended you use the web.config file that is included with v2.6. If you have any custom settings in your existing web.config files (e.g. appSettings), it will probably be easiest to copy your custom settings into the BlogEngine.NET v2.6 web.config file. If you have any custom settings, those can be copied into the v2.6 web.config file now. Otherwise, you can just use the v2.6 web.config file as-is.

4. Web.config file (for database installations)

If you are upgrading from BlogEngine.NET 2.6, there are no changes to the web.config files.

Upgrading from BlogEngine.NET 2.5 or earlier
If you will be using a Database for data storage, Web.config files you can use are located in the /setup/ folder. Because of the variety of changes to the web.config files, it is strongly recommended you start from these sample web.config files, and copy your specific connection string into the sample web.config file. For example, for SQL Server, in the /setup/SQLServer folder is a file named SQLServerWeb.Config. For MySQL, the file is /setup/MySQL/MySQLWeb.Config, etc. Copy this file to the blog root, delete the existing Web.config file in the blog root, and then rename this sample config file to Web.config (i.e. rename SQLServerWeb.Config to Web.Config).

At this point, the Web.config file you copied to the blog root and renamed contains a sample DB connection string. The sample DB connection string will look similar to:

connectionString="Data Source=MySQLServer;User ID=user;Password=password;persist security info=False;initial catalog=BlogEngine;"

Replace this sample connection string with the connection string in your existing Web.config file.

If you have any other specific customizations to your existing Web.config file (e.g. appSettings), add those into this Web.config file.

5. Database Upgrade Script (for database installations)

If you are upgrading from BlogEngine.NET 2.7, there are no upgrade scripts to run.

6. App_Data folder (for BOTH database and non-database installations)

If you are upgrading from BlogEngine.NET 2.7, there is nothing you need to do with your App_Data files or folders.

Upgrading from earlier version
In your v2.8 installation is the App_Data folder.

If you are upgrading from v2.5, delete all of the files and folders in the App_Data folder except these ones which are new in v2.7:
1. packages.xml
2. packagefiles.xml
If you are upgrading from a version prior to v2.5, then delete all of the files and folders in App_Data EXCEPT for the following 4 new items which were new items introduced in v2.5 or v2.6 that you do not have in your App_Data folder so you will want to keep these 4 items.
1. blogs.xml
2. The blogs directory directly under App_Data.
3. packages.xml
4. packagefiles.xml

Once the files/folders have been deleted from the App_Data folder, copy all of your App_Data contents (files/folders) from your existing blog to the App_Data folder.

7. Theme folder, Robots.txt & Other Custom Files

8. Deploy to Web Server

Please make sure you have a backup of everything you will delete (see step 1).

After you have deleted the BlogEngine.NET files/folder off your web server, upload the v2.8 files and folders you prepared in the previous steps.

9. Check App_Data folder Write Permissions

FAQs & Troubleshooting

Nothing at this time.

Updated Wiki: Upgrading to BlogEngine.NET 2.8

rtur — Mon, 15 Apr 2013 15:09:27 GMT

Upgrading to BlogEngine.NET 2.8

Recommended Path to Upgrade

The cleanest way to upgrade to v2.8 is to start from a v2.8 installation, and then copy your existing data and settings into v2.8. The upgrade steps follow.

1. Backup

Make a full backup of your existing BlogEngine installation. This is very important. If anything goes wrong, you can always restore to your backup.

2. Install v2.8

Install v2.8 on your computer, in a new folder.

3. Web.config file (for non-database installations)

If you are upgrading from BlogEngine.NET 2.6, there are no changes to the web.config files.

4. Web.config file (for database installations)

If you are upgrading from BlogEngine.NET 2.6, there are no changes to the web.config files.

At this point, the Web.config file you copied to the blog root and renamed contains a sample DB connection string. The sample DB connection string will look similar to:

connectionString="Data Source=MySQLServer;User ID=user;Password=password;persist security info=False;initial catalog=BlogEngine;"

Replace this sample connection string with the connection string in your existing Web.config file.

If you have any other specific customizations to your existing Web.config file (e.g. appSettings), add those into this Web.config file.

5. Database Upgrade Script (for database installations)

If you are upgrading from BlogEngine.NET 2.7, there are no upgrade scripts to run.

6. App_Data folder (for BOTH database and non-database installations)

If you are upgrading from BlogEngine.NET 2.7, there is nothing you need to do with your App_Data files or folders.

Upgrading from earlier version
In your v2.8 installation is the App_Data folder.

If you are upgrading from v2.5, delete all of the files and folders in the App_Data folder except these ones which are new in v2.7:
1. packages.xml
2. packagefiles.xml
If you are upgrading from a version prior to v2.5, then delete all of the files and folders in App_Data EXCEPT for the following 4 new items which were new items introduced in v2.5 or v2.6 that you do not have in your App_Data folder so you will want to keep these 4 items.
1. blogs.xml
2. The blogs directory directly under App_Data.
3. packages.xml
4. packagefiles.xml

Once the files/folders have been deleted from the App_Data folder, copy all of your App_Data contents (files/folders) from your existing blog to the App_Data folder.

7. Theme folder, Robots.txt & Other Custom Files

8. Deploy to Web Server

Please make sure you have a backup of everything you will delete (see step 1).

After you have deleted the BlogEngine.NET files/folder off your web server, upload the v2.8 files and folders you prepared in the previous steps.

9. Check App_Data folder Write Permissions

FAQs & Troubleshooting

Nothing at this time.

Updated Wiki: Upgrading to BlogEngine.NET 2.8

rtur — Mon, 15 Apr 2013 15:02:42 GMT

Upgrading to BlogEngine.NET 2.7

Recommended Path to Upgrade

The cleanest way to upgrade to v2.8 is to start from a v2.8 installation, and then copy your existing data and settings into v2.8. The upgrade steps follow.

1. Backup

Make a full backup of your existing BlogEngine installation. This is very important. If anything goes wrong, you can always restore to your backup.

2. Install v2.8

Install v2.8 on your computer, in a new folder.

3. Web.config file (for non-database installations)

If you are upgrading from BlogEngine.NET 2.6, there are no changes to the web.config files.

4. Web.config file (for database installations)

If you are upgrading from BlogEngine.NET 2.6, there are no changes to the web.config files.

At this point, the Web.config file you copied to the blog root and renamed contains a sample DB connection string. The sample DB connection string will look similar to:

connectionString="Data Source=MySQLServer;User ID=user;Password=password;persist security info=False;initial catalog=BlogEngine;"

Replace this sample connection string with the connection string in your existing Web.config file.

If you have any other specific customizations to your existing Web.config file (e.g. appSettings), add those into this Web.config file.

5. Database Upgrade Script (for database installations)

If you are upgrading from BlogEngine.NET 2.7, there are no upgrade scripts to run.

6. App_Data folder (for BOTH database and non-database installations)

If you are upgrading from BlogEngine.NET 2.7, there is nothing you need to do with your App_Data files or folders.

Upgrading from earlier version
In your v2.8 installation is the App_Data folder.

If you are upgrading from v2.5, delete all of the files and folders in the App_Data folder except these ones which are new in v2.7:
1. packages.xml
2. packagefiles.xml
If you are upgrading from a version prior to v2.5, then delete all of the files and folders in App_Data EXCEPT for the following 4 new items which were new items introduced in v2.5 or v2.6 that you do not have in your App_Data folder so you will want to keep these 4 items.
1. blogs.xml
2. The blogs directory directly under App_Data.
3. packages.xml
4. packagefiles.xml

Once the files/folders have been deleted from the App_Data folder, copy all of your App_Data contents (files/folders) from your existing blog to the App_Data folder.

7. Theme folder, Robots.txt & Other Custom Files

8. Deploy to Web Server

Please make sure you have a backup of everything you will delete (see step 1).

After you have deleted the BlogEngine.NET files/folder off your web server, upload the v2.8 files and folders you prepared in the previous steps.

9. Check App_Data folder Write Permissions

FAQs & Troubleshooting

Nothing at this time.

New Comment on "AddEntry"

tsamuels — Fri, 29 Mar 2013 20:06:25 GMT

I can't see where to add a new post. For example I can't see the big content field as mentioned above. Any ideas? I'm logged in as admin.

Updated Wiki: FAQ

rtur — Wed, 27 Feb 2013 16:43:12 GMT

Frequently Asked Questions

Here is a list of the most frequently asked questions about BlogEngine.NET.

Can BlogEngine.NET be installed within an existing website?
How do I update the "About the Author" section of the blog?
Is BlogEngine.NET open source and completely free?
Is my mother able to use it?
What are the demands for the web server?
What database is it running on?
How can I switch where data is stored (XML to Database or vice versa)?
Can I customize the design of the blog?
I have trouble. Can you help out?
How is BlogEngine.NET licensed?
I want to contribute to BlogEngine.NET. What do I do?
How do I reset lost admin password?
How do I allow only logged in users to post comments?

Can BlogEngine.NET be installed within an existing website?

Yes. Install it in its own folder and configure the directory it resides in as an application in IIS.

Some hosting providers may not allow the level of trust used in BlogEngine.NET by default. If you receive an error similar to:

"Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.",

You can try one of the following to resolve the issue:

Comment out the "trust" line in web.config
Ask your hosting provider if they can configure the directory where BlogEngine.NET is installed as a virtual directory.
Ask your hosting provider to verify that the directory has been configured as an application in IIS.

How do I update the "About the Author" section of the blog?

In the default Standard theme, edit the content of this section by clicking "edit" in on the side bar of your blog.

An alternative way to display About the Author information is to create a 'Page' in the control panel. The Title of the Page can be About the Author. Enter information about the author in the WYSIWYG editor. Once the page has been created, you can add a link to the About page on your blog. This can be achieved by adding a Page List widget, or by adding a TextBox widget with a hyperlink to the About page, or by editing your theme file (site.master) and adding a hyperlink to the About page.

Is BlogEngine.NET open source and completely free?

Yes. BlogEngine.NET is built by passionate developers who have too much spare time, just to make an open source blog engine to give away absolutely free.

Is my mother able to use it?

Yes. We have gone to great lengths to make BlogEngine.NET as easy as possible to use – both from an end user as well as a developer or theme designer's point of view.

What are the demands for the web server?

The only thing needed to run BlogEngine.NET is a web server that support ASP.NET 2.0 and write permissions on the App_Data folder.

What database is it running on?

None. BlogEngine.NET uses XML to store all posts, pages etc. by default. However, if you prefer to use a database, BlogEngine.NET includes a "DbBlogProvider" that allows you to store data in databases which support standard SQL -- MS SQL Server, MySql, SQLite and Vista DB among many others. Configuration changes necessary to store data in a SQL Server database can be found here. If there isn't a data provider already available, you can easily write your own provider. We have enginereed our framework to make this very easy and simple to do.

How can I switch where data is stored (XML to Database or vice versa)?

If you're just starting off with BlogEngine.NET, all of your data will be stored in XML files in your App_Data folder. Some web hosts such as GoDaddy who have an automatic BlogEngine.NET setup option, might setup your blog so data is stored in a database instead. If your blog is new, you don't yet have any data, and you want to switch from XML storage to Database storage, find out how here.

If you have an existing blog and you want to switch the backend your data is stored in (switch from XML to Database or Database to XML), a BlogEngine.NET Provider Migration tool is available!

Can I customize the design of the blog?

Yes. If you don't like the themes provided with BlogEngine.NET, you can modify an existing one to match your taste or create a new one from scratch. Creating themes for BlogEngine.NET only requires basic knowledge about ASP.NET and HTML. Additionally, BlogEngine.NET takes full advantage of ASP.NET 2.0's master page structure. Find out more about creating themes.

I have trouble. Can you help out?

Yes, as long as the trouble is BlogEngine.NET related. For information about the use of BlogEngine.NET or how to create themes, you can find almost everything you need in the Documentation. For issues, suggestions and discussions please visit the Discussions.

How is BlogEngine.NET licensed?

BlogEngine.NET is licensed under the Microsoft Reciprocal License (Ms-RL), which basically means that you can do anything you want to the source code as long as you release it under the same license.

I want to contribute to BlogEngine.NET. What do I do?

We welcome anybody who wants to contribute. Please read our contribute page to find out how you can get involved.

How do I reset lost admin password?

If you are using default XML provider:

1. Get to your website (usually by FTP to your web server).
2. Open /app_data/users.xml in the text editor, for example notepad.
3. Remove password from your admin account, meaning:

change from:
<UserName>Admin</UserName>
<Password>long-encrypted-key-here</Password>

to:
<UserName>Admin</UserName>
<Password></Password>

If you are using SQL then instead of XML file update DB table:
UPDATE be_Users SET Password = '' WHERE UserName = 'admin'

4. Restart web site, easiest way is to open web.config and add a space to the comment and save it. Comments are:


Now you should be able to log in as admin/admin.

If you don't have Admin account in the users.xml file, add new user tag like so:

<User>
<UserName>Admin</UserName>
<Password></Password>
<Email>post@example.com</Email>
<LastLoginTime>2007-12-05 20:46:40</LastLoginTime>
</User>

Once logged in as admin, you can delete and create again any user account from admin panel.

How do I allow only logged in users to post comments?

Set up role for self registration

1. In the admin panel, go to Users -> Roles and create new role, for example "Commentors".
2. Hover over "Tools" for this role when it added to the list and select "Rights".
3. On the "Rights" screen, hover over "Copy rights from" and click "Anonymous role".

Revoke "Create comment" right from anonymous

1. In the "Roles" screen, hover over "Tools" for anonymous and select "Rigts".
2. In the comments section, uncheck "Create Comment".

Set up self registration

1. In the admin panel, go to Settings -> Advanced and under "Security Settings" section check "Enable self registration". This will add registration option to logon screen.
2. In the "Initial Role" dropdown, select "Commentors" role created in the first step.

Whith this in place, only logged in users should be able to post comments.

Updated Wiki: FAQ

rtur — Wed, 27 Feb 2013 16:41:39 GMT

Frequently Asked Questions

Here is a list of the most frequently asked questions about BlogEngine.NET.

Can BlogEngine.NET be installed within an existing website?
How do I update the "About the Author" section of the blog?
Is BlogEngine.NET open source and completely free?
Is my mother able to use it?
What are the demands for the web server?
What database is it running on?
How can I switch where data is stored (XML to Database or vice versa)?
Can I customize the design of the blog?
I have trouble. Can you help out?
How is BlogEngine.NET licensed?
I want to contribute to BlogEngine.NET. What do I do?
How do I reset lost admin password?
How do I allow only logged in users to post comments?

Can BlogEngine.NET be installed within an existing website?

"Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.",

You can try one of the following to resolve the issue:

Comment out the "trust" line in web.config
Ask your hosting provider if they can configure the directory where BlogEngine.NET is installed as a virtual directory.
Ask your hosting provider to verify that the directory has been configured as an application in IIS.

How do I update the "About the Author" section of the blog?

Is BlogEngine.NET open source and completely free?

Yes. BlogEngine.NET is built by passionate developers who have too much spare time, just to make an open source blog engine to give away absolutely free.

Is my mother able to use it?

Yes. We have gone to great lengths to make BlogEngine.NET as easy as possible to use – both from an end user as well as a developer or theme designer's point of view.

What are the demands for the web server?

The only thing needed to run BlogEngine.NET is a web server that support ASP.NET 2.0 and write permissions on the App_Data folder.

What database is it running on?

How can I switch where data is stored (XML to Database or vice versa)?

Can I customize the design of the blog?

I have trouble. Can you help out?

How is BlogEngine.NET licensed?

BlogEngine.NET is licensed under the Microsoft Reciprocal License (Ms-RL), which basically means that you can do anything you want to the source code as long as you release it under the same license.

I want to contribute to BlogEngine.NET. What do I do?

We welcome anybody who wants to contribute. Please read our contribute page to find out how you can get involved.

How do I reset lost admin password?

How do I allow only logged in users to post comments?

Updated Wiki: FAQ

rtur — Wed, 27 Feb 2013 16:39:55 GMT

Frequently Asked Questions

Here is a list of the most frequently asked questions about BlogEngine.NET.

Can BlogEngine.NET be installed within an existing website?
How do I update the "About the Author" section of the blog?
Is BlogEngine.NET open source and completely free?
Is my mother able to use it?
What are the demands for the web server?
What database is it running on?
How can I switch where data is stored (XML to Database or vice versa)?
Can I customize the design of the blog?
I have trouble. Can you help out?
How is BlogEngine.NET licensed?
I want to contribute to BlogEngine.NET. What do I do?
How do I reset lost admin password?
How do I allow only logged in users to post comments?

Can BlogEngine.NET be installed within an existing website?

"Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.",

You can try one of the following to resolve the issue:

Comment out the "trust" line in web.config
Ask your hosting provider if they can configure the directory where BlogEngine.NET is installed as a virtual directory.
Ask your hosting provider to verify that the directory has been configured as an application in IIS.

How do I update the "About the Author" section of the blog?

Is BlogEngine.NET open source and completely free?

Yes. BlogEngine.NET is built by passionate developers who have too much spare time, just to make an open source blog engine to give away absolutely free.

Is my mother able to use it?

Yes. We have gone to great lengths to make BlogEngine.NET as easy as possible to use – both from an end user as well as a developer or theme designer's point of view.

What are the demands for the web server?

The only thing needed to run BlogEngine.NET is a web server that support ASP.NET 2.0 and write permissions on the App_Data folder.

What database is it running on?

How can I switch where data is stored (XML to Database or vice versa)?

Can I customize the design of the blog?

I have trouble. Can you help out?

How is BlogEngine.NET licensed?

BlogEngine.NET is licensed under the Microsoft Reciprocal License (Ms-RL), which basically means that you can do anything you want to the source code as long as you release it under the same license.

I want to contribute to BlogEngine.NET. What do I do?

We welcome anybody who wants to contribute. Please read our contribute page to find out how you can get involved.

How do I reset lost admin password?

How do I allow only logged in users to post comments?

Set up role for self registration

1. In the admin panel, go to Users -> Roles and create new role, for example "Commentors".
2. Hover over "Tools" for this role when it added to the list and select "Rights".
3. On the "Rights" screen, hover over "Copy rights from" and click "Anonymous role".

Revoke "Create comment" right from anonymous

1. In the "Roles" screen, hover over "Tools" for anonymous and select "Rights".
2. In the comments section, uncheck "Create Comment".

Set up self registration

1. In the admin panel, go to Settings -> Advanced and under "Security Settings" section check "Enable self registration". This will add registration option to logon screen.
2. In the "Initial Role" drop-down, select "Commentors" role created in the first step.

With this in place, only logged in users should be able to post comments.

Updated Wiki: FAQ

rtur — Wed, 27 Feb 2013 16:31:34 GMT

Frequently Asked Questions

Here is a list of the most frequently asked questions about BlogEngine.NET.

Can BlogEngine.NET be installed within an existing website?
How do I update the "About the Author" section of the blog?
Is BlogEngine.NET open source and completely free?
Is my mother able to use it?
What are the demands for the web server?
What database is it running on?
How can I switch where data is stored (XML to Database or vice versa)?
Can I customize the design of the blog?
I have trouble. Can you help out?
How is BlogEngine.NET licensed?
I want to contribute to BlogEngine.NET. What do I do?
How do I reset lost admin password?
How do I allow only logged in users to post comments?

Can BlogEngine.NET be installed within an existing website?

"Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.",

You can try one of the following to resolve the issue:

Comment out the "trust" line in web.config
Ask your hosting provider if they can configure the directory where BlogEngine.NET is installed as a virtual directory.
Ask your hosting provider to verify that the directory has been configured as an application in IIS.

How do I update the "About the Author" section of the blog?

Is BlogEngine.NET open source and completely free?

Yes. BlogEngine.NET is built by passionate developers who have too much spare time, just to make an open source blog engine to give away absolutely free.

Is my mother able to use it?

Yes. We have gone to great lengths to make BlogEngine.NET as easy as possible to use – both from an end user as well as a developer or theme designer's point of view.

What are the demands for the web server?

The only thing needed to run BlogEngine.NET is a web server that support ASP.NET 2.0 and write permissions on the App_Data folder.

What database is it running on?

How can I switch where data is stored (XML to Database or vice versa)?

Can I customize the design of the blog?

I have trouble. Can you help out?

How is BlogEngine.NET licensed?

BlogEngine.NET is licensed under the Microsoft Reciprocal License (Ms-RL), which basically means that you can do anything you want to the source code as long as you release it under the same license.

I want to contribute to BlogEngine.NET. What do I do?

We welcome anybody who wants to contribute. Please read our contribute page to find out how you can get involved.

How do I reset lost admin password?

How do I allow only logged in users to post comments?

1. Goes here...

New Comment on "SQLServerBlogProvider"

donrolling — Mon, 18 Feb 2013 20:34:22 GMT

Here are two helpful points to address firepol's question: 1. In order to change the membership and role providers to also use the database, do the following: Web.config: <membership defaultProvider="SqlMembershipProvider"> <roleManager defaultProvider="SqlRoleProvider" enabled="true" cacheRolesInCookie="false"> 2. In order to use the membership stuff, you'll have to run a command on the database that will create the procs and tables that MS Membership requires. This can be done by following the instructions here: http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx, or just by running aspnet_regsql.exe in C:\WINDOWS\Microsoft.NET\Framework\[Correct Framework Folder]

New Comment on "Installation"

sczerno — Mon, 04 Feb 2013 15:14:11 GMT

If a category has a dash in it, for example "Hyper-V", it is displayed as a child category.

blogengine Wiki & Documentation Rss Feed

Updated Wiki: Upgrading to BlogEngine.NET 2.8

Upgrading to BlogEngine.NET 2.8

Recommended Path to Upgrade

1. Backup

2. Install v2.8

3. Web.config file (for non-database installations)

4. Web.config file (for database installations)

5. Database Upgrade Script (for database installations)

6. App_Data folder (for BOTH database and non-database installations)

7. Scripts folder

8. Styles folder

9. Theme folder, Robots.txt & Other Custom Files

10. Deploy to Web Server

11. Check App_Data folder Write Permissions

FAQs & Troubleshooting

Updated Wiki: Upgrading to BlogEngine.NET 2.8

Upgrading to BlogEngine.NET 2.8

Recommended Path to Upgrade

1. Backup

2. Install v2.8

3. Web.config file (for non-database installations)

4. Web.config file (for database installations)

5. Database Upgrade Script (for database installations)

6. App_Data folder (for BOTH database and non-database installations)

7. Scripts folder

8. Styles folder

9. Theme folder, Robots.txt & Other Custom Files

10. Deploy to Web Server

11. Check App_Data folder Write Permissions

FAQs & Troubleshooting

Updated Wiki: Upgrading to BlogEngine.NET 2.8

Upgrading to BlogEngine.NET 2.8

Recommended Path to Upgrade

1. Backup

2. Install v2.8

3. Web.config file (for non-database installations)

4. Web.config file (for database installations)

5. Database Upgrade Script (for database installations)

6. App_Data folder (for BOTH database and non-database installations)

7. Scripts folder

8. Styles folder

9. Theme folder, Robots.txt & Other Custom Files

10. Deploy to Web Server

11. Check App_Data folder Write Permissions

FAQs & Troubleshooting

Updated Wiki: Upgrading to BlogEngine.NET 2.8

Upgrading to BlogEngine.NET 2.8

Recommended Path to Upgrade

1. Backup

2. Install v2.8

3. Web.config file (for non-database installations)

4. Web.config file (for database installations)

5. Database Upgrade Script (for database installations)

6. App_Data folder (for BOTH database and non-database installations)

7. Scripts folder

8. Styles folder

9. Theme folder, Robots.txt & Other Custom Files

10. Deploy to Web Server

11. Check App_Data folder Write Permissions

FAQs & Troubleshooting

New Comment on "Installation"

New Comment on "SyndicationSetup"

New Comment on "ChangingThemes"

Updated Wiki: Installation

Installation

Table of Contents

1 - Installation Overview

2 - Choosing a version for download

3 - Fresh Installation

Get the web project folder

Load the web project on your web server

Set folder as a .NET 4.0 application

Add write permissions for App_Data folder

Navigate to the web page

Login and Setup your user name

4 - Upgrading From Previous Version

4.1 Upgrading to version 2.8

4.2 Upgrading to version 2.7

4.3 Upgrading to version 2.6