I'm pleased to announce that Pebble 2.0.0-RC1 is available to download. Notwithstanding any major bugs, this is functionally the same as the final 2.0.0 release. The highlights in this release are the addition of a rich text editor and the pluggable TrackBack confirmation strategies.

I could have waited a little longer to get this out, but I wanted to get feedback earlier rather than later. Also, it gives me some more time to finish off the outstanding documentation. The changelog for this release is as follows.

• Fixed "page not found" error when uploading files to theme.
• Fixed problem with last modified date on response feeds.
• Added category list into the sidebar of the default theme.
• Added an "archive by month" list into the sidebar of the default theme (commented out).
• Integrated FCKeditor (rich text editor) for blog entries, static pages and comments.
• Added net.sourceforge.pebble.event.response.MarkApprovedListener for automatic approval of responses.
• Fixed problem where changing timezone causes Pebble to crash (all blog entries now stored in a yyyy/mm/dd hierarchy based on GMT).
• Added auto-upgrade utility - this restructures blog data into GMT and reset the theme and plugins back to their default values.
• Added secureUrl to applicationContext-pebble.xml for secure login.
• Added reference to pebbleSecurityRealm (via securityRealm property of pebbleConfiguration bean) to applicationContext-pebble.xml file.
• Upgraded Acegi to 1.0.1 and the changed authenticationProcessingFilter bean to be an instance of net.sourceforge.pebble.security.AuthenticationProcessingFilter.
• Changed the package name for Comment Confirmation Strategy implementations to net.sourceforge.pebble.confirmation.
• TrackBack links now need to be generated, are single use and expire after 10 minutes.
• Enhanced the confirmation strategy concept to be applicable to TrackBack link generation.
• Added a TrackBackAutoDiscoveryDecorator to support publication of TrackBack links for auto-discovery by supported clients.

For most users, there are no specific upgrade intsructions if you are upgrading from a previous 2.0.0 milestone. However, you should be aware that Pebble will perform the following activities the first time you start it up following an upgrade. You should backup your Pebble data directory before upgrading.

• Restructure the directory hierarchy in which blog entries are stored to be GMT based.
• Set your theme back to "default".
• Reset the following plugins back to their default configuration.
  • Permalink Provider
  • Content Decorators
  • Blog Listeners
  • Blog Entry Listeners
  • Comment Listeners
  • Comment Confirmation Strategy
  • TrackBack Listeners
  • TrackBack Confirmation Strategy
  • Lucene Analyzer
  • Logger

Once you are happy that Pebble is working as expected, you should set your theme back to the one you were using prior to the upgrade (via the blog properties page) and customize the plugins as required (via the plugins page). As always, support is available via the pebble-user mailing list. Enjoy!

Responses[6]

Posted by Simon Brown on 18 July 2006 21:46:00 BST #