Title: sinnvoll Booking Flow Author: sinnvollFÜHREN Published: 2026年8月12日 Last modified: 2026年9月29日 --- プラグインを検索 ![](https://ps.w.org/sinnvoll-booking-flow/assets/banner-772x250.png?rev=3643871) ![](https://ps.w.org/sinnvoll-booking-flow/assets/icon-256x256.png?rev=3643871) # sinnvoll Booking Flow 作者: [sinnvollFÜHREN](https://profiles.wordpress.org/rmiarka/) [ダウンロード](https://downloads.wordpress.org/plugin/sinnvoll-booking-flow.1.12.5.zip) * [詳細](https://ja.wordpress.org/plugins/sinnvoll-booking-flow/#description) * [レビュー](https://ja.wordpress.org/plugins/sinnvoll-booking-flow/#reviews) * [インストール](https://ja.wordpress.org/plugins/sinnvoll-booking-flow/#installation) * [開発](https://ja.wordpress.org/plugins/sinnvoll-booking-flow/#developers) [サポート](https://wordpress.org/support/plugin/sinnvoll-booking-flow/) ## 説明 sinnvoll Booking Flow lets you add seminar and event booking forms to any WordPress page or post with a shortcode. Visitors register for your events, you manage attendees and bookings from the admin, and everyone gets automatic confirmation emails. #### Key features * **Booking widget** for any event via `[sinnvoll_bf_widget id="EVENT_ID"]` * **Event lists** by IDs or timeframe via `[sinnvoll_bf_event_list]` * **Multiple attendees per booking** with per-attendee details * **Ticket capacity** and minimum-tickets handling per event * **Configurable confirmation emails** with placeholders (booker, attendee, event, booking details) and multi-language templates * **Admin management** of events, bookings and attendees, including resend of confirmation emails * **CSV export** of bookings and attendees * **GDPR tools**: data export and erasure integration with WordPress Privacy, plus optional automatic anonymisation of old records * **Cancellation policy** and statutory right-of-withdrawal (revocation) form via shortcode * **Spam protection** for booking submissions (keyword/domain filters, minimum submit time) * **Custom frontend texts** in multiple languages #### Shortcodes * `[sinnvoll_bf_widget id="EVENT_ID" lang="de|en"]` — full booking widget for one event * `[sinnvoll_bf_button id="EVENT_ID"]` — just the “book” button * `[sinnvoll_bf_event_list timeframe="future|past|all"]` — list of events * `[sinnvoll_bf_confirmation]` — booking confirmation messages on your success page * `[sinnvoll_bf_revocation_form]` — statutory right-of-withdrawal form * `[sinnvoll_bf_cancellation_policy]` — outputs your cancellation policy text #### More power with sinnvoll Booking Flow Pro Need more? [sinnvoll Booking Flow Pro](https://sinnvoll-fuehren.com/sinnvoll-booking-flow/) adds coupons, PDF certificates for attendees, waiting lists, multiple ticket types per event, bookable add-ons, bulk emails to attendees, a visual form editor, Excel export and calendar invitations. One-time purchase, 12 months of updates and support included. ### Privacy This plugin processes personal data as part of running bookings on your site. All data stays in your WordPress database; the plugin makes no calls to external services. What it stores: * **Booking data** you collect through the form (names, email addresses and any fields you configure), for as long as you keep the bookings. * **Consent log:** when a visitor submits a booking, the plugin records which consent checkboxes were accepted together with a timestamp, the visitor’s IP address and browser user agent, as proof of consent. The optional data retention settings anonymise the IP address after the configured period. * **Audit log:** administrative changes to bookings and attendees are recorded with the acting user, IP address and user agent, so changes remain traceable. * **Rate limiting:** public booking submissions are counted per client IP using a short-lived, hashed counter (a transient). No raw IP is persisted for this purpose and no cookie is involved. * **Security cookie:** see the FAQ above for the `sinnvoll_bf_cid` cookie. The plugin integrates with WordPress’ personal-data export and erasure tools (Tools Export/Erase Personal Data) and registers suggested wording in the Privacy Policy editor (Settings Privacy). Reviewing and publishing your site’s privacy notice remains your responsibility. ## スクリーンショット [⌊The booking widget your visitors see — dates, price, remaining places and the booking form.⌉⌊The booking widget your visitors see — dates, price, remaining places and the booking form.⌉[ The booking widget your visitors see — dates, price, remaining places and the booking form. [⌊Manage all your events with status, capacity and bookings at a glance.⌉⌊Manage all your events with status, capacity and bookings at a glance.⌉[ Manage all your events with status, capacity and bookings at a glance. [⌊The attendee list of an event — who booked what, with CSV export.⌉⌊The attendee list of an event — who booked what, with CSV export.⌉[ The attendee list of an event — who booked what, with CSV export. ## インストール 1. Upload the plugin files to `/wp-content/plugins/sinnvoll-booking-flow`, or install through the WordPress Plugins screen directly. 2. Activate the plugin through the “Plugins” screen in WordPress. 3. Go to **sinnvoll Booking Flow** in the admin menu to create your first event. 4. Add a booking widget to any page with `[sinnvoll_bf_widget id="EVENT_ID"]` (the event ID is shown on the event list). 5. Configure confirmation emails, sender details and texts under **sinnvoll Booking Flow Settings**. ## FAQ ### How do I show a booking form on a page? Create an event in the admin, note its ID, then place `[sinnvoll_bf_widget id="EVENT_ID"]` on any page or post. ### Can visitors register more than one attendee? Yes. A single booking can contain multiple attendees, each with their own name and email. ### Does it send confirmation emails? Yes. Confirmation emails are sent automatically and are fully configurable, including placeholders and multiple languages. ### Does it help with GDPR? The plugin provides tools that support GDPR workflows: it integrates with WordPress’ personal-data export and erasure tools and offers optional automatic anonymisation of old records. It does not make your site compliant on its own — compliance always depends on how you configure and operate your site, your legal texts, and your own processes. ### Does the plugin set any cookies? It sets one cookie, `sinnvoll_bf_cid`, only when a booking widget or revocation form that needs a security token is rendered for a logged-out visitor. It stores a random pseudonymous identifier — it contains no booking data and is not used for tracking — and serves solely to tie the form’s security nonce to the visitor’s browser, hardening the public booking form against cross-site request forgery and automated abuse. It is designed to function as a strictly necessary security cookie, but this plugin cannot make legal determinations for your site — you are responsible for assessing your local consent and disclosure requirements and listing the cookie in your cookie/privacy notice. The plugin registers suggested text in WordPress’ Privacy Policy editor (Settings Privacy) to help with this. ### In which format can I export bookings? Bookings and attendees can be exported as CSV, which opens in any spreadsheet application. ## 評価 このプラグインにはレビューがありません。 ## 貢献者と開発者 sinnvoll Booking Flow はオープンソースソフトウェアです。以下の人々がこのプラグイン に貢献しています。 貢献者 * [ sinnvollFÜHREN ](https://profiles.wordpress.org/rmiarka/) “sinnvoll Booking Flow” は2ロケールに翻訳されています。 [翻訳者](https://translate.wordpress.org/projects/wp-plugins/sinnvoll-booking-flow/contributors) のみなさん、翻訳へのご協力ありがとうございます。 [“sinnvoll Booking Flow” をあなたの言語に翻訳しましょう。](https://translate.wordpress.org/projects/wp-plugins/sinnvoll-booking-flow) ### 開発に興味がありますか ? [コードを閲覧](https://plugins.trac.wordpress.org/browser/sinnvoll-booking-flow/) するか、[SVN リポジトリ](https://plugins.svn.wordpress.org/sinnvoll-booking-flow/) をチェックするか、[開発ログ](https://plugins.trac.wordpress.org/log/sinnvoll-booking-flow/) を [RSS](https://plugins.trac.wordpress.org/log/sinnvoll-booking-flow/?limit=100&mode=stop_on_copy&format=rss) で購読してみてください。 ## 変更履歴 #### 1.12.5 * Fixed: The field list in booking emails ({all_fields}) showed the submit button as if it were an answer (“Book Now: 1”), and text blocks likewise. Only fields a person actually fills in are listed now. * Fixed: Consent labels in that list showed the link markers from the form, as in “I agree to the **privacy policy**“. The words stay, the underscores are gone. * New: A filter for the value a field shows in the {all_fields} list, so a field whose choices are supplied at display time can show their names instead of the submitted values. #### 1.12.4 * Fixed: A stylesheet rule could keep an admin control visible after it had been marked as hidden, because it outranked the class that hides it. * Internal: Admin table headers in the card layout are readable again, and the test suite now mirrors WordPress’ own sanitising more closely. #### 1.12.3 * Fixed: An event set to “Pending” was confirmed automatically as soon as the first person registered, so everyone from then on received the confirmation email instead of the provisional one. This happened whenever no minimum number of participants was set — which is the default. A minimum of zero now means “do not confirm automatically”, and the event stays pending until you confirm it yourself. * Tested up to WordPress 7.1.2. #### 1.12.2 * Fixed: Searching in the Bookings tab of an event could end on a blank page saying you are not allowed to access it, even as an administrator. Switching to the tab loaded it in the background, which lost the page reference the search then submitted. * Fixed: Searching in Bookings or Attendees could fail with “the link you followed has expired” when the page had been open for a while. The search is no longer treated as a bulk action, so it needs no fresh security token. * Accessibility: Screen readers now announce admin messages as they appear, name every form field, mark rejected fields and point them at the reason, read out which column a table cell belongs to, and say which sub-tab is the current one. * Accessibility: Two buttons in the booking form and the attendee editor said “ Remove” in English on every site, regardless of language. They now use the site’s own wording. * Improved: Restoring a trashed booking re-reads its state under the row lock, so two people restoring at once can no longer raise the event maximum twice. * Fixed: When an operation raised an event’s maximum and then failed, the raise stayed. It is now taken back, so the event never keeps a larger maximum than anyone asked for. * Fixed: Saving a form template whose fields could not be written reported success and left an empty template behind — the form then rendered with no fields at all. The failure is now reported and nothing is saved. * Fixed: Consent settings that still pointed at option names from before the prefix migration are rewritten on update, so an existing privacy or terms page keeps working. * Fixed: Creating the protected log directory could end in a fatal error, because it relied on a WordPress constant that only exists on some requests. It happened on the very first write and then disappeared by itself, which made it hard to catch. #### 1.12.1 * New: Restoring a booking or an attendee from the trash now asks “Increase event max tickets if full” instead of failing on a full event — for single rows and for bulk restores. The maximum grows by exactly the missing seats. * Improved: Every booker and attendee e-mail is now built entirely in the language of the booking — dates, field labels, add-on texts and calendar attachments, not only the template itself. Admin notifications keep the site language. * Improved: The restore notice now says whether the event or a ticket type is full. #### 1.12.0 * Security: The public booking form’s security token is now really bound to the visitor’s browser (a strictly necessary cookie, set only on pages with a booking or withdrawal form). Booking pages are marked as not cacheable so a cached page can never hand one visitor’s token to another. * Changed: The public booking form no longer checks for double bookings before submitting (that check could confirm to anyone who knew a name and e-mail address whether the person attends an event). Instead, when the same e-mail address already has a live booking for the event, the booker’s own confirmation e-mail now says so and offers the withdrawal link. * Improved: A visitor whose browser blocks cookies sees a clear notice in the booking form instead of an error page; an expired form leads back to the form with an explanation. * Improved: Cancelled or expired registrations no longer count as duplicates in the admin editor, and a booking without any attendee now shows the matching hint instead of a generic error. * Fixed: A licence-warning translation that could break the admin notice on German sites. * New: The booking form updates its price summary live, based on the number of attendees — adding or removing an attendee recalculates immediately, and typing names never triggers a request. * Fixed: The withdrawal link in confirmation emails works again, and each link is now valid for exactly one submission. * Fixed: The personal data export (Tools Export Personal Data) now really includes bookings, attendees, and the stored billing address. * Fixed: Confirming an event no longer removed its attendees from the capacity count and the statutory withdrawal period. * Improved: Saving a booking in the admin area is now all-or-nothing — if any part of the save cannot be stored, the whole booking stays exactly as it was and the editor says so. * Improved: Changing a booking’s status in the editor now applies the same checks and follow-ups (capacity, attendee statuses, emails) as the list actions. * Improved: Deleting an event permanently refuses to leave related records behind; restoring from trash brings back only what was trashed together, and respects the event capacity. * Improved: Capacity is reserved reliably even when several bookings arrive at the same moment. * Improved: Public endpoints (price preview, withdrawal) carry their own request limits, and admin messages now always show the text that matches the action. * Improved: Add-ons can now apply their changes inside the same save operation, so a failed save leaves nothing half-applied. * Fixed: Status emails from bulk actions are only sent when the status change actually succeeded. * Fixed: Saving an event now reports a problem instead of showing “successfully saved” when the event could not be stored; your entries stay in the form so you can try again. * Fixed: Duplicating an event is all-or-nothing — if the copy or any of its ticket types cannot be created, nothing half-finished is left behind and the message says so. * Improved: Restoring an event from the trash is all-or-nothing as well, and a database problem while reading is no longer mistaken for “there was nothing to restore”. #### 1.11.17 * Fixed: The per-IP limit on booking submissions could count too few attempts when several arrived at the same moment, so it engaged later than configured. Attempts are now counted in a way that cannot lose one. #### 1.11.16 * Fixed: A leftover scheduled task from older versions kept running twice a day even though nothing used it any more; deactivating the plugin now removes it. #### 1.11.15 * Fixed: In the booking dialog the keyboard focus could land in the invisible spam- protection field instead of the first real field — typing immediately after opening could end up nowhere and get the booking flagged as spam. #### 1.11.14 * Fixed: On sold-out events with an active waiting list, the “Add attendee” button refused to add anyone (“Only 0 seats left”) — the seats-left check now stands down in waiting-list mode, where the server accepts any number of attendees. #### 1.11.13 * Fixed: All plugin strings could appear in English on translated sites even though complete translations exist — the wp.org language pack is now loaded explicitly instead of relying on WordPress’ just-in-time loading. #### 1.11.12 * Fixed: Required checkbox groups (e.g. attendance days) demanded ALL options to be ticked — the browser silently blocked guests who selected only some. At least one is now enough, with a clear browser message when none is selected. * Improved: When a required field is empty, the booking error now names the field instead of showing a generic message. * Improved: When the submitted form is older than the current form definition ( stale page cache), guests are asked to reload the page instead of seeing a generic error. #### 1.11.11 * Changed: The bookings export now shows the option labels guests actually selected( e.g. “Freitag (ab 17:00 Uhr)”) instead of raw stored values (friday) — for radio, select and checkbox-group fields, using each booking’s form snapshot. * Changed: The bookings export no longer includes the internal ticket-type ID column; the ticket name is already part of the attendee data. #### 1.11.10 * Fixed: The bookings export (CSV and Pro Excel) showed empty cells for all custom form fields — only the column headings appeared. Values from the booking form( e.g. radio selections, checkbox groups, consents) now export correctly. * Changed: The bookings export no longer creates columns for form elements that never carry a value (HTML blocks, the submit button, the attendee controls). #### 1.11.9 * Fixed: Event tabs (e.g. Coupons in Pro) could show a stale list after creating or editing entries in a modal — tab content was served from a five-minute browser cache. Tabs now always load fresh on every activation. * Compatibility: Tested with WordPress 7.1. #### 1.11.8 * New: Event cards show “Price from:” with the lowest ticket price when an event has multiple ticket types with different prices (translatable via the Texts screen). * Changed: “Hide tax” on a ticket type now means final price — the booking costs exactly the displayed amount; no tax is calculated or stored for such tickets. * Changed: The price summary in the booking form collapses to a single Total line when there is no tax to show (0% rate or final-price tickets); the full breakdown returns when a taxed ticket type is selected. * Fixed: Hidden price-summary lines were still visible due to a CSS specificity conflict. #### 1.11.7 * Fixed: Status badges in the attendee and booking lists (and the CSV export) now show translated labels instead of the raw English status value. * Fixed: The admin toolbar above attendee/booking lists no longer overlaps the table header when its controls wrap onto a second line. * Fixed: Setting attendees to booked/cancelled/missed now shows a matching success notice instead of “Attendee moved to trash.”; German trash notices now say “Papierkorb”. #### 1.11.6 * New: Guest emails now follow the language the booking was made in. The booking form language is stored with each booking; confirmation and cancellation emails use it, falling back to the event language and then the site language. Events gained a Language setting (default: site language), and the widget renders in the event’s language when the shortcode has no lang attribute. Admin notifications intentionally stay in the site language. #### 1.11.5 * Initial release on the WordPress plugin directory. ## メタ * バージョン **1.12.5** * 最終更新日 **1週間前** * 有効インストール数 **10未満** * WordPress バージョン ** 6.5またはそれ以降 ** * 検証済み最新バージョン: **7.1.3** * PHP バージョン ** 8.1またはそれ以降 ** * 言語 * [English (US)](https://wordpress.org/plugins/sinnvoll-booking-flow/)、[German](https://de.wordpress.org/plugins/sinnvoll-booking-flow/)、 [German (Austria)](https://de-at.wordpress.org/plugins/sinnvoll-booking-flow/). * [プラグインを翻訳](https://translate.wordpress.org/projects/wp-plugins/sinnvoll-booking-flow) * タグ * [attendees](https://ja.wordpress.org/plugins/tags/attendees/)[booking](https://ja.wordpress.org/plugins/tags/booking/) [events](https://ja.wordpress.org/plugins/tags/events/)[registration](https://ja.wordpress.org/plugins/tags/registration/) [RSVP](https://ja.wordpress.org/plugins/tags/rsvp/) * [詳細を表示](https://ja.wordpress.org/plugins/sinnvoll-booking-flow/advanced/) ## 評価 レビューはまだ送信されていません。 [Your review](https://wordpress.org/support/plugin/sinnvoll-booking-flow/reviews/#new-post) [すべてのレビューを見る](https://wordpress.org/support/plugin/sinnvoll-booking-flow/reviews/) ## 貢献者 * [ sinnvollFÜHREN ](https://profiles.wordpress.org/rmiarka/) ## サポート 意見や質問がありますか ? [サポートフォーラムを表示](https://wordpress.org/support/plugin/sinnvoll-booking-flow/)