-
Bug
-
Resolution: Fixed
-
Critical
-
4.2.0
-
None
-
None
-
4.3 M2
This problem occurs since the migration of services to the new parameters API.
Before this migration, all parameters were stored as String. Now, they are stored with the right type (Long for a parameter of type "long", Boolean for a parameter of type "boolean")
Example with the search service V2:
- Add the serach service V2 in a zone-item
-
- Results per page is proposed to its default value (10)
- Empty the field and save
- Reparameterize the service
- the field Results per page is filled with the default value instead of empty => KO
- Bloque
-
CMS-9978 [ContentComparator] Delete old API's warnings
- Closed
-
REPOSITORY-426 [New Attribute API] Make the old API able to read data setted via the new API
- Closed
- created
-
REPOSITORY-480 Change the storage of empty repository data
- Closed
- Duplique
-
REPOSITORY-404 Discern empty values from not initialized values
- Closed
- Est référencé par
-
CMS-10022 In the search service, the number 10 is automatically filled in the box "number of results per page" when I leave empty
- Closed
-
CMS-10374 [Search service v2] Non-mandatory long parameters (the return)
- Closed