I'm quite new to cakephp, I made a few sample apps and I was really
impressed by the quality of the framework. Therefore I decided to use
it on a real application: a blog with a voting system. Really
simple...
I tried to make a list of posts, with the number of votes and rank of
each one, and I found the first problem: It didn't work , and after
hours of searching and thanks to the comunity (http://
groups.google.com/group/cake-php/browse_thread/thread/
4b1351b60bb2093f), I found I had to use the linkable behaviour, which
is not included on the framework. That's a bit weird, because my
problem was absolutely trivial... however I don't consider it to be a
problem of the framework at all, au contraire, as long as I can solve
it using the external behaviour, the modular architecture of cakephp
make this solution very usable.

The real problem came when I tried to sort the paginated results by an
aggregated value, like the number of votes of each post, the solution
was... to either modify the framework's core OR to incur in design
errors by creating a field in the database for the aggregated value
(https://trac.cakephp.org/ticket/5220)(http://groups.google.com/group/
cake-php/browse_thread/thread/be2b28b177da3339) Both solutions are
obviously unacceptable.

As much as I like cakephp, specially it's QA policy, I'm frightened by
finding all these problems on such an easy app, and so my question is:
Am I just being unlucky? or maybe Is not cakephp what I need? or maybe
there are trivial solutions for my problems, only that I failed to
find them?

Thank You.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to