Hi Armando, I was hoping to update the code to permit this (and demonstrate why I don´t think it's a good idea in many cases) yesterday, but didn´t get time to do it yet.
I see a number of problems in it´s use: 1) If you paginate /Controller/ - then the action will become "page", "show" etc. If you paginate the home page the controller becomes "page", "show" etc. 2) Would eliminate the possibility to use the parameters show, page, direction (and others, but these are the interesting ones). 3) How to successfully paginate /Controller/Action/Param aswell as /Controller/Action/Param1/Val1 The beauty of using GET data, especially in the mode that it is employed is that it doesn´t interfere or need to care what the current url is, but it shouldn´t be too difficult to modify such that the component can accept an array of values and if present, use that instead of looking GET data (and modify the links accordingly). In any case, thanks for your comment :) Cheers, AD7six --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
