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
Different payment options for different events | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Different payment options for different events

Different payment options for different events

Posted: January 8, 2013 at 4:05 pm

Viewing 3 reply threads


Shannon Bentley

January 8, 2013 at 4:05 pm

Just wondering if it’s possible to offer certain payments for certain events? I have come events that we don’t mind if people pay offline (check)…but we definitely don’t want that option available for other events. Is it possible to restrict what payments are available for an event?


Jonathan Wilson

  • Support Staff

    •

January 8, 2013 at 5:36 pm

Hi Shannon,

We don’t have that functionality at this time. I have added it to the feature request list, and I will add your vote to it.


Shannon Bentley

January 9, 2013 at 9:36 am

Thanks. This is CRITICAL to my application so I’m now desperately trying to find a work-around. I’ve changed all my events that are paid offline to “free” and I’m in the process of tracking down all the code that writes “Free Event” to change it to “Pay at Venue” (using F4 in all the files). I have found all but one occurrence and I’ve spent the last 3.5 hours trying to find one last one. I’m hoping you can help since you know this software inside & out. It’s on the first registration page that a person is taken to after clicking on the calendar…it lists the date, start time, end time, price, available spaces, and then Registration Details where the person enters their name & e-mail. I can’t seem to get rid of the “Free Event” here. Any help would be greatly appreciated!!! I’M DESPERATE!!!


Chris Reynolds

  • Support Staff

    •

January 9, 2013 at 1:25 pm

Rather than editing the core files (which will get overwritten in an update), a better solution is to use Poedit to edit the language files and make a single change (rather than a bunch of separate changes across multiple files).

http://staging.eventespresso.com/wiki/how-to-change-wording-with-poedit/

At this time, it’s not possible to restrict a specific payment option for a specific price. The closest thing I could suggest would be specific payment options based on event category, but that would be for the entire event, not for different price levels within a single event. This is not likely to be added until after 3.2 is released and possibly later as it would require quite a bit of changing in how the payment and pricing system works.
Viewing 3 reply threads

The support post ‘Different payment options for different events’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by Chris Reynolds 12 years ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server