It's been a long time, but today I'm happy to announce the release of pecio 2.0.5 which comes with some nice new features and improvements:

• hierarchial menupoint order in the administration
• file/directory-permission check before and after the installation
• filemanager accessible outside of the editor
• new default height for the editor
• updated to the latest CKEditor (version 3.3.1)
• email notification option for new comments on blog posts
• "disable comments"-option for single posts
• "blog on start"-option is now also accessible via the blogposts area
• template chooser for articles is back again :)
• little bug fix in slug generation
• further code documentation
• perhaps some more little things I don't remember

I'm sorry that you had to wait so long for this release but there are a lot of other projects I'm working on, that's sometimes a bit difficult to coordinate ;) However I hope you feel comfortable with all those new features and improvements!

There are also two new Plugins that you can download:

• PHP Code - for inclusion of php code into articles/posts/texts
  • please note that it's a bit tricky to use this inside the CKEditor. But if you're turning into the "Source" mode of the editor, everything should be fine
• Pecio URLs - can be used to insert urls of articles/posts/categories/etc. into your content

The administration area of the contact form plugin has a little issue with the stylesheet at the moment, but I think I'll fix that soon.

Please also note that, if you are updating from a previous version of pecio, this version will make changes to pecio's database table layout, so do not forget to backup your database and your pecio installation! To make the update you just have to follow the update guide.

I hope that I can set up a wiki with some tutorials for template and plugin development etc. very soon. Some more templates are also planned.

For some weeks now, pecio's source code is available on github: http://github.com/iperatoner/peciocms

Github offers, as most of the project platforms out there, the possibility to add issues (bugs, feature requests, etc.) to a project. Today I added the things that were on my todo list. If you have any further ideas for features/improvements or if you found bugs, just create an account on github.com and add your issues.

There's also the possibility to vote on issues. So, if you like a feature request or if you are affected to a bug, you can vote on that issue and I can see which things are most important for the users.

In the last few weeks I had to work a lot with Wordpress because I'm administrating a website using it.

While fiddling around with templates, plugins and Wordpress itself, I've discovered many great features in Wordpress. And some days I'm asking myself: "Why are people using pecio cms when there are other ones with -  for some part - a lot more features and better usability?".

So today I want to ask you, why you like pecio cms or why you dislike it (also compared to other ones).

I hope I can find some tips in what direction to go with the CMS.