Hey Annie, I had similar problems when I started and still have
problems sometimes (although less often now) regarding where things go
and try to stick to the MVC architecture. This is sort of what i think
about when i have this problem.
1. If i am doing a complicated query (more than one conditi
Thanks again,
It's starting to make sense now -- switching views depending on the
result of the validation wasn't something I was really contemplating
but I see how that would be a cleaner solution. I may be on IRC later
to confirm my understanding!
Much appreciated.
On May 1, 10:10 am, "Marcin
if you do it my way - the error message from the validate array will
be put under the dropdown on the same page.
in the action there would be something similar to bake generates but
with $this->Model->validates() iinstead of save()
if it valdiates - show the other view with the table
you can come
Thanks for the quick reply.
I'm not sure whether that solves my problem: I'm okay with selecting
which output to produce, my problem is in the construction of the
books table/warning message. Where does this occur?
What I've got at the moment is something like this in the view:
if(!$showtable)
Hey,
>From what you said you want to make a validation rule like >0 (if 0 is
the value of ---please select a genre---) and Model::validate() it
(you probably dont want to save it), if it valdiates - show the books
On Thu, May 1, 2008 at 9:54 AM, annie.r.knight
<[EMAIL PROTECTED]> wrote:
>
> ...
... at least I hope it's simple for you guys. Clearly it's not simple
for me otherwise I wouldn't be asking here. I'm using 1.2.
I'm trying to get the structure of my app 'right' in terms of MVC
execution flow (and CakePHP's implementation of this flow). Here's my
situation:
I've got a page wher
