Important: Address postcode and street number accept text
Description
The shipped Configuration/ listed the
number
flag for the
zip
and
street properties of
the
physical set. The flag turns a field into a TCA
number
field in the backend record editor and into a number input in
the frontend editing form of EXT:. A TCA
number
field stores an integer, so the backend saved 01067 as
1067, 12a as 12 and a postcode such as SW1A 2AA as 0, and
the frontend form refused 12a and SW1A 2AA.
The flag is removed from both properties. They are text fields again, as their
TCA and their
varchar
columns declare, and they stay required.
Impact
Postcodes and street numbers are stored exactly as entered, in the backend
and in the frontend editing form. Values saved before this change are not
repaired: a leading zero that was dropped stays dropped, and a street number
saved as 12 instead of 12a has to be corrected by hand.
Affected Installations
Every installation that edits addresses.
An installation that ships its own Configuration/
with a
validations
map replaces the shipped map as a whole, because
the files are merged by their top-level keys. Such a copy keeps the
number
flag on
zip
and
street until it is removed
there as well. The shipped set reads as follows now, the other sets of the
copy are left out here:
validations:
physicalAddress:
street:
- required
streetNumber:
- required
zip:
- required
city:
- required
country:
- required
Flush the TYPO3 caches afterwards, the settings are cached.