PHPackages ubl/booking - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. ubl/booking ActiveTypo3-cms-extension ubl/booking =========== Managed bookings of rooms for fe users 3.0.3(5mo ago)28GPL-2.0-or-laterPHPPHP >=7.4.0 Since Mar 14Pushed 5mo ago4 watchersCompare [ Source](https://github.com/ubleipzig/tx-booking)[ Packagist](https://packagist.org/packages/ubl/booking)[ Docs](https://git.sc.uni-leipzig.de/ubl/bdd_dev/webmasterei/tx-booking)[ RSS](/packages/ubl-booking/feed)WikiDiscussions 11.5\_lts Synced 2mo ago READMEChangelogDependencies (4)Versions (24)Used By (0) ubl/booking =========== [](#ublbooking) Manages bookings of rooms for typo3 frontend users This extension was created out of the need to manage bookings for group study rooms available to students and patrons of leipzig university library. Anonymous website visitors get an overview of rooms and occupation in a specific period of time, manageable in the typo3-backend. Logged users additionally can book timeslots of rooms according to the defined maximum of bookings per day and location. Requirements ------------ [](#requirements) - Typo3 > 11.0 < 11.5.99 - PHP >= 7.4 - Icon font >= 0.9.0 Usage ----- [](#usage) This extension provides a plugin which has to be assigned to the designated page. ### Create a Location [](#create-a-location) Add a *New content element->Plugins->General Plugin*. Under Tab *Plugin* choose **Booking for Rooms**. #### Configuration [](#configuration) After switching back to the Tab *Plugin* you have several options to specify: - **Maximum bookings per day and user**Defines how many bookings a user can place per day, regardless on how many rooms you will make available on this page. Defaults to 5 bookings if nothing is specified. - **Count of weeks available for booking in advance**Defines how many weeks users will be able to book in advance. Current week plus what you define here. Default is 2 weeks if nothing specified. - **Count of weeks available for looking back**Defines how many weeks one can go back to see the occupation. Defaults to 1 week if nothing is specified. - **Administrative accounts**Defines the frontend user accounts that are treated as admins. they are not limited by all prior settings. On the tab *Behaviour* one has to specify the *Record Storage Page* where rooms, bookings, opening hours and closing days will be stored. If not overridden as described in the **Advanced Customization**-Section all opening hours and closing days created here count for all rooms created here. #### Create a Room [](#create-a-room) To create a room go to the page that you specified as *Record Storage Page*in the *Configuration*-Section earlier, *Create a new Record* and choose **Rooms** You have to provide at least a *Room name*. #### Enable Stylesheets [](#enable-stylesheets) To enable the default CSS stylesheets that come with the extension one has to include them into the root template. Go to *Web->Template*, select *Info/Modify* in the Dropdown-box and click on *Edit the whole template record*. Select the tab *Includes*, add *Booking CSS Styles (booking)* from *Available Items* to *Selected Items* and click *Save*. You have now added the extension's stylesheet to the page and enabled icon font styles. ### define Closing Days [](#define-closing-days) Closing days are useful for bank holidays for example. To create a closing day go to the page that you specified as *Record Storage Page*in the *Configuration*-Section earlier, *Create a new Record* and choose **Closing Day** You have to provide at least a *Closing day name* and a *Date*. The days are shown as non-bookable in week overview, and it's not possible to create bookings from the frontend on these days. However, there is no validation on bookings one creates from backend, but they are not shown in frontend either. ### define Opening Hours [](#define-opening-hours) By default, all hours of all days a week are bookable. With opening hours one can define the opening hours of a day. To create opening hours for a day go to the page that you specified as *Record Storage Page*in the *Configuration*-Section earlier, *Create a new Record* and choose **Opening Hours** Select the day of week you want to specify opening hours for and then select the hours of duty. If you select no hours at all the day is closed for bookings entirely. Like this one can create weekly closed days i.e. sunday. Advanced Customization ---------------------- [](#advanced-customization) By default, closing days and opening hours count for all rooms. However, if you want to define different rules for different rooms you can create a new *Record Storage Page* and specify it for the designated room(s). Open an already created room-record and register newly created *Record Storage Page*under *Opening times storage pages*. You even can register multiple pages, if you like to make use of an inheritance principle. The rule is, what comes first counts. For example if you define opening hours for Monday on two pages the opening hours of the page that is listed first are taken. Closing days are inherited as well. However, overriding makes no sense here. To get a better overview of bookings made for a room you also can specify a storage page for a rooms bookings. Register the designated storage page under *Booking storage page*and continue. Future bookings are stored under that page, but bookings from the plugin's storage page are taken in account as well so you don't have to worry about old bookings. Cleanup old Bookings -------------------- [](#cleanup-old-bookings) There is a cleanup-command which can be used with typo3's commandline interface or the scheduler to clean up old bookings. Be aware that plugin configured looking back weeks are not respected here. You specify the count of weeks to keep from now on. Go to *Scheduler->Add Task* - from *Class* choose **Extbase CommandController Task** - specify the *Frequency* according to your needs (once a week is sufficient) - from the list of *CommandController Command* choose **Booking Cleanup: cleanupBookings** - save the task \*\*important! otherwise the form element for the argument is not appearing - specify the count of weeks to keep in the *weeks* argument field. 0 (zero) or empty means that all bookings prior to the current week are removed ### Health Score 43 — FairBetter than 91% of packages Maintenance69 Regular maintenance activity Popularity7 Limited adoption so far Community12 Small or concentrated contributor base Maturity73 Established project with proven stability Bus Factor1 Top contributor holds 93.9% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~166 days Recently: every ~46 days Total 20 Last Release 179d ago Major Versions 1.0.2 → 2.0.02017-06-14 2.3.4 → 3.0.02025-09-19 ### Community Maintainers ![](https://avatars.githubusercontent.com/u/7923633?v=4)[Leipzig University Library](/maintainers/ubleipzig)[@ubleipzig](https://github.com/ubleipzig) ![](https://www.gravatar.com/avatar/2306f04b1413eaae6e0f33007cc87094fc92018cd885740f1e58c3d0d17fa4fe?d=identicon)[useltmann](/maintainers/useltmann) --- Top Contributors [![ndege](https://avatars.githubusercontent.com/u/1499473?v=4)](https://github.com/ndege "ndege (31 commits)")[![ckaz](https://avatars.githubusercontent.com/u/8236627?v=4)](https://github.com/ckaz "ckaz (2 commits)") --- Tags typo3-cms-extensioncmsextensiontypo3booking ### Code Quality TestsPHPUnit ### Embed Badge ![Health badge](/badges/ubl-booking/health.svg) ``` [![Health](https://phpackages.com/badges/ubl-booking/health.svg)](https://phpackages.com/packages/ubl-booking) ``` ### Alternatives [typo3/cms-composer-installers TYPO3 CMS Installers 6113.7M52](/packages/typo3-cms-composer-installers) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)