Migrating Croogo to CakePHP 1.3
After a month of releasing Croogo 1.2, I have decided to start migrating the project to CakePHP 1.3. I wanted to wait for a good coverage of unit tests before migrating, but the new features introduced by the framework are just too good (and useful) for a project like this.
New repository address
I have moved the repository to http://github.com/croogo/croogo. This is a fork of the repository I had under my personal account. As you may have already noticed, I have recently created another repository localized locale that currently contains locales of three different languages. There will be more sub-repos like this in future, and having all repositories under a single github account made sense to me.
New issue tracker: Lighthouse
Github is great for hosting repositores but I don't like their issue tracker, so I will be using Lighthouse from now on.
Join, help find bugs, submit tickets, or request new features here: http://croogo.lighthouseapp.com
1.2.x series ends here
I have tagged a new release 1.2.1, and is available for download here. New features include caching, optimizing code to make it slightly faster, and a few bug fixes.
When to expect Croogo 1.3?
As soon as the migration is complete, probably by the end of February (or by next week depending how much free time I have). Don't expect any new features since the milestone is focused on migration only.
And oh, if you like my current theme then you have to wait till Croogo 1.3 is available, because theme packaging will be a lot easier then ;)
11 Comments
I love your code in croogo.
may I also suggest that you should also provide croogo running on cakephp 1.2.x because I am not yet into 1.3 totally.
Jojo
Excellent work! :D
I am a beginning CakePHP developer, currently working on a Redmine clone (http://tracker.ogitor.org/) - I actually used the Candycane project @ the Chaw as a starting point, but now they are really totally separate projects.
What is more fitting for a cake baker than a cake powered blog?
Thanks! :)
And then my question:
I see that you are working hard on Croogo 1.3.
Is it possible to upgrade an existing Croogo blog?
Or should I hold off my blogging a bit?
I downloaded an archive of master today, btw. (I can't use git on my shared host).
Thanks!
Jacob 'jacmoe' Moen
Happy blogging with Croogo!
I already started hacking, but I have no luck with it yet.
It is being sanitised.
Trying http://github.com/josegonzalez/bb_geshi, but maybe I should go shopping for a tinymce plugin/extension instead. :)
But you can create a syntax highlighter plugin for Croogo very easily utilizing the hook system. Here is the hint: use HookHelper::afterSetNode() for modifying the 'body' value. See exampe code: http://github.com/croogo/croogo/blob/master/plugins/example/views/helpers/example_hook.php#LC46
I used SyntaxHighlighter and a TinyMce plugin, and documented the process here:
http://www.jacmoe.dk/blog/syntax-highlighting-in-croogo
I am not sure if it's the best way of doing it, but the changes are minimal.
Thanks again for a great piece of software. :)
A programmers blog without code highlighting is not good. ;)
Consider this as a core option as it is fairly common.
Add new comment