Support

November 23, 2016 at 12:46 pm

The workaround that doesn’t involve any custom coding is you add a new field to the registration form for the actual attendee name. So you’ll still capture the registrant/contact person’s info (the person who completes the registration form while logged into the website), then additionally the form can capture the information about the person who will be attending.

November 25, 2016 at 10:46 am

I’ll try to keep the replies in this thread organized by following up with two separate replies to your questions.

Is there a way to make those fields read-only?

Those fields can be made read-only by injecting some JavaScript onto the page that targets those specific fields to make them read only. Here’s a link to a gist that has some example code:

https://gist.github.com/joshfeck/abebd6fb3cdc796bf1f913de6c6d1816

You can add the above to a functions plugin or into your WordPress theme’s functions.php file.

November 28, 2016 at 2:52 pm

The exact code that you’ll use depends on which field(s) you’re using to capture the attendee information. The code example that’s linked up in the documentation shows how to add the value of a field from the registration form. So you can reuse the code from that example, and change the ID that’s used the example to get the field for the attendee name. Then you change the part of the code where it outputs by removing the $gravatar . ' ' . $contact->full_name() and replace with the attendee name data.

December 2, 2016 at 7:37 am

Yes for sure.

December 2, 2016 at 7:18 pm

I’m not sure exactly what mods you need to make, because the mods you will need to make will depend on some factors like if they’re registering for multiple events, or more than one time per event. I can point out a few ways to break things down a bit, but in the end it may be better to not use the short code for this, and instead build your own short code, or even inject the template via a hook.

So one way to achieve what you’re out to to is run a secondary loop based on the registrations within that transaction for that contact. That loop can be run in the loop-espresso_event_attendees.php template. Right after the loop starts, you first grab all the related registrations for that event:

$registrations = $contact->get_many_related('Registration',
            array(array('EVT_ID' => $event->id())));

then you can start another loop:

foreach($registrations as $registration ) :
// call to EEH_Template::get_template_part() here
endforeach; //end inner loop
endforeach: //end outer loop

There are a few downsides to this method, one being that if they’ve registered more than one time, you’ll end up with some repeats in the list (because it will loop through all of their registrations in that event). The other downside is you’ll need to modify the content-espresso_event_attendees.php template so it can loop through the answers the custom questions.

Which, actually, if you look at the example code for the content- template, there’s a limit set to 1. You may be able to get away with raising that limit which will then output more than just attendee name, without modifying the loop file.

The thing I don’t like about any of the above is it’s going to take a significant amount of work to make the short code do something it wasn’t designed to do. Instead of doing the above, I can suggest doing a simple query on the database and output the list using an action hook. Here’s a simplified example that should get you on the right path:

https://gist.github.com/joshfeck/322566085d07254c94b55ed6fcb40c23