Edit resets todays date

[Alan_uk]

I have a date field and when it displays on the Edit page the current value is replaced by today's date. Is there anyway to stop this?

A user may well be changing another field and not realise that the date field has been reset.

On the Add page it's fine to have today's date.

using
Catalog 2.0.0 beta1 33
and just in case Catalog uses feedit
feedit 0.1.0 beta1 15

[MacKP]

Hi Alan_uk,
normaly that is not what the catalog is doing...
What have you made for settings at the Edit-Modul?
Is there a restirction you set?

And: catalog Build is now higher than yours (try an update)

And:
What are you doing with feedit 0.1.0 beta1 15 thats nothing fron the catalog i think. The catalog has his own Frontend Editing Modules...

regards

[Alan_uk]

Hi Alan_uk,
What have you made for settings at the Edit-Modul?
Is there a restirction you set?

Hi MacKP. Many thanks for responding.

Edit Module is set:
Module Type: Catalog Edit
Catalog: FoBMCP Spotted
Editable Fields [ticked] Date Spotted [date_spotted:date]
+ other fields
Redirect page: Detail - that works OK
Disable the security question: [ticked]
Catalog layout: catalog_edit
Catalog template: mod_catalogedit
Protect Mode: [ticked] FoBMCP Spotters
CSS ID/class: FoBMCP_Edit
Restricted fields: None

I updated to latest:
Update catalog 2.0.0 beta1 build 43
1 file(s) updated
129 file(s) unchanged
Actions successful.
Update DC_DynamicTable 0.1.0 stable build 17
1 file(s) unchanged
Actions successful.

I uninstalled feedit just in case (it is an extension to forms)

The problem is still there!

[MacKP]

Hi Alan_uk,
I see your Problem in an Test installation...
Can you make a Ticket for that -> http://code.google.com/p/typolight-catalog/issues

Thanks and regards

[Alan_uk]

Hi Alan_uk,
I see your Problem in an Test installation...
Can you make a Ticket for that -> http://code.google.com/p/typolight-catalog/issues

Done. Maybe I should have added to the ticket that this error is stopping deployment of the application. I hope it is an easy problem to fix. I suspect it's the calendar widget that is over writing the form field value from the database