I used basic URL parameters just as you would any other URL options array.
*$this->Paginator->options(array('url'=> array('controller' => 'users',
'action' => 'index', 'plugin' => 'user_manager')));*
*
*
It gets set in the view, I just added it in with the rest of the paging
options (numbers, next
What options did you end up using?
On Tuesday, October 29, 2013, Ed Propsner wrote:
> I was able to work everything out using $this->paginator options(). I
> appreciate the help :)
>
>
> On Mon, Oct 28, 2013 at 2:17 AM, Ed Propsner wrote:
>
> You're absolutely right, I was definitely confusing t
I was able to work everything out using $this->paginator options(). I
appreciate the help :)
On Mon, Oct 28, 2013 at 2:17 AM, Ed Propsner wrote:
> You're absolutely right, I was definitely confusing the two. I suppose
> that I'm so used to referencing the plugin as camel-case everywhere else
>
Why not making this a clean component or custom View class, e.g.
SerializeView etc?
Hacking this in the AppController (which should stay lean) doesnt sound
right to me.
Also, re-usability is not very good this way.
And don't use private, use protected :P
Am Montag, 28. Oktober 2013 01:50:38 UT
No question here, just thought I'd share a solution to a problem I needed
to solve.
I'm working on a decoupled application where the back-end is all CakePHP
and the front-end is all Javascript. The front-end communicates with the
back-end as a RESTful API. I could write a handful of posts in he
