![\"FooEvents](\"https:\/\/www.fooevents.com\/wp-content\/uploads\/2026\/03\/fooevents-2.png\" "\\"\\"")
<\/p>\n<\/p>\n
This release introduces the new Attendee Details Page, ticket theme updates, ticket theme version notices, PDF ticket folder protection, and an updated DOMPDF library.<\/p>\n
FooEvents for WooCommerce version 2.0.0<\/strong> is an important release that addresses several long-standing challenges and lays a stronger foundation for the future of the platform. It introduces meaningful improvements across key areas and helps set a clear direction for how FooEvents will continue to evolve over time.<\/p>\n The biggest change in this update\u00a0is the new Attendee Details Page<\/a>. Instead of collecting attendee information during checkout, FooEvents can now redirect customers to a dedicated, customizable page before checkout where customers complete the required attendee details for each ticket and then continue to payment.<\/p>\n This new workflow adds full support<\/strong> for both the classic WooCommerce checkout experience<\/strong> e il WooCommerce Checkout Block<\/strong>, giving FooEvents a more consistent and reliable foundation across both checkout types.<\/p>\n In addition, by moving attendee details into a dedicated flow, it creates a cleaner path to payment and makes the overall purchase journey easier to follow and more in line with industry standards.<\/p>\n The Attendee Details Page is a standard WordPress page, so it’s easy to customize and make your own using the block editor or your favorite page editor. The attendee fields inherit WooCommerce form styling, so they will match the rest of your checkout forms without any customization needed.<\/p>\n The Attendee Details Page is in Beta and is not currently enabled by default. It can be enabled in the FooEvents<\/strong> > Impostazioni<\/strong> > Partecipanti<\/strong> section. Read this guide<\/a> for further details.<\/p>\n Supporting both the legacy shortcode-based WooCommerce checkout flow and the newer block-based checkout introduced various challenges and significant technical overhead. After exploring many options, we settled on the new Attendee Details Page as it <\/strong>gives FooEvents a single attendee collection workflow that works across both checkout experiences. That means fewer edge cases, fewer compromises, efficient code, and a clearer path forward as WooCommerce continues to develop its checkout architecture.<\/p>\n Previously, FooEvents extensions only offered limited support for the WooCommerce Checkout Block. With the new attendee workflow, FooEvents works consistently with all FooEvents extensions, including:<\/p>\n Depending on your event setup, this means you can still capture the booking, seating, and attendee data you need, but in a workflow that is cleaner and more consistent than before.<\/p>\n The new attendee workflow is currently opt-in, so nothing changes on your site unless you choose to enable it. Over time, this will become the default experience on new installations.<\/p>\n This release also introduces a new ticket theme update<\/a> option that can be used to upload new versions of ticket themes.<\/p>\n Previously, updating a ticket theme often meant replacing files manually using FTP. That worked, but it was not ideal for many users and made theme maintenance more technical than it needed to be.<\/p>\n Con FooEvents for WooCommerce version 2.0.0<\/strong>, updating ticket themes is now much easier thanks to the new upload and overwrite workflow. This makes it simpler to install new ticket theme versions, apply updates, and keep themes aligned with the latest FooEvents features.<\/p>\n Alongside the new update workflow, we have also added ticket theme version notices.<\/p>\n These notices help identify when a ticket theme may be out of date, making it easier to spot when an update is needed. This gives store owners better visibility into the state of their ticket themes and helps reduce the chance of running outdated templates for longer than intended.<\/p>\n FooEvents PDF tickets<\/a> use an \u201cunlisted link\u201d model, similar to Google Drive\u2019s \u201canyone with the link\u201d sharing setting. Ticket file names are generated using an algorithm that produces obscure, non-sequential names, making them extremely difficult to guess, even if someone understands how FooEvents generates them.<\/p>\n That said, you can never be too safe to we have introduced a new advanced feature that adds additional protection to PDF ticket folders<\/a>, helping reduce the chance of direct access to generated ticket files.<\/p>\n This release also includes an updated DOMPDF library.<\/p>\n Keeping core PDF-generation dependencies up to date is important for stability, rendering accuracy, compatibility, and security. By updating DOMPDF, this update strengthens the PDF ticket generation stack and helps ensure it remains compatible with modern server environments and future improvements.<\/p>\n Some ticket themes require minor updates to ensure compatibility with this version. You can read more about it here<\/a>.<\/p>\nIntroducing the Attendee Details Page<\/h2>\n
![\"FooEvents](\"https:\/\/www.fooevents.com\/wp-content\/uploads\/2026\/03\/fooevents-attendee-details-page-steps.png\" "\\"\\"")
<\/p>\nBuilt for Classic Checkout and the Checkout Block<\/h3>\n
\n
Looking Ahead<\/h3>\n
Ticket Theme Updates Are Now Easier to Manage<\/h2>\n
![\"Updating](\"https:\/\/www.fooevents.com\/wp-content\/uploads\/2026\/03\/Screenshot-2026-03-10-at-09.03.06.png\" "\\"\\"")
<\/p>\nNew Ticket Theme Version Notices<\/h2>\n
![\"FooEvents](\"https:\/\/www.fooevents.com\/wp-content\/uploads\/2026\/03\/Screenshot-2026-03-10-at-12.56.58.png\" "\\"\\"")
<\/p>\nPDF Ticket Folder Protection<\/h2>\n
Updated DOMPDF Library<\/h2>\n
We\u2019d Love Your Feedback<\/h2>\n