Create an event in the admin, note its ID, then place [sinnvoll_bf_widget id=\"EVENT_ID\"]<\/code> on any page or post.<\/p><\/dd>\nCan visitors register more than one attendee?<\/h3><\/dt>\nYes. A single booking can contain multiple attendees, each with their own name and email.<\/p><\/dd>\n
Does it send confirmation emails?<\/h3><\/dt>\nYes. Confirmation emails are sent automatically and are fully configurable, including placeholders and multiple languages.<\/p><\/dd>\n
Does it help with GDPR?<\/h3><\/dt>\nThe 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 \u2014 compliance always depends on how you configure and operate your site, your legal texts, and your own processes.<\/p><\/dd>\n
Does the plugin set any cookies?<\/h3><\/dt>\nIt sets one cookie, sinnvoll_bf_cid<\/code>, only when a booking widget or revocation\nform that needs a security token is rendered for a logged-out visitor. It stores\na random pseudonymous identifier \u2014 it contains no booking data and is not used\nfor tracking \u2014 and serves solely to tie the form's security nonce to the\nvisitor's browser, hardening the public booking form against cross-site request\nforgery and automated abuse. It is designed to function as a strictly necessary\nsecurity cookie, but this plugin cannot make legal determinations for your site\n\u2014 you are responsible for assessing your local consent and disclosure\nrequirements and listing the cookie in your cookie\/privacy notice. The plugin\nregisters suggested text in WordPress' Privacy Policy editor (Settings \u2192\nPrivacy) to help with this.<\/p><\/dd>\nIn which format can I export bookings?<\/h3><\/dt>\nBookings and attendees can be exported as CSV, which opens in any spreadsheet application.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.11.8<\/h4>\n\n\n- 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).<\/li>\n
- Changed: \"Hide tax\" on a ticket type now means final price \u2014 the booking costs exactly the displayed amount; no tax is calculated or stored for such tickets.<\/li>\n
- 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.<\/li>\n
- Fixed: Hidden price-summary lines were still visible due to a CSS specificity conflict.<\/li>\n<\/ul>\n\n
1.11.7<\/h4>\n\n\n- Fixed: Status badges in the attendee and booking lists (and the CSV export) now show translated labels instead of the raw English status value.<\/li>\n
- Fixed: The admin toolbar above attendee\/booking lists no longer overlaps the table header when its controls wrap onto a second line.<\/li>\n
- 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\".<\/li>\n<\/ul>\n\n
1.11.6<\/h4>\n\n\n- 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.<\/li>\n<\/ul>\n\n
1.11.5<\/h4>\n\n\n- Initial release on the WordPress plugin directory.<\/li>\n<\/ul>","raw_excerpt":"Seminar and event booking forms for trainers, coaches, and education providers.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/327756","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=327756"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/rmiarka"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=327756"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=327756"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=327756"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=327756"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=327756"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=327756"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}