Customizing Registrant Info on the backend

Hello,
I love that I can view the registrant information from the backend. Is it possible to customize the information that shows up there? I know when I use the Export Registrants bit, I get everything, I'm just wondering about the display on the EB Dashboard/Registrants Tab.
~Kathy

Um, I may have just found it. :blush:

Okay, so I did find how to *add* information to the registrants list displayed on the front end. But that brings up two follow-up questions for me:
1) Is it possible to *subtract* information to display on the front end? I don't actually want to display the default first and last name, the date people registered, or the number of registrants.
2) Is it possible to add information to the list *on the backend*? If this isn't an existing feature, where would I go to fiddle with it?

Thanks!
~Kathy

Hi Kathy

1) Is it possible to *subtract* information to display on the front end? I don't actually want to display the default first and last name, the date people registered, or the number of registrants.

=> Currently don't have an option to allow you to remove these fields from the list. So you will have to edit code to remove the fields you don't want. The file you need to modify is components/com_eventbooking/view/registrantlist/tmpl/default.php, it should not be hard to do the modification

2) Is it possible to add information to the list *on the backend*? If this isn't an existing feature, where would I go to fiddle with it?

=> It is still not possible to do that at the moment. You will have to modify the code if you want to add more information. The file is administrator/components/com_eventbooking/view/registrants/tmpl/default.php. However, it is not easy to do that kind of modification unless you know PHP programming very well

Tuan

Thanks Tuan. I was able to change registrantlist to display the information I wanted, but I'm having trouble modifying registrants/tmpl/default. I even just added "kathy" to the class of one of the tags, just to see if it would come out in the html, but it didn't appear. Does that view feed the little registrants list visible from the dashboard, the big one visible under the registrants tab, or both?

Alternately, is there a way to access the fields I defined for registrantlist (controlled through the configuratioin) in the csv export function?

Hi Kathy

Unfortunately, that option is not yet available in the extension. Something we can try to add support for in future release (maybe near future , in about 4 weeks)

Regards,

Tuan

Hi Tuan

I'm using jDBexport ( extensions.joomla.org/extension/jdbexport ) to compose an Excelfile that my teachers can download from the front end. This is highly configurable with SQL statements to get all the data out as desired. My users can't handle csv files. Works great with logos, header, footer, formatting etc. what I would like to include are more custom fields. Since Event booking allows to add as many custom fields of any type and column heading, this makes it not that easy for the export.

I imagine that there has to be some kind of a do while statement to build the different columns for the custom fields in the export. At the moment I have no clue what to search for on the Internet. Could you tell me in what file you are composing the MySQL statement for the export function (exporting the registrants) of Event Booking?

At the moment my export only uses one custom field (birthdate) and I need to have more (gender etc.)

It would be great if you could give me a hint, so I know what to look for.

Thank you

Roger

Hi Roger

1. The data for custom fields are stored in #__eb_field_values table

2. You can look at the file administrator/components/com_eventbooking/controller/controller.php , function csv_export to see how I get data for custom fields and use it for the support

Hope it gives you some useful information

Regards,

Tuan

Tuan, any movement on allowing custom fields to be visible through the Registrants Management table? My event managers are getting confused trying to locate the correct records for any updates because our most important information is in the custom fields.