Yes, that's correct. It now uses a period instead of a slash.
On Tue, Jul 1, 2008 at 1:50 PM, Bryan D <[EMAIL PROTECTED]> wrote:
>
> Thanks guys, that works perfectly. I take it the Player.id form is
> now preferred over Player/id ? I ported my app from Cake 1.1 to 1.2,
> and probably missed a f
Thanks guys, that works perfectly. I take it the Player.id form is
now preferred over Player/id ? I ported my app from Cake 1.1 to 1.2,
and probably missed a few things.
On Jun 30, 4:41 am, "Jonathan Snook" <[EMAIL PROTECTED]> wrote:
> On Sun, Jun 29, 2008 at 6:19 AM, Mr. Matt <[EMAIL PROTECTED]
On Sun, Jun 29, 2008 at 6:19 AM, Mr. Matt <[EMAIL PROTECTED]> wrote:
>
> I believe this should work:
>
> input('Player/id', array('type' => 'text')); ?>
Just to clarify, it's Player.id (notice the . instead of the /)
--~--~-~--~~~---~--~~
You received this message
I believe this should work:
input('Player/id', array('type' => 'text')); ?>
On Jun 27, 5:54 pm, Bryan D <[EMAIL PROTECTED]> wrote:
> I would like to allow a model's primary key field (named id) to be
> editable, at least upon creation of a new object. I noticed that using
> syntax like:
> input
I would like to allow a model's primary key field (named id) to be
editable, at least upon creation of a new object. I noticed that using
syntax like:
input('Player/id') ?>
doesn't work because CakePHP converts it to a hidden field
automatically. Is there some way I can override this?
I worked