Most WordCamps run free, capacity-limited extras alongside the main event – Contributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/, a Social Dinner, a workshop. Those seats are meant for confirmed attendees, but CampTix has no built-in way to enforce that. So organizers improvise: a separate signup form anyone on the internet can fill in, a spreadsheet cross-checked against the attendee list by hand, or an honor system that quietly oversells the room. Non-attendees grab limited seats, organizers spend hours reconciling lists, and no-shows leave chairs empty that a real attendee could have used.

We’ve built a CampTix addon that closes that gap, and before it goes to a pull request we’d like the community’s eyes on it especially from anyone who has run a Contributor Day or a side event and felt this pain firsthand.

This isn’t a new idea. Issue #1371 “Tickets: Add the ability to handle secondary event tickets” – opened by a WCEU WordCamp Europe. The European flagship WordCamp event. organizer in 2024 and discussed by CampTix maintainers – requests exactly this, and the addon meets all of that issue’s acceptance criteria. Along the way it also structurally resolves #598 (Contributor Day attendance stats – attendees of a side event become real CampTix attendees, so check-in and stats just work) and the side-event case of #623 (people no longer appear twice on the public Attendees page).

The working name is activity tickets (more on the name below – it’s one of the things we want feedback on).

An organizer creates the extras as ordinary CampTix tickets (price 0, quantity = capacity), then ticks which tickets are activity tickets under CampTix → Setup → Activity Tickets. Optionally, they can restrict which main tickets qualify. That’s the entire setup.

From then on, an activity ticket can only be registered by someone who is logged in with their WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ account and already holds a confirmed main-event ticket from an earlier, completed order. Each person registers themselves, once per activity, and every activity registration is automatically linked to their main ticket.

What the attendee sees: buy a ticket → return to the Tickets page → register for the activities you want → done. Visitors who don’t qualify yet still see the activity tickets, with a notice explaining why they can’t register yet:

“Contributor Day can only be registered by attendees who already have an event ticket. Buy your ticket first, then come back to register.”

On a later visit, tickets they already hold show an “Already registered” label instead of silently disappearing, and a notice up top lists everything they hold – with a manage link per ticket and an “Email me these links” action for anyone who lost their confirmation email.

What the organizer sees: attendee records show the link in both directions, the CSV/XML export gains “Activity of (main ticket #)” and “Activity tickets” columns, and – if the Admin Flags addon is active – the main attendee is auto-flagged per held activity (e.g. activity-contributor-day) for filtering and integrations.

The addon is built and fully verified locally – not yet merged. It passes WordPress coding standards The Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. May also refer to The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the PHP coding standards. cleanly, a 54-test automated suite, and a 40-check live end-to-end run against a real WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. site setup, including on the newest supported PHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php version. A pull request against wordcamp.org will follow this feedback round.

1. The name. “Activity ticket” is the current working name (an earlier round of feedback ruled out “Companion ticket” – it reads as a guest/plus-one ticket). Does “Activity ticket” read right to you, and does it translate well for your community? Suggestions welcome – the name is display-only and easy to change.

2. Your stories. If you’ve run a Contributor Day, a Social Dinner, or any capacity-limited side event: does this flow match how your event actually works? What edge cases have you hit – transfers, speakers and volunteers, walk-ins, waitlists – that we should think about?

Please share your thoughts in the comments here. Thanks for reading!