Release Notes 1.8 (Readme)

 

(Below is the unedited readme file provided with Version 1.8.5223.1 & 1.8.5223.2)

Congratulations! You are almost ready to go.

You can create a VDir manually and point it to the ./dasblogce folder, or you can run the CreateDasBlogVdir.vbs script to create the script automatically.

Important Reminder

NOTE: Not everything that is accessible via an URL exists on the file system! Please do not automatically assume we've left a file out of the distribution. For example, deleteitem.ashx does not exist as a file! It is a line in your web.config. Read this file carefully for more details on merging these new features into your web.config.

Merging

If you are upgrading from a previous version, you WILL need to manually merge some new lines into your web.config if you want to maintain your existing web.config. I suggest Beyond Compare from ScooterSoftware for your comparing and merging needs.

Bugs

Report bugs here: http://sourceforge.net/tracker/?group id=127624&atid=709018. Don't email bug reports directly to Scott and Omar.

What to Upload?

If you downloaded the WebFiles distribution, you'll want to upload everything in the "dasblogce" folder and below as that represents the root of your blog. See the specific upgrade instructions for your version later in this document.

The "upgradedasblog" folder contains a command line application that you can run on your content folder if you are upgrading from a previous version of DasBlog. DO NOT upload the contents of the "upgradedasblog" folder, it is a local application.

Running DasBlog on ASP.NET 2.0

If you are running DasBlog on ASP.NET 1.1 you can skip this section. If you are running DasBlog on ASP.NET 2.0 you need to read the supplied web.config carefully as this issue apply to you.

Add cookieless="UseCookies" to the <forms> element of your web.config (Details)

Upgrading from 1.6 or Earlier

DasBlog 1.6 stored data like comments and trackbacks in *.dayextra.xml files. It also had a bug that stored entries in the wrong timezone. To fix these older bugs and improve performance you’ll need to run a one-time upgrade process on your dasblog/content folder. You’ll also have the opportunity to mark all your entries as Public, as the new version of DasBlog respects that setting.

Run the upgradedasblog/DasBlogUpgrader.exe with your content directory as a parameter.

For example:

DasBlogUpgrader.exe c:\dasblog\content

This utility will also give you the opportunity to clean your posts of old referral spam. You can edit the DasBlogUpgrader.exe.config to include other naughty words that you want removed from your files. Your posts will not be changed, only referrals, pingbacks and trackbacks.

Next, proceed to the instructions to upgrade from 1.7 below

Upgrading from 1.7

In the interest of simplification, some DLLs aren't needed from your existing installation. You can delete your bin folder and redeploy completely, but if you just copied DasBlog 1.8 files over your existing files, note that newtelligence.DasBlog.Util.Html.dll and newtelligence.Web.UI.WebControls.dll are no longer needed and may be safely deleted.

NOTE: DasBlog 1.8 includes a few new configuration changes. After upgrading, be sure to visit your Admin’s Edit Configuration page and peruse all the new settings and confirm the existing ones.

If you have an existing web.config, be sure to merge it with the web.config in this archive. Significant changes to the web.config in 1.8 are as follows.

We suggest that you do a line by line merge comparing your web.config with the new one using a diff tool like BeyondCompare or KDiff. Alternatively, you can use our default web.config if you’ve made no changes to yours.

NOTE: The goal of these changes mean to simplify DasBlog and remove lines you have to care about from the web.config.

  • The newtelligence.Web.UI.WebControls assembly is REMOVED, with all its classes moved to newtelligence.DasBlog.Web.Core.
    • The newtelligence.ControlImages configSection has moved to a different assembly:       
      <section name="newtelligence.ControlImages" type="newtelligence.DasBlog.Web.Core.WebControls.ControlImageModuleSectionHandler, newtelligence.DasBlog.Web.Core" />
    • The <newtelligence.ControlImages> type has moved:
      <add type="newtelligence.DasBlog.Web.Core.WebControls.ShadowBox" name="shadowbox" />
  • The newtelligence.DasBlog.Themes isn’t required at all anymore (see Themes below) and you can remove the <configSections> element and the whole < newtelligence.DasBlog.Themes > section lower down in the file. Make sure the file is still well-formed XML.
  • These files don't exist in your file system. They are not real files. They are HTTP Handlers/Endpoints. You need to add a few new elements in the <httpHandlers> section to get these new features, including
    <add verb="*" path="cptrk.ashx" type="newtelligence.DasBlog.Web.Services.CrosspostReferrerHandler, newtelligence.DasBlog.Web.Services" />
    <add verb="*" path="deleteItem.ashx" type="newtelligence.DasBlog.Web.Services.DeleteItemHandler, newtelligence.DasBlog.Web.Services" />
  • The <forms> section has changed a little. We have changed the cookie name, although this is optional.
    <forms name=".DASBLOGAUTH" protection="All" timeout="60" path="/"/>
    IMPORTANT: If you are running multiple instances of DasBlog on the same machine/domain, set the path=”” attribute to the value of the virtual directory. For example, if you’re running http://www.foo.com/myblog1 then make path=”/myblog1

Upgrading from a 1.8 Release Candidate

Make sure you upload everything fresh to avoid compatibility troubles. Upload all the DLLs, ASPX and ASCX files as some have changed since the RCs.

Themes

One of our goals is to make it easier to share Themes for use within DasBlog. However, earlier versions would require you to copy/unzip the theme into the themes folder AND include a bunch of information about the themes paths and assets within the web.config. Users and Theme Authors alike found this tedious. So, DasBlog 1.8 introduces the concept of “Theme Manifests” to promote xcopy installation and distribution of new themes.

Each theme directory needs a theme.manifest file that describes the name, title, and relative directory of that them, including any optional “named assets.” For example, this manifest includes custom images for the itemLink and dayLink.

Note, however that 99% of themes DO NOT use named assets, so chances our yours doesn’t either. So, the first time your theme loads, if there isn’t a theme.manifest we will generate one for you. If your theme looks funky or changes between 1.7 and 1.8, perhaps you need to include your named assets in the theme.manifest file that were previously expressed in your web.config.

<?xml version="1.0" encoding="utf-8" ?>

<theme name="discreetBlogBlue" title="Discreet Blog Blue" templateDirectory="themes/discreetBlogBlue"

            imageDirectory="themes/discreetBlogBlue">

    <image name="itemLink" fileName="images\bryanbell\discreetBlogBlue\bluePermaLink.gif" />

    <image name="dayLink" fileName="images\bryanbell\discreetBlogBlue\bluePermaLink.gif" />

</theme>

 

Again 99% of users won’t need to do a thing to get themes working in 1.8; they will just work.

Tip: Check your themes templates if you think something odd is happening. There may be hardcoded text in the HTML for disclaimers or links.

FreeTextBox

DasBlog uses an external component called FreeTextBox (http://www.freetextbox.com) for Rich Text editing support. We’ve shipped with versions 3.0.5000.1 and up, and this version ships with version 3.0.5000.6.

WARNING: DasBlog RC1 shipped with FTB 3.0.5000.5. This release updates FTB to .6, so make sure your web.config is updated to match the example below and that you update your FreeTextBox.dll.

NOTE: Make sure you upload the whole /FTB folder from this release.

However, folks want to upgrade FreeTextBox independently of DasBlog. So, we’ve included this new section in the web.config to enable you in the future.

<runtime>

 <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

  <dependentAssembly>

   <assemblyIdentity name="FreeTextBox" publicKeyToken="5962a4e684a48b87" culture="neutral"/>

   <bindingRedirect oldVersion="3.0.5000.0-3.0.5000.5" newVersion="3.0.5000.6"/>

  </dependentAssembly>

 </assemblyBinding>

</runtime>

If a new version of FTB came out, this section lets you tell ASP.NET “I know you asked for one of these versions, I’d rather you use THIS version. This evaluation happens at runtime when ASP.NET starts up. Hypothetically, if you wanted to use some new version 3.0.5000.9, for example, you could change oldVersion=”3.0.5000.0-3.0.5000.8” and newVersion=”3.0.5000.9” and you would be all set.

We are working on providing other alternative Rich Text Editing components in the future. This version include support for FireFox and IE. However, if you’re really not happy with this component, you might consider composing your posts offline with BlogJet (http://www.blogjet.com)

IMPORTANT: Permissions

Still … there are still a few little steps missing to get it all running:

·    On IIS 5.0 (Windows 2000), the account used to execute web applications (IWAM xxx) needs read/write permissions to the content, siteconfig, and logs subdirectories.

·    The ASP.NET worker process identity, usually “{machinename}\ASPNET” on IIS5.0 (Windows 2000 and Windows XP) or “NETWORK SERVICE” on IIS 6.0 (Windows Server 2003) also need read/write access to the content, siteconfig, and logs subdirectories.

·    Go to the siteConfig directory in (likely in c:\inetpub\wwwroot\{sitename}) and open the site.config file. In that file, change the settings (quite obvious when you look at them). The most important change is to set the <Root> value to the proper URL for your weblog.

·    Open the siteSecurity.config in the same directory and set up your own account with a proper password.

Breaking Changes

  • The stylesheet() macro previously (and mistakenly) assumed your CSS stylesheet would be in the theme’s images folder. Now it generates URLs to your CSS that do NOT include the images folder. Be sure to View Source on your HTML to ensure you are getting the output you expect if you are using this macro.
  • Your blog themes are cached in memory for performance reasons. If you edit an existing theme template DasBlog will recognize the change and invalidate the catch. However, if you ADD new files to an existing theme, like category specific templates, you will need to restart your application. This can be done by “touching” (adding a space to) the web.config if you don’t have administrative access to your web server.

 

 

 
Readme | Release 1.8