I think I understood your problem, but you have to pass the parameters
to the paginator helper somehow in order to see them in the pagination
links.

Named params is just the way I know it works, and it's also the way
the page parameter is handled.

The only thing you have to do in your controller, is to check the GET
params for the case the form has been sent, and also check the named
params for the case a pagination link has been taken.

Your main problem seems to be that you want the urls to look the same
for both cases, but after a look into the paginator-helper, I don't
think it is possible. Even if you set the option to array('url' = '?
where='.$city.'&name='.$name) the paginator will make /?
where=london&name=blabla/page:2 out of it.

Maybe you find another way, otherwise you should use the compromise
before you start the dirty tricks. ;-)

Michael


On 4 Sep., 01:06, Jaime <[EMAIL PROTECTED]> wrote:
> Thanks schneimi, but I'm already familiar with named parameters. The
> problem is that after submiting a HTML form where data is passed by
> GET,  you are driven to a new url with the query string  (/?
> param=value) instead of a nice named-params one (/param:value).
>
> Of course I can force a redirect to rewrite the url, but this seems a
> dirty trick.
--~--~---------~--~----~------------~-------~--~----~
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