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 Incorrect description for member pricing | Event Espresso - Staging Server
Hi
We are using the WP user integration and all EE components are latest versions. We have an event where there is an event price called ‘Non-member admission’ – cost £55 and a second called ‘Member admission’ – cost £49.50.
When members are logged in they are getting the correct price but the description says ‘Non-member admission’ – which is very confusing for them, causing some people to abandon registration and start over again. (Leaving us with pending registrations to delete.)
We have changed the ‘Non-member admission’ to say ‘General admission’ for now. I searched your support forum and found a post on this from January that said this is expected behaviour but you were going to raise a ticket for a change.
Can I add my vote to a change on this as our members would find it very helpful if their attendee price information could explictly say that it was a members price. Thanks.
How is the ticket set up? For instance is it one ticket type with a Non member price and a member price e.g. http://d.pr/i/uqYO or is it set up differently?
Can you link to the post in January you are referring to please?
Thanks for the link and clarification that has helped. The ticket for that is still outstanding. I have changed the ticket settings so hopefully this will be looked at sooner. I still can’t say if/when it will be resolved however.
Viewing 3 reply threads
The support post ‘Incorrect description for member pricing’ 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.