{"id":145088,"date":"2025-09-05T06:38:41","date_gmt":"2025-09-05T13:38:41","guid":{"rendered":"https:\/\/help.fooevents.com\/?post_type=docs&#038;p=145088"},"modified":"2026-02-06T00:36:19","modified_gmt":"2026-02-06T08:36:19","slug":"temas-de-bilhetes-personalizados","status":"publish","type":"docs","link":"https:\/\/help.fooevents.com\/pt\/docs\/topics\/tickets\/ticket-themes\/custom-ticket-themes\/","title":{"rendered":"Temas de bilhetes personalizados"},"content":{"rendered":"<p>This document shows how to build a custom FooEvents ticket theme by starting with the <strong>Canvas Ticket Theme<\/strong>. Canvas is a starter template designed as a foundation for custom ticket designs. It outputs all FooEvents ticket data in a simple, clean format with basic HTML and a little PHP, which makes it ideal for extending and branding.<\/p>\n<p>We\u2019ll cover the folder layout, where themes live, how the config works, how to assign your theme to a product, and the key places to customize markup safely for both HTML email and PDF output.<\/p>\n<h3><strong>Prerequisites<\/strong><\/h3>\n<ul>\n<li>A <a href=\"https:\/\/woocommerce.com\/\" target=\"_blank\" rel=\"noopener\">WooCommerce<\/a> site with <a href=\"https:\/\/www.fooevents.com\/\" target=\"_blank\" rel=\"noopener\">FooEvents<\/a> installed and activated.<\/li>\n<li>FTP\/SFTP access (or equivalent) to upload files.<\/li>\n<li>A code editor (VS Code, Sublime, PhpStorm, etc.).<\/li>\n<li>A test product configured as a FooEvents event so you can send ticket previews and resends.<\/li>\n<\/ul>\n<h3><strong>1) Download the Canvas Ticket Theme<\/strong><\/h3>\n<p>Download and unzip the free <a href=\"https:\/\/www.fooevents.com\/product\/canvas-ticket-theme\/\" target=\"_blank\" rel=\"noopener\">Canvas Ticket Theme<\/a> to your local computer.<\/p>\n<h3><strong>2) Theme files<\/strong><\/h3>\n<p>These are the key files you will edit when working on your custom ticket theme:<\/p>\n<pre><code>\u251c\u2500 <strong>config.json<\/strong>        \u2190 Declares name and compatibility (HTML\/PDF\/POS)\r\n\u251c\u2500 <strong>header.php<\/strong>         \u2190 Email\/PDF head + opening body markup and CSS\r\n\u251c\u2500 <strong>ticket.php<\/strong>         \u2190 Main body; executes once per ticket\r\n\u251c\u2500 <strong>footer.php<\/strong>         \u2190 Closing body\/html tags, footer CSS overrides\r\n\u251c\u2500 <strong>images\/<\/strong>            \u2190 Image assets (including preview thumbnail)\r\n\u251c\u2500 <strong>readme.txt<\/strong>         \u2190 Theme metadata (human-facing)\r\n\u2514\u2500 <strong>License\/<\/strong>           \u2190 GPL\r\n\u2514\u2500 <strong>preview.jpg<\/strong>        \u2190 Thumbnail shown in the Ticket Themes screen.\r\n<\/code><\/pre>\n<p>The main files you will be working on are the following template files:<\/p>\n<ul>\n<li><code><strong>header.php<\/strong><\/code> will typically include a strict XHTML email doctype, resets, Outlook\/Apple Mail tweaks, and a <code>$font_family<\/code> placeholder that Canvas already wires up.<\/li>\n<li><code><strong>ticket.php<\/strong><\/code> renders the ticket content; it\u2019s executed <strong>for each ticket<\/strong> in the email.<\/li>\n<li><code><strong>footer.php<\/strong><\/code> closes out the HTML\/PDF document.<\/li>\n<\/ul>\n<h3><strong>3) Update the name of the ticket theme\u00a0<\/strong><\/h3>\n<p>Create a working copy of the Canvas Ticket Theme so you can modify it without touching the original.<\/p>\n<h4>Folder Name:<\/h4>\n<p>Rename the unzipped folder to a unique slug, for example, change &#8216;canvas_custom_theme&#8217; to something like &#8216;myticket_theme&#8217;. Give your theme a distinct name and declare which outputs it supports. Use lowercase and underscores only (no spaces). This folder name becomes your theme\u2019s handle.<\/p>\n<h4>config.json (Canvas default):<\/h4>\n<pre><code class=\"language-json\">{\r\n  \"name\": \"Canvas Ticket Theme\",\r\n  \"supports-html\": \"true\",\r\n  \"supports-pdf\": \"true\",\r\n  \"supports-pos\": \"false\"\r\n}<\/code><\/pre>\n<p>In the config.json file you can also decide whether this custom theme will also support PDF tickets. If you intend to design only for HTML email, set:<\/p>\n<pre><code class=\"language-json\">\"supports-pdf\": \"false\"\r\n<\/code><\/pre>\n<p>If you\u2019ll support both HTML and PDF, keep it <code>\"true\"<\/code> and test both outputs separately.<\/p>\n<p><strong>Note:<\/strong> These values are strings <code>\"true\"\/\"false\"<\/code> in Canvas; keep that format for compatibility.<\/p>\n<h4>readme.txt<\/h4>\n<p>Update the \u201cTicket Theme Name\u201d and description to reflect your custom theme. This file is informational but helps when scanning many custom themes.<\/p>\n<h4>preview.jpg<\/h4>\n<p>Update the preview.jpg image thumbnail so that your ticket theme is easy to identify.<\/p>\n<h3><strong>4) Uploading Your Ticket Theme to Your Site<\/strong><\/h3>\n<p>FooEvents ticket themes are located in a FooEvents theme folder on your site. FooEvents automatically discovers themes in this directory. Using FTP\/SFTP, upload your new ticket theme folder to the following location on you site:<\/p>\n<pre><code>\/wp-content\/uploads\/fooevents\/themes\/<\/code><\/pre>\n<h3><strong>5) Assign the custom theme to a product<\/strong><\/h3>\n<p>In order to test and use a ticket theme, you will need to assign it to a product. Open a WooCommerce product that has been <a href=\"https:\/\/help.fooevents.com\/docs\/topics\/events\/event-setup\/\">configured as a FooEvents event<\/a>, and set the ticket theme settings to use this ticket theme so you can send actual test tickets while you iterate.<\/p>\n<p>In WordPress, edit your event product and open <strong>Product data \u2192 Ticket Settings<\/strong>. Set the <strong>HTML ticket theme<\/strong> to <strong>MyTicket Theme<\/strong>, then save.<\/p>\n<p>If you\u2019re also using <a href=\"https:\/\/www.fooevents.com\/products\/fooevents-pdf-tickets\/\" target=\"_blank\" rel=\"noopener\">FooEvents PDF Tickets<\/a>, you can either disable it while you are testing, or if you have decided to make your ticket theme PDF-compatible, be sure to select your new theme under the <strong>PDF Ticket Theme<\/strong> setting.<\/p>\n<h3><strong>6) Canvas header and footer (email-safe boilerplate)<\/strong><\/h3>\n<p>Use Canvas\u2019s email header and footer as a foundation for HTML email compatibility (and reasonable PDF output). The header includes conditional CSS for Outlook (MSO), resets that prevent Gmail\/Apple Mail reformatting, and conservative defaults that keep layouts stable across clients and PDF rendering.<\/p>\n<h3><strong>7) The <code>ticket.php<\/code> loop: structure and key patterns<\/strong><\/h3>\n<p>Understand how the ticket themes render data so you can safely move\/skin elements.<\/p>\n<p>Canvas executes <code>ticket.php<\/code> <strong>once per ticket<\/strong>. The file typically contains two conceptual parts:<\/p>\n<ol>\n<li>A \u201cheader\u201d area that only renders <strong>once<\/strong> (for the first ticket in the batch email or when previewing).<\/li>\n<li>A repeated block that renders for <strong>every ticket<\/strong>.<\/li>\n<\/ol>\n<h4>\u201cFirst ticket only\u201d guard<\/h4>\n<p>You\u2019ll see logic like this at the top:<\/p>\n<pre><code class=\"language-php\">&lt;?php if ( ( ! empty( $ticket['ticketNumber'] ) &amp;&amp; 1 === $ticket['ticketNumber'] ) || ( __( 'Preview Event', 'woocommerce-events' ) === $ticket['name'] ) ) : ?&gt;\r\n    &lt;!-- Header area that should output once --&gt;\r\n&lt;?php endif; ?&gt;\r\n<\/code><\/pre>\n<p>When resending to the <strong>purchaser<\/strong> and multiple tickets are included in one email, this ensures the header area prints only once.<\/p>\n<h4>HTML vs PDF example<\/h4>\n<p>Canvas commonly distinguishes output based on the ticket type. This is done to ensure compatibility with the DOMPDF library which is used to render PDF files:<\/p>\n<pre><code class=\"language-php\">&lt;?php if ( ! empty( $ticket['type'] ) &amp;&amp; 'PDF' === $ticket['type'] ) : ?&gt;\r\n  &lt;p&gt;&lt;strong&gt;PDF Version&lt;\/strong&gt;&lt;\/p&gt;\r\n&lt;?php else : ?&gt;\r\n  &lt;p&gt;&lt;strong&gt;HTML Version&lt;\/strong&gt;&lt;\/p&gt;\r\n&lt;?php endif; ?&gt;\r\n<\/code><\/pre>\n<p>Use this to apply small format-specific differences if your design needs it. Keep changes minimal; it\u2019s easy to introduce divergence between HTML and PDF.<\/p>\n<h4>Logos \/ header images<\/h4>\n<p>Canvas prints the logo and header image if provided in <strong>Product \u2192 Ticket Settings<\/strong>:<\/p>\n<pre><code class=\"language-php\">&lt;?php if ( ! empty( $ticket['WooCommerceEventsTicketLogo'] ) ) : ?&gt;\r\n  &lt;p&gt;&lt;img src=\"&lt;?php echo esc_attr( $ticket['WooCommerceEventsTicketLogo'] ); ?&gt;\" alt=\"&lt;?php echo esc_attr( $ticket['name'] ); ?&gt;\" style=\"max-width:100%;\"\/&gt;&lt;\/p&gt;\r\n&lt;?php endif; ?&gt;\r\n\r\n&lt;?php if ( ! empty( $ticket['WooCommerceEventsTicketHeaderImage'] ) ) : ?&gt;\r\n  &lt;p&gt;&lt;img src=\"&lt;?php echo esc_attr( $ticket['WooCommerceEventsTicketHeaderImage'] ); ?&gt;\" alt=\"&lt;?php echo esc_attr( $ticket['name'] ); ?&gt;\" style=\"max-width:800px\"\/&gt;&lt;\/p&gt;\r\n&lt;?php endif; ?&gt;\r\n<\/code><\/pre>\n<h4>Page breaks (for print\/PDF)<\/h4>\n<p>Canvas uses modulo logic on the ticket number to insert page breaks:<\/p>\n<pre><code class=\"language-php\">&lt;?php if ( 0 !== $ticket['ticketNumber'] % 2 ) : ?&gt;\r\n  &lt;div style=\"page-break-before: always;\"&gt;&lt;\/div&gt;\r\n&lt;?php endif; ?&gt;\r\n<\/code><\/pre>\n<p>This example inserts a page break <strong>after every odd-numbered ticket<\/strong>. <span style=\"font-size: 16px;\">Adjust the modulo logic for your layout (e.g., break every 1, 2, or 3 tickets).<\/span><\/p>\n<h4>Common dynamic fields you\u2019ll see<\/h4>\n<ul>\n<li>Event name: <code>&lt;?php echo esc_attr( $ticket['name'] ); ?&gt;<\/code><\/li>\n<li>Dates\/times (varies by event type): <code>WooCommerceEventsDate<\/code>, <code>WooCommerceEventsEndDate<\/code>, <code>WooCommerceEventsHour<\/code>, <code>WooCommerceEventsMinutes<\/code>, <code>WooCommerceEventsPeriod<\/code>, <code>WooCommerceEventsTimeZone<\/code>, etc.<\/li>\n<li>Add to Calendar: <code>fooevents_ics<\/code> AJAX endpoint with <code>event<\/code> and <code>ticket<\/code> params.<\/li>\n<li>Add to Wallet: <code>fooevents_wallet_pass<\/code> AJAX endpoint with <code>ticket<\/code> ID.<\/li>\n<li>Barcode\/QR: <code>&lt;?php echo esc_attr( $barcodeURL ); ?&gt;<\/code><\/li>\n<li>Variations: iterate <code>WooCommerceEventsVariationsFromID<\/code><\/li>\n<li>Bookings: <code>WooCommerceEventsBookingSlot<\/code>, <code>WooCommerceEventsBookingDate<\/code><\/li>\n<li>Seating: <code>fooevents_seating_options_array<\/code><\/li>\n<li>Attendee fields: <code>WooCommerceEventsAttendeeName<\/code>, <code>WooCommerceEventsAttendeeLastName<\/code>, <code>WooCommerceEventsAttendeeTelephone<\/code>, <code>WooCommerceEventsAttendeeCompany<\/code>, etc.<\/li>\n<li>Custom attendee fields: <code>fooevents_custom_attendee_fields_options_array<\/code><\/li>\n<li>Zoom: <code>WooCommerceEventsZoomText<\/code> (if enabled)<\/li>\n<\/ul>\n<p><strong>Security:<\/strong> Canvas uses escaping (<code>esc_attr<\/code>, <code>wp_kses_post<\/code>, <code>esc_attr_e<\/code>) consistently. Preserve these when moving fields around.<\/p>\n<h4>Difference Between Single and Multiple PDF Ticket Theme Templates<\/h4>\n<p>\u200bIf you are using the &#8220;Single&#8221; template and a customer purchases multiple tickets, then each ticket will appear on its own page in the same PDF file. Each ticket will have its own header image, logo and event details. If you are using the &#8220;Multiple&#8221; template then the event logo and details will appear at the top of the page followed by 3 tickets and then again the event details followed by 3 tickets etc. The idea is that the event details and 3 tickets fit on one page, but if you are displaying a lot of information then these tickets might run over onto the next page. To change this you can either display less information or override the template to remove some of the padding or reduce the font size.<\/p>\n<h3><strong>8) Referencing theme images<\/strong><\/h3>\n<p>Load images from your theme\u2019s <code>images\/<\/code> folder with a reliable path.<\/p>\n<p>Depending on the base, Canvas provides variables you can concatenate. You\u2019ll commonly see one of these patterns:<\/p>\n<pre><code class=\"language-php\">&lt;img src=\"&lt;?php echo $theme_packs_url . $theme_name; ?&gt;\/images\/myimage.png\" alt=\"...\" \/&gt;\r\n<\/code><\/pre>\n<p><em>or<\/em><\/p>\n<pre><code class=\"language-php\">&lt;img src=\"&lt;?php echo $themePacksURL . 'theme\/images\/'; ?&gt;myimage.png\" alt=\"...\" \/&gt;\r\n<\/code><\/pre>\n<p>Inspect <code>header.php<\/code> in Canvas to confirm the variables in your copy. Always resolve to an <strong>absolute URL<\/strong> for email.<\/p>\n<h3><strong>9) HTML\/CSS guidelines for email and PDF<\/strong><\/h3>\n<p>Keep markup conservative so it renders consistently across clients and in PDFs.<\/p>\n<ul>\n<li>Use table-based layout or minimal <code>&lt;div&gt;<\/code>s; no complex flex\/grid.<\/li>\n<li>Inline critical styles (especially fonts, colors, spacing).<\/li>\n<li>Avoid web fonts in PDFs or provide robust fallbacks.<\/li>\n<li>Minimize nested elements and floats.<\/li>\n<li>Use <code>page-break-before\/after<\/code> for PDF pagination, but test with your final content.<\/li>\n<li>Keep images responsive with <code>max-width:100%; height:auto;<\/code> and <strong>absolute<\/strong> URLs.<\/li>\n<li>Test HTML and PDF outputs separately after changes.<\/li>\n<\/ul>\n<h3><strong>10) Assign, preview, and iterate<\/strong><\/h3>\n<p>Validate the theme with realistic data.<\/p>\n<ul>\n<li>In <code>Product data \u2192 Ticket Settings<\/code>, confirm <strong>HTML Ticket Theme<\/strong> (and <strong>PDF Ticket Theme<\/strong> if applicable) is set to your custom theme.<\/li>\n<li>Create a test order or <strong>resend<\/strong> an existing ticket to your own inbox.<\/li>\n<li>If tickets are emailed to the <strong>purchaser<\/strong> and an order contains multiple tickets, the email will include <strong>multiple ticket blocks<\/strong>\u2014verify spacing and headings still look right.<\/li>\n<\/ul>\n<p>Repeat: edit, upload changed files and\u00a0resend.<\/p>\n<h3><strong>11) Common tweaks &amp; patterns<\/strong><\/h3>\n<p><strong>Conditional rendering by output type<\/strong><\/p>\n<pre><code class=\"language-php\">&lt;?php if ( ! empty( $ticket['type'] ) &amp;&amp; 'PDF' === $ticket['type'] ) : ?&gt;\r\n  &lt;!-- PDF-specific tweak --&gt;\r\n&lt;?php else : ?&gt;\r\n  &lt;!-- HTML-specific tweak --&gt;\r\n&lt;?php endif; ?&gt;\r\n<\/code><\/pre>\n<p><strong>Only show a section once for the first ticket<\/strong><\/p>\n<pre><code class=\"language-php\">&lt;?php if ( ! empty( $ticket['ticketNumber'] ) &amp;&amp; 1 === (int) $ticket['ticketNumber'] ) : ?&gt;\r\n  &lt;!-- One-time header content --&gt;\r\n&lt;?php endif; ?&gt;\r\n<\/code><\/pre>\n<p><strong>Modulo-based page breaks<\/strong><\/p>\n<pre><code class=\"language-php\">&lt;?php if ( 0 === $ticket['ticketNumber'] % 3 &amp;&amp; 0 !== $ticket['ticketNumber'] ) : ?&gt;\r\n  &lt;div style=\"page-break-before: always;\"&gt;&lt;\/div&gt;\r\n&lt;?php endif; ?&gt;\r\n<\/code><\/pre>\n<p><strong>Safe output<\/strong><\/p>\n<pre><code class=\"language-php\">&lt;h2&gt;&lt;?php echo esc_attr( $ticket['name'] ); ?&gt;&lt;\/h2&gt;\r\n&lt;p&gt;&lt;?php echo wp_kses_post( $ticket['WooCommerceEventsTicketText'] ); ?&gt;&lt;\/p&gt;\r\n<\/code><\/pre>\n<h3><strong>12) Testing checklist<\/strong><\/h3>\n<ul>\n<li>Preview + resend tests for <strong>HTML<\/strong> and <strong>PDF<\/strong> (if supported).<\/li>\n<li>Multi-ticket email to <strong>purchaser<\/strong> renders multiple ticket blocks neatly.<\/li>\n<li>Images resolve (no broken links; absolute URLs).<\/li>\n<li>Major email clients: Gmail (web\/mobile), Apple Mail, Outlook desktop\/web.<\/li>\n<li>If PDFs are enabled: print to PDF or generate official PDF tickets and confirm pagination, margins, and fonts.<\/li>\n<\/ul>\n<h3><strong>13) Troubleshooting<\/strong><\/h3>\n<ul>\n<li><strong>Theme not showing in dropdown:<\/strong> Confirm folder path and <code>config.json<\/code> <code>\"name\"<\/code> is unique; clear caches and reload the product edit screen.<\/li>\n<li><strong>Images not loading in email:<\/strong> Ensure absolute URLs; avoid protocol-relative URLs; confirm asset permissions.<\/li>\n<li><strong>Weird spacing in Outlook:<\/strong> Reduce nested elements, rely on tables, and simplify CSS.<\/li>\n<li><strong>PDF layout issues:<\/strong> Use simpler structures, add explicit page breaks, avoid floats and complex positioning.<\/li>\n<\/ul>\n<h3><strong>Other Themes<\/strong><\/h3>\n<p>The same process can be applied to any <a href=\"https:\/\/www.fooevents.com\/products\/ticket-themes\/\" target=\"_blank\" rel=\"noopener\">FooEvents Ticket theme<\/a>. They follow the same underlying structure and approach. Find a theme that is similar to your design, and use it as a starting point.<\/p>\n<h3><strong>Summary<\/strong><\/h3>\n<p>Start with <strong>Canvas<\/strong>, give it a unique name in <code>config.json<\/code>, place it in <code>\/wp-content\/uploads\/fooevents\/themes\/<\/code>, and assign it to a test product. Customize the markup in <code>header.php<\/code>, <code>ticket.php<\/code>, and <code>footer.php<\/code>, keeping the HTML conservative and styles inline. Use the first-ticket guard for single-run elements, conditionally tweak HTML vs PDF output if needed, and rely on page breaks for PDF pagination. Test previews, resend real tickets, and validate multi-ticket emails before going live.<\/p>\n","protected":false},"featured_media":0,"parent":880,"menu_order":7,"comment_status":"closed","ping_status":"closed","template":"","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"default","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-145088","docs","type-docs","status-publish","hentry"],"comment_count":0,"_links":{"self":[{"href":"https:\/\/help.fooevents.com\/pt\/wp-json\/wp\/v2\/docs\/145088","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.fooevents.com\/pt\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/help.fooevents.com\/pt\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/help.fooevents.com\/pt\/wp-json\/wp\/v2\/comments?post=145088"}],"version-history":[{"count":1,"href":"https:\/\/help.fooevents.com\/pt\/wp-json\/wp\/v2\/docs\/145088\/revisions"}],"predecessor-version":[{"id":146301,"href":"https:\/\/help.fooevents.com\/pt\/wp-json\/wp\/v2\/docs\/145088\/revisions\/146301"}],"up":[{"embeddable":true,"href":"https:\/\/help.fooevents.com\/pt\/wp-json\/wp\/v2\/docs\/880"}],"next":[{"title":"Atualiza\u00e7\u00e3o de temas de bilhetes","link":"https:\/\/help.fooevents.com\/pt\/docs\/topics\/tickets\/ticket-themes\/updating-ticket-themes\/","href":"https:\/\/help.fooevents.com\/pt\/wp-json\/wp\/v2\/docs\/131862"}],"prev":[{"title":"Bilhetes PDF FooEvents - Atualiza\u00e7\u00e3o do Dompdf 9 de mar\u00e7o de 2026","link":"https:\/\/help.fooevents.com\/pt\/docs\/topics\/tickets\/ticket-themes\/fooevents-pdf-tickets-dompdf-update-9-march-2026\/","href":"https:\/\/help.fooevents.com\/pt\/wp-json\/wp\/v2\/docs\/146327"}],"wp:attachment":[{"href":"https:\/\/help.fooevents.com\/pt\/wp-json\/wp\/v2\/media?parent=145088"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/help.fooevents.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=145088"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}