Bug #4836
closed
Input type "datetime" doesn't show a calendar anymore in the web form of Directives
Added by Nicolas CHARLES almost 11 years ago.
Updated about 8 years ago.
Category:
Web - Config management
Description
The following code, in a metadata.xml, should show a calendar in the directive field, but it isn't:
<INPUT>
<NAME>TEST</NAME>
<DESCRIPTION>We should have a calendar</DESCRIPTION>
<CONSTRAINT>
<TYPE>datetime</TYPE>
</CONSTRAINT>
</INPUT>
Content is properly validated, if it's not the proper date, we have the error message
Wrong value hft for field 'We should have a calendar': expecting a datetime in ISO 8601 standard.
a calendar would really help to follow the proper format
- Target version changed from 2.6.13 to 2.6.14
- Target version changed from 2.6.14 to 2.6.16
- Target version changed from 2.6.16 to 2.6.17
- Target version changed from 2.6.17 to 2.6.18
- Target version changed from 2.6.18 to 2.6.19
- Target version changed from 2.6.19 to 2.6.20
- Target version changed from 2.6.20 to 2.10.10
- Target version changed from 2.10.10 to 2.10.11
- Target version changed from 2.10.11 to 2.10.12
- Target version changed from 2.10.12 to 2.10.13
- Target version changed from 2.10.13 to 2.10.14
- Target version changed from 2.10.14 to 2.10.15
- Target version changed from 2.10.15 to 2.10.16
- Target version changed from 2.10.16 to 2.10.17
- Target version changed from 2.10.17 to 2.10.18
- Target version changed from 2.10.18 to 2.10.19
- Target version changed from 2.10.19 to 2.10.20
- Target version changed from 2.10.20 to 277
- Target version changed from 277 to 2.11.18
- Target version changed from 2.11.18 to 2.11.19
- Target version changed from 2.11.19 to 2.11.20
- Target version changed from 2.11.20 to 2.11.21
- Target version changed from 2.11.21 to 2.11.22
- Target version changed from 2.11.22 to 2.11.23
- Target version changed from 2.11.23 to 2.11.24
- Target version changed from 2.11.24 to 308
- Target version changed from 308 to 3.1.14
- Target version changed from 3.1.14 to 3.1.15
- Target version changed from 3.1.15 to 3.1.16
- Target version changed from 3.1.16 to 3.1.17
- Target version changed from 3.1.17 to 3.1.18
- Target version changed from 3.1.18 to 3.1.19
- Status changed from New to Rejected
- Priority set to 0
As we don't have any technique with a date, this is not bug (and I don't even know if it is still here).
I'm closing it and we will open a problem is one, we have a technique which need it.
Also available in: Atom
PDF