Croogo 1.3.1 released!

Submitted by Derick Ng on 14 June 2010 - 1:28am

After 62 commits and closing 26 tickets, here comes Croogo 1.3.1! This version is more of a maintenance release taking care of bugs, improving existing features, and adding test cases. Hopefully a stable version will be available after the next 2 or 3 releases.

Download

Get the latest version from GitHub: http://github.com/croogo/croogo/downloads.

The changes

  • Taxonomy: This is the major change in this release. Previously, a Term could only belong to a particular Vocabulary. Now the relation is HABTM, so they can belong to as many Vocabularies you want.
  • Theming: Menus, Node lists (recent posts), and Vocabularies are rendered via separate elements (like Blocks) for making theming easier for designers. Also a number of extra fallbacks have been added for nodes views. You can read more about it here.
  • Failed login attempts: A limit on the number of failed login attempts has been introduced.
  • XSS Vulnerability: There was a vulnerability in the comments section for using jQuery Tipsy. Updating it fixed the issue.
  • Installer: Install plugin has been modified to accept all cakephp supported database drivers. But it has been tested with MySQL only.
  • Test cases: More test cases added, and more will be added in next release. It is unlikely I will remove the 'Beta' label from this project unless I am happy with the test case coverage.
  • Bug fixes: There were some annoying bugs that were fixed. Thanks to everyone who reported.

There are still many other things to list. See all commits since previous release here: http://github.com/croogo/croogo/compare/v1.3...v1.3.1.

Upgrading existing Croogo websites

Last two releases didn't have any changes in the database, so upgrading was as easy as uploading new files to your server. But this release has a few changes in taxonomy, which led to changes in the database tables. I failed to prepare the migration files using CakeDC's migrations plugin, and I apologize for that. If you are eager to help everyone with that, feel free to fork the repository and add the migration files. You can also contact me and I will provide you with any information you need for preparing them.

If you find bugs, please post them on Lighthouse. You can also join our mailing list on Google Group which is pretty active.