andrasguseo

<?php
/**
 * Block: RSVP
 * Form Email
 *
 * This is a template override that will lock the 'email' field with the email of the user who is logged in,
 * if the "Tickets > Settings > General > Require users to log in before they RSVP" is enabled.
 * If the setting is disabled, the field content can be changed.
 * 
 * Override this template in your own theme by creating a file at:

andrasguseo

<?php
/**
 * Import tweak to allow importing Tickets Commerce Tickets from a CSV file
 *
 * Usage: Add the snippet with Code Snippets or to your functions.php file.
 *        Install and activate WooCommerce.
 *        Run the ticket import according to https://theeventscalendar.com/knowledgebase/importing-data-from-a-csv-file/
 *        Confirm the tickets are created.
 *        Deactivate and delete WooCommerce if not needed
 *

andrasguseo

<?php
/**
 * Next and previous links on the single event page point to the next event in the event's category.
 * If an event has no categories, it will show the next event, regardless of any categories.
 * If an event has multiple categories, it will show the next event which has any of the categories.
 *   After that, it will show events having categories of this event.
 *
 * Usage: Add the snippet with Code Snippets or to your functions.php file.
 *
 * @author: Andras Guseo

andrasguseo

<?php
/**
 * Deletes orphaned 'old' recurring events, after the events have been migrated.
 * You know you have orphaned events if on the Event admin list the number of All events 
 * and the number of items don't match.
 * @see https://dl.dropbox.com/scl/fi/tmljvc5fzzpr48arklsbt/shot_250326_225112.png?rlkey=dkg0qjh72zhafasnitbrfokv5&dl=0
 *
 * Creating a database dump before and running a test on a staging site first is recommended!
 * Creating a database backup before running the snippet on a production site is recommended!
 *

andrasguseo

<?php
/**
 * Deletes Tickets Commerce Orders and related Tickets/Attendees, 
 * which are missing a related event or post.
 * Creating a database dump before and running a test on a staging site first is recommended.
 *
 * Usage: Add the snippet with Code Snippets as a "run once" snippet. 
 *        Run the snippet when needed.
 *
 * @author: Andras Guseo

andrasguseo

<?php
/**
 * Format the event cost by using a space as the thousand separator.
 *
 * Usage: Add the snippet with Code Snippets or to your functions.php file.
 *        Enter the cost without a thousand separator, when creating the event.
 *
 * @since March 5, 2025 Initial version.
 *
 * @param double $cost the event cost

andrasguseo

<?php
/**
 * Set WooCommerce orders for Ticket products to 'completed' status automatically based on certain criteria.
 * 
 * You can further tweak the behavior by adjusting the snippet:
 * - based on order status: line 29
 * - based on payment gateway: line 36
 */
add_action( 'woocommerce_thankyou', function ( $order_id ) {
	// Bail if there is no order.

andrasguseo

<?php
/**
 * Change the time zone of all events and adjust the UTC times accordingly.
 *
 * Usage: Add the snippet with Code Snippets.
 *        Set your target time zone on line 20.
 *        Optional: Set your target time zone abbreviation on line 33.
 *        Save it as a 'Run once' snippet.
 *        Go to the Snippet list and click on 'Run' next to the snippet.
 *

andrasguseo

<?php
/**
 * When importing from Other URL with Event Aggregator, only import/update the event
 * category, if it hasn't been changed on the destination site yet.
 *
 * Usage: Add the snippet with a plugin like Code Snippets, or to the functions.php file.
 *
 * @author: Andras Guseo
 *
 * Plugins required: The Events Calendar, Event Aggregator

andrasguseo

<?php
/**
 * Block REST API requests coming from Event Aggregator. Basically blocks imports.
 * It can block other sites trying to siphon events with EA through the "Other URL" source.
 *
 * Usage: Add the snippet with a plugin like Code Snippets or to your functions.php file.
 *
 * @author: Andras Guseo
 *
 * Plugins required: The Events Calendar