This is the home of the Make Community team for the WordPress open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project!
Here is where we have policy debates, project announcements, and assist community members in organizing events.
Everyone is welcome to comment on posts and participate in the discussions regardless of skill level or experience.
Get Involved
If you love WordPress and want to help us do these things, join in!
When you organise a WordCampWordCampWordCamps 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. you get to a point where you need to issue coupons for speakers, organisers, volunteers and sponsors. Usually, coupons are “shared” with others from that group: volunteers will share a coupon code, speakers will share a different coupon code, and so on.
Using a shared coupon code also means that we need to verify every coupon that was used: is the buyer entitled to use the coupon code? Not every WordCamp team does this, but the WCEUWCEUWordCamp Europe. The European flagship WordCamp event. team does this.
For WCEU 2023 below is an overview of coupon codes that are needed:
Photographers: 24
Volunteers: 190
Speakers: 70
Organisers: 99
Sponsors: 208
Total of 591coupon codes
As you can imagine this number causes quite a huge workload on the team that is responsible for the tickets, especially when they come across a name that is not on the list: then these names need to be flagged and also verified. Maybe this name was initially missed on the list? Or maybe this name is replacing someone else?
Smaller WordCamps may have around 125 coupon codes, but they don’t have a dedicated team just for the attendee services, but probably one person responsible for the tickets and verifying the coupon codes.
Using a personalised and unique code for everyone entitled to a coupon code is the best solution. Coupon codes are matched against a name and if there’s a mismatch: you know who to approach. Also: the personal coupon code can’t be shared endlessly with other people who are not involved in the WordCamp. And, not less important: it saves us from cancelling tickets that have been booked by people who shouldn’t use the tickets and also from hurting people’s feelings as they might feel offended when we contact them to inform them.
There are WordCamps that have created workarounds for personalised coupons, all were done through some side coding solutions, not as a real solution. So there is definitely a need for personalised coupon codes.
In the past couple of weeks, Vagelis Papaioannou developed a pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party that generates personalised coupon codes. You can find his repository on GitHub. It’s an add-on to the CampTix plugin. This plugin would really help WordCamp organisers create personalised coupons and save them a lot of time and unnecessary work.
As a WordCampWordCampWordCamps 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. organizer, I would like to see CampTix Attendee data populate in a Google Sheet instead of only being available as a downloadable CSV file. This would allow organizers to make a live set of data available for their needs including but not limited to on-demand badge printing.
Integration with on-demand badge printing solutions
I am an organizer of WordCamp US 2022 and am posting this during contributor dayContributor DayContributor 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://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.. Over the last 3 days, I observed the process we had in place between WCUSWCUSWordCamp US. The US flagship WordCamp event. and the vendor we used to print our badges.
About two weeks before the event, a CampTix export was created.
Unnecessary columns in the export were removed leaving only the columns the vendor needed: name, pronouns, company, Twitter handle, and ticket type (attendee, sponsor, speaker, media, volunteer, organizer).
A review of the export was performed, by hand, and removed characters that the vendor couldn’t print (leaving only UTF-8 characters).
About one week before the event, the modified export was sent to the badge vendor.
The badge vendor uploaded our CSV file to Google Drive, and mapped the various columns to positions where text would appear on the badge.
Due to last minute changes to ticket details, the export from two weeks before the event was stale in a few cases:
Attendees that update their ticket information (name change, company change etc.) caused old information to still appear on the badge.
Attendees that refunded their ticket still had a badge available to be printed.
Attendees who purchased an available (recently refunded) ticket weren’t able to print their badge.
A manual process was necessary to update incorrect information, or add missing people to the vendor’s Google Sheet.
Organizers only need to create an “export” once
Recent exports I have in my Downloads folder
Over the course of planning a WordCamp, I find I am often pulling a fresh CampTix export. For the same reasons that I spelled out in the section above, an export becomes increasingly less valuable as time passes. While the CampTix Summarize tool is useful when looking for a count of attendees and how they answered a particular question, sometimes more specific information is needed. For example, it’s useful to see the attendee’s name and their answer, especially in the case of:
Microsponsors
T-shirt sizes
Life-threatening allergies
AccessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) needs
For me, the export CSV file isn’t usable until I open it in a spreadsheet application and I don’t have one installed on my computer. So, I end up uploading the file into my WordCamp’s Google Drive and open the file with Google Sheets before I can begin working with it. It would simplify the workflow by having the data immediately available in Google Sheets.
Integration Proposal
We already allow a non-logged user to access CampTix data through the Attendance UIUIUI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.. This proposal adds a new tab on the screen below called Export Integration. It would have a radio field titled Enabled and a text area field titled Secret Link similar to the screenshot.
CampTix Attendance UI
Once the Secret Link from the Export Integration is generated, it should be embedded inside the Google Sheets function IMPORTDATA() which would populate the sheet. If there are multiple use cases for Google Sheet integrations, additional Google Sheet files can be created that invoke the IMPORTRANGE() function. If only a select number of columns or rows are needed for a particular use case, the limited access use case could be wrapped by a QUERY(). Here’s an example that might make sense for the microsponsor scenario: =QUERY(IMPORTRANGE("1gcuSqpN-x1NCn5ZaEKc_IhoBFQAlMhpjtjE1eUL4ZJo"), "SELECT C, D, E WHERE B='Microsponsor'", FALSE)
Feedback
I’m seeking feedback on this proposal through the end of September. Please let me know if you have any questions or need clarification.
There are changes coming to the ticket selection table, order summary, registration form, and edit form to improve the accessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) of registering for a WordCampWordCampWordCamps 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.. The changes will deployDeployLaunching code from a local development environment to the production web server, so that it's available to visitors. tomorrow, March 3rd, around 16:00 UTC.
Right now, most form fields didn’t have an “accessible name”, instead the form relies on the table layout to show which question corresponds to each input. This only works for sighted users— for anyone using a screen reader, the form fields are functionally unlabelled.
After this change, all inputs will have labels attached, so screen readers and other assistive tech will be able to connect the questions (for example, First Name) to the text input for the answer. This also changes some of the markup, which might affect your WordCamp’s style, if you have any custom CSSCSSCSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site..
All ticket questions are now wrapped in a label element
All inputs have a unique ID (but this should not be used for styling)
Questions with multiple answers (radio buttons or checkboxes) now have their answers wrapped in a fieldset
The ticket selection table has also been updated so navigating through selecting a ticket is easier.
The quantity dropdown now uses the ticket name as the label
The ticket name is now wrapped in a label, instead of strong, and that table cell is now a th instead of td.
This fixes metaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. ticket #1591, you can see the full changes on the GitHub PR. Please check your tickets page, especially if you’ve done any custom styling to it, and let us know in #meta-wordcamp on slackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (or here in the comments) if you see anything unexpected.
The task that was assigned to be at WCEUWCEUWordCamp Europe. The European flagship WordCamp event. was to draft documentation for the Camptix Notify functionality of WordCampWordCampWordCamps 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. sites, including some notes on the date format for the Purchased Date field in the filterFilterFilters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. conditions.
I’ve tried to keep the documentation as non technical as possible, but as a developer I would appreciate feedback from the rest of the community.
I therefore ask anyone interested to review the document via Google Drive and leave your comments/suggestions on this post so that we can discuss changes or improvements.
I’d like to give this a two week deadline for comments until Friday the 13th (dun dun dun!) of July, in order to move the process of having this included into the WordCamp docs along promptly.
I have a couple of observations about CampTix that I’d like to share with the team.
This is the first year we have used CampTix for WordCampWordCampWordCamps 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. Sydney and we have received quite a lot of queries from attendees asking 1) can we send them a proper invoice? and 2) where is my ticket?
1) There are no tax or currency on this receipt and the title of the email is “Your ticket to WordCamp Sydney 2016”. It’s not very intuitive that this is an invoice and not very helpful for claiming tax back as a business expense. It looks more like a payment notification. Perhaps the design could be tweaked to make it look more like an invoice.
There is also no way to regenerate this email if say the email gets intercepted by spam filters and the recipient never gets it. We tell them to login to their PayPal account and print the transaction but I’m sure it would be super easy to add a button to resend receipt/invoice.
2) where is my ticket?
The email’s title is “Your Ticket to WordCamp Sydney 2016”, however the body of the email looks more like a notification of purchase rather than a ticket.
We’ve had about 60 people saying that their ticket was not emailed, only to figure out that they didn’t realise that email was their ticket.
It could be due to the fact we’ve use eventbrite in the past which emails attendees something that looks like a conference ticket that they can print out and bring with them (name, event title, date, ticket type etc).
I’m sure the CampTix email could be designed better to make it look like an actual ticket.
Heads up! Today we’re changing the PayPal account that’s connected to CampTix from the account owned by the WordPress FoundationWordPress FoundationThe WordPress Foundation is a charitable organization founded by Matt Mullenweg to further the mission of the WordPress open source project: to democratize publishing through Open Source, GPL software. Find more on wordpressfoundation.org. to an account owned by the Foundation’s subsidiary, WordPress Community SupportWordPress Community SupportWordPress Community Support PBC is a Public Benefit Corporation, created specifically to be the financial and legal support for WordCamps, WordPress Meetup groups, and any additional “official” events organized within the WordPress Community Events program., PBC.
Since we have already talked to PayPal about making this switch, they know to expect high volume on this new account, and we don’t anticipate any issues with payment processing for WordCampWordCampWordCamps 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. tickets. If you notice issues with ticket purchasing, please notify us in wordpress.slack.com in the #meta-wordcamp channel, and we’ll investigate.
This change will, unfortunately, break self-serve refunds for folks who have purchased tickets in the past 2 months. We’re going to handle those refunds manually. This will be inconvenient, but we think the hassle is worth the benefit of creating a clean financial break with the Foundation for ticket revenue.
As of today, if you are contacted by an attendee requesting a refund for a ticket purchased between 1/1/2016 and 3/1/2016, please email support@wordcamp.org with the following info:
Purchaser’s name:
Purchaser’s email address:
PayPal Transaction ID for the ticket purchase:
Date of the ticket purchase:
Date of the event:
As long as the ticket purchase happened between between 1/1/2016 and 3/1/2016 and the refund request came in before the event, we will refund the ticket within a week of receiving the email to support@wordcamp.org. We’ll probably do refunds in batches on a weekly basis, I’m guessing on Fridays. 🙂
