Hot out of the oven CakePHP 1.3 alpha
This article is also available in the following languages:
The CakePHP development team is happy to announce the release the alpha build of CakePHP 1.3.
The CakePHP development team is happy to announce the release the alpha build of CakePHP 1.3. We've been hard at work improving upon the already great 1.2 and implementing new features to ease development and increase the flexibility of CakePHP. There have been a number of changes to existing features and its recommended that you review the migration guide[1] for changes in existing classes and features. Also checkout the new features guides[2] for the new features introduced in 1.3. As the 1.3 code branch stabilizes, methods that are currently deprecated and generating errors will be removed. It is therefore important to update the necessary methods to their new names.
If you would like to help with the ongoing development of 1.3, you can do so in a number of ways. Firstly filing clear and concise tickets for any issues with new or existing code helps get the issues resolved. You can also contribute by forking the CakePHP project on code.cakephp.org and implementing features and test cases in your forks. This speeds up development as cherry picking commits is faster and easier than applying patches.
The future roadmap places CakePHP 1.3, as a stepping stone towards the also in development CakePHP 2.0 branch which will feature a mostly backwards compatible API. The CakePHP 2.0 branch can be found at http://code.cakephp.org/cakephp2
Finally, we'd like to thank the community for their ongoing support and contributions in making CakePHP as great as it is.
Download a packaged release, [3]
Read the changelog [4]
[1] http://code.cakephp.org/wiki/1.3/migration-guide
[2] http://code.cakephp.org/wiki/1.3/new-features
[3] http://cakeforge.org/frs/?group_id=23&release_id=452
[4] http://code.cakephp.org/wiki/changelog/1_3_0-alpha
If you would like to help with the ongoing development of 1.3, you can do so in a number of ways. Firstly filing clear and concise tickets for any issues with new or existing code helps get the issues resolved. You can also contribute by forking the CakePHP project on code.cakephp.org and implementing features and test cases in your forks. This speeds up development as cherry picking commits is faster and easier than applying patches.
The future roadmap places CakePHP 1.3, as a stepping stone towards the also in development CakePHP 2.0 branch which will feature a mostly backwards compatible API. The CakePHP 2.0 branch can be found at http://code.cakephp.org/cakephp2
Finally, we'd like to thank the community for their ongoing support and contributions in making CakePHP as great as it is.
Download a packaged release, [3]
Read the changelog [4]
[1] http://code.cakephp.org/wiki/1.3/migration-guide
[2] http://code.cakephp.org/wiki/1.3/new-features
[3] http://cakeforge.org/frs/?group_id=23&release_id=452
[4] http://code.cakephp.org/wiki/changelog/1_3_0-alpha
I want to request a feature which I have found very useful and very much needed. I dont know where else can I post about this.
I want to be able to output multiple times during an ajax request to show accurate progress on the server side. This is a very useful feature for admin interfaces to many many types of applications, as admins usually needs to perform operations that could take a while... like almost a minute.
I appreciate all the hard work guys!!
It took me a couple minutes to find it, but it on the right side bar - direct link http://cakephp.lighthouseapp.com/projects/42648/13-new-features
As for addressing the issues with the wiki, I was unaware of any issues with the code parsing, as it works with out issue for me on all browsers I have. So if we aren't notified of any issues there is no way we can solve them.
The bakery has had a rewrite started, but development has slowed down. And getting people involved is not as simple as 'appointing' them. We can't just conscript people into helping out, they need to come forward and volunteer. Anyone interested in helping get the existing issues with the bakery and helping progress the existing development can contact me. I'm on the irc channel most of the north american day every day, and watch the mailing list, the rest is up to you.
I just found my tickets again (throuh firefox history).
As a proof of my intention to contribute I just submitted again a few tickets, forked the project in git and commited some stuff. I hope I'll get feedback.
As teknoid said, contribution makes more sense than complaining. In fact, I don't understand why the guys moved from trac to chaw, because chaw is missing some esssential features.
I like the framework very much, though, and thank you all guys for your effort. I also enjoyed cakefest very much and got to know many cool people there.
I would also like to contribute to the cakephp2 project, but don't know where to start. Maybe someone can list all the missing features or address the todos so I can help here, too.
At least the bug tracker gets a response like worksforme when the devs don't want to address a particular issue. Not only that but the cookbook could use several new sections, and while I find it simple to comment and edit, adding a new section seems to be quite difficult.
I understand that this is a volunteer project, but there are many members of the community who want to help. Perhaps someone can be nominated to serve the community in this capacity, maybe for a share of that google adsense revenue I just noticed in the API.
Teknoid, I think Ernst had some right to be upset, when someone tries to contribute it is nice to get some sort of response (especially in the case of bakery articles).
At the same time CakePHP has made my job 100% easier. I use it everyday on professional projects. I suggest some sort of editor for the bakery and cookbook that is willing and able to put in the time, maybe even a voting system on whether a certain article should be published or a certain change should be allowed to the cookbook.
I appreciate everyones hard work on this project and frankly, it is the engine that feeds my family. But criticism is not a bad thing if it leads to better results!
We've been using it for a a little while now, and it is getting better than ever.
Well done.
p.s. complaining does little to help, this is open source. find a way to help out instead.
I like your project, and often want to contribute (I think I got some useful stuff), but you guys make it so hard to do that.
First of all, your wiki is f*ing buggy. It eats the code blocks away (javascript?) in ALL BROWSERS EXCEPT SAFARI. Since I never knew that, I thought it was an server-side issue until I downloaded safari today. Now I can read code examples in the wiki! yeah! ..very basic.
Second of all, I submitted a bunch of tickets, but I CANNOT figure out in which status they are. I neither receive an email on a status change, I cannot filter them, i cannot search (which makes it very very very hard to submit tickets because I don't want to submit bugs/enhancement if they have been already submitted)
... one little thing, I cannot remember my password on bakery because I have to use here an uppercase letter and I never use one... Why am I forced to do that?! bakery is not such an important thing.
I wrote an article on bakery. Okay, maybe it was not that good (It got written within 15minutes, I should have done it better). But if you don't publish it, you should at least write me an e-mail. I would have improved it in that case, or would know now that you don't like the idea at all.
Yes, there are a lot of problems in this area... The team seems to be focused on the development only. They need to serve information to the fools.
For the moment i find Cake the best FW in the area... but THEY really need to improve something on the documentation level. AND A LOT!
Comments are closed for articles over a year old