I tried to delete my topic, but too late. I was venting my
frustrations in the wrong place. :)
> Nice job guys !
>
> @ jacmoe : playing with alpha releases may cause issues ... that's why it's
> labeled Alpha
>
> On Thu, Nov 5, 2009 at 9:13 AM, mike karthauser <
[hidden email]>wrote:
>
>
>
> > On 5 Nov 2009, at 03:59, jacmoe <
[hidden email]> wrote:
>
> > > I am not exactly thrilled..
> > > Tried to a week to upgrade my Cake 1.2 powered project to Cake 1.3 -
> > > everything went smoothly, except for Ajax pagination.
>
> > > Now, not even the Cake console is working..
>
> > > C:\wamp\www\app>cake bake
>
> > > ♀
> > > Welcome to CakePHP v1.3.0 Console
> > > ---------------------------------------------------------------
> > > App : app
> > > Path: C:\wamp\www\app
> > > ---------------------------------------------------------------
> > > Interactive Bake Shell
> > > ---------------------------------------------------------------
> > > [D]atabase Configuration
> > > [M]odel
> > > [V]iew
> > > [C]ontroller
> > > [P]roject
> > > [F]ixture
> > > [T]est case
> > > [Q]uit
> > > What would you like to Bake? (D/M/V/C/P/F/T/Q)
> > >> m
> > > ---------------------------------------------------------------
> > > Bake Model
> > > Path: C:\wamp\www\app\models\
> > > ---------------------------------------------------------------
> > > Use Database Config: (default/test)
> > > [default] >
>
> > > Fatal error: Class 'ConnectionManager' not found in C:\wamp\www\cake
> > > \console\lib
> > > s\tasks\model.php on line 827
>
> > > WTF?
>
> > > I don't think I am going to waste any more time upgrading.. :)
>
> > > It is indeed alpha software.
> > > I'll stick to Cake 1.2 and maybe migrate to another framework.
>
> > Sounds like you had fun. Perhaps sticking to stable releases would be
> > best.
>
> > > On Nov 4, 6:28 am, mark_story <
[hidden email]> wrote:
> > >> The CakePHP development team is happy to 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
> > >> athttp://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>
>
You received this message because you are subscribed to the Google Groups "CakePHP" group.
