[SOLVED] Modifying [REGISTRATION_DETAIL]

Hi Tuan,

in use is EB 2.14.5 with multiple ticket types and a custom fee field.

I need to change the content of the tag [REGISTRATION_DETAIL], the main reason being the issue that the table "ticket information" does not reflect the price and sub total change resulting from the custom fee field.
(Shall we call that a bug, or is there a good reason for the "wrong" price and sub total being displayed even though a custom fee field has altered the amounts? Obviously, it's hugely confusing for users.)

Tuan, could you please provide an easy fix for the table to display the correct "after custom fee field" amounts?

The tag [REGISTRATION_DETAIL] and its content is used all over the place.
For further changes required, please let me know if my following guesses are complete and correct:

1. Much if not all of the data seems to be generated in the function "getEmailContent" in helper.php, despite the function name indicating "Email" only. Correct, or do I need to look elsewhere as well?
2. The HTML seems to be coming from the view /components/com_eventbooking/view/emailtemplates/tmpl/individual_detail.php, despite the folder name indicating "email" only, again. Correct, or are other views involved as well?t
3. If I wanted to avoid using the tag alltogether but build my own content/layouts for
   - Registration Completed page (/components/com_eventbooking/view/complete/tmpl/default.php)
   - Emails to registrant and admin
   - Invoice, ticket and other docs
   not all individual field tags seem to be available everywhere, plus the issue with the wrong ticket prices/sub totals after custom fee field use would remain. Or would you generally say it'd save me time, efforts and nerves when abandoning the [REGISTRATION_DETAIL] and building it all with individual field tags?

Thanks in advance for your reply!

Hello Thomas

This is not a bug. The ticket types data doesn't have anything related to custom fee field which you setup. It only depends on the price of the ticket type which you setup and the quantity which registrants choose for their purchase

Any custom fee fields if you create will only affect total registration fee which users have to pay (which is displayed in a separate section - almost at the bottom of [REGISTRATION_DETAIL] tag)

Back to your other questions:

1. That's correct. All the data which is used to generate [REGISTRATION_DETAIL] is from getEmailContent which you figured out

2. In that folder, there are two files:
- individual_detail.php : This layout will affect the registration complete page if you use [REGISTRATION_DETAIL] of thanks you message
- email_individual_detail.php : This layout will affect the email sent to registrant if you use [REGISTRATION_DETAIL] tag

So basically, two files, one is used to display on registration complete page (thank you page) and one is used to display on user email

3. I don't really understand / get the last question. I am not sure if you can build the layout yourself using individual tags. The reason is because we don't have any tag to support showing ticket types data at the moment. If you want to add support for a tags which is used to show tickets type data, you would need to build it yourself

You can look at method buildTags in helper.php file to see all the tags supported by the extension to allow building each of the layout you want using individual tags

Regards,

Tuan

Many thanks for your very prompt reply, Tuan!

I understand what you're saying, but you'll have to admit that it is utterly confusing for registrants when they're seeing amounts under ticket information that do not add up to the totals below.
So, I guess I'll have to dig in deeper and implement the math including custom fee field myself. Siiiiiigh...

1. + 2.: Very helpful, thanks.

3. Well, my question was basically if it'd be easier to either (A) modify the pre-fabricated [REGISTRATION_DETAIL] tag, or to ( not use it at all but use individual tags instead.
However, with tags missing for ticket types it seems I'll be off best with (A). I've seen this thread , but for the work I need to do it appears more efficient to act on the similar code in the getEmailContent function and the existing views.

I think there's a lot of room for improvement re. custom fee fields, multiple ticket types, and the correlation in between. Hoping for 3.x!

Anyway, thanks again for now.

That's actually depends on the purpose of how you are using it. Just for information, the custom fee fields feature is independent with Ticket Types, that feature is supported in Events Booking long time ago while ticket types was just introduced recently

Features are being added/improved from time to time. So if you have suggestions to make product better, please suggest it on features wishlist forum (as we discussed via support tickets)

Regards,

Tuan

Tuan Pham Ngoc wrote: Just for information, the custom fee fields feature is independent with Ticket Types

Yes, and as you said earlier, anything from custom fee fields is added only to the bottom line.
But...
a. the custom fee doesn't show as line item with description and $ amount anywhere, and
b. I feel, independently, custom (fee) fields for ticket types = them "playing together" would be a tremendous benefit for many, many use cases.

So, please spare me another post in the other forum, and please add both to the global wishlist - thanks much.
With a bunch of mods I've solved both points for me here & now - so, case closed.