Tag Archive: blogengine.net


BlogEngine.NET Widget: Quote of the Day

I love quotes.

Install BlogEngine.NET on Subdirectory of Godaddy Share Hosting

GoDaddy sets your Application Path with the name of your subfolder (e.g. blog)

So any link using the tilde (~) points to this full (and ugly) application path, that’s why the BlogEngine.NET doesn’t work for installing under a subdirectory of GoDaddy hosting plans by default. So if you want to install the BlogEngine.NET under a subdirectory of GoDaddy Share hosting, you need do modification of the BlogEngine.NET codes by yourself.

Fortunately, after Google, I found there was someone already did this for us – Mike, and you can download his/her modified version which named as ModPack from codeproject http://modpack.codeplex.com/

Below is my experience about how to deploy my BlogEngine.NET site to Godaddy share hosting,

1.

Ping Services for BlogEngine.NET

Ping Services

Using the Ping Service, BlogEngine.NET will automatically ping one or more servers each time a new post is created or an old one is updated. An XML-RPC signal is sent to one or more “ping servers”, which can then generate a list of blogs that have new material.

BlogEngine.NET comes with several preset servers to make sure your blog posts gets indexed as soon as they are created/updated.

Adding a new Ping URL
Adding a new server is straight forward, just copy-paste the URL of the Ping service you want to inform and click “add”.

External Links
For a comprehensive and updated list of available Ping Servers:

using fckeditor in BlogEngine.NET

here is what i did to make it work. I provide all steps to have a complete documentation.
“Webroot” is the directory where you installed blogengine.net in. You should change the web.config
in the last step, because you have to restart your application anyway.

  • Download the FCKEditor main package at http://www.fckeditor.net/download.
    • Extract the zip file to your webroot. You now have a folder fckeditor in your webroot.
  • Download the FCKEditor.NET package at http://www.fckeditor.net/download.
    • Extract the zip file to a temporary folder.
    • Copy FredCK.FCKeditorV2.dll from {temporary folder}\bin\Release\2.0\ to the \bin\ directory of your webroot.
  • Create a folder “userfiles” in your webroot. Add write permissions to this folder for the Network Service account (Windows Server 2003).
  • Switch off HTTP compression in the blog settings
  • add_entry.aspx ({webroot}\admin\Pages\):
    • add <%@ Register Assembly="FredCK.FCKeditorV2" Namespace="FredCK.FCKeditorV2" TagPrefix="fck" %>
    • replace with
    • remove upload fields (txtUploadImage, txtUploadFile)
  • add_entry.aspx.cs ({webroot}\admin\Pages\):
    • replace txtContent.Text with txtContent.Value
    • remove all references to the old upload fields (txtUploadImage, txtUploadFile)
    • the function SizeFormat() can also be removed
  • fckconfig.js ({webroot}\fckeditor\):
    • set _FileBrowserLanguage to 'aspx'
    • set _QuickUploadLanguage to 'aspx'
  • config.ascx ({webroot}\fckeditor\editor\filemanager\connectors\aspx\):
    • you have to implement a session check in CheckAuthentication() or just return true (not recommended)
  • Set enableSessionState=”true” in the section in web.config

Can someone give me a hint how to implement the session check in the CheckAuthentication() method?

Google Sitemap and BlogEngine.NET

There seem to be some confusion about the Google Sitemap support of BlogEngine.NET, so I thought I would elaborate on it. First of all, BlogEngine.NET has a build-in sitemap handler so you don’t need to write it yourself.

BlogEngine.NET comes with many build-in handlers such as:

  • microsumary.axd
  • sitemap.axd
  • syndication.axd
  • commentfeed.axd
  • opensearch.axd
  • rsd.axd

…and more not so interesting ones.

All the handlers are accessible by typing http://www.yourblog.com/handler.axd where handler can be any one of them. So, in order to see the generated Google Sitemap just type in http://www.yourblog.com/sitemap.axd in your browser. Here is mine.

Auto discovery

You can tell Google manually about the location of your sitemap file or you can put the URL in the robots.txt file. I recommend putting it in the robots.txt because then Yahoo, MSN, Ask and Google can find it. Yahoo, MSN and Ask also supports the Google Sitemap format.

Just add this line to your robots.txt file:

sitemap: http://www.yourblog.com/sitemap.axd

This line can be the only line in the robots.txt if you don’t want to provide more information to the robots and spiders.

BlogEngine.NET 1.4.5.0 CodeFormatterExtension.cs not found issue Solution

Solution of the Issue:
move file \App_Code\Extensions\CodeFormatter.cs to \App_Code\Extensions and rename the file to CodeFormatterExtension.cs

Repro Steps of the Issue:
1. Install BlogEngine.NET 1.4.5.0
2. Sign in as Administrator Role
3. Go to Extensions – > CodeFormatterExtension
4. Click View Link

Result of the Issue:
The CodeFormatterExtension is listed but you get CodeFormatterExtension.cs file not found error

Note:
Demo Usage of this Extension:
[code:c#]
using System;
namespace ConsoleApplication1
{

Solution of the issue:
1. Sign in as Administrator role
2. Go to Settings -> Basic Settings
3. Make sure the Server time offset is set appropriately

Repro steps of the issue:
1. Access Any RSS related link that points to syndication.axd,
such as subscribe link from top Nav or RSS icon link,

Result:
Get following HTTP 500 Server Error from the server,


Server Error in '/' Application.
Specified argument was out of the range of valid values.
Parameter name: utcDate
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: utcDate

Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:
[ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: utcDate]

Powered by WordPress | Theme: Motion by 85ideas.