Implement TimeParsers in the backend.
Version: unspecified
Severity: normal
Whiteboard: u=dev c=backend p=3
Description
Description
Details
Details
- Reference
- bz62184
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T87764 Bugs related to time datatype (tracking) | |||
| Resolved | Lydia_Pintscher | T50962 localize display of time values | |||
| Resolved | None | T47046 Normalizing file names for display | |||
| Resolved | None | T50860 [ui] First version of geocoordinate datatype support | |||
| Resolved | None | T50888 Improve data value validation and error handling in api | |||
| Resolved | None | T50965 time data values are not validated when saved via api | |||
| Resolved | None | T63254 Item values are not linked when Javascript is disabled | |||
| Resolved | None | T51014 Use value formatters for displaying values on Entity pages (non-JavaScript view) | |||
| Resolved | adrianheine | T63738 Spaces in commons file names are replaced by plus signs instead of underscores | |||
| Resolved | adrianheine | T51186 Property value parsing, formatting and validation should be done (only?) in the backend | |||
| Resolved | None | T64185 Use backend formatter and parser for time | |||
| Resolved | None | T64184 Create PHP Time Parsers for wbparsevalue |