That's a valid consideration, but yes, if I enabled that field to be
populated based on another field, I would expect it to change regardless of
it was a add form or a change form. The attribute doesn't read
"sometimes_prepopulate_fields". Nor does it read
"always_prepopulate_fields" for that mat
On Sep 30, 9:27 pm, "Keith Eberle" <[EMAIL PROTECTED]> wrote:
> Yea... I didn't know for sure, but I thought it used to. That's why I
> asked. I wonder why that functionality wasn't there by default...
Because in many cases it would be a usability problem. What if you've
manually adjusted the
Yea... I didn't know for sure, but I thought it used to. That's why I
asked. I wonder why that functionality wasn't there by default...
keith
On Tue, Sep 30, 2008 at 9:22 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 30, 2008 at 2:41 PM, lingrlongr <[EMAIL PROTECTED]>wrote:
>
>>
>
On Tue, Sep 30, 2008 at 2:41 PM, lingrlongr <[EMAIL PROTECTED]> wrote:
>
> Before the new forms and admin came, I could've sworn that the
> prepopulate_from (now prepopulated_fields) stuff worked when creating
> a new object in the admin, __AND__ when you edit an existing object.
>
> Can someone c
Before the new forms and admin came, I could've sworn that the
prepopulate_from (now prepopulated_fields) stuff worked when creating
a new object in the admin, __AND__ when you edit an existing object.
Can someone confirm if this should work for editing objects too?
Currently, it does not.
Keith
5 matches
Mail list logo