frommeandClaude Opus 5.5
d9f74e271e
settings.dateFrom and settings.dateTo were still type=input with eval=date. TYPO3 13 only migrates renderType=inputDateTime to type=datetime, so these were rendered as text inputs whose JavaScript expects an ISO 8601 value. It got the stored timestamp (e.g. 1793491200), threw "Invalid ISO8601 DateTime string", and the edit form of these plugin elements never finished loading. The datetime element converts the stored timestamps itself and, without a dbType, saves timestamps again, so stored values and the frontend stay as they are. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Queries for plugin renaming
update tt_content set list_type='epproducts_searchbar' where list_type='epproducts_pi1';
update tt_content set list_type='epproducts_product_detail' where list_type='epproducts_pi3';
update tt_content set list_type='epproducts_searchresult' where list_type='epproducts_pi2';
update tt_content set list_type='epproducts_product_teasergroup' where list_type='epproducts_pi4';
update tt_content set list_type='epproducts_country_detail' where list_type='epproducts_pi5';
update tt_content set list_type='epproducts_region_teasergroup' where list_type='epproducts_pi6';
update tt_content set list_type='epproducts_region_detail' where list_type='epproducts_pi10';
update tt_content set list_type='epproducts_city_teasergroup' where list_type='epproducts_pi7';
update tt_content set list_type='epproducts_city_detail' where list_type='epproducts_pi11';
update tt_content set list_type='epproducts_hotel_teasergroup' where list_type='epproducts_pi8';
update tt_content set list_type='epproducts_hotel_detail' where list_type='epproducts_pi12';
update tt_content set list_type='epproducts_faq' where list_type='epproducts_pi9';