Would it be possible to display the unique Transaction-ID that is generated by the system on the front-end views? I would like both registrants and administrators to be able to see the Transaction-IDs. I am requiring registrants who make their offline payments to state the Transaction ID. It would be very helpful if administrators could refer to the Transaction-ID as well when checking payments against registrations.
At the same time, how can I suppress the display of the number of registrants from those views? For my application, this is irrelevant data. Perhaps I could display the Transaction-ID instead?
Here are the screens where I would like the Transaction ID to appear. As mentioned, the Number of registraions is an irrelevant field for me -as there will only be individual registrations, so one at a time.
For this, you will need to modify code in the file components/com_eventbooking/themes/default/registrants/default.php
Try to open that file, you can easily do the modification. To show Transaction ID for each record, you can use $row->transaction_id.
Once the modification is done, you can move the modified file to PATH_TO_TEMPLATE/html/com_eventbooking/registrants folder and the change won't be lost when you update to future releases of the extension
To be honest, I don't quite know what you mean by "template override". How do you create such a thing?
I have saved copies of the relevant default.php files in a safe place and can restore them to their respective directories if necessary. But I assume there must be a smarter way -which I am unaware of.
For backend view, you modified the file administrator/components/com_eventbooking/view/registrants/tmpl/default.php, correct?
Then move that file to administrator/templates/isis/html/com_eventbooking/registrants folder so that the change won't be lost when you update to future release
For frontend, you need to do the same. Move the modified file to PATH_TO_TEMPLATE/html/com_eventbooking/registrants folder (PATH_TO_TEMPLATE is the path to the template which you are using in frontend of your site)