Why not just make it hidden?

On Mon, Mar 2, 2009 at 11:01 AM, FranktheTank
<frankbirchstu...@gmail.com> wrote:
>
> @CraigFisher: I ended up going readonly too - using the field as
> disabled was not quite as intuitive as I was hoping.  It wasn't any
> harder and selecting it for styling it was easy.
>
> @mscdex: I was looking for a generic form related attribute.  id would
> be a better example than width, but there's probably an option in the
> options array for setting the id.  Perhaps a rel attribute or
> something like that - I can't think if rel is allowed in an input tag,
> but I think you get the idea.
>
> Thanks all!
> Frank
>
>
> On Feb 18, 4:05 am, CraigFisher <crayfis...@gmail.com> wrote:
>> I got caught by the phantom data loss:  the $data array after POSTing
>> doesn't contain the all the fields from the Model->read; only those
>> that aren't disabled - so if you fail validation, and theformis
>> redisplayed, the data which was originally populated via the Model-
>>
>> >read will have lost the fields which were disabled.
>>
>> Readonly and css was the way that I used... otherwise you can't use
>> the 'Input' styling for consistent looks & view code.
>>
>> -C
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to 
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to