feat: Kalender-Code replaces the product's calendar hotel
Every hotel field now has one job. The hotel's code and aliases are import codes only (dates, lookups); a new Kalender-Code (calendar_code) decides the availability a record shows and may be shared by a house's summer and winter records. The product's "Unterkunft für Belegungskalender" is replaced by the checkbox "Kalender anzeigen" (show_calendar): a product page shows the calendar of the hotel it displays, the season still decides which one. - Price calendar, price tables, Belegungskalender, iCal feeds and /api/calendar-hotels read the Kalender-Code. A feed without one answers 404 instead of an empty calendar. - The upgrade wizard epProductsCalendarCode fills both fields from calendar_hotel, preserving today's calendars; the deploy runs it between the schema update and the switch. calendar_hotel stays in the database, so the previous release keeps working. ep:calendar-codes lists the product pages whose calendar differs from it. - HotelCodeResolver is the one lookup of import codes (date import, /api/hotel, Travelinfo); a code on several records resolves to the record whose own code it is, then the lowest uid, with a warning. Saving a code that is already another visible record's import code is refused with a message naming that record. - /api/product without hotel attaches the product's only visible Unterkunft (422 otherwise) and adds board_description, additional_services and calendar_hotel_code. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
1 parent
659e72fc8c
commit
5455973dba
25 files changed
+880
-127
No files matched your search
+10
@@ -112,6 +112,15 @@ task('deploy:check:site-settings', function () {
|
||||
}
|
||||
});
|
||||
|
||||
// Data migrations that the new release needs, named one by one: a wizard already done is skipped,
|
||||
// and pending core or third-party wizards are not run unattended
|
||||
set('upgrade_wizards', ['epProductsCalendarCode']);
|
||||
task('typo3:upgrade:run', function () {
|
||||
foreach (get('upgrade_wizards') as $wizard) {
|
||||
run("{{bin/php}} {{release_path}}/{{bin/typo3}} upgrade:run $wizard --no-interaction");
|
||||
}
|
||||
});
|
||||
|
||||
// current_path instead of the recipe's release_path, so it also works after a rollback
|
||||
task('typo3:cache:flush', function () {
|
||||
run('{{bin/php}} {{current_path}}/{{bin/typo3}} cache:flush');
|
||||
@@ -131,6 +140,7 @@ task('deploy', [
|
||||
'deploy:writable',
|
||||
// The schema has to exist before the new code starts serving traffic.
|
||||
'typo3:extension:setup',
|
||||
'typo3:upgrade:run',
|
||||
// deploy:publish == deploy:symlink, deploy:unlock, deploy:cleanup, deploy:success
|
||||
'deploy:publish',
|
||||
]);
|
||||
|
||||
Reference in new issue
Block a user