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
Event Depending Payment Types | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Event Depending Payment Types

Event Depending Payment Types

Posted: September 25, 2013 at 3:07 am

Viewing 1 reply thread


Marcel Snoeck

September 25, 2013 at 3:07 am

I have the following problem.
We want to create several events, but they have different payments.
1. Event with standard payment module for example “Mollie IDEAL”
2. Event with payment at the door and not payment via example “Mollie IDEAL”

We don’t want that people who book for event 1 that they can select pay at the door.
And for event 2 they should only see pay at the door.

How and can I arrange that.


Dean

  • Support Staff

    •

September 25, 2013 at 3:41 am

Hi Marcel,

Currently that isn’t possible barring customising the plugin, the gateways are sitewide not on a per event basis.

One idea I had recently was to set an event category (e.g. “door” and “online”) and then modify the templates to display the event category in a hidden form input. Then use jQuery to selectively hide or show a gateway dependant upon that event category id.

I haven’t tested that idea but in theory it should work. Only caveat is that users with javascript turned off will see both gateways.
Viewing 1 reply thread

The support post ‘Event Depending Payment Types’ 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 Dean 11 years, 5 months ago ago

Topic Tags

Tagged: , , , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server