Re: Defining Plugin

2013-10-28 Thread Ed Propsner
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 within the app and since functions are camel-case and they are referenced as such in the URL, it wasn't a far stretch to make the mistake of constructing

Re: Defining Plugin

2013-10-28 Thread Ed Propsner
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 crotchf...@gmail.com 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

Re: Defining Plugin

2013-10-28 Thread Reuben Helms
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 crotchf...@gmail.com wrote: You're absolutely right, I was

Re: Defining Plugin

2013-10-28 Thread Ed Propsner
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,

Re: Defining Plugin

2013-10-27 Thread CrotchFrog
I did find one place so far that this problem with plugin names is creating an issue whereas I feel that it should not be. Working with a table (in a plugin) I define a heading as *$this-paginator-sort('username', 'Username'); *which in turn creates the link as a

Re: Defining Plugin

2013-10-27 Thread Reuben
I've never used pagination for a plugin in before, but I'm guessing specifying the plugin for the model would be required. i.e. $this-paginator-sort('username', 'Username', array('model'='SomePlugin.Model')); Though I guess with doing that, there would have to be an assumption that the model

Re: Defining Plugin

2013-10-27 Thread euromark
Yes, I guess you have been creating non-conventional links so far. Mainly because you are confusing framework internal naming schemes with URL naming scheme The latter defines everything underscore_lowercased, even the plugin. The first refers mainly to classes, which will always be named

Defining Plugin

2013-10-25 Thread CrotchFrog
I've noticed recently some strange behavior when it comes to naming conventions and Plugins. For example if I create a link somewhere within a plugin ie. *$this-Html-link('Some Link', array('controller' = 'controller', 'action' = 'action')); * Following the link would land you on the page