Known Issues

 
  • Known documented bugs are listed at SourceForge
  • Current features requests are documented at another location at SourceForge

As to a roadmap or where the development team is going next, that is yet to be determined and documented. When it is we expect it to be documented first at SourceForge and here!

Release 1.9.6264.0

  • If operating under ASP.NET 2.0 the edit configuration page used by the administrator has some errors, they can be worked around, resolved in later releases.
  • The theme selection combo box does not work with the FireFox browsers 1.5 or 2.0.

RARE EDGE CASES

INSTALL ISSUE: System does not operate! (Read-Only files)

A rare but frustrating problem is sometimes manifested. Upon a good install, no comments can be added to the default post, and the configuration file does not update etc. There are various system file update failures. These are just some of the examples.

This problem is cased by a rare case of dasblog xml or configuration files being marked as Read-Only! Only the files in SiteConfig and contents directories are affected on a new install. 

The developer release files themselves are not set to Read-Only, it appears that this is a Microsoft file protection issue.

When the dasblog release package is downloaded from SourceForge, the users Microsoft OS (XP etc.) marks the files as either Blocked or potentially blocked. i.e. they have attributes like this:

"This file came from another computer and might be blocked
to help protect this computer"

If you FTP these files in this state to a host, in some cases they are then marked as Read-Only on the site.

Again this is a problem, but not a developer release file problem!

You can fix the problem after the fact on your host, or fix the files locally and reload them to your host!
/INSTALL ISSUE:

404 ON LINKS:

While 404 error issues usually mean you have a permission problem of some type, there is a rare version of this permission issue. If you turn the IIS feature "Cache ISAPI extensions" on, the default for the extension ashx is "Confirm file exists".   

(Turn off "confirm file exists" for all files if you are going to use Cache ISAPI extensions)

Dasblog does not have real ashx files, but the system will try to confirm them and throw these permission type errors. The dasblog version 1.8 readme documents that ashx files do not exist, but it does not point out this gotcha!!! This issue was discovered and documented at http://dasblog.us.

By the way turning your "Cache ISAPI extensions" settings on is a good idea per Microsoft! (It is not the default)

/404 ON LINKS:

 
Known Issues