Re: Poll: what do you hate about CakePHP?
What I hate about cakephp is the lack of basic examples in the documentation. Not even having a proper menu example, pagination example, category example, admin cms section and so on .. is very frustrating for someone new to cakephp. Building the blog tutorial is a start, you need to take it much further. -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/groups/opt_out.
Re: Poll: what do you hate about CakePHP?
I didn't resurrect the thread, but, while I do agree with you that the documentation is far better than it was in 2009, I find that a lot of advanced features and usage aren't documented. The book is fantastic as a general introduction to Cake and its most common features, but I find myself looking in the core code quite a bit to figure out certain things. But, this isn't necessarily a bad thing - I think that you really should be familiar with the source code if you're going to use Cake. And I also know that it's not possible to have extensive documentation on every single little feature. On Sunday, October 13, 2013 4:42:05 AM UTC-7, mark_story wrote: > > What do you find lacking with the documentation? I think we've made great > improvements from 2009 when this thread was first started. > > -Mark > -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/groups/opt_out.
Re: Poll: what do you hate about CakePHP?
What do you find lacking with the documentation? I think we've made great improvements from 2009 when this thread was first started. -Mark -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/groups/opt_out.
Re: Poll: what do you hate about CakePHP?
Poor documentation On Thursday, May 7, 2009 10:29:55 PM UTC, Nate wrote: > > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/groups/opt_out.
Re: Poll: what do you hate about CakePHP?
On Fri, Jun 19, 2009 at 10:02 AM, bato wrote: > > No PHP4 support!! My two cents: - Prototype-based ajax. (jQuery is my js framework of choice.) - $ajax->div and $ajax->divEnd is boring - poor sqlite3 support Atenciosamente. -- MARCELO DE F. ANDRADE Belem, PA, Amazonia, Brazil Linux User #221105 http://mfandrade.wordpress.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
No PHP4 support!! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
I don't like: --Source code that has no comments other than at the method level-- makes it hard to find the bugs that are afflicting me... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Hi Grzegorz,
> I just came up with something, It's not something I hate - just an
> idea to improve Model (?):
>
> If Model could keep track of queries that it calls debugging would be
> simple, I think of something like this:
>
> //in controller:
> $this->Thing->clearQueryTrace(); //remove unimportant info
> //+
> $a = $this->Thing->find('all');
> $b = $this->Thing->find('count'); // just examples
> //++
> debug($this->Thing->getQueryTrace()) // dump every query that was
> called between + and ++
>
> In many cases I get the idea how to use stuff (models) from queries
> that it generates. It would be convenient if I didn't have to look for
> those queries in the table of 70 other queries (in 2nd debug level).
>
> Does it make sense to you?
I like this idea!
Jon
--
jon bennett
w: http://www.jben.net/
iChat (AIM): jbendotnet Skype: jon-bennett
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
I just came up with something, It's not something I hate - just an
idea to improve Model (?):
If Model could keep track of queries that it calls debugging would be
simple, I think of something like this:
//in controller:
$this->Thing->clearQueryTrace(); //remove unimportant info
//+
$a = $this->Thing->find('all');
$b = $this->Thing->find('count'); // just examples
//++
debug($this->Thing->getQueryTrace()) // dump every query that was
called between + and ++
In many cases I get the idea how to use stuff (models) from queries
that it generates. It would be convenient if I didn't have to look for
those queries in the table of 70 other queries (in 2nd debug level).
Does it make sense to you?
On 11 Cze, 15:25, "jitka (poLK)" wrote:
> > A bug, is a bug, is a bug.
>
> Feel free to repeat it indefinitely. To me, bug is a bug only if
> a) others are able to reproduce it and
> b) it is not a feature.
>
> I think you are bug, a bug, a bug, because you don't work for me. Now
> decide if you'll close it as wontfix, worksforme or needmoreinfo.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
> A bug, is a bug, is a bug. Feel free to repeat it indefinitely. To me, bug is a bug only if a) others are able to reproduce it and b) it is not a feature. I think you are bug, a bug, a bug, because you don't work for me. Now decide if you'll close it as wontfix, worksforme or needmoreinfo. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
WRONG. Certain bugs require certain circumstances specific to the users problem. If a user simply says "this doesn't work", how is the team supposed to fix if they dont know what YOU ARE DOING to cause the problem. Thats what test cases are for On Jun 10, 8:59 pm, Mr-Yellow wrote: > > I "hate" contributions constraints like: "Make a Unit Test" when I > > report a bug or like: "Fork the project and use Git" when I just want > > to update the .po file for CookBook. > > Amen. > > Search any existing issue with CakePHP and you'll find a ticket where > someone reported it as a bug and had it set to "wontfix" because the > dev refused to accept a problem without full tests and patches written > by the poster. > > A bug, is a bug, is a bug. Regardless of how much of a wanker the guy > reporting it is or how little info is included, still needs to be a > ticket, be looked into, be fixed. > > -Ben --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
> I "hate" contributions constraints like: "Make a Unit Test" when I > report a bug or like: "Fork the project and use Git" when I just want > to update the .po file for CookBook. Amen. Search any existing issue with CakePHP and you'll find a ticket where someone reported it as a bug and had it set to "wontfix" because the dev refused to accept a problem without full tests and patches written by the poster. A bug, is a bug, is a bug. Regardless of how much of a wanker the guy reporting it is or how little info is included, still needs to be a ticket, be looked into, be fixed. -Ben --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
> 4. Having to provide text and html bodies for email. (Should be able > to create html mail and have Cake write the text version > automatically). Having worked with email a great deal in the past, you need this control as there are quirks and customisations needed in some situations. -Ben --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Please do not NEVER EVER going to return database result as array.
those people who want this need to have their head check. do you know
how much pain to debug the results?
The reason I stick with Cakephp is the power model and their return
result in Array (believe me I am fixing a CodeIgniter site and work on
many many zend projects. If I have a say - I use CakePHP).
OK here is my 2 cents. I don't hate Cake. But we could do with a bit
more documentation. Do you know paginator accept a parameter "*" ?
took me couple months to find that out ... I wish they could list all
the available parameter if they are already there.
Joel
On May 8, 2:08 pm, Smelly Eddie wrote:
> I hate that it is a powerful framework that can make the tedious work
> of developing sites a breeze. Its strict adherence to the tried and
> true MVC model is a pain point as well. Why so logical?
>
> I hate the active community involvement and powerful documentation and
> API sites. I hate that people expect Cake to do every little thing.
>
> It is a framework! Not a solve everything-all-in-one-cms-portal-file-
> manager-blog-forum.
>
> Use the framework to create an upload component, it takes all of 5
> minutes!!
>
> On May 8, 8:56 am, "Dennis S. Hennen" wrote:
>
> > Consider Post hasMany Comment
>
> > Comment->find('all') returns {n}.Comment.*
>
> > Post->find('all') gives you Comment.{n}.*
>
> > If I want a helper to do processing on a list of comments, I have to
> > handle both potential formats, or massage the data.
>
> > Related to this is the $primary parameter to the afterFind callback.
>
> > Perhaps find results as objects instead of arrays?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Hmm, http://book.cakephp.org and you just posted on the support forum. I don't hate much - well sometimes I do but normally it's because I'm doing something wrong! I'd like the bake script to be capable of producing more "secure" code output including using some aspects of the security component, sanitizing user form data, whitelisting form fields etc. This would be pretty helpful in getting apps up and running even more quickly. I'd also like to see bugs/enhancements posted to the tracker to be included in new releases more quickly, but I realise that all changes need to be properly scrutinized so I wouldn't want this to happen at the expense of pushing out buggy releases. Chris On Jun 7, 4:56 pm, Lamonte wrote: > Lack of a proper documentation > Lack of a support forum --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Lack of a proper documentation Lack of a support forum On Fri, Jun 5, 2009 at 1:32 PM, Celso wrote: > > We love cakePHP ! > But...I hope something like this: > > --> $javascript->validate() > --> $ajax->form(.., array( validate => 'myvalidateFunc' ) ) > --> $javascript->datepicker() > --> $javascript->tooltip() > --> self detect Relationship > --> php5 >= only > > > -- For all your Programming and Technology Information Visit www.BinaryCrunch.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
We love cakePHP ! But...I hope something like this: --> $javascript->validate() --> $ajax->form(.., array( validate => 'myvalidateFunc' ) ) --> $javascript->datepicker() --> $javascript->tooltip() --> self detect Relationship --> php5 >= only --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
I had another minor issue too. When changing a table's primary
key, I'd like to just setting this adequately with the $primaryKey
model atribute and the relationships use it.
Personally I hate to have to change $belongsTo relationship to
add the "foreignKey" parameter too. I'd like if Cake identify the
name used for the other table's primary key and use it as a part
of the convention instead of "_id".
For example, I think it could be better if we can do something like
this
class Country extends AppModel {
$primaryKey = 'isocode';
// ^--- primary key defined...
class Trip extends AppModel {
$belongsTo = 'Country';
// ^-- instead of: $belongsTo = array('Country'=>
array('foreignKey'=> 'country_isocode'))
I know we could use 'country_id' in the database as a foreign
key, but I it not so intuitive.
Best regards.
--
MARCELO DE F. ANDRADE
Belem, PA, Amazonia, Brazil
Linux User #221105
http://mfandrade.wordpress.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
I just want to add one minor thing: I don't like that debug() is making print_r() instead of var_dump(), so when I want to debug some variable and see nothing - I know that there's null, false, true or empty string or string full white chars, so I need to make my own debugging with pre tags and var_dump. That just inconvenient On 27 Maj, 14:40, keymaster wrote: > > We've got a few good goals for the upcoming version... > > http://thechaw.com/cakephp/wiki/1.3/Hit_List --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
> We've got a few good goals for the upcoming version... http://thechaw.com/cakephp/wiki/1.3/Hit_List --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Guys, Thanks so much for all the feedback. Some of it we can act on now, some of it we may be able to act on in the future, and some of it we might never be able to resolve directly, but it's helpful to know what's important to you regardless. We've got a few good goals for the upcoming version, and we'll try to work in any changes that are in-sync with those goals. As always, time is our main limitation, so if you'd like to help out, the 1.3 source code is available on The Chaw (http://thechaw.com/ cakephp/source/branches). We're trying a new approach with orienting branches around features. Anyway, thanks again everyone for the feedback and continued community involvement. We're all working hard to keep CakePHP the best web development platform around. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
- Nested view support llike smarty. Currently, most of view in my project is in elements so that view supports nest. - form->checkbox is unuseful. Cannot insert another logic between each checkboxes by using $options [‘multiple’] => 'checkbox' I create $option['multiple'] => true option for $option['type'] => 'checkbox', and loop these by foreach. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
El mié, 20-05-2009 a las 08:19 -0700, avairet escribió: > I "hate" the lack of rigor with relational model and SQL norm. I think > "compound primary keys", sub-queries, multi-level JOIN should be > implemented. It will permit to avoid "artificial id" in HABTM for > example and thus tons of intermediate queries. More data types should > be available too (like ENUM and SET for MySQL). +1 > I "hate" the limited internationalisation of core methods like > Validate::alphanumeric() or Inflector::slug(). Accented and special > chars should be available and mb_ functions might be used, maybe by > including localized chars files (setting a var in config/core.php for > example). More internationalisation for Validate::phone() or > Validate::ssn() would be great too. We can help you to do that: please > delegate some responsibilities to the numerous dynamic international > communities! +1 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
"If you still use PHP4 on production servers your framework might not be your biggest problem :-) " True that Alex, true that. On May 20, 10:09 am, Alexandru Ciobanu wrote: > On 05/20/2009 10:20 AM, Constantin Botnari wrote:> Smelly i totally agree > with you :) and for all haters of php4 support > > in cake : people php4 support is vital for an framework !!! that means > > i can develop my cake app for any php version starting from php4 an > > ending with php5! its a real pain for an developer if he has to > > develop an web app and production server is built with php4.. > > PHP4 support was nice (not vital) one year ago, now it's pretty much > useless... > As of 2008-08-08 the PHP team completely ignores PHP4; this means not > even critical security fixes. > If you still use PHP4 on production servers your framework might not be > your biggest problem :-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Oh yeah, +1 on everything you sad man. That action thing is a real
mystery and a major pain.
On May 21, 4:49 pm, "rich...@home" wrote:
> One minor niggle-ette for me:
>
> I hate how form helpers $form->create() doesn't default to the current
> actions (it defaults to add). I always end up having to type:
>
> create("User", array("action"=>$this->action)) ?>
>
> oh, and another:
>
> $html->css() defaults to inline, it should default to putting it in
> the $script_for_layout. As it doesn't, you have to type:
>
> $html->css("my_css", null, array(), false);
>
> (same with the $javascript helper too)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
One minor niggle-ette for me:
I hate how form helpers $form->create() doesn't default to the current
actions (it defaults to add). I always end up having to type:
create("User", array("action"=>$this->action)) ?>
oh, and another:
$html->css() defaults to inline, it should default to putting it in
the $script_for_layout. As it doesn't, you have to type:
$html->css("my_css", null, array(), false);
(same with the $javascript helper too)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
I hate that $scaffold does not generate a code archive, so I can learn from it all when baking and customizing etc.. For example, I have a simple unresolved problem that works perfect with simple $scaffold, but getting this to work manually is a pain. The question could be answered if the $scaffold code was available, because it does what I need by default.. Here is my issue for anyone who might be versed enough with cakephp: http://www.nabble.com/fetching-associated-records-from-url-td23640799.html -- View this message in context: http://www.nabble.com/Poll%3A-what-do-you-hate-about-CakePHP--tp23436684p23640867.html Sent from the CakePHP mailing list archive at Nabble.com. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Totaly agree with avairet's comment about the site design... Some clients want to know what tools we use, and when they search about cakephp thinks that is a software for kids. avairet escribió: > Thank you for this ironic but serious message Nate! > To respect your humoristic formulation, here is my "hateful" > contribution! > And sorry for my simple English… hope it's understandable. ;) > > I "hate" the lack of rigor with relational model and SQL norm. I think > "compound primary keys", sub-queries, multi-level JOIN should be > implemented. It will permit to avoid "artificial id" in HABTM for > example and thus tons of intermediate queries. More data types should > be available too (like ENUM and SET for MySQL). > > I "hate" contributions constraints like: "Make a Unit Test" when I > report a bug or like: "Fork the project and use Git" when I just want > to update the .po file for CookBook. > > I "hate" the instability of official documentation. Yes CookBook is > better than ever, but there are still a lot of sections without > explanations, some with obsolete explanations, others that are > frequently modified… it's difficult for both newcomers and translators > to navigate through it and find the good information. A PDF export – > global or partial - would be useful too > > I "hate" translation tool and process for CookBook, it is complex, > heavy to manipulate, frequently modified and debugged. Ok, there were > new features recently developed (thanks to AD7six, Gwoo and others for > this work), but is not enough to attract and motivate new translators… > Two little suggestions for the moment: give validation rights to > locale community AND/OR let us write our own documentation, inspired > by, but not a perfect clone of the original. > > I "hate" the multi-communicational channels of community : Bakery, > official website, Ohloh journal, multiple IRC's chans, multiple > GoogleGroups, Trac, TheChaw, CakeFest, unofficial forum, core > developpers and contributors blogs… it's like a puzzle! The > heterogeneity of designs between those different websites of the > Cake's galaxy make it even more disorganized. > > In the same way, I "hate" Cake's logo (this cake is more like a cheese > 时 ) and official website design (not clear enough, too funny and not > enough serious for deciders in comparison to Symfony and ZF designs). > > I hate methods with more than 4 parameters or with mixed parameters (a > string or an array or null). > I hate Cake's shortcuts that just embbed PHP native functions like "e > ()", "up()", "low()"… (for the majority of PHP's IDE, autocomplete > works well for that). > > I "hate" the limited internationalisation of core methods like > Validate::alphanumeric() or Inflector::slug(). Accented and special > chars should be available and mb_ functions might be used, maybe by > including localized chars files (setting a var in config/core.php for > example). More internationalisation for Validate::phone() or > Validate::ssn() would be great too. We can help you to do that: please > delegate some responsibilities to the numerous dynamic international > communities! > > Other opinions that I'm supporting too: > ++ PHP 4 to full PHP5 syntax > ++ ACL more flexibility (e.g. user attached to two groups) > ++ Objects instead arrays, especially for find's returns > ++ GUI for Bake, because we're not all CLI gurus… hmmm, ok, we should > be! 时 > ++ More complete Bake > ++ Plugins management > ++ Form::error messages > ++ Jquery > ++ automagic slug field > > That's all... for the moment! > > OK, I know that a framework can NOT make the coffee and that I can > create my own logic when needed. > But I would like to say that in my point of view, the more Cake will > be professional, industrial and rigorous, the more it will be adopted > by PHP users and deciders who currently look at Symfony or Zend > Framework side, even if Cake is more fun and easy to use. > > I like Cake and its philosophy, I want to develop its usage and > recognition around the World, so let’s work together to make a better > Cake! ;) > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
On Wed, May 20, 2009 at 3:45 AM, GreyCells wrote: > >> The reason is primarily that link URLs >> would be lost > > I currently use html2text by Jon Abernathy, which retains links as > footnotes. Thanks for the tip. I'm going to have a look through that now. But how would this help if you were relying on Cake to create the text version for you? Big FYI, there's a vulnerability (as of last january): http://www.madirish.net/?article=225 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Thank you for this ironic but serious message Nate! To respect your humoristic formulation, here is my "hateful" contribution! And sorry for my simple English… hope it's understandable. ;) I "hate" the lack of rigor with relational model and SQL norm. I think "compound primary keys", sub-queries, multi-level JOIN should be implemented. It will permit to avoid "artificial id" in HABTM for example and thus tons of intermediate queries. More data types should be available too (like ENUM and SET for MySQL). I "hate" contributions constraints like: "Make a Unit Test" when I report a bug or like: "Fork the project and use Git" when I just want to update the .po file for CookBook. I "hate" the instability of official documentation. Yes CookBook is better than ever, but there are still a lot of sections without explanations, some with obsolete explanations, others that are frequently modified… it's difficult for both newcomers and translators to navigate through it and find the good information. A PDF export – global or partial - would be useful too I "hate" translation tool and process for CookBook, it is complex, heavy to manipulate, frequently modified and debugged. Ok, there were new features recently developed (thanks to AD7six, Gwoo and others for this work), but is not enough to attract and motivate new translators… Two little suggestions for the moment: give validation rights to locale community AND/OR let us write our own documentation, inspired by, but not a perfect clone of the original. I "hate" the multi-communicational channels of community : Bakery, official website, Ohloh journal, multiple IRC's chans, multiple GoogleGroups, Trac, TheChaw, CakeFest, unofficial forum, core developpers and contributors blogs… it's like a puzzle! The heterogeneity of designs between those different websites of the Cake's galaxy make it even more disorganized. In the same way, I "hate" Cake's logo (this cake is more like a cheese �� ) and official website design (not clear enough, too funny and not enough serious for deciders in comparison to Symfony and ZF designs). I hate methods with more than 4 parameters or with mixed parameters (a string or an array or null). I hate Cake's shortcuts that just embbed PHP native functions like "e ()", "up()", "low()"… (for the majority of PHP's IDE, autocomplete works well for that). I "hate" the limited internationalisation of core methods like Validate::alphanumeric() or Inflector::slug(). Accented and special chars should be available and mb_ functions might be used, maybe by including localized chars files (setting a var in config/core.php for example). More internationalisation for Validate::phone() or Validate::ssn() would be great too. We can help you to do that: please delegate some responsibilities to the numerous dynamic international communities! Other opinions that I'm supporting too: ++ PHP 4 to full PHP5 syntax ++ ACL more flexibility (e.g. user attached to two groups) ++ Objects instead arrays, especially for find's returns ++ GUI for Bake, because we're not all CLI gurus… hmmm, ok, we should be! �� ++ More complete Bake ++ Plugins management ++ Form::error messages ++ Jquery ++ automagic slug field That's all... for the moment! OK, I know that a framework can NOT make the coffee and that I can create my own logic when needed. But I would like to say that in my point of view, the more Cake will be professional, industrial and rigorous, the more it will be adopted by PHP users and deciders who currently look at Symfony or Zend Framework side, even if Cake is more fun and easy to use. I like Cake and its philosophy, I want to develop its usage and recognition around the World, so let’s work together to make a better Cake! ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
On 05/20/2009 10:20 AM, Constantin Botnari wrote: > Smelly i totally agree with you :) and for all haters of php4 support > in cake : people php4 support is vital for an framework !!! that means > i can develop my cake app for any php version starting from php4 an > ending with php5! its a real pain for an developer if he has to > develop an web app and production server is built with php4.. > PHP4 support was nice (not vital) one year ago, now it's pretty much useless... As of 2008-08-08 the PHP team completely ignores PHP4; this means not even critical security fixes. If you still use PHP4 on production servers your framework might not be your biggest problem :-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Smelly i totally agree with you :) and for all haters of php4 support in cake : people php4 support is vital for an framework !!! that means i can develop my cake app for any php version starting from php4 an ending with php5! its a real pain for an developer if he has to develop an web app and production server is built with php4.. i was so happy when i found this framework easy to use.. with so powerful support for both php versions.. and with understandable MVC model :) i am happy with cake and i really don't want support for php4 to be removed in next releases. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
> The reason is primarily that link URLs > would be lost I currently use html2text by Jon Abernathy, which retains links as footnotes. > it's possible to > send an HTML-only email. That's really bad form 100% agree - which is why Cake should default to best practice by automatically creating a text version (if text template is undefined). If you're creating a plain text email, you probably don't want/need an html version. On May 19, 8:13 pm, brian wrote: > On Tue, May 19, 2009 at 12:21 PM, GreyCells > wrote: > > > 4. Having to provide text and html bodies for email. (Should be able > > to create html mail and have Cake write the text version > > automatically). > > I disagree with this. I prefer to create 2 versions of the content and > echo each variable in its view. The reason is primarily that link URLs > would be lost if the content is simply run through strip_tags() for > the plaintext version. What I do is run it through a RegExp to append > the URL in brackets after the word(s) that would have had the link. I > also like to add in newlines where certain headers are so everything > isn't jumbled together. And then there's the question of layouts, > which will generally be very different. > > One big annoyance I see in Email, though, is that it's possible to > send an HTML-only email. That's really bad form, IMHO. Obviously, this > isn't a frustration I'm *subjected to* but I don't think the Cake devs > should be encouraging HTML-only email. My SwiftMailer component (much > modified from a very old one found at Bakery) defaults to text and > creates an HTML version in addition to the plaintext if requested. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
On Tue, May 19, 2009 at 12:21 PM, GreyCells wrote: > > Not so much hates, but frustrations when coding new apps (I'm sure > you've heard them all before, Nate:) > > 2. More callbacks in Auth, Session and Email to allow logging + App > specific behaviour. (via App[Auth|Session|Email]) Excellent suggestion! Second that. > 4. Having to provide text and html bodies for email. (Should be able > to create html mail and have Cake write the text version > automatically). I disagree with this. I prefer to create 2 versions of the content and echo each variable in its view. The reason is primarily that link URLs would be lost if the content is simply run through strip_tags() for the plaintext version. What I do is run it through a RegExp to append the URL in brackets after the word(s) that would have had the link. I also like to add in newlines where certain headers are so everything isn't jumbled together. And then there's the question of layouts, which will generally be very different. One big annoyance I see in Email, though, is that it's possible to send an HTML-only email. That's really bad form, IMHO. Obviously, this isn't a frustration I'm *subjected to* but I don't think the Cake devs should be encouraging HTML-only email. My SwiftMailer component (much modified from a very old one found at Bakery) defaults to text and creates an HTML version in addition to the plaintext if requested. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Upvote for this post. The ACL component was really neat, until I tried to actually use it. It was more difficult to try and use it than to just roll my own. Auth Component works great, I wish ACL worked great with Auth. Also ++ to commenters who asked for more real-world tutorials. The manual is very well done, but it doesn't document very much of what cake does. Even the API isn't totally helpful on a lot of stuff -- you have to dig through source or IRC. The ACL component is a major gripe. For everyone wishing for more tutorials, go write them! For the Cake shortcomings, it's still light years ahead of what I was doing when I was hand coding PHP. Unfortunately, it's been frustrating enough at times that I'm going to take a serious look @ Zend. On May 8, 8:13 am, James K wrote: > My biggest request: Think outside the blog tutorial!! > > A lot of the supporting components work great in the context of a very > simple, one controller for one model with 4 actions for CRUD setup, > but become impractical or impossible to use outside that. The ACL > component is probably the biggest offender of this. > > So many people have problems with ACL because none of the built-in ACL > schemes actually work in the real world. Also the query load is > immense - why can't the ACL component pull down an entire tree branch > in one query (you use MPTT, so this is pretty easy), then post-process > it instead of running a query for every node? Once your tree gets to > be of any real size, your application gets crippled under dozens (if > not hundreds) of ACL queries. > > In a large application my company just built, we had to roll our own > ACL component for role based permissions because the ACL component > simply couldn't do it. We pull down the permissions a branch at a > time, and cache them per role. There may be up to 15 ACL checks done > in a single action (with full CRUD). If we were to use the built-in > ACL check method, we'd be running 15 x 4 checks (one CRUD item at a > time). Multiply THAT by a query for every node it has to go down and > you can quickly see how this gets out of control. > > You could say this is way outside the scope of what the ACL component > was intended to do, and that's totally fair. My argument is that the > ACL component simply doesn't work in any real world scenarios and as > such causes an immense amount of grief for people trying to learn how > to leverage it in their own applications. I see very confused people > post on here every day about ACL and most times, unless they're > willing to roll their own ACL component, they're stuck. You'd almost > be better off without it. > > The ORM has issues with being tailored to the blog tutorial as well. > Another big issue people seem to have is with HABTM relationships and > the inability to direct Cake's use of joins. Once you're forced to > fall back to hand-written queries, you lose all the useful callbacks. > There must be some middle ground here - even if it means writing your > queries in a way Cake can parse and understand. > > Beyond those sorts of things, Cake remains my framework of choice. All > in all, it is EXTREMELY flexible and consistently saves me months of > development time. Any issues I can bring up could be considered minor > gripes when compared to what Cake DOES get you. > > Cheers and thanks for your hard work and continued dedication to this > project. This is a huge service to PHP developers everywhere. Don't > let the whiners get to you ;) > > - James > > On May 7, 6:29 pm, Nate wrote: > > > Well, maybe hate's a strong word. Let's say, what do you like the > > least? Kind of an odd question, I know, but since we've kick-started > > development of a new version, I'd like to know what the most > > frustrating things with the framework are, even if they're things we > > can't fix right away. > > > I'll get us started: PHP 4 support. > > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
- No callbacks in associative queries
- Lack of (or not up to date) documentation
- Integrating jQuery instead of Prototype may be better, but I think
I'll still write my own js code by hand to have more control over it
anyway
On 8 mai, 15:08, Smelly Eddie wrote:
> I hate that it is a powerful framework that can make the tedious work
> of developing sites a breeze. Its strict adherence to the tried and
> true MVC model is a pain point as well. Why so logical?
>
> I hate the active community involvement and powerful documentation and
> API sites. I hate that people expect Cake to do every little thing.
>
> It is a framework! Not a solve everything-all-in-one-cms-portal-file-
> manager-blog-forum.
>
> Use the framework to create an upload component, it takes all of 5
> minutes!!
>
> On May 8, 8:56 am, "Dennis S. Hennen" wrote:
>
> > Consider Post hasMany Comment
>
> > Comment->find('all') returns {n}.Comment.*
>
> > Post->find('all') gives you Comment.{n}.*
>
> > If I want a helper to do processing on a list of comments, I have to
> > handle both potential formats, or massage the data.
>
> > Related to this is the $primary parameter to the afterFind callback.
>
> > Perhaps find results as objects instead of arrays?
>
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Well, I have been using cake for over a year now. It is a great and powerful framkwork to say the least. It makes a lot of work a lot easier. But, from experience, it has really crappy oracle support. There needs to be more support built in. Oracle is complex, yes, but I cannot even do "User.TableName". There is a lot in Oracle that you cannot do in Cake without an a really complicated custom query. I mean custom queries don't even support the "*" selector. That is a little annoying to me. Otherwise, it is really awesome. On May 7, 6:29 pm, Nate wrote: > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Not so much hates, but frustrations when coding new apps (I'm sure you've heard them all before, Nate:) 1. Auth, Session and Email should all be fat models with a thin component interface if required. 2. More callbacks in Auth, Session and Email to allow logging + App specific behaviour. (via App[Auth|Session|Email]) 3. Http Basic/Digest Auth should be in Auth, not Security, so acl etc can be shared easily. 4. Having to provide text and html bodies for email. (Should be able to create html mail and have Cake write the text version automatically). 5. Me, not be disciplined enough with my time to contribute back fully... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Absolutely, right about form errors.
On May 18, 4:54 pm, "dr. Hannibal Lecter" wrote:
> Here's another interesting kick in the Matt Groening.
>
> Inability to use FormHelper::error() to show our own errors on the
> fly, i.e. $form->error('Arse.biscuits', 'A pair of women's knickers is
> missing'); regardless of whether I'm using a model to create a form or
> not.
>
> Workaround:
>
> $form->validationErrors['Arse']['biscuits'] = 'Dancing like a mad
> eejit is not an allowed action';
> echo $form->error('Arse.biscuits');
>
> But why?? Form error should be looking for an validation error message
> only if I didn't provide one as a param. Am I the only one who finds
> that logical?
>
> On May 18, 2:27 pm, Henrique Machado wrote:
>
> > What about create a true poll for it?
>
> > First create a poll for all suggestions, after create a poll to vote on that
> > suggestions and voilá =)
>
> > Henrique Machado
>
> > 2009/5/18 Aivaras
>
> > > Hey,
>
> > > actually the most annoying thing is that we cannot download separate parts
> > > of Cake. It would be cool if advanced users could choose what do they need
> > > for their project, just like mootools made in their download page. I
> > > certainly understand that this is just *wishful thinking* because Cake's
> > > core uses nearly everything :x
>
> > > Anyway, upload component would be totally usable!
>
> > > Also, switching from scriptaculous + prototype to jQuery would be awesome.
> > > People would create and share plugins, which means that our lovely
> > > community
> > > would become even bigger and ADmad would be even more mad (sorry AD :x)
>
> > > Enjoy,
> > > Faifas
>
> > > On Sat, May 16, 2009 at 06:00, Brendon Kozlowski
> > > wrote:
>
> > >> Thought of another one.
>
> > >> Paginate settings, and paginate call. Why do they have the same
> > >> name? When learning how Cake works, although it's proper OOP to do
> > >> so, it's a bit confusing to see:
>
> > >> $this->paginate = array('contain' => 'User');
> > >> $this->set('posts', $this->paginate());
>
> > >> I think it would be clearer (from a "name the variable what it is"
> > >> type of coding style) to use something like:
> > >> $this->paginateOptions = array('contain' => 'User');
>
> > >> Every time I see $this->paginate when skimming through code, I
> > >> immediately see the method, completely forgetting it's also a
> > >> property. I "hate" that. ;)
>
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
- php4 support++ - existence of an AJAX helper ++ - Complex plugin setup ++ - Database i8n (could be a lack of documentation on the current implementation) ++ And with Database i8n I mean the whole process: - Automatically showing translated fields for all languages at once in the form when adding/editing. - Automatically saving them all when saving. - Automatically using the correct one for field when the language is set. On 8 touko, 01:29, Nate wrote: > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
+1 for the MeioUpload behavior and its seamless integration ... or something similar to be included int the core behaviors. On 19 mai, 07:17, DanielMedia wrote: > +1 with Matt Curry on this: > > "Remove Model::recursive. All find calls would return just the model > and if you wanted associated models you HAVE TO use Containable." > > - Built in functionality for custom find types. Right now there are > some nice hacks that you can put into your AppModel to define your own > custom find types but this should work out of the box. > > - The MEIO upload behavior (or something like it) could be added to > the core. That behavior has greatly simplified managing uploads for me > and is quite flexible. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
+1 with Matt Curry on this: "Remove Model::recursive. All find calls would return just the model and if you wanted associated models you HAVE TO use Containable." - Built in functionality for custom find types. Right now there are some nice hacks that you can put into your AppModel to define your own custom find types but this should work out of the box. - The MEIO upload behavior (or something like it) could be added to the core. That behavior has greatly simplified managing uploads for me and is quite flexible. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
You are definitely right indeed.
Faifas
On Mon, May 18, 2009 at 18:54, dr. Hannibal Lecter wrote:
>
> Here's another interesting kick in the Matt Groening.
>
> Inability to use FormHelper::error() to show our own errors on the
> fly, i.e. $form->error('Arse.biscuits', 'A pair of women's knickers is
> missing'); regardless of whether I'm using a model to create a form or
> not.
>
> Workaround:
>
> $form->validationErrors['Arse']['biscuits'] = 'Dancing like a mad
> eejit is not an allowed action';
> echo $form->error('Arse.biscuits');
>
> But why?? Form error should be looking for an validation error message
> only if I didn't provide one as a param. Am I the only one who finds
> that logical?
>
> On May 18, 2:27 pm, Henrique Machado wrote:
> > What about create a true poll for it?
> >
> > First create a poll for all suggestions, after create a poll to vote on
> that
> > suggestions and voilá =)
> >
> > Henrique Machado
> >
> > 2009/5/18 Aivaras
> >
> > > Hey,
> >
> > > actually the most annoying thing is that we cannot download separate
> parts
> > > of Cake. It would be cool if advanced users could choose what do they
> need
> > > for their project, just like mootools made in their download page. I
> > > certainly understand that this is just *wishful thinking* because
> Cake's
> > > core uses nearly everything :x
> >
> > > Anyway, upload component would be totally usable!
> >
> > > Also, switching from scriptaculous + prototype to jQuery would be
> awesome.
> > > People would create and share plugins, which means that our lovely
> community
> > > would become even bigger and ADmad would be even more mad (sorry AD :x)
> >
> > > Enjoy,
> > > Faifas
> >
> > > On Sat, May 16, 2009 at 06:00, Brendon Kozlowski <
> brendon...@hotmail.com>wrote:
> >
> > >> Thought of another one.
> >
> > >> Paginate settings, and paginate call. Why do they have the same
> > >> name? When learning how Cake works, although it's proper OOP to do
> > >> so, it's a bit confusing to see:
> >
> > >> $this->paginate = array('contain' => 'User');
> > >> $this->set('posts', $this->paginate());
> >
> > >> I think it would be clearer (from a "name the variable what it is"
> > >> type of coding style) to use something like:
> > >> $this->paginateOptions = array('contain' => 'User');
> >
> > >> Every time I see $this->paginate when skimming through code, I
> > >> immediately see the method, completely forgetting it's also a
> > >> property. I "hate" that. ;)
> >
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Here's another interesting kick in the Matt Groening.
Inability to use FormHelper::error() to show our own errors on the
fly, i.e. $form->error('Arse.biscuits', 'A pair of women's knickers is
missing'); regardless of whether I'm using a model to create a form or
not.
Workaround:
$form->validationErrors['Arse']['biscuits'] = 'Dancing like a mad
eejit is not an allowed action';
echo $form->error('Arse.biscuits');
But why?? Form error should be looking for an validation error message
only if I didn't provide one as a param. Am I the only one who finds
that logical?
On May 18, 2:27 pm, Henrique Machado wrote:
> What about create a true poll for it?
>
> First create a poll for all suggestions, after create a poll to vote on that
> suggestions and voilá =)
>
> Henrique Machado
>
> 2009/5/18 Aivaras
>
> > Hey,
>
> > actually the most annoying thing is that we cannot download separate parts
> > of Cake. It would be cool if advanced users could choose what do they need
> > for their project, just like mootools made in their download page. I
> > certainly understand that this is just *wishful thinking* because Cake's
> > core uses nearly everything :x
>
> > Anyway, upload component would be totally usable!
>
> > Also, switching from scriptaculous + prototype to jQuery would be awesome.
> > People would create and share plugins, which means that our lovely community
> > would become even bigger and ADmad would be even more mad (sorry AD :x)
>
> > Enjoy,
> > Faifas
>
> > On Sat, May 16, 2009 at 06:00, Brendon Kozlowski
> > wrote:
>
> >> Thought of another one.
>
> >> Paginate settings, and paginate call. Why do they have the same
> >> name? When learning how Cake works, although it's proper OOP to do
> >> so, it's a bit confusing to see:
>
> >> $this->paginate = array('contain' => 'User');
> >> $this->set('posts', $this->paginate());
>
> >> I think it would be clearer (from a "name the variable what it is"
> >> type of coding style) to use something like:
> >> $this->paginateOptions = array('contain' => 'User');
>
> >> Every time I see $this->paginate when skimming through code, I
> >> immediately see the method, completely forgetting it's also a
> >> property. I "hate" that. ;)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
What about create a true poll for it?
First create a poll for all suggestions, after create a poll to vote on that
suggestions and voilá =)
Henrique Machado
2009/5/18 Aivaras
> Hey,
>
> actually the most annoying thing is that we cannot download separate parts
> of Cake. It would be cool if advanced users could choose what do they need
> for their project, just like mootools made in their download page. I
> certainly understand that this is just *wishful thinking* because Cake's
> core uses nearly everything :x
>
> Anyway, upload component would be totally usable!
>
> Also, switching from scriptaculous + prototype to jQuery would be awesome.
> People would create and share plugins, which means that our lovely community
> would become even bigger and ADmad would be even more mad (sorry AD :x)
>
> Enjoy,
> Faifas
>
>
>
> On Sat, May 16, 2009 at 06:00, Brendon Kozlowski
> wrote:
>
>>
>> Thought of another one.
>>
>> Paginate settings, and paginate call. Why do they have the same
>> name? When learning how Cake works, although it's proper OOP to do
>> so, it's a bit confusing to see:
>>
>> $this->paginate = array('contain' => 'User');
>> $this->set('posts', $this->paginate());
>>
>> I think it would be clearer (from a "name the variable what it is"
>> type of coding style) to use something like:
>> $this->paginateOptions = array('contain' => 'User');
>>
>> Every time I see $this->paginate when skimming through code, I
>> immediately see the method, completely forgetting it's also a
>> property. I "hate" that. ;)
>>
>>
>
> >
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Hey,
actually the most annoying thing is that we cannot download separate parts
of Cake. It would be cool if advanced users could choose what do they need
for their project, just like mootools made in their download page. I
certainly understand that this is just *wishful thinking* because Cake's
core uses nearly everything :x
Anyway, upload component would be totally usable!
Also, switching from scriptaculous + prototype to jQuery would be awesome.
People would create and share plugins, which means that our lovely community
would become even bigger and ADmad would be even more mad (sorry AD :x)
Enjoy,
Faifas
On Sat, May 16, 2009 at 06:00, Brendon Kozlowski wrote:
>
> Thought of another one.
>
> Paginate settings, and paginate call. Why do they have the same
> name? When learning how Cake works, although it's proper OOP to do
> so, it's a bit confusing to see:
>
> $this->paginate = array('contain' => 'User');
> $this->set('posts', $this->paginate());
>
> I think it would be clearer (from a "name the variable what it is"
> type of coding style) to use something like:
> $this->paginateOptions = array('contain' => 'User');
>
> Every time I see $this->paginate when skimming through code, I
> immediately see the method, completely forgetting it's also a
> property. I "hate" that. ;)
> >
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Thought of another one.
Paginate settings, and paginate call. Why do they have the same
name? When learning how Cake works, although it's proper OOP to do
so, it's a bit confusing to see:
$this->paginate = array('contain' => 'User');
$this->set('posts', $this->paginate());
I think it would be clearer (from a "name the variable what it is"
type of coding style) to use something like:
$this->paginateOptions = array('contain' => 'User');
Every time I see $this->paginate when skimming through code, I
immediately see the method, completely forgetting it's also a
property. I "hate" that. ;)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
- No virtual fields support On 8 Mag, 00:29, Nate wrote: > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
'field' => 'title' --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
> To get all the translations for all the languages is a nightmare.
Solution exists.
$this->Article->Behaviors->attach('Translate', array('title' =>
'Title'));
$article = $this->Article->find('first');
You'll get title for returned article in current locale, and also
result of 'hasMany Title' association without condition on locale
(therefore all existing titles of this article).
Another approach would be (using the same sql queries):
$this->Article->Behaviors->attach('Translate', array('title'));
$I18nModel =& $this->Article->translateModel();
$article = $this->Article->find('first');
$titles = $I18nModel->find('all', array(
'conditions' => array(
'model' => 'Article',
'foreign_key' => $article['Article']['id']
)
));
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
DateTime type on Mysql Table, it's better using timestamp with datetime format (-00-00 00:00:00) Seems it doesn't important, but we know that datetime bits is bigger than timestamps. That's way, all my created and modified table using timestamp. On Thu, 2009-05-07 at 15:29 -0700, Nate wrote: > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
+1 for better ACL documentation, offcial docs and the tutorials out there have been very frustrating for me :( Juancho On Thu, May 7, 2009 at 5:29 PM, Nate wrote: > > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
@Miles J: That's why a toggle would be nice in the core to use associative or full fledged model objects. It would be nice to run model functions off the returned object in either the controller or view without having to set the model's id. Furthermore, if you needed to manipulate two objects of the same model in one controller action there's no easy way to execute their model function without passing the id in and handling that in the model. It's a little sloppy, and it doesn't have to be. /shrug But what I'd really want are: 1) full fledged cake console 2) migrations I'd be a real happy camper with those two =) Nick On May 13, 3:40 am, Miles J wrote: > @nurvzy - Returning objects from a mysql resource and slower then an > associative array. I for one would hate to have to use objects within > views. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
1. Lets loose PHP4 asap
2. Hidden input fields should a default class applied something
like: .hidden-input perhaps - if you have forms with coloured
background then it can be a real nightmare making sure hidden fields
stay hidden (not everybody uses firefox) - I'm sure everybody has
scratched their heads over the little stripes that sometimes randomly
appear in forms !
3. It would be great if there was another layer of built in helpers so
we could overload the core helpers e.g. FormHelper extends
FormHelperBase extends AppHelper - what is now FormHelper becomes
FormHelperBase and FormHelper become an empty class that you can just
use to override methods in the built in helpers.
4. $model->find() bringing back all the associated data unless you
tell it not too - it should be the other way around - if you need
associations create them, use things like Containable and Rafael
Bandeira's Linkable behaviour.
There is a lot to be said for the built in admin in Django (although
on balance I think it maybe take it a bit far) - I think there are
ideas that could be borrowed - built in and configured ACL seems a
great idea and lots of built in widget / component type things are
handy.
On a general note though I'd just really like to say thanks to all the
core developers and everyone who contributes for building such a cool
framework.
Cheers
John
On May 13, 11:47 am, "Mark (Germany)"
wrote:
> after so many years still too "american"!
> no real multi-lingual support for usage in other languages than just
> englisch
>
> e.g. the mb_() function problem i already pointed out 12 months ago
> with utf8 as default + mb_() functions there wouldn't be any trouble
>
> On 13 Mai, 11:57, majna wrote:
>
> > Think Routing.admin and prefix routing implementation is not complete.
> > -prefix routing ignores reverse routing and pagination
> > -Routing.admin accepts only one string
>
> > maybe Routing.admin should be removed and replaced with prefix routing
> > completely.
>
> > On May 8, 3:08 pm, Smelly Eddie wrote:
>
> > > I hate that it is a powerful framework that can make the tedious work
> > > of developing sites a breeze. Its strict adherence to the tried and
> > > true MVC model is a pain point as well. Why so logical?
>
> > > I hate the active community involvement and powerful documentation and
> > > API sites. I hate that people expect Cake to do every little thing.
>
> > > It is a framework! Not a solve everything-all-in-one-cms-portal-file-
> > > manager-blog-forum.
>
> > > Use the framework to create an upload component, it takes all of 5
> > > minutes!!
>
> > > On May 8, 8:56 am, "Dennis S. Hennen" wrote:
>
> > > > Consider Post hasMany Comment
>
> > > > Comment->find('all') returns {n}.Comment.*
>
> > > > Post->find('all') gives you Comment.{n}.*
>
> > > > If I want a helper to do processing on a list of comments, I have to
> > > > handle both potential formats, or massage the data.
>
> > > > Related to this is the $primary parameter to the afterFind callback.
>
> > > > Perhaps find results as objects instead of arrays?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
after so many years still too "american"!
no real multi-lingual support for usage in other languages than just
englisch
e.g. the mb_() function problem i already pointed out 12 months ago
with utf8 as default + mb_() functions there wouldn't be any trouble
On 13 Mai, 11:57, majna wrote:
> Think Routing.admin and prefix routing implementation is not complete.
> -prefix routing ignores reverse routing and pagination
> -Routing.admin accepts only one string
>
> maybe Routing.admin should be removed and replaced with prefix routing
> completely.
>
> On May 8, 3:08 pm, Smelly Eddie wrote:
>
> > I hate that it is a powerful framework that can make the tedious work
> > of developing sites a breeze. Its strict adherence to the tried and
> > true MVC model is a pain point as well. Why so logical?
>
> > I hate the active community involvement and powerful documentation and
> > API sites. I hate that people expect Cake to do every little thing.
>
> > It is a framework! Not a solve everything-all-in-one-cms-portal-file-
> > manager-blog-forum.
>
> > Use the framework to create an upload component, it takes all of 5
> > minutes!!
>
> > On May 8, 8:56 am, "Dennis S. Hennen" wrote:
>
> > > Consider Post hasMany Comment
>
> > > Comment->find('all') returns {n}.Comment.*
>
> > > Post->find('all') gives you Comment.{n}.*
>
> > > If I want a helper to do processing on a list of comments, I have to
> > > handle both potential formats, or massage the data.
>
> > > Related to this is the $primary parameter to the afterFind callback.
>
> > > Perhaps find results as objects instead of arrays?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Think Routing.admin and prefix routing implementation is not complete.
-prefix routing ignores reverse routing and pagination
-Routing.admin accepts only one string
maybe Routing.admin should be removed and replaced with prefix routing
completely.
On May 8, 3:08 pm, Smelly Eddie wrote:
> I hate that it is a powerful framework that can make the tedious work
> of developing sites a breeze. Its strict adherence to the tried and
> true MVC model is a pain point as well. Why so logical?
>
> I hate the active community involvement and powerful documentation and
> API sites. I hate that people expect Cake to do every little thing.
>
> It is a framework! Not a solve everything-all-in-one-cms-portal-file-
> manager-blog-forum.
>
> Use the framework to create an upload component, it takes all of 5
> minutes!!
>
> On May 8, 8:56 am, "Dennis S. Hennen" wrote:
>
> > Consider Post hasMany Comment
>
> > Comment->find('all') returns {n}.Comment.*
>
> > Post->find('all') gives you Comment.{n}.*
>
> > If I want a helper to do processing on a list of comments, I have to
> > handle both potential formats, or massage the data.
>
> > Related to this is the $primary parameter to the afterFind callback.
>
> > Perhaps find results as objects instead of arrays?
>
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
@nurvzy - Returning objects from a mysql resource and slower then an associative array. I for one would hate to have to use objects within views. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
@Sergei U why wouldn't helpers and components be in the controller. Where else would they go. On May 13, 1:12 am, Sergei wrote: > Don't like: > > * PHP4 support (some years back I thought it as advantage!) > * too resticted by conventions (at first I liked it too) > * $helpers=array(..) and $components=array(..) in controllers. > > I really like the new Yii framework -- very powerful, fast and more > important, flexible. Comparing to Cake. > > On 8 май, 07:29, Nate wrote: > > > Well, maybe hate's a strong word. Let's say, what do you like the > > least? Kind of an odd question, I know, but since we've kick-started > > development of a new version, I'd like to know what the most > > frustrating things with the framework are, even if they're things we > > can't fix right away. > > > I'll get us started: PHP 4 support. > > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
A plugin management system, for plugin, component, behavior, etc... would be nice --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Don't like: * PHP4 support (some years back I thought it as advantage!) * too resticted by conventions (at first I liked it too) * $helpers=array(..) and $components=array(..) in controllers. I really like the new Yii framework -- very powerful, fast and more important, flexible. Comparing to Cake. On 8 май, 07:29, Nate wrote: > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
I have to add one point to the lack of advanced documentation ... it
is getting better but it's not quite there yet ... API docs are
relatively good, but I think they lack some examples of for example
how to use parameters in function calls. I have not found it feasible
to go through core cake code to determine what a specific function
does with a given parameter ... maybe some people like that ;)
I also agree that cake does not have to solve all our issues, we are
better of writing those ourselves ... however, I have often searched
the Bakery for code I could reuse and have found out that many pieces
of code are either really old or there is no good documentation for
them available and therefore have not find anything highly usable from
them ... any ideas how this (code reusability) could be improved?
Maybe some kind of "official" Cake plugin and code snippet repository,
which requires authors to test components against new core versions
etc and update and develop plugin/behaviour/components code.
-J
On May 8, 4:08 pm, Smelly Eddie wrote:
> I hate that it is a powerful framework that can make the tedious work
> of developing sites a breeze. Its strict adherence to the tried and
> true MVC model is a pain point as well. Why so logical?
>
> I hate the active community involvement and powerful documentation and
> API sites. I hate that people expect Cake to do every little thing.
>
> It is a framework! Not a solve everything-all-in-one-cms-portal-file-
> manager-blog-forum.
>
> Use the framework to create an upload component, it takes all of 5
> minutes!!
>
> On May 8, 8:56 am, "Dennis S. Hennen" wrote:
>
> > Consider Post hasMany Comment
>
> > Comment->find('all') returns {n}.Comment.*
>
> > Post->find('all') gives you Comment.{n}.*
>
> > If I want a helper to do processing on a list of comments, I have to
> > handle both potential formats, or massage the data.
>
> > Related to this is the $primary parameter to the afterFind callback.
>
> > Perhaps find results as objects instead of arrays?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
+1 for a "slug" automagical field ! On 13 mai, 05:47, Reuben Helms wrote: > Cake PHP is leaps and bounds ahead of what I used to use, but I'd like to > see... > * Improved support for Search Engine Friendly URLs. There are many types of > SEF, and while there are already published versions of a few of them, I'd > like to see some core support, so that a new revision of Cake doesnt break > them. Types of SEF support I'd like to see are: > * SEF Slug additions. This is the one that usually gets used. The a > search engine friendly slug is appended to the URL. i.e. > /controller/view/1/my-content-title > * SEF Slug replacements. This is were the id gets replaced with a SEF > slug. i.e. /controller/view/my-content-title maps to /controller/view/1 > * Virtual Paths. This is where a controller/action/id gets mapped to a > virtual path. Probably the trickiest to do, and perhaps well beyond the > scope of supporting in Cake Core. The path would be mapped to a > controller/action/id on the way in, and links would be recognised and > converted on the way out. > > * Naming of helpers. Often, I need to overload the Form or HTML helper with > custom actions, or additional actions. When I do this, I have a > CustomFormHelper that extends the default FormHelper, but I then have to > reference the newer helper via $customForm. Given that I'm extending > FormHelper, and still have access to all of those functions provided to it, > I'd like to specify that $form references CustomFormHelper. Downside of > this is that the programmer becomes partially responsible for resolving for > variable conflicts if they incorrectly name something, or have a helper in > the app controller that conflicts with a helper name in the actual > controller. > > On Fri, May 8, 2009 at 8:29 AM, Nate wrote: > > > Well, maybe hate's a strong word. Let's say, what do you like the > > least? Kind of an odd question, I know, but since we've kick-started > > development of a new version, I'd like to know what the most > > frustrating things with the framework are, even if they're things we > > can't fix right away. > > > I'll get us started: PHP 4 support. > > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Cake PHP is leaps and bounds ahead of what I used to use, but I'd like to see... * Improved support for Search Engine Friendly URLs. There are many types of SEF, and while there are already published versions of a few of them, I'd like to see some core support, so that a new revision of Cake doesnt break them. Types of SEF support I'd like to see are: * SEF Slug additions. This is the one that usually gets used. The a search engine friendly slug is appended to the URL. i.e. /controller/view/1/my-content-title * SEF Slug replacements. This is were the id gets replaced with a SEF slug. i.e. /controller/view/my-content-title maps to /controller/view/1 * Virtual Paths. This is where a controller/action/id gets mapped to a virtual path. Probably the trickiest to do, and perhaps well beyond the scope of supporting in Cake Core. The path would be mapped to a controller/action/id on the way in, and links would be recognised and converted on the way out. * Naming of helpers. Often, I need to overload the Form or HTML helper with custom actions, or additional actions. When I do this, I have a CustomFormHelper that extends the default FormHelper, but I then have to reference the newer helper via $customForm. Given that I'm extending FormHelper, and still have access to all of those functions provided to it, I'd like to specify that $form references CustomFormHelper. Downside of this is that the programmer becomes partially responsible for resolving for variable conflicts if they incorrectly name something, or have a helper in the app controller that conflicts with a helper name in the actual controller. On Fri, May 8, 2009 at 8:29 AM, Nate wrote: > > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
@Smelly Eddie checked further postings! LOL
I love cakephp. In fact i have been building major projects in cake
php for last 2 years now. And mind you it has never let me down.
I had (or may have) complaints (and already covered in this post) but
every time i was able to find a quick solution for that. So its OK.
None+. :)
On May 8, 6:08 pm, Smelly Eddie wrote:
> I hate that it is a powerful framework that can make the tedious work
> of developing sites a breeze. Its strict adherence to the tried and
> true MVC model is a pain point as well. Why so logical?
>
> I hate the active community involvement and powerful documentation and
> API sites. I hate that people expect Cake to do every little thing.
>
> It is a framework! Not a solve everything-all-in-one-cms-portal-file-
> manager-blog-forum.
>
> Use the framework to create an upload component, it takes all of 5
> minutes!!
>
> On May 8, 8:56 am, "Dennis S. Hennen" wrote:
>
> > Consider Post hasMany Comment
>
> > Comment->find('all') returns {n}.Comment.*
>
> > Post->find('all') gives you Comment.{n}.*
>
> > If I want a helper to do processing on a list of comments, I have to
> > handle both potential formats, or massage the data.
>
> > Related to this is the $primary parameter to the afterFind callback.
>
> > Perhaps find results as objects instead of arrays?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
My ramblings: - Bake only accesible via command line - if this had a web gui, it'd be a real selling point for Cake, I think, and a big time saver. - ACL - needs to be simplified, at least in terms of jargon and explanation. As someone posted before, Cake seems to use the most complex terminology just for the sake of it! - declaring helpers in controllers - small point, but it always got to me that the controllers are bound to the views and vice verca in this way. VIews should be the only part of an app that know about helpers? - rename beforeFilter to beforeAction - come on, that's what it is :) - DB optimisation - as mentioned, this still isn't quite right, even though it's come on leaps and bounds with containable, ad-hoc inner joins, etc. But it could still be easier/better - more default values per model - if models had default field lists like they do order by statements etc... - More JQuery support - Categorisation of code in the bakery, for exampe, thjere ar eoften several behaviours for similar jobs, if these could all eb categorised and rated by other bakers, it would be a lot easier to choose.. On May 12, 12:44 pm, Ernesto wrote: > Some add: > > - can't overload core helpers > > On 8 Mag, 00:29, Nate wrote: > > > Well, maybe hate's a strong word. Let's say, what do you like the > > least? Kind of an odd question, I know, but since we've kick-started > > development of a new version, I'd like to know what the most > > frustrating things with the framework are, even if they're things we > > can't fix right away. > > > I'll get us started: PHP 4 support. > > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Some add: - can't overload core helpers On 8 Mag, 00:29, Nate wrote: > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
I wish a better Translate behavior! The recent one is really not great. To get all the translations for all the languages is a nightmare. The idea of http://www.palivoda.eu/2008/04/i18n-in-cakephp-12-database-content-translation-part-2/ is much better though there are some bugs in the proposed solution. Would be great to have it in Cake core. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Thanks (again) nate for this opening to the community ! My 2 cents : -> CakePHP (Several good things have already been said so I kept the most important to me) + No namespaces : CakePHP 2.0 must be PHP5.3+ + Better plugin management : dependencies management, versions, some API changes (HTMLHelper ...) to make it easier to use in plugins + Bake might permit to choose the application language + A CoffeeBehavior ... because it's a shame to not have a good coffee to go with a beautiful Cake :o) -> Community + More tolerance towards ticket openers : I saw many people totally hate you guys because their tickets go "won't fix" because a test was missing ... everyone can't spend 2 hours on a ticket, it has to be understood otherwise no more feedbacks ! + Missing a Uber-Bakery containing "official" plugins, behaviors ... with their SCM. The place where one can find the right code when he needs it. Note: it does not means that a "messy" bakery is not useful, but in my opinion the community needs a place to find the best plugins and behaviors to contribute instead of reinventing the wheel. + Less tools but more homogeneity : tools are not clear enough for newcomers (or not so good english speakers). Between thechaw, bakery, cake, cakeforge, IRC, Google group, CakePlanet (blogs), Ohloh, twitter (etc.) it's hard to follow everything without missing important announcements. + (Last but not least ^^) Include local communities for communication purposes. As one of the french community leader, I cannot read all the google groups messages or announcement or other discussions because we have our own forum with people to help, discussions, tutorials to maintain and several other things. However, it would be great if this kind of discussion was broadcasted through local communities along with announcements. PROPOSAL => send an email to each community contact (e.g cakephp-translators mailing-list) when an important announcement is made so we can transmit it to our communities. ... and my "multi-language Cake" with built-in translations ! Thanks again for this interesting discussion, I hope a summary of all these points will be communicated elsewhere. I love CakePHP and its developers, thank you for everything which has been done ... Pierre (aka real34) On 12 mai, 22:18, yodi wrote: > 1. PHP 4 Support *let's make CakePHP more fast with full PHP 5 > 2. Prototype and Scriptlous * it's better using Jquery > 3. No CounterCache HABTM > 4. Complex and heavy ACL * it's works to me but very hard for newbie > 5. Still not effective form helper html > > imagine how long code using form helper for link of image like this : > > > On Thu, 2009-05-07 at 15:29 -0700, Nate wrote: > > Well, maybe hate's a strong word. Let's say, what do you like the > > least? Kind of an odd question, I know, but since we've kick-started > > development of a new version, I'd like to know what the most > > frustrating things with the framework are, even if they're things we > > can't fix right away. > > > I'll get us started: PHP 4 support. > > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
1. PHP 4 Support *let's make CakePHP more fast with full PHP 5 2. Prototype and Scriptlous * it's better using Jquery 3. No CounterCache HABTM 4. Complex and heavy ACL * it's works to me but very hard for newbie 5. Still not effective form helper html imagine how long code using form helper for link of image like this : On Thu, 2009-05-07 at 15:29 -0700, Nate wrote: > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
There are a lot of things to like in cakephp, but if I had to say what aggravates me the most it's the seemingly wasteful and inefficient SQL calls that cake makes. The first time I turned on debug = 2 I was astounded at the close to 100 sql calls on a basic page that 1 or 2 SQL statements should have covered. It seems like when working with find queries with tables two or more levels removed from the originating model, all hell breaks loose as cake is unable to figure out JOINS more than one level deep. This also makes it impossible to set conditions on a table field that's two or more levels removed from the original. So after first learning $uses and recursive, then jettisoning that for "containable" behaviour, it turns out I have to write custom SQL queries after all as soon as my app gets a little more complicated than the beginner examples. I think there could be some major improvements there, and I understand they are on the way for v2; but I'm surprised this doesn't come up more often. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
PHP 4 support. Real use of plugins that are as easy as drag and drop. Better bakery, code is cut and pasted, why not support svn or git, preferably git for all code put on the bakery? A proper support forum, google groups is great, but the form seems to be structured in a way that many people find helpful. AJAX helper, I realize this is already in development by Mark, but thought i'd mention it anyways. JQUERY! Better template structure for baked views, i'd prefer just baking the admin, who really bakes the front end of there app anyways? (including nicely formatted views for easy jquery integration or even default integration). Regardless of the small things listed above, I wouldn't switch from cakephp in a million years. I love it, and will continue using it. Thanks for all your time and effort. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Don't quite understood... You can always unbind relationships and select the fields you want with find On May 8, 6:00 am, "gaurav.v.sharma" wrote: > if one could modify the amount of data that cake fetches during any > operation. For example the action index fetches more result than > needed thereby making the application a bit slower... > and improved tutorials on advanced techniques used in cake like acl.. > > On May 8, 3:29 am, Nate wrote: > > > Well, maybe hate's a strong word. Let's say, what do you like the > > least? Kind of an odd question, I know, but since we've kick-started > > development of a new version, I'd like to know what the most > > frustrating things with the framework are, even if they're things we > > can't fix right away. > > > I'll get us started: PHP 4 support. > > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
@Hannibal Lecter: I do use classPaths. Sometimes to achieve proximity of related MVC files for a feature of my application I have to create an 'app' for each feature; each of these apps has a complete cake application structure including config, tmp, app_controllers etc. (beside the regular, feature-related MVC folders) which is redundant. Especially the config folder may contain files which are an exact copy of the main application's config. Nesting/pushing MVC files into deeper levels in the default cake's MVC structure can help organize folders for different features BUT the proximity is lost and my files get spread out. If I want to make a single improvement / bug-fix to an existing feature I have to look / make changes in multiple places. then I cannot just simply commit/ update/deploy the a single feature folder. Instead I have to commit/ update/deploy files in different places. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Thought of another: Full Fledged Database Migrations. A lot like RubyonRails or even PHPonTrax database migrations would be ideal. There are some great addons that achieve close to this, would be great if it was fully supported in the core. Nick On May 8, 12:36 pm, nurvzy wrote: > Dislike: > PHP 4 Support. > > Wishlist: > 1) Fully functional bake console. Test controller/model code in, run > a quick function off a model, etc... extremely useful. > 2) I would love a toggle setting in the core.php for cake to return > Model Objects rather than Associative Arrays via find. > > Pled: > Please keep Ajax Helper, I use it often it. =) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Dislike: PHP 4 Support. Wishlist: 1) Fully functional bake console. Test controller/model code in, run a quick function off a model, etc... extremely useful. 2) I would love a toggle setting in the core.php for cake to return Model Objects rather than Associative Arrays via find. Pled: Please keep Ajax Helper, I use it often it. =) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
well said Smelly Eddy... perfect irony
On May 8, 6:08 pm, Smelly Eddie wrote:
> I hate that it is a powerful framework that can make the tedious work
> of developing sites a breeze. Its strict adherence to the tried and
> true MVC model is a pain point as well. Why so logical?
>
> I hate the active community involvement and powerful documentation and
> API sites. I hate that people expect Cake to do every little thing.
>
> It is a framework! Not a solve everything-all-in-one-cms-portal-file-
> manager-blog-forum.
>
> Use the framework to create an upload component, it takes all of 5
> minutes!!
>
> On May 8, 8:56 am, "Dennis S. Hennen" wrote:
>
> > Consider Post hasMany Comment
>
> > Comment->find('all') returns {n}.Comment.*
>
> > Post->find('all') gives you Comment.{n}.*
>
> > If I want a helper to do processing on a list of comments, I have to
> > handle both potential formats, or massage the data.
>
> > Related to this is the $primary parameter to the afterFind callback.
>
> > Perhaps find results as objects instead of arrays?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
I'll toss out a new one: Remove Model::recursive. All find calls would return just the model and if you wanted associated models you HAVE TO use Containable. -Matt http://www.pseudocoder.com On May 7, 6:29 pm, Nate wrote: > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
*chuckle*
my two cents is that if it doesn't do what you want it to, then
fucking code the solution for what your problem is, and then submit
patches/tests to trac.
On May 8, 7:08 am, Smelly Eddie wrote:
> I hate that it is a powerful framework that can make the tedious work
> of developing sites a breeze. Its strict adherence to the tried and
> true MVC model is a pain point as well. Why so logical?
>
> I hate the active community involvement and powerful documentation and
> API sites. I hate that people expect Cake to do every little thing.
>
> It is a framework! Not a solve everything-all-in-one-cms-portal-file-
> manager-blog-forum.
>
> Use the framework to create an upload component, it takes all of 5
> minutes!!
>
> On May 8, 8:56 am, "Dennis S. Hennen" wrote:
>
> > Consider Post hasMany Comment
>
> > Comment->find('all') returns {n}.Comment.*
>
> > Post->find('all') gives you Comment.{n}.*
>
> > If I want a helper to do processing on a list of comments, I have to
> > handle both potential formats, or massage the data.
>
> > Related to this is the $primary parameter to the afterFind callback.
>
> > Perhaps find results as objects instead of arrays?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
The existence of an AJAX helper... On Fri, May 8, 2009 at 1:45 PM, Alexandru Ciobanu wrote: > > On 05/08/2009 01:29 AM, Nate wrote: > > I'll get us started: PHP 4 support. > > > > > +1 PHP 4 > > Library independent AJAX helper (i've noticed it's under development in > the 1.3 branch) > > > > > > > > > > > -- Éber Freitas Dias www.eberfdias.com www.dejamps.net --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
On 05/08/2009 01:29 AM, Nate wrote: > I'll get us started: PHP 4 support. > > +1 PHP 4 Library independent AJAX helper (i've noticed it's under development in the 1.3 branch) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Nate, Thank you for asking for such feedback - it's very infrequent that developers ASK what people don't like, rather than just getting annoying people blabbing about what they don't like. Both situations garner great feedback, but one of the two typically give nicer, more friendly responses. :) What I don't like: ...Community: - No support "forum". I still have a perpetual license to Invision Power. If you guys want it (CakePHP team), it's yours. - No yearly "Give Back to CakePHP Day". I think it'd be nice if once a year, the Cake team made a big fuss over people donating things back to CakePHP; either monetary donations for server costs, test coverage, tutorials/articles, or code. - No web-based chat connection to IRC (can be helpful, but not necessary) Bug Reporting: - Requiring tests submitted on all bug reports. I know I've found a bug, but I've been unable to create a functional test report, and as such my report was closed. I'm still working on trying to figure it out, but it's almost been 6 months, and (what I believe to be) the bug still exists. I also understand WHY this was incorporated, but if something's very easily reproduced with instruction, is the test case truly necessary? Cake Bake: ...don't get me wrong, I LOVE the bake tool, but... - No skeleton behavior, plugin, component, helper options in the creation tool - No conventions on shell-based output formatting and maximum character line length (shell output helper?) Miscellaneous: - PHP4 support: I don't know of any companies right now that can't handle upgrading to PHP5. I remember hearing about a fork and then phase-out of PHP4 code, but sooner rather than later would be great. - Difficult to define configurations for different hosts (dev, test, production); I believe Rails supports this, we do have Fredistrano though - No timezone setting in configuration for PHP's date_default_timezone_set() which could (potentially) alleviate many confused users getting "incorrect" times in their created/updated fields Thanks CakePHP team! On May 7, 6:29 pm, Nate wrote: > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Nothing I hate but one thing I find is really lacking, one that would
facilitate sharing code (pl and one that would ease development.
Really lacking to me are objects for objects instead of arrays in the
models, for example a People->find('all') would return objects on
which you can call methods : $person->fullName(). It's currently the
only thing I find is a real problem when your app starts growing and
you add more logic in your models. Currently if you need to manipulate
your data before displaying you have to either do it in the view which
is ugly or find a way to pass your data array back to a model static
function, determine if you got all the data you need in the given
array and return you result.. Considering find methods return the data
in a different form depending on wether you did a find('first') or find
('all'), how the models are linked, or the fact that you could just
have an id and not the full data it's quite a pain. Felix's
AppModel::normalize (http://debuggable.com/posts/normalizing-cakephp-
model-records:48b7ed7f-9498-4b9c-8734-6f014834cda3) is a clever way to
do it and what I use right now but I think objects are the right next
step to clean code and reusability.
What would facilitate sharing code is a simplification of plugin
system, right now it works but is a bit complicated to set up and use,
which I think explains the relatively low amount of plugins available
on the Bakery and elsewhere. Compare this to the Rails world where
virtually every shared code is in plugin form : it's easy to integrate
in your app and stay up to date with a simple svn:externals or git
submodule. When you grab a component or datasource on the bakery you
have to copy and paste it in your app and updating later is kinda
difficult, especially if you use it in several apps. Having easy to
create and use plugins would facilitate the sharing of code and I
think speed up the growth of the framework's ecosystem. I guess this
plugin thing ain't that easy because as far as I know PHP lacks the
module system from Ruby which lets you inject code into existing
classes, easing the creation of plugins that can do almost anything.
But maybe there's another solution to that or the new namespaces will
help.
Last thing I think would help greatly is a full fledged console in
which you can instanciate objects, test your models and controllers
without the need to debug() and log() in a view. You can already do
cool stuff with the actual console but for example you can't (or I
don't know how) test a model method or a save, you can only do finds.
I use this all the time when working with Rails (I use both
frameworks) and it's really nice to quickly check something in your
code.
Well besides those that's all, nothing to hate about Cake really it's
an awesome tool. Thanks for gathering feedback, looking forward to see
what's coming out of all these ideas people post.
Do you plan on posting the results somewhere so we can grab stuff we
really care about and work on integrating it once it's been decided it
would be added to the core ?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
PHP4 support Not able to delete entire namespace from cache 1.2 seems a bit slow from time to time compared 1.1 More documentation on more advanced things would be nice On May 8, 12:29 am, Nate wrote: > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
what a brave topic - i like it, nate!
On May 8, 2:56 pm, "Dennis S. Hennen" wrote:
> Consider Post hasMany Comment
>
> Comment->find('all') returns {n}.Comment.*
>
> Post->find('all') gives you Comment.{n}.*
>
> If I want a helper to do processing on a list of comments, I have to
> handle both potential formats, or massage the data.
- This on is an issue for me as well.
- i have no problem with php4 support but as well didn't need it so
far
- i would wish more extensive ajax-js-clientside-mvc support (but is
probalby a js-framework issue)
- man, i have to think hard, it's just great :-) and I'm sure, you
will come up with great features!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
BIG HATRED:
++1 @ Park/dr. Hannibal Lecter: Ignoring callbacks on associative
queries (See also the associated ticket: https://trac.cakephp.org/ticket/2056
)
That ticket should have high severity and priority
Hoping for:
+ var $displayField only taking one field.
Better would be something like var $displayField = array
('%ModelA.fieldname1 foo %AssocModelB.fieldname2 bar
%fieldnameofThisModel3!') or alike. Additionally overwriting/creating
function displayField() { ... } should be a callback that gets called
(and maybe even cached) when a displayField is requested which could
allow complex displayFields very easily.
+ 2.0 going straight for PHP 6.x or at least 5.3+
Minor annoyances:
+ View Helper not being extendable / mixinable (there are dirty
solutions available though) - like you want to extend html helper and
still use $html->foobar in views.
+ View folder (/app/views) merging on standard view "routes" and
elements (what if you have a model Element and ElementsController - or
LayoutController) and layouts
+ Standard controller routes sharing one namespace with webroot/*
(lets say you have an UploadsController and an /app/webroot/uploads
directory, ... bad)
+ Cake Bake not offering standard solutions for trees and self-joins /
recursive structures that work out of the box
+ PolymorphicBehavior not in core
+ Cake Bake teaches (and does rightly so) many people how to work with
cake => Cake Bake output not using elements (but could be used alot to
reduce code size)
+ Cake Bake not using jQuery. A standard (cake bake default) template
could help for acceptance/hype of cakephp like "whoot in that short
time I made that fancy thing". Return on error validation could use
ajax, paginator could use ajax (for pages and sorting)
Loves:
Documentation, its awsome, cakebook is godly, both, what is there and
that you can extend but that it gets reviewed before, its just how it
should be. I can whole-heartly tell customers: If I die you can get an
upper average php developer, give him this CD with all the sources and
he can learn into cakephp no problem and extend and maintain the
application. Love you guys!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
You can write AppController method to load comonent and call Component::startup and initialize, but proper loading on the fly is not possible by cake design: - initialize is called before Controller:beforeFilter(); (before any controller code) I'm not sure why some one needs additional callback fired before "beforeFilter"? Is there any example where code in component needs to be executed before Controller::beforeFilter? tnx. On May 8, 9:37 am, Alberto Pagliarini wrote: > Simple way to initialize a component on the fly. > > ClassRegistry::init is very useful for model... I'd like it (or > something similar) works with component > > -- > -- bato --- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
My biggest request: Think outside the blog tutorial!! A lot of the supporting components work great in the context of a very simple, one controller for one model with 4 actions for CRUD setup, but become impractical or impossible to use outside that. The ACL component is probably the biggest offender of this. So many people have problems with ACL because none of the built-in ACL schemes actually work in the real world. Also the query load is immense - why can't the ACL component pull down an entire tree branch in one query (you use MPTT, so this is pretty easy), then post-process it instead of running a query for every node? Once your tree gets to be of any real size, your application gets crippled under dozens (if not hundreds) of ACL queries. In a large application my company just built, we had to roll our own ACL component for role based permissions because the ACL component simply couldn't do it. We pull down the permissions a branch at a time, and cache them per role. There may be up to 15 ACL checks done in a single action (with full CRUD). If we were to use the built-in ACL check method, we'd be running 15 x 4 checks (one CRUD item at a time). Multiply THAT by a query for every node it has to go down and you can quickly see how this gets out of control. You could say this is way outside the scope of what the ACL component was intended to do, and that's totally fair. My argument is that the ACL component simply doesn't work in any real world scenarios and as such causes an immense amount of grief for people trying to learn how to leverage it in their own applications. I see very confused people post on here every day about ACL and most times, unless they're willing to roll their own ACL component, they're stuck. You'd almost be better off without it. The ORM has issues with being tailored to the blog tutorial as well. Another big issue people seem to have is with HABTM relationships and the inability to direct Cake's use of joins. Once you're forced to fall back to hand-written queries, you lose all the useful callbacks. There must be some middle ground here - even if it means writing your queries in a way Cake can parse and understand. Beyond those sorts of things, Cake remains my framework of choice. All in all, it is EXTREMELY flexible and consistently saves me months of development time. Any issues I can bring up could be considered minor gripes when compared to what Cake DOES get you. Cheers and thanks for your hard work and continued dedication to this project. This is a huge service to PHP developers everywhere. Don't let the whiners get to you ;) - James On May 7, 6:29 pm, Nate wrote: > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
If I understand correctly, what you're looking for can be easily
changed with the "recursive" property of a model.
For example, in the index action of my Products controller, I do
something like this:
function index () {
$this->Product->recursive = 0;
//rest of the code here...
}
The higher the value you asign to this property, the deeper the level
of records Cake will fetch.
On 8 mayo, 08:00, "gaurav.v.sharma" wrote:
> if one could modify the amount of data that cake fetches during any
> operation. For example the action index fetches more result than
> needed thereby making the application a bit slower...
> and improved tutorials on advanced techniques used in cake like acl..
>
> On May 8, 3:29 am, Nate wrote:
>
> > Well, maybe hate's a strong word. Let's say, what do you like the
> > least? Kind of an odd question, I know, but since we've kick-started
> > development of a new version, I'd like to know what the most
> > frustrating things with the framework are, even if they're things we
> > can't fix right away.
>
> > I'll get us started: PHP 4 support.
>
> > Who's next? TIA for the input.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
I hate that it is a powerful framework that can make the tedious work
of developing sites a breeze. Its strict adherence to the tried and
true MVC model is a pain point as well. Why so logical?
I hate the active community involvement and powerful documentation and
API sites. I hate that people expect Cake to do every little thing.
It is a framework! Not a solve everything-all-in-one-cms-portal-file-
manager-blog-forum.
Use the framework to create an upload component, it takes all of 5
minutes!!
On May 8, 8:56 am, "Dennis S. Hennen" wrote:
> Consider Post hasMany Comment
>
> Comment->find('all') returns {n}.Comment.*
>
> Post->find('all') gives you Comment.{n}.*
>
> If I want a helper to do processing on a list of comments, I have to
> handle both potential formats, or massage the data.
>
> Related to this is the $primary parameter to the afterFind callback.
>
> Perhaps find results as objects instead of arrays?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Simple way to initialize a component on the fly. ClassRegistry::init is very useful for model... I'd like it (or something similar) works with component -- -- bato --- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
I don't like: - PHP4 support - PHP4 support (I hate it so much) - AjaxHelper (it's existence, without it we will have a lot less traffic on this mailing list) - Too deep nesting of search results in some querys, but I can't figure a way of using arrays and make it not so deep Regards, - Dardo. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Consider Post hasMany Comment
Comment->find('all') returns {n}.Comment.*
Post->find('all') gives you Comment.{n}.*
If I want a helper to do processing on a list of comments, I have to
handle both potential formats, or massage the data.
Related to this is the $primary parameter to the afterFind callback.
Perhaps find results as objects instead of arrays?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Agree: - php4 support++ - upload++ - callbacks on associative queries++ Also: - saveAll() limitations (currently limited to one level deep) - more configurability - eg. configure which controller subfolder a particular controller/model is located in (currently has to search through all folders in $controllerPaths bootstrap variable, takes unnecessary time) - js, css minification/compression, packing, gzipping - debugKit in core (or similiar) - gzip ... Thanks for involving everyone in the brainstorming. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Good initiative ! This poll has been relayed on the french forum (http://forum.cakephp- fr.org/viewtopic.php?pid=3340). I'll send you a summary in the next few days ! Pierre On 8 mai, 14:28, jstein wrote: > On May 8, 10:39 am, Affinity > wrote: > > > Lack of a good, proper support forum. > > I'll vote for that too. I would surely be more active, if the forum > had an NNTP-interface. > > Regards > > Jonathan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
- saveall not recursive besides first level - too complex ACL mangement - broken IniAcl ( https://trac.cakephp.org/ticket/6103 ) - sometimes poor documentation -- pietro --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
On May 8, 10:39 am, Affinity wrote: > Lack of a good, proper support forum. I'll vote for that too. I would surely be more active, if the forum had an NNTP-interface. Regards Jonathan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
- Lack of support forum On 8 Mag, 00:29, Nate wrote: > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
if one could modify the amount of data that cake fetches during any operation. For example the action index fetches more result than needed thereby making the application a bit slower... and improved tutorials on advanced techniques used in cake like acl.. On May 8, 3:29 am, Nate wrote: > Well, maybe hate's a strong word. Let's say, what do you like the > least? Kind of an odd question, I know, but since we've kick-started > development of a new version, I'd like to know what the most > frustrating things with the framework are, even if they're things we > can't fix right away. > > I'll get us started: PHP 4 support. > > Who's next? TIA for the input. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Vote ++ for more complete documentation
On Fri, May 8, 2009 at 11:46 AM, majna wrote:
>
> Habtm implementation:
> Model::_deleteLinks($id)
> "Cascades model deletes through HABTM join keys."
>
> I just found out reason why some records gets randomly deleted from
> habtm:
> cake ignores 'condition' filed in habtm assocciation definition.
> example:
> var $hasAndBelongsToMany = array(
> 'Tag' =>
> array('className' => 'Tag',
> 'joinTable' => 'content_tags',
> 'foreignKey' => 'content_id',
> 'associationForeignKey'=> 'tag_id',
> 'conditions' => "content_type='News'",
> ..
> Now, cake will use 'condition' to find results,
> but ignore when deleting!
>
> So if you have (in this example) tags for Video,Product,Photo..,
> by deleting News with id=1,
> cake will delete tags for Product id=1, Video id=1.. and so on.
>
> Delete is often followed by redirect to referrer and hard to debug
> sql.
>
> This miss-behavior is in cake 1.x, and, as I can see, in 1.2.x.
> You can define 'deleteQuery'=> '' in habtm assocciation but why?
>
> @nate should I open ticket for this?
>
>
> On May 8, 12:29 am, Nate wrote:
>> Well, maybe hate's a strong word. Let's say, what do you like the
>> least? Kind of an odd question, I know, but since we've kick-started
>> development of a new version, I'd like to know what the most
>> frustrating things with the framework are, even if they're things we
>> can't fix right away.
>>
>> I'll get us started: PHP 4 support.
>>
>> Who's next? TIA for the input.
> >
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
Re: Poll: what do you hate about CakePHP?
Habtm implementation:
Model::_deleteLinks($id)
"Cascades model deletes through HABTM join keys."
I just found out reason why some records gets randomly deleted from
habtm:
cake ignores 'condition' filed in habtm assocciation definition.
example:
var $hasAndBelongsToMany = array(
'Tag' =>
array('className'=> 'Tag',
'joinTable'=> 'content_tags',
'foreignKey'=> 'content_id',
'associationForeignKey'=> 'tag_id',
'conditions'=> "content_type='News'",
..
Now, cake will use 'condition' to find results,
but ignore when deleting!
So if you have (in this example) tags for Video,Product,Photo..,
by deleting News with id=1,
cake will delete tags for Product id=1, Video id=1.. and so on.
Delete is often followed by redirect to referrer and hard to debug
sql.
This miss-behavior is in cake 1.x, and, as I can see, in 1.2.x.
You can define 'deleteQuery'=> '' in habtm assocciation but why?
@nate should I open ticket for this?
On May 8, 12:29 am, Nate wrote:
> Well, maybe hate's a strong word. Let's say, what do you like the
> least? Kind of an odd question, I know, but since we've kick-started
> development of a new version, I'd like to know what the most
> frustrating things with the framework are, even if they're things we
> can't fix right away.
>
> I'll get us started: PHP 4 support.
>
> Who's next? TIA for the input.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
