Hi Jean
since our database is using European date format, I've installed your TransformDateInput plugin. I've seen that it has a hook for add_records and it works perfectly for the add_record form.
I've been wondering if the plugin could be "enriched" so that it also works for the modify_record form
. I see the following difference to the add_record hook: in the beginning, the date format stored in the database has to be converted to the European format (the date must be displayed in the correct format on the modify_record form -> <%GT::Date::date_transform($datefieldname,'%yyyy%-%mm%-%dd%','%dd%.%mm%.%yyyy%')%>) before it will be submitted back to the database and converted again (after the record modification). This means that the plugin should be able to do a two-way operation instead of a one-way operation. It would be nice if the plugin could handle both ways for the modify_record hook (otherwise, I would have to use the code mentioned above directly in the template).
Thanks for your help,
Oliver
since our database is using European date format, I've installed your TransformDateInput plugin. I've seen that it has a hook for add_records and it works perfectly for the add_record form.
I've been wondering if the plugin could be "enriched" so that it also works for the modify_record form
. I see the following difference to the add_record hook: in the beginning, the date format stored in the database has to be converted to the European format (the date must be displayed in the correct format on the modify_record form -> <%GT::Date::date_transform($datefieldname,'%yyyy%-%mm%-%dd%','%dd%.%mm%.%yyyy%')%>) before it will be submitted back to the database and converted again (after the record modification). This means that the plugin should be able to do a two-way operation instead of a one-way operation. It would be nice if the plugin could handle both ways for the modify_record hook (otherwise, I would have to use the code mentioned above directly in the template). Thanks for your help,
Oliver
