Quills 1.6 (Beta release) (Sep 24, 2007)

Quills

This is not a final release. Experimental releases should only be used for testing and development. Do not use these on production sites, and make sure you have proper backups before installing.

A Plone 3.0 compatibility release

For additional information about this project, please visit the overview page .

Available downloads

Release Notes

Tested with Plone 3
StateBeta release
LicenseGPL
Release Manager Tom Lazar
Quills has undergone some substantial changes ever since its last stable release (0.9), many geared towards adapting Zope3 and Plone 3.0 techniques. This release aims at tying all of that together. The 1.6 branch will also be the last version of Quills that uses its own Archetype based content types (Weblog and WeblogEntry). The development after 1.6 will concentrate on providing blogging features in a more generic way, much like Plone4Artists provides multimedia features without introducing custom content types.

Details on that approach can be found in the README from QuillsEnabled.

Take Quills 1.6 for a spin!

If you're looking for a 'full grown', future-proof blogging solution for Plone 3.0 give this release a spin! The easiest way to do that is to checkout the buildout we provided. Here's a one-liner that should work on *NIX systems:

svn co https://svn.plone.org/svn/collective/Quills/bundles/quills-buildout/tags/1.6-beta1 quills ; cd quills ; python bootstrap.py ; ./bin/buildout ; ./bin/instance fg

If you don't have subversion installed, you can also just download and expand the tarball provided above, change into the new directory, bootstrap it and fire up the instance:

tar xzf quills-1.6-beta1.tgz ; cd quills-1.6-beta1 ; python bootstrap.py ; ./bin/buildout ; ./bin/instance fg

Then go to http://localhost:8080/manage (log in as admin with password admin) and add a Plone Site selecting the quills.app profile.

Then visit that site and install the Quills Product via the add-ons controlpanel. You can now add blog instances and blog away!

Give feedback

This beta release still has known issues and there are certainly still many kinks that need to be ironed out. You can help us greatly in creating a polished release that lives up to Plone's own standards by creating issues in Quills issue tracker. Thanks!

Feature enhancements in this release

The following features are associated with this release:

Plone-ification
Quills should work with Plone, not against it.
Automated pings to Technorati, Pingomatic, etc
It is common to send 'pings' to various services such as technorati.com and pingomatic.com upon updating a blog. The ping informs the remote service that changes have been made so that they may reindex the blog.
Quills should not move posts into archive folders
Merge with, rather than overriding, Plone's default portlets

Change log

Traversal based archives The biggest change is that we have moved away from the archive folder hierarchy. Instead, posts are stored in a flat (BTree)folder, with traversal adapters used to "fake" the archive hierarchy.

MetaWeblog API support (again): This release has been tested with ecto and MarsEdit. YMMV

Workflowed Multi-User support. The old archive method involved moving entries upon publication, which caused major pain for users that didn't have the Manager or Owner role. Now Quills honours the new Contributor and Reviewer roles, i.e. by assigning any combination of these two roles (also locally) Managers can let people create and/or publish blog entries without granting them any further privileges.

New style Portlets. (Almost) all portlets have been migrated to the new Portlet style and can thus be managed like all others.

Missing features

Two major features haven't made it into this release: trackbacks and migration.

Do not install this release onto an existing instance. It will not work (and possible break stuff!)

Migration is planned for the final release, obviously but still needs work. Trackbacks won't be implemented until we have a compelling commenting story for Plone. This may or may not arrive in time for 1.6 final. Note: we will be working on this issue at the upcoming conference.