|
Nicholas
|
February 11, 2014 at 3:06 am
I’m using the member pricing plugin as some tickets are for sale only after login – this is all working fine.
The standard tickets are balanced with the member tickets as the system requires (there are three of each type) but when purchased they appear as a guest ticket rather than the member ticket type purchased. This is showing in the attendee list and the ‘My Events Management’ page and is making it hard to determine the member/non-member attendance.
EE is Version 3.1.36.4.P, members add-on is Version 1.9.8.p
Thanks
|
|
Anonymous
|
February 11, 2014 at 3:42 am
Hi Nicholas,
At first I suspected the function you are using from this thread http://staging.eventespresso.com/topic/manually-added-attendees-are-shown-as-admin-under-option-rather-than-by-ticket/ may have been causing this, but I’ve just tested the above and the attendee was given the Member Admission.
Quick question do you edit/update the attendees after they have purchased?
|
|
Nicholas
|
February 11, 2014 at 3:49 am
I haven’t added the function specified in that post. In this case the attendee wasn’t edited, it was a straightforward purchase.
Why would it create a guest ticket for the purchase rather than the one specified when purchasing a member ticket?
|
|
Anonymous
|
February 11, 2014 at 4:05 am
It shouldn’t and I can not reproduce locally currently, which is why I suspected that function (as at the time I didn’t have it installed) but that’s not the case
Do you have any custom functions/customization’s running currently?
Was the Price correct?
Just trying to narrow things down a little as the test registration I’ve just ran shows correctly in both the attendee list http://d.pr/i/ad0g & My events http://d.pr/i/QqlF
|
|
Nicholas
|
February 11, 2014 at 4:39 am
So I tested some more to see what the pattern was and it’s always the same- if I purchase a public ticket the description is correct (e.g. non-member) in the attendee list but if I log in to purchase a ticket at the member price then these always appear in the attendee list as the equivalent public ticket description.
There are no customisations (apart from some CSS) so I’m really stuck on why this is happening. It’s a live environment and they do need the ticket types to show up correctly.
|
|
Nicholas
|
February 11, 2014 at 5:02 am
sorry, yes price is correct. In both cases the free and paid member tickets were correct.
I’m seeing that it is showing ‘Name 2’ for a guest ticket and ‘Name 2’ for a member ticket but then different numbers for the other standard/member tickets. Do these need to be unique?
|
|
Anonymous
|
February 11, 2014 at 6:19 am
I’m not sure how you have these setup, but if you have both the public and member ticket set with the same name, how are you currently identifying the two in the admin?
|
|
Nicholas
|
February 11, 2014 at 6:33 am
It’s been set up through the ticket interface. EE provides the ‘name X’ title automatically but the first ticket shown always has Name 2 for both standard and member tickets – however I’m not sure that is the issue. see the screenshot: http://testserver.nicholaspealldesign.com/cwn-image/
|
|
Josh
|
February 11, 2014 at 12:44 pm
Hi Nicholas,
I can confirm what you’re seeing, and it’s related to the Multi Event Registration add-on. If this were going through the single event registration it would record the correct price label (but that’s more limited because you can’t select more than one ticket type). We’ll try to see if we can find a fix for this.
|
|
Nicholas
|
February 11, 2014 at 2:45 pm
Ok thanks for looking at it, it’s one of the last few things to wrap up on this project (until their next request…)
|
|
Dean
|
February 12, 2014 at 4:40 am
Edit: wrong thread, sorry!
-
This reply was modified 10 years, 11 months ago by
 Dean. Reason: made a boo boo
|
|
Nicholas
|
February 12, 2014 at 4:44 am
I was just going to say… if it had only been a single bracket. Look forward to an update sometime on this, I have an EE review meeting on Fri
|
|
Josh
|
February 12, 2014 at 9:51 am
Hi Nicholas,
I found a fix and after a quick round of testing I find it works well. The affected code is within the espresso_ticket_information function of /includes/main.php.
Here’s the entire function with the code changes:
Since I’m unsure of the state of the release cycle for Event Espresso 3 (as the focus is now on Event Espresso 4), I’m not sure if this change will be in the very next release. It may be the case, however, you can copy the function into /wp-content/uploads/espresso/custom_functions.php and the function you copy there will load from there.
|
|
Nicholas
|
February 12, 2014 at 10:21 am
Hi Josh
I haven’t needed to add any custom functions to EE so I just want to be sure what to adjust here to ensure the code works ok.
The affected code is within the espresso_ticket_information function of /includes/main.php.
Could you please detail what the correct process is, I don’t want to eff this up!
Thanks
|
|
Josh
|
February 12, 2014 at 10:44 am
You copy over the entire function that’s there now and replace with what I posted above -or- upload this posted copy of custom_functions.php to /wp-content/uploads/espresso/ using FTP.
https://gist.github.com/joshfeck/8960666
|
|
Nicholas
|
February 16, 2014 at 11:17 am
Hi Josh
Thanks a lot, I added the file to the path you specified and now the purchased ticket type is showing up correctly.
|
|
Josh
|
February 17, 2014 at 8:15 am
Hi Nicholas,
I’m glad that worked out.
|
