3e36136bfadd1225ab5be181a156d3e110f80903
The export read MyE&P's contingents/calendar, which marks every day without a MyE&P price as BLOCKED. Group houses without winter prices (e.g. SVS) were published to groups.swiss as fully booked for the whole winter, and their on-request runs were lost. It now reads contingents/availability, the plain bpn-connect snapshot the iCal feed already uses, as TYPO3 10 did. getContingentCalendar() had no other caller and is removed. Co-Authored-By: Claude Opus 5.5 <[email protected]>
E&P Reisen websites (TYPO3 13)
TYPO3 13 LTS for www.ep-reisen.de and its subsites (ski-boarderweek, snowzone, semesterende-skireisen,
ski-wochenenden, …). Products, hotels, regions and dates live in packages/ep_products, templates
and assets in packages/ep_theme. Dates, prices and availability come from MyE&P (EP/myep),
which in turn reads bpn-connect.
Local setup
DDEV project: ddev start, then ddev composer install and ddev npm install && ddev npm run build.
Rebuild the assets after template changes: Tailwind purges classes it does not find in the
templates.
Documentation
- docs/cms-api.md: the API TYPO3 serves to MyE&P and the chatbot
(
/api/hotel,/api/product,/api/calendar-hotels,/api/content/*). - docs/calendars.md: price calendar, Belegungskalender and iCal feed: where the data comes from, caching, and what to check when a calendar does not load.
Deployment
deploy.php (Deployer). A deploy runs extension:setup, resets OPcache and flushes all caches.
License
GPL-2.0 or later
Languages
JavaScript
40.6%
PHP
36.4%
HTML
22%
SCSS
0.8%
Shell
0.2%