Thank you Sam! I'll use the route. Cheers
On 30 jul, 17:42, Sam Sherlock <[email protected]> wrote: > For an easier life I would stick with conventions and set the route cal to > route to the CalsController > > Router::connect('/cal', array( > 'controller' => 'cals', > 'action' => 'index')); > > but you can have the model useTable an 'some_unconventional_name' > with the following in the model > public $useTable = 'cal'; > > - S > > On 30 July 2011 23:43, Roland Pish <[email protected]> wrote: > > > > > > > > > I have a model named "Cal". I wanted its table name to "cal" (not > > "cals"). > > > Now, I would like that its controller could be accessed as: mysite.com/ > > cal/* <http://mysite.com/%0Acal/*> (and avoid being accessed as > > mysite.com/cals/*). > > > A plus would be that I can declare the controller as: class > > CalController extends... > > > Is this possible? > > > Thanks in advance. > > > -- > > Our newest site for the community: CakePHP Video Tutorials > >http://tv.cakephp.org > > Check out the new CakePHP Questions sitehttp://ask.cakephp.organd help > > others with their CakePHP related questions. > > > To unsubscribe from this group, send email to > > [email protected] For more options, visit this group > > athttp://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
