Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the blackhole-bad-bots domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the debug-bar domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the easy-pricing-tables domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the geoip-detect domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the members domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the affiliate-wp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-bbpress domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6121
Tristan Mills's Profile - Event Espresso – Staging Server
Event Espresso
MENUMENU
  • Pricing 
  • Features
    • Sell & Scan Tickets
    • Event Creation & Management
    • Event Registration Forms
    • Collect Payments
    • Attendee Insights
    • Mobile Event App
    • Security & Compliance
  • Use Cases
    • Conferences
    • Courses
    • Workshops
    • Festivals
    • Non-Profits
    • See All Use Cases
  • Add-ons
    • Promotions and Discount Codes
    • Events Calendar
    • Stripe Payment Gateway
    • Attendee Mover
    • WordPress User Integration
    • Events Table View Template
    • See All Add-ons
  • Support
    • Contact Us
    • Quick Start Guide
    • Support Forums
    • Documentation
  • Resources
    • Blog
    • Guides & Strategies
    • Competitor Comparison
    • Videos
Sign In

Tristan Mills

    Need a support license?

    Purchase a support license right now so you can:

    • - Receive software updates and downloads
    • - Have one-click updates from your WordPress dashboard
    • - Get help from our support team

    Buy a support license or contact us so we can help you choose one today for your events.

    My Topics

    • You can create a new topic by using the "Start a Topic" button in the support forums.

    • json – output from /events/ doesnt match docs description

      Updated byDean 11 years, 2 months ago ago

    • update on Added questions completed fields not showing up in admin ?

      Updated byDean 11 years, 3 months ago ago

    • Why doesnt JSON provide output for attendees additional questions?

      Updated byDean 11 years, 3 months ago ago

    • example php for JSON needed

      [Resolved] Updated byTristan Mills 11 years, 3 months ago ago

    • Cannot update 'Total Amount Paid to Date' in admin

      Updated byAnonymous 11 years, 3 months ago ago

    • automatically delete unpaid registrations [abandonned carts] ?

      Updated byDean 11 years, 4 months ago ago

    • Added questions completed fields not showing up in admin

      Updated byJosh 11 years, 4 months ago ago

    • How can I find -number of attendees- in the surcharge function in pricing.php

      Updated bySidney Harrell 11 years, 5 months ago ago

    • How do I send number of attendees / ticket quantity, to custom payment gateway

      Updated byAnonymous 11 years, 5 months ago ago

    • SagePay Gateway

      [Resolved] Updated byTristan Mills 11 years, 5 months ago ago

    Follow Us

    Subscribe to our newsletter and move your events forward

    Get event ideas, blog posts, and recommendations on how to use Event Espresso to host successful events!



    Subscribe to our newsletter
    • Features
    • Event Creation & More
    • Sell & Scan Tickets
    • Collect Payments
    • Attendee Insights
    • App Integrations
    • Security & Compliance
    • Add-on Feature Plugins
    • Product
    • Pricing
    • Use Cases
    • Requirements
    • Reviews & Testimonials
    • Demo Event Espresso
    • About
    • About Event Espresso
    • Common Questions
    • Privacy Notice
    • Privacy Policy
    • Terms & Conditions
    • Support
    • My Account
    • Contact Us
    • Support Resources
    • Support Forums
    • Developer Center
    • Github Profile
    • Tell A Friend
    • Resources
    • Blog
    • Guides & Strategies
    • Public Roadmap
    • Hire a Consultant
    • Change Log
    • Competitor Comparison
    Event Espresso - Staging Server