ou know the deal. This is rb.log 1.1.2.
This is a development release. If you have comments, suggestions, questions, etc., please contact me.

rb.log 1.0 is the official stable release.

Having said that, 1.1 is the code base for NO SIGNAL and should work just fine. See Long Term Plans for more info on what's in the 1.1 branch and where it's going. If you are currently running 1.0 or previous, you'll need to manually modify your SQL schema (see below and sql/rblog.sql) for more info. 1.2 will include a migration tool.

I honestly forget what all has been added since 1.1.1. Howeve, there have been a number of fixes and improvements. A rudimentary (though not entirely satisfactory) page caching mechanism has been incorporated. Authors can be authorized to include mod_ruby code in their posts (allowing web log posts to include dynamic content). I think the TrackBack support is new.

Let this be a lesson. Release more often.

This is rb.log 1.0.2. It's got some upgrades to the SecurityManager class to coexist with 1.1.2.

This is rb.log 1.0.1. It adds some version safing features to allow it to peacefully coexist on the same host as newer versions of rb.log. But you really want to use something from the 1.1 branch.

You know the deal. This is rb.log 1.1.1.
This is a development release. If you have comments, suggestions, questions, etc., please contact me.

rb.log 1.0 is the official stable release.

Having said that, 1.1 is the code base for NO SIGNAL and should work just fine. See Long Term Plans for more info on what's in the 1.1 branch and where it's going. If you are currently running 1.0 or previous, you'll need to manually modify your SQL schema (see below and sql/rblog.sql) for more info. 1.2 will include a migration tool.

New stuff since 1.1:

• Themes!! This dude takes themes/skins/call it what you will now. It ships with three: plain, nosignal, and printer (which is used by the 'P' link in the post title). For more info on making nosignal work, check the README in the themes/nosignal directory.
  
• Version safing. Each library registers itself with a version and they are requested by version. This allows us to have multiple conflicting versions of rb.log installed on the same host. If it detects that the wrong version of the library is currently loaded, it'll load the proper one.
  
• Down with globals! Apart from a global namespace (which is solved above), all global variables have been replaced with thread storage.
  
• Calendars. See the nosignal theme for an example.
  
• RSS aggregation. See the nosignal theme for an example.
  
• Post formatting selection has been changed. Interpretting the post as plain text is now an option as well.
  
• Posts dated in the future will not be shown. So you can make your post, set the date to the future, and it will reveal itself at the appointed time.
  
• The ability to have multiple databases in the config file and to hit one or the other based on a HTTP supplied parameter... Would be useful for guest blogs, multiple projects in one site, etc. See NO SIGNAL for an example of this. The code is also in the nosignal theme (in the RSS aggregation).
  
• If-Modified-Since and Last-Modified support. (configurable, off by default).
  

Check out rb.log 1.1. This is a development release. If you have comments, suggestions, questions, etc., please contact me.

rb.log 1.0 is the official stable release.

Having said that, 1.1 is the code base for NO SIGNAL and should work just fine. See Long Term Plans for more info on what's in the 1.1 branch and where it's going. If you are currently running 1.0 or previous, you'll need to manually modify your SQL schema (see below and sql/rblog.sql) for more info. 1.2 will include a migration tool.

This release has:

• E-mail subscription
• The ability to mark a post visible or invisible.
• Move all the index building, pinging, etc. into Rblog.
• Rearchitect things like searches. Every search will be of the form s=mode/query. So a search by year, month, day will be s=ymd/2003.3.15 or so. This will make it easier to do things like build URLs that will preserve the current state of open dropdown menus while replacing all the searches with e.g. a calendar date.
• Pages should be called as subroutines. parameters could be stored in thread variables.
• Comments could be emailed to the Post's Author. Set on a per-Author basis.
• Moved from rss-xml.rhtml to rss-xml.rbx in order to support setting Content-Type to text/xml. A little .htaccess magic like Redirect /blog/rss-xml.rhtml http://www.foo.org/blog/rss-xml.rbx should do the trick.
• Change the security management to be like SecrurityManager#require(perm) block
• Pinnable posts
• Form field names no longer called foo.bar but foo_bar. The first '_' always separates the instance name from the method. So post_no_autobr translates to post.no_autobr. This is used in Rblog#reconstitute.
• Post post-dating

Table alterations:

• Drop Configuration.pong.
• Add Configuration.email_notify.
• Add Post.hidden.
• Add Post.email_notify.
• Add Post.pinned.
• Add Blogroll.ctime.
• Add Subscriber.

If you downloaded 1.0 before just now (Mar 15, 9:39am EST), you should do it again. One fix didn't make it's way in. My bad.