DasBlog

Themes (From Version 1.9 forward) 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 ... [More] about the themes paths and assets within the web.config. Users and Theme Authors alike found this tedious. So, DasBlog 1.8 introduced 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. <?xml version="1.0" encoding="utf-8" ?> <theme name="dasblueblog" title="dasblueblog" templateDirectory="themes/dasblueblog" imageDirectory="themes/dasblueblog">     <image name="dayLink" fileName="dayLink.gif" /> </theme>   How do themes’ and templates work? Here’s a quick overview on how themes and templates work in dasBlog: Whenever dasBlog renders an HTML page, it does so using templates from one of the configured themes, which are installed for the current dasBlog site. A theme is a set of templates and bitmaps that define the appearance of the pages in your blog. Themes & Templates Basics In any dasBlog website you will find, by default, a “themes” subdirectory that contains several subdirectories, named “candidBlue”, discreetBlogBlue”, “justHtml” and so on. In each directory you will find at least three files: · homeTemplate.blogtemplate · dayTemplate.blogtemplate · itemTemplate.blogtemplate If you look at these files in a text editor, you will find that all of them contain HTML fragments with a couple of strange tags which are enclosed in “<%” and “%>” marks. These are macros and we’ll get to them in a moment. The homeTemplate.blogtemplate file contains the main template for all HTML pages rendered by the engine when using the theme. It contains a complete HTML page instrumented with macros that automatically render elements such as the title, the footer area, the calendar and all the other elements that are common for every page. The dayTemplate.blogtemplate file contains the template for each “day”  that is rendered for the front page, the category pages and for the pages, you get to when you select a date from the calendar. The dayTemplate is rendered for each day for which blog entries are found. The populated fragments that result from processing the macros for a single day are rendered, directly following each other, as the replacement text for the <%bodytext%> macro of the homeTemplate. The itemTemplate.blogtemplate file contains the blog template for every blog-entry rendered onto a page. All items for a particular day are rendered as a sequence of processed itemTemplates inside the <%items%> macro in the dayTemplate. The macros, behave differently depending on the page and on whether you are logged in as administrator or are just a visitor. For all of the administration pages, the <%bodytext%> macro in the homeTemplate will not resolve into a list of items, but rather into the body of the administration page you want to work with. The same applies to the comment page, for instance. In each theme directory you can create subdirectories that correspond to the names of the categories on your blog. If you have a category “My Dog” and create a subdirectory called “My Dog”, you can store a different set of templates there. This set will be used for the category page. It’s important to note that the theme names be unique within the themes directorry, otherwise dasBlog will simply fail to start up properly. The templateDirectory attribute in the manifest contains a relative path from your site’s main directory to the directory where the *.blogtemplate files for a theme can be found. The imageDirectory attribute points to the directory where the images for that theme can be found. The Radio Userland compatible macro <%radio.macros.imageUrl(‘filename’)%> will properly resolve references to images inside your template to this location and the <%radio.macros.imageRef(‘filename’)%> macro will insert a complete <img> tag. The arguments to these macros are paths to filenames that are relative to the imageDirectory of a theme. So, if you use <%radio.macros.imageUrl(‘myphoto.jpg’)%> the macro will return an absolute URL to the file ‘myphoto.jpg’ in the current theme’s imageDirectory. If you don’t like one or multiple of these themes, it’s safe to remove them, but you must have at least one theme and that theme must be defined as the default theme in the siteConfig/site.config file; so, for instance, like this: <Theme>default</Theme> Adding themes: If you want to add a theme, create a new directory in the themes directory with an appropriate manifest file and new supporting files. A bit special are the <image> entries that you can find illustrated embedded in the entry for the “default” theme in the example above. DasBlog uses a set of standard images for rendering some of its elements, such as the “permalink” image (itemLink.gif) , the calendar day image () or the images for the administrator mode such as the edit ( editbutton.gif) or delete ( deletebutton.gif) images. All of these images can be replaced by a theme in two ways. The first, and simplest method, is to place a file with the same name as one of the standard files into your theme directory. In this case, the files must also be using the GIF format just as the default images. If you want to replace the files with files having a different name or file format, you can create an <image> entry as shown above. The <image> entry’s name must be the name of the image that should be overridden (without the file extension) and the fileName must be a file name relative to the theme’s imageDirectory. You can select the current theme for your site simply on the configuration page or by modifying the <Theme> entry in the siteConfig/site.config directory. Modifying or Creating Themes: Modifying or creating new themes is quite easy if you know your HTML. All you need is an HTML editor that, preferably, knows a bit about style sheets, the "macro reference" below and with a bit of looking around in the existing themes. One thing you will find is that dasBlog renders a couple of quite complex elements by itself that cannot be found in those templates. However, the appearance of all of these elements can be tightly controlled using cascading style sheets (CSS), because we defined CSS classes for almost all elements dasBlog renders. So if you want to tweak the look of the calendar or the blogroll, you can do so using style sheets in your homeTemplate. The CSS class names are documented alongside the macros that render the elements in the macro reference. The above is pretty much all you need to know about themes in dasBlog. [Less]

If you want to run dasBlog on Windows 2003 64bit IIS6, download the 32bit version and make the following changes. You will need to replace the 32bit "BasicFrame.WebControls.BasicDatePicker.dll" with the 64bit version available in the source ... [More] directory "lib". The file is "BasicFrame.WebControls.BasicDatePicker.dll.64bit", rename it and replace the file"BasicFrame.WebControls.BasicDatePicker.dll" in your "bin" directory. Restart IIS and problem solved. Note: I understand that the compiled version of dasBlog 2.0 is supposed to be CPU agnostic, except for the date picker, which was provided to Microsoft as a freebee created bit specific (a 32bit version and a 64bit version is included in the source, the default setup is for the 32bit .dll). I understand that dasBlog on Vista IIS7 is a little more involved you may want to read Scott Hanselmans blog on the subject. http://www.hanselman.com/blog/32bitnessAnd64bitnessAndMigratingDasBlogOnIIS7AndASPNETUnderVista64.aspx [Less]

If you want to run dasBlog on Windows 2003 64bit IIS6, download the 32bit version and make the following changes. You will need to replace the 32bit "BasicFrame.WebControls.BasicDatePicker.dll" with the 64bit version available in the source ... [More] directory "lib". The file is "BasicFrame.WebControls.BasicDatePicker.dll.64bit", rename it and replace the file"BasicFrame.WebControls.BasicDatePicker.dll" in your "bin" directory. Restart IIS and problem solved. Note: I understand that the compiled version of dasBlog 2.0 is supposed to be CPU agnostic, except for the date picker, which was provided to Microsoft as a freebee created bit specific (a 32bit version and a 64bit version is included in the source, the default setup is for the 32bit .dll). I understand that dasBlog on Vista IIS7 is a little more involved you may want to read Scott Hanselmans blog on the subject. http://www.hanselman.com/blog/32bitnessAnd64bitnessAndMigratingDasBlogOnIIS7AndASPNETUnderVista64.aspx This weblog is sponsored by DasBlog. [Less]

Version 2.0 of dasBlog is released, and dasBlog goes ASP.NET 2.0 (with medium trust). After a long period as a .NET 1.1 application with .NET 2.0 compatibility, dasBlog has finally migrated completely to ASP.NET 2.0. This means that we can ... [More] take adavantage of the 2.0 platform and provide newer features! Tony Bunce has a fine write-up on the issues we ran into with dasBlog on Medium Trust. Here's some highlights: "The goal of medium trust is for hosting providers to provide functional ASP.NET 2.0 hosting while also protecting against rogue or malicious applications. Unfortunately that protection comes at the cost of application flexibility. ...There are a few features that are limited in a medium trust environment: SMTP on alternative ports and Mail to Weblog via POP3...dasBlog will let you know that you don't have these privileges by displaying warnings on the configuration page. There is some good news though, these limitations won't affect most users.  Many hosting providers that run limited trust environments don't run in the default medium trust, but rather a "modified full trust".  In that case you may already have all the permissions you need for all of the features to work." What is dasBlog? dasBlog is an ASP.NET blogging application. It runs on ASP.NET 2.0, (all versions 1.9x and prior run on ASP.NET 1.1 & ASP.NET 2.0) and is developed in C#. dasBlog is an evolution of the BlogX weblog engine initially written by Chris Anderson and contributors. The initial conversion from Blogx was created by Clemens Vasters. dasBlog adds lots of additional features like Trackback, Pingback, Mail notifications, and over 50 other major modifications some unique only to dasBlog. dasBlog does not require a database, so it is easier to get setup and cheaper to host. All that dasBlog requires is that you grant write access to a folder so that dasBlog can save your information. dasBlog is under active development and is always seeking more contributors! If you feel that you can contribute to the project, we'd love to hear from you. This weblog is sponsored by DasBlog. [Less]

Version 2.0 of dasBlog is released, and dasBlog goes ASP.NET 2.0 (with medium trust). After a long period as a .NET 1.1 application with .NET 2.0 compatibility, dasBlog has finally migrated completely to ASP.NET 2.0. This means that we can ... [More] take adavantage of the 2.0 platform and provide newer features! Tony Bunce has a fine write-up on the issues we ran into with dasBlog on Medium Trust. Here's some highlights: "The goal of medium trust is for hosting providers to provide functional ASP.NET 2.0 hosting while also protecting against rogue or malicious applications. Unfortunately that protection comes at the cost of application flexibility. ...There are a few features that are limited in a medium trust environment: SMTP on alternative ports and Mail to Weblog via POP3...dasBlog will let you know that you don't have these privileges by displaying warnings on the configuration page. There is some good news though, these limitations won't affect most users.  Many hosting providers that run limited trust environments don't run in the default medium trust, but rather a "modified full trust".  In that case you may already have all the permissions you need for all of the features to work." What is dasBlog? dasBlog is an ASP.NET blogging application. It runs on ASP.NET 2.0, (all versions 1.9x and prior run on ASP.NET 1.1 & ASP.NET 2.0) and is developed in C#. dasBlog is an evolution of the BlogX weblog engine initially written by Chris Anderson and contributors. The initial conversion from Blogx was created by Clemens Vasters. dasBlog adds lots of additional features like Trackback, Pingback, Mail notifications, and over 50 other major modifications some unique only to dasBlog. dasBlog does not require a database, so it is easier to get setup and cheaper to host. All that dasBlog requires is that you grant write access to a folder so that dasBlog can save your information. dasBlog is under active development and is always seeking more contributors! If you feel that you can contribute to the project, we'd love to hear from you. [Less]

/dasblogce 2.0/dasBlog 2.0.7226.0/dasBlog-2.0.7226.0-Source.zip

/dasblogce 2.0/dasBlog 2.0.7226.0/dasBlog-2.0.7226.0-Source.zip

/dasblogce 2.0/dasBlog 2.0.7226.0/dasBlog-2.0.7226.0-Web-Files.zip

/dasblogce 2.0/dasBlog 2.0.7226.0/dasBlog-2.0.7226.0-Web-Files.zip

Released at Wed, 15 Aug 2007 04:29:12 GMT by shahineoIncludes files: dasBlog-2.0.7226.0-Web-Files.zip (2769842 bytes, 0 downloads to date), dasBlog-2.0.7226.0-Source.zip (4585530 bytes, 0 downloads to date)[Download] [Release Notes]