# |
Aug 7th 2008, 22:29 |
Jonah |
am i missing something? |
# |
Aug 7th 2008, 22:28 |
Jonah |
this means that you have to manually check that all the fields were passed? |
# |
Aug 7th 2008, 22:28 |
Jonah |
uhh... |
# |
Aug 7th 2008, 22:26 |
Jonah |
it should not return true if not all the required fields are passed to it |
# |
Aug 7th 2008, 22:26 |
Jonah |
why is validates() not validating fields that are not passed to it? this is a security hole |
# |
Aug 7th 2008, 22:19 |
cobol |
well, we'll see |
# |
Aug 7th 2008, 22:19 |
cobol |
yeah. question is if it will remember it if I had get parameters up in the url |
# |
Aug 7th 2008, 22:18 |
markstory |
paginator remembers sort and such. |
# |
Aug 7th 2008, 22:18 |
markstory |
try it find out :) |
# |
Aug 7th 2008, 22:18 |
cobol |
will go away |
# |
Aug 7th 2008, 22:18 |
cobol |
one or the other, either the parameters or the page result |
# |
Aug 7th 2008, 22:18 |
cobol |
but i imagine as soon as i hit submit, or change pages, |
# |
Aug 7th 2008, 22:18 |
cobol |
with a submit action, to filter the properties |
# |
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? |