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
no results... | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium no results…

no results…

Posted: March 21, 2013 at 7:03 am

Viewing 3 reply threads


Duncan Bates

March 21, 2013 at 7:03 am

Dear sirs I use EE for my wife’s yoga business
http://kurs.ragdollyoga.com/?page_id=49

I’m using the Multi event system linking registration page back to a master event record. Do this so I can create an event list and an events callendar . This all works great, my problem now is that when students sign up on the master record registration, they basically pay a single fee that covers all events in the series. Say Class Hatha runs once a week for 8 weeks. want the students to register and pay on the first event of this series, I therefor set the price for this event to 8 times price of one hour. In the events list as on the link above you’ll see that the price comes out at 800kr which covers 8 weeks of clases. Students now get a bit confused if 800 is for a single class or all 8 since I don’t know how to add a bit more detailed infor in the event list. In the events details I specify in tyext that this covers 8 weeks. Any way I can enable a detailing field for the events list where I can indicate that the price covers 8 weeks worth of clases?

Duncan


Garth

  • Support Staff

March 21, 2013 at 11:33 pm

Hi Duncan,

I’d recommend adding some specificity to the ticket e.g. “Entire Class (includes 8 sessions)”.


Duncan Bates

March 22, 2013 at 3:57 am

Thanks Garth. Added information about this in the event description so it show’s up on the registration page, and Calendar.Hover. This is good.
The event list only shows a subset of the event info, where I’d like to add this info. Tried changing the standard Pricing Name, but pricing still shows up as Pris.


Dean

  • Support Staff

March 22, 2013 at 4:56 am

Hello Duncan,

If you mean the general term for Price, then you would need to edit that via the language files or via a script like this. The ticket option names do not affect the general site wide term for Price.

Viewing 3 reply threads

The support post ‘no results…’ 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.

Event Espresso - Staging Server