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 6114

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 6114

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 6114

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 6114

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 6114
Runemester'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

Runemester

    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.

    • Export all attendees – date paid error

      Updated byJosh 10 years, 10 months ago ago

    • Quickpay picks up sub-total instead of total using multi registration

      [Resolved] Updated byRunemester 11 years, 5 months ago ago

    • Localization of invoice

      Updated byJosh 11 years, 7 months ago ago

    • payment overview – swapped total and sub total

      Updated byJosh 11 years, 7 months ago ago

    • Customize display of currency_symbol

      Updated byJosh 11 years, 7 months ago ago

    • QuickPay not recording transaction/reg/payment ID

      [Resolved] Updated byRunemester 12 years, 3 months ago ago

    • QuickPay not recording transaction/reg/payment ID

      [Resolved] Updated byJosh 12 years, 3 months ago ago

    • NULL-text printed during payment process

      [Resolved] Updated byRunemester 12 years, 5 months ago ago

    • empty ESPRESSO_PAYMENTS / Thanks page

      [Resolved] Updated byFranz Skaaning 12 years, 5 months ago ago

    • Dynamically linking category labels to category pages

      [Resolved] Updated byJosh 12 years, 6 months ago ago

    • Display events as 'free event' instead of 0.00 in event meta

      [Resolved] Updated byRunemester 12 years, 6 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