comment-snipsnap-help-91 snipsnap-help

There are perhaps multiple issues here:

1. If you are using open source software and even writing your own macros, you should perhaps try to debug the software yourself. I tried to understand the cause of your problem but did not succeed. The SnipSnap community is probably too small that anyone besides leo and funzel might help with a problem like yours. And they seem to be very busy these days.
2. I would not dare to use the file system as a storage for important data if I have the possibility to use a database. Sure, being able to use the file system is nice to get started with SnipSnap but there are many problems assocated with file storage and SnipSnaps implementation has some additional ones (I admit that these first two remarks sound harsh).
3. For personal blogging there are more advanced and better supported solutions than SnipSnap. I think SnipSnap is useful if you happen to be a Java programmer and want to be able to patch the system yourself (The nice look might be another reason).
4. Progress is slow. SnipSnap is not your usual kind of open source project. It is a hybrid, since the developers AFAIK are not (mainly) working on SnipSnap in their spare time, but as part of their job and so need funding to be able to proceed. And - again AFAIK - they are not really looking for volunteers contributing to SnipSnap (there might even be difficult copyright issues with contributed code).

So we must either wait for leo and funzel to be able to spend more time on SnipSnap. Or generate some funding to support them. Or be content with SnipSnap as it is. Or create our own branch of SnipSnap. Or move on to another Weblog/Wiki.

I am currently willing to stay with SnipSnap since it works stable for me (the only problem disturbing me is Tomcat's unwillingness to shutdown properly with SnipSnap).