EventON PDFer - WordPress Plugin

How to Configure EventON PDFer for PDF Tickets and RSVP Confirmations

EventON PDFer should not be treated as a standalone calendar or a universal PDF generator for any WordPress content. It is a narrow operational layer inside the EventON ecosystem. Its job is to attach a PDF file to emails that are already being sent through EventON Tickets or EventON RSVP. That is why this guide focuses not on a general product overview, but on the workflow of "event - ticket or RSVP - email - PDF file - entry check."

Below, you will find a breakdown of site preparation, addon installation, enabling generation in EventON > Settings > PDFer, configuring the HTML template, testing PDFs for paid tickets, and a separate workflow for RSVP confirmations. It also shows how to diagnose situations where the email is sent without an attachment, the PDF is generated with broken layout, a WooCommerce order does not trigger ticket delivery, or the attendee cannot find the expected file in the email.

This guide is intended for an event site owner, WordPress administrator, technical editor, or developer who needs to quickly understand where PDFer's responsibility begins and ends. PDFer itself does not sell tickets, replace WooCommerce, create RSVP forms, or scan attendees at the door. It strengthens an already configured confirmation delivery process, so the quality of the final result depends on the underlying setup of EventON, Tickets, RSVP, WooCommerce, and email delivery.

Where PDFer Fits in the EventON Workflow

The biggest mistake people make when first looking at PDFer is expecting it to provide its own download page, an export button on every event, or a separate registration system. According to the official description, the addon works through EventON in one of two scenarios: purchased tickets through Tickets or confirmations through RSVP. For tickets, WooCommerce is also required, because it handles the order, ticket product, payment status, and the emails after which EventON Tickets sends the ticket to the buyer.

If you think of the process as a chain, EventON stores the event and its event page, Tickets or RSVP create the attendee action, and PDFer turns that confirmation into an attached PDF file. The practical takeaway is straightforward: test PDFer on a fully assembled registration or purchase workflow, not on an empty event. Otherwise, you may enable PDF generation and still see no file because no ticket was created, the order was not completed, the RSVP email is not being sent, or your mail setup blocks attachments.

PDFer settings include an option to enable generation and a way to configure the template using basic HTML markup. The official page also makes one important preview limitation clear: the user can preview the HTML design that will be used for the future PDF, but not the fully generated PDF exactly as it will appear in the inbox. That affects testing order: first check the HTML preview, then the actual email, then the file itself.

What the Official Workflow Confirms

For Tickets, PDFer adds a PDF version of the ticket to the email sent after purchase. For RSVP, it adds a PDF confirmation to the RSVP email. In both cases, the file is meant to be easy to download and print, not just a duplicate of the public event page. If you already use Check-ins or QR Code with EventON, the PDF can serve as a printable pass for entry, but attendee validation itself still has to happen through the relevant addon or a manual list.

Why This Is Not the Same as Standard PDF Export

PDFer should not be described as a tool for bulk calendar export, PDF event flyers, conference programs, or arbitrary event lists unless that is confirmed by your installed version and the developer's documentation. The officially confirmed use case is PDF tickets and PDF confirmations. Everything in this article is built around that scope so it does not promise features your setup may not actually include.

Who This Confirmation Delivery Method Works Best For

A PDF attachment is useful when an attendee needs to save the confirmation separately from the email, print it, show it at entry, or forward it to an organizer without digging through a long email thread. For a small event site, a standard EventON email may be enough. But if entry is managed by volunteers, venue staff, or a registration team, a separate PDF often reduces confusion: the attendee has a file, the organizer has a predictable format, and the person checking entry does not have to search the email body for order details.

EventON PDFer is especially appropriate in three kinds of situations. First, paid events where Tickets and WooCommerce are already configured and the buyer needs to receive the ticket as an attachment. Second, RSVP events without ticket sales, such as an open lecture, private meetup, workshop, club event, or retreat where participation needs to be confirmed. Third, venues where visitors arrive with a printed pass or save the file on their phone, and the entry team verifies the name, event, date, location, or QR code if one is added through other EventON addons.

You should not enable PDFer just to get a nicer attachment if the site still cannot reliably send email, tickets do not move through a completed order, the RSVP form has not been tested, or the administrator does not yet know what information belongs in the confirmation. A PDF file will not fix weak email delivery or replace a test order. It makes an existing process cleaner, but it does not create that process from scratch.

The practical rule is simple: if a person already receives an email after registering and that email can reasonably be treated as participation confirmation, PDFer can improve that step. If there is no confirmation workflow yet, build the workflow first.

What to Check Before Installation

Before installing PDFer, it is worth doing a quick environment check. This saves time because most PDF attachment issues do not show up at the moment you turn on PDFer. They usually surface in neighboring layers: server memory, PHP extensions, WooCommerce statuses, mail transport, email templates, and cache conflicts.

Core Dependencies

The minimum setup depends on the scenario. For RSVP, you need EventON and the RSVP addon. For tickets, you need EventON, the Tickets addon, and WooCommerce. If you use Check-ins, QR Code, or Seats, they can complement entry validation, but they do not replace PDFer. Do not start troubleshooting PDFer until you have confirmed that the underlying ticket or RSVP process works without a PDF.

• Make sure EventON is active and the event is published.
• For tickets, confirm that WooCommerce is installed, the cart and checkout pages work, and a test order can move to the required status.
• For Tickets, verify that a ticket is enabled in the event, with price, SKU, and capacity filled in if needed.
• For RSVP, confirm that the form opens, submits, and creates an attendee confirmation.
• Check email delivery: the email without a PDF should reach the test address.

Server Resources and Memory

Generating a PDF is heavier than sending a standard HTML email. EventON's official system requirements specifically call out higher resource needs for sites using addons, Tickets, and WooCommerce. In practice, that means on weak hosting the PDF may fail to generate, the email may stop mid-process, and a PHP error may appear in the WordPress logs. If the site sells tickets, do not limit testing to the event page alone. Walk through the full order flow.

Safe check: enable PDFer on a test or staging site first. If no staging site is available, use a private test event, a separate test ticket, and an admin email address so you do not send real emails to attendees while configuring the setup.

Templates and Theme

The PDFer changelog shows that support for child themes was added for ticket PDFs and that layout issues related to ticket placement on the PDF page were fixed. That is an important signal: if you plan to modify the template, use a child theme or the built-in template mechanism instead of editing addon files directly. After an update, any changes made inside the plugin folder can disappear, and broken HTML markup can stop PDF generation entirely.

Also check whether your theme already overrides the Tickets or RSVP email templates. Official EventON documentation shows that emails can be copied into the theme folder and edited there. That is convenient, but with an old override in place, the new PDF workflow may behave differently than it does on a clean installation.

Installation and a Careful First Test

PDFer is installed like a standard WordPress addon. EventON's general addon instructions boil down to uploading the ZIP file through Plugins > Add New, choosing Upload, installing it, and activating it. At this stage, do not touch the templates or HTML yet. First make sure WordPress recognizes the addon and that a PDFer section appears in the EventON settings.

1. Open the WordPress admin panel and go to Plugins > Add New.
2. Select Upload Plugin, upload the addon ZIP archive, and click Install Now.
3. After installation, click Activate.
4. Open EventON > Settings > PDFer and confirm that the section is available.
5. Do not change the template design yet: enable only the minimum PDF generation settings and save.

If the PDFer section does not appear, do not move on to a test order. Check whether the main EventON plugin is active, whether a PHP error appeared after activation, whether the server meets EventON's addon requirements, and whether WordPress disabled the plugin after a critical error. If WordPress sent a site recovery email, keep it for troubleshooting, but do not expose server paths or personal order data in public materials.

Test Workflow for Tickets

For tickets, simply creating an event is not enough. You need to enable the ticket in the event settings, fill in the details, publish the event, complete the purchase flow, and move the order to the status that triggers the EventON Tickets email. The official Tickets documentation highlights a few practical details: the price must be a decimal value, the SKU matters for WooCommerce product identification, and once the event is published, a related product is created.

Test Workflow for RSVP

For RSVP, test the form on the public event page. If the form opens in a lightbox and looks bad on some devices, EventON documentation describes an alternative: display the RSVP form inside the eventCard. This is not directly a PDFer setting, but it matters as part of the overall registration experience. If the attendee cannot submit an RSVP, the PDF confirmation will never appear.

Configuring PDFer After Activation

The PDFer settings section should answer two questions: when the PDF should be created and what the file should look like. According to the official page, the toggle lives in EventON > Settings > PDFer, and the template can be customized with basic HTML. Do not try to build a complex design right away. PDF engines are stricter about HTML and CSS than browsers are: tables, nested blocks, external fonts, and unusual styles may render differently in the final PDF.

Minimum Working Configuration

For the first pass, keep the template as simple as possible. The goal is to prove that the file is being generated and attached to the email. Only after that should you add a logo, extra lines, color accents, and branding elements. As a guideline, use the information the attendee actually needs at the door: the event name, attendee or buyer name, date and time, location, ticket type or RSVP status, and a service identifier if one already exists in the ticketing flow.

• Enable PDF generation only for the scenario you actually use: Tickets, RSVP, or both.
• Save the template with a simple structure, without complicated grids or external scripts.
• Check the HTML preview in the RSVP or Ticket record if your version provides one.
• Send a real test email and open the attachment in a standard PDF viewer.
• After each edit, save a reference PDF so it is easier to identify the change that broke the layout.

What to Include Only When Necessary

Do not overload the PDF with the entire event page. For entry to an event, you rarely need the long description, gallery, map, promotional blocks, or the full page text. The less unnecessary data you put into the PDF, the more likely it is to print reliably. If you need to add attendance rules, entry instructions, or the address, keep it to a short block. If you want a map, first verify how it renders in the PDF and whether it makes the file too large.

Example of a Simple HTML Structure

The example below is not a universal PDFer API template and not a required set of variables. It is simply a safe markup approach: start with a table layout, short lines, and inline styles, because those elements tend to be more predictable in PDF output than complex flex or grid layouts. Use only the specific variables and fields available in your version of PDFer or in the documentation for the installed addon.

<table style="width:100%; border-collapse:collapse; font-family:Arial, sans-serif;">
  <tr>
    <td style="padding:12px; border-bottom:1px solid #ddd;">
      <strong>Event Name</strong><br>
      Date, time, and location
    </td>
  </tr>
  <tr>
    <td style="padding:12px;">
      Attendee: Attendee Name<br>
      Confirmation Type: Ticket or RSVP
    </td>
  </tr>
</table>

The post-edit check is simple: the PDF should open, the text should stay within the page boundaries, and the email should arrive with one expected attachment. If that works, add styling gradually. If the PDF stops generating after adding a block, roll back the last edit and check the HTML for unclosed tags.

PDF Tickets: Order, Status, and Attachment

The Tickets workflow is the most sensitive one because it involves EventON, Tickets, WooCommerce, email delivery, and PDFer. The user sees only the ticket email, but inside the site several status transitions happen: the event creates a ticket product, the visitor places an order, WooCommerce changes the order status, EventON Tickets sends the email, and PDFer adds the file. If any one of those steps fails, the PDF may never appear even when PDFer itself is configured correctly.

Creating the Ticket in the Event

Open the Event Tickets block in the event, enable the ticket, and fill in the key fields. It is best not to skip the SKU: the Tickets documentation explicitly states that WooCommerce uses it for product identification. If the price is entered in a format Tickets does not accept, you may end up with an empty cart or a failed purchase flow. For testing, use a simple price and a single ticket type, then add more advanced options later.

Minimum Ticket Test

1. Create a private or test event.
2. Enable the ticket, enter the price in decimal format, and fill in the SKU.
3. Publish or update the event so the related WooCommerce product is created.
4. Open the public event page and confirm that the ticket appears in the eventCard.
5. Place a test order and move it to the status that triggers the ticket email.

Why Order Status Matters More Than the PDF Button

PDFer should not send the ticket before the ticketing workflow considers the order ready. The PDFer changelog includes an old fix related to preventing PDF generation from appearing for incomplete orders. That is why WooCommerce order status should always be part of troubleshooting. If the order is stuck in pending payment, never reaches automatic completion, or your payment gateway changes statuses in an unusual way, the email with the PDF may never go out.

If manually moving the order to completed sends the PDF email, but the automatic payment gateway callback does not, the problem may not be the PDF template at all. It may be the timing of status changes and email actions. In that case, do not try to fix the HTML blindly. First save the error log, test the behavior without PDF generation, and compare the exact step where email delivery stops.

What the Buyer Should Receive

The buyer's end result should be predictable: an email with the ticket and a PDF attachment that can be downloaded and printed. If QR Code, Check-ins, or Seats are enabled, the ticket may also carry entry or seat data, but that comes from adjacent addons. For PDFer, what matters is that the file is tied to the correct event and retains the order data it needs.

PDF for RSVP: Confirmation Without Ticket Sales

The RSVP workflow is simpler because it does not require a WooCommerce order. But it is no less important to test: if the RSVP form is unstable, the email is not sent, or the attendee submits incomplete data, the PDF confirmation will not be useful. Here, PDFer helps turn the RSVP email into a more practical pass the attendee can save separately.

For events without payment, a PDF confirmation often solves an operational problem: it is easier to verify the attendee name and event at the door than to search through a list of emails. This works well for workshops, open classes, training sessions, private meetups, presentations, local clubs, and events with limited seating. But if you do not actually have a guest check-in process, the PDF may turn into an unnecessary attachment.

Test the Form Before the PDF

First send an RSVP without complex PDF customization. Make sure the attendee receives the confirmation, the administrator sees the submission, and the event data is correct. If the form opens in a lightbox and conflicts with the theme or mobile layout, EventON offers the option to show the RSVP form inline inside the eventCard. That switch may be more useful than trying to configure the PDF while the form itself is not working reliably.

What to Include in an RSVP PDF

For RSVP, it is usually enough to include the attendee name, event title, date, location, participation status, and a short entry instruction. Do not include personal data in the PDF that the person checking entry does not actually need. If you collect extra RSVP fields, include only the ones that genuinely help the organizer, such as a selected session, guest count, or accessibility note if that is part of the workflow.

Quick Result Check

• The PDF arrives together with the RSVP email, not as a separate confusing message.
• The file shows the correct event, not an old test template.
• The attendee details are readable without zooming in.
• The date, location, and key identifier are not cut off when printed.
• If the RSVP changes, the behavior of any follow-up email is clear to the administrator.

The RSVP workflow clearly shows what PDFer is for: it does not complicate registration, it makes the confirmation more convenient for both the attendee and the team at entry.

Templates, HTML, and Safe Customization

PDF customization is both the biggest temptation and the most common source of problems. The official PDFer changelog mentions basic HTML for ticket PDFs, custom ticket PDF templates, layout fixes, and child theme support. The Tickets and RSVP documentation also shows that emails can be overridden through the theme folder. All of that points in the right direction: change the design through supported templates and careful HTML markup, not by editing plugin files directly.

What You Can Safely Change

Safe customization starts with content. First decide which lines belong in the PDF. Then confirm which variables and fields are available in your version. Only after that should you change the visual design. If you do not have a confirmed list of PDFer variables, do not drop random PHP functions into the template. A PHP error can stop the email entirely, while an HTML error more often results in a broken PDF layout.

• Add a logo only after confirming that a simple PDF works without images.
• Use short inline styles if the PDFer interface accepts HTML.
• Avoid complex CSS properties, external fonts, and scripts.
• For template changes, use a child theme or a documented override path.
• Retest the PDF after updates, because the changelog shows regular fixes to PDF generation.

How Not to Break the Email

The safest sequence is this: first test the default template, then make one small edit, then send a new email. Do not change the logo, table, extra fields, styles, and translation all at once. If the email stops sending, you will not know what actually caused it. If the email sends but the PDF will not open, focus on the HTML. If the email does not send at all, check for a PHP error, the order status, the mail transport, and a conflict with another plugin.

Limitation: do not edit EventON, Tickets, RSVP, or PDFer files inside the plugin folder. An update can overwrite those changes, and a critical error in the ticket template can stop confirmations from being sent.

Localization and Readability

If the site is in Russian, the PDF should be understandable to a Russian-speaking attendee. But technical fields, plugin names, and EventON system labels may still remain in English if that is how the interface works. Check encoding, Cyrillic text, line wrapping, and print output. PDF engines sometimes handle fonts differently, so Russian characters need to be tested in the actual file, not only in the HTML preview.

Practical Example: A PDF Pass for a Festival Using Tickets and RSVP

Imagine a small festival website with two types of events: paid workshops sold through Tickets and WooCommerce, and free open sessions collected through RSVP. The organizer wants attendees to receive equally clear confirmations: a paid ticket as a PDF and a free RSVP pass as a PDF. This is a strong use case for EventON PDFer because one product covers two similar but distinct confirmation delivery workflows.

Goal

Get two verifiable outcomes: the buyer of a paid workshop receives an email with a PDF ticket after the order is completed, and the attendee of a free session receives an email with a PDF confirmation after submitting RSVP. Both files should contain the event title, attendee name, date, location, and a short entry instruction.

Preparation

Before configuring PDFer, the site should already have EventON, Tickets, RSVP, and WooCommerce working for paid events. Create two test events: one with a ticket and one with RSVP. For the ticket, fill in the price, SKU, and capacity if needed. For RSVP, test the form and the email without a PDF. Do not use real attendee addresses until the workflow has passed testing.

Steps

1. Enable PDF generation in EventON > Settings > PDFer and save the settings.
2. Keep the PDF template simple: event title, date, location, attendee, confirmation type.
3. Place a test order for the paid event and move it to the required status.
4. Open the resulting email, download the PDF, and check readability.
5. Submit an RSVP for the free event from a different test email address.
6. Compare the two PDFs: the data may differ, but both should be equally clear for the person checking entry.

Verification

Do not check only for file presence. Open the PDF on a computer and a phone, print one page, check the attachment size, verify Cyrillic support, and confirm that the file belongs to the correct event. If the ticket includes a seat, ticket type, or QR code from another addon, make sure that information is still present in the PDF.

A Common Issue That Gets in the Way

For the paid event, the email may depend on the WooCommerce status. RSVP has no equivalent status, so the issue may show up only for tickets. If the RSVP PDF arrives but the ticket PDF does not, do not blindly rework the global PDFer template. First check the order, SKU, status, the Tickets email without PDF, and the error log.

How to Verify the Result After Setup

Testing PDFer should look more like a control checklist than a quick glance in the admin panel. The setup is only considered working when the administrator sees the event, the attendee receives the email, the PDF opens, the data matches, and the person checking entry understands how to use the file.

Email Check

If the event is high-volume, send test emails to multiple mail services. Some email systems are stricter about attachments, large images, and HTML emails. If the email lands in spam, PDFer may have nothing to do with it. Check the sender setup, SPF/DKIM/DMARC for the domain, the SMTP plugin, and the attachment size.

PDF Check

Open the file in several PDF viewers. Check whether fields are cut off, the logo has shifted, the text has turned into strange characters, or Cyrillic letters have disappeared. If the PDF is meant for printing, print one file on a standard sheet of paper. If the PDF is meant to be scanned, test the code or identifier with the exact tool your entry team will be using.

Post-Update Check

After updating EventON, Tickets, RSVP, WooCommerce, or PDFer, rerun a short test. This is not just a formality: the PDFer changelog shows that the developer fixed PDF generation, preview behavior, ticket page breaks, and template support. Updates can improve behavior, but old template overrides in the theme sometimes remain unchanged.

Quick takeaway: a working PDFer setup is not "the setting is enabled," but "the test email arrived, the PDF opened, the data is correct, and the entry team can actually use the file."

Performance, Email, and Data Security

A PDF attachment adds load to both the server and the mail channel. On a small site, that may be almost invisible, but with a high volume of orders, PDF generation becomes part of a critical workflow. If the server runs out of memory, the email may never send. If the attachment is too large, the mail service may delay or reject it. If the template includes unnecessary personal data, you make user data handling more complicated than it needs to be.

Email Delivery

For stable sending, use a proper SMTP transport or a proven WordPress mail integration. EventON specifically recommends using an SMTP plugin to resolve email delivery issues. PDFer should not be the first step in your mail setup. First make sure standard Tickets and RSVP emails are delivered reliably.

PDF Size

Do not insert large images unless they are truly necessary. A logo can be optimized, background images are usually better left out, and long event descriptions should stay on the website page. If an attendee receives multiple tickets, test how PDFer handles each one and whether it creates a file that becomes awkward to send by email. The PDFer changelog includes a fix related to printing each ticket on its own page, so testing multi-ticket orders is especially important.

Personal Data

A PDF can easily travel farther than a standard email: an attendee may forward it to a colleague, print it, or show it at the door. So include only the data actually needed for attendance and verification. Do not add the full address, phone number, admin notes, payment details, or WooCommerce internal data unless the person checking entry genuinely needs them.

When EventON PDFer Is the Right Choice

EventON PDFer is worth using if you already have a working EventON site with Tickets or RSVP, email delivery is stable, and attendees need a separate PDF file for printing, saving, or entry verification. In that case, the addon fills a specific gap: it turns a confirmation into a file that is easy to open independently of the email.

If you are still setting up the calendar itself, have not tested WooCommerce statuses, do not yet know which emails go out after RSVP, or want a PDF catalog of all events, PDFer should not be your starting point. Build the core registration and purchase workflow first. Then enable PDF, test the file, and customize the template step by step.

Before deploying on the live site, run through a short control check: test ticket, test RSVP, email without PDF, email with PDF, one-page print test, Cyrillic check, and post-update retest. If all of that passes, you can download the installation package and move on to a careful rollout for real events.