| # |
Aug 7th 2008, 22:18 |
cobol |
i'd have a form there |
| # |
Aug 7th 2008, 22:18 |
cobol |
well |
| # |
Aug 7th 2008, 22:17 |
markstory |
use dogpoo => smelly |
| # |
Aug 7th 2008, 22:16 |
cobol |
what i can't find anywhere is how to pass the parameters int he URL |
| # |
Aug 7th 2008, 22:16 |
cobol |
i understand how to add the parameters to the query |
| # |
Aug 7th 2008, 22:13 |
markstory |
cobol: look up making custom paginators. it can be done. |
| # |
Aug 7th 2008, 22:12 |
markstory |
for what? |
| # |
Aug 7th 2008, 22:12 |
Snapp |
markstory: whats the convention for cake tho.. I have a feeling its camelCased. |
| # |
Aug 7th 2008, 22:11 |
cobol |
it's not possible to pass a parameter and still retain pagination's parameters???? |
| # |
Aug 7th 2008, 22:11 |
markstory |
perhaps some custom work. |
| # |
Aug 7th 2008, 22:11 |
cobol |
since pagination has all that muck up there |
| # |
Aug 7th 2008, 22:11 |
cobol |
i'm not sure how to pass the parameters |
| # |
Aug 7th 2008, 22:11 |
cobol |
but |
| # |
Aug 7th 2008, 22:10 |
cobol |
yes i get that |
| # |
Aug 7th 2008, 22:10 |
markstory |
in your conditions. |
| # |
Aug 7th 2008, 22:10 |
markstory |
use 'BETWEEN ? AND ?' => array(date1, date2); |
| # |
Aug 7th 2008, 22:10 |
markstory |
cobol: I heard of this thing called php, you could program it in :) |
| # |
Aug 7th 2008, 22:06 |
cobol |
so if i have a paginated view, how would i go about setting up something like 'only show records created between these dates' |
| # |
Aug 7th 2008, 22:05 |
markstory |
lqdice__: I dunno, about finding out what field. |
| # |
Aug 7th 2008, 22:04 |
lqdice__ |
or perhaps have it print out which fields its checking for and which its been submitted |
| # |
Aug 7th 2008, 22:04 |
lqdice__ |
markstory: is it possible to know which field ? |
| # |
Aug 7th 2008, 22:04 |
markstory |
hash of fields is wrong. |
| # |
Aug 7th 2008, 22:04 |
lqdice__ |
markstory: anyway to see why the security component is not letting my form submit ? |
| # |
Aug 7th 2008, 22:02 |
Jonah |
hmm k |
| # |
Aug 7th 2008, 22:01 |
markstory |
Jonah: set a more complete validation rule, I would think. |
| # |
Aug 7th 2008, 22:01 |
markstory |
) |
| # |
Aug 7th 2008, 22:01 |
markstory |
its in Model::invalidFields() though! |
| # |
Aug 7th 2008, 22:01 |
Jonah |
appmodel? |
| # |
Aug 7th 2008, 22:01 |
Jonah |
how can I change them? |
| # |
Aug 7th 2008, 22:01 |
markstory |
Jonah: I don't know off the top of my head. :) |
| # |
Aug 7th 2008, 22:01 |
markstory |
Snapp: I do camelcased. |
| # |
Aug 7th 2008, 22:01 |
Jonah |
what are the defaults for validation? |
| # |
Aug 7th 2008, 22:00 |
markstory |
it merges the simple regex with the defaults for validation which have required == true. |
| # |
Aug 7th 2008, 21:59 |
markstory |
Jonah: not a bug. |
| # |
Aug 7th 2008, 21:54 |
Snapp |
What is the convention for function names in controllers? |
| # |
Aug 7th 2008, 21:53 |
stabb |
jerryleeeeeeeeeee |
| # |
Aug 7th 2008, 21:53 |
Jonah |
'rule' => VALID_EMAIL, causes it to think it is required |
| # |
Aug 7th 2008, 21:53 |
Jonah |
This I found a bug |
| # |
Aug 7th 2008, 21:52 |
Jonah |
nvm |
| # |
Aug 7th 2008, 21:52 |
jerrylee |
and what if i did want it to redirect to listing()? |
| # |
Aug 7th 2008, 21:52 |
Snapp |
The Conventions for controller function names is camelCased? |