Making custom fields optional in frontend and confirmation mail

Hi everybody!
A client of mine needed to be able to decide wether some of the custom fields for events should be displayed in frontend and/or confirmation mails. (He uses these for additional payment-infos, that should appear inside the mails but not the event-page on the website.)

(Very) short description: I implemented this by simply adding corresponding options to the component's and mailer-plugin's xml files and an if-statement to the template file for event-display as well as adding custom fields to the mailer.php's SQL-query and mailing function.

I, of course, would love to see my customizations merged into the project to be update-proof - are you guys interested?

Hi, it's an interesting solution. But I think it's for a very case. So I fear, it will not be integrated to the core. But I am not representative.

I like it!

Nice work, but I'm not representative either.
I think we should discuss within the team and let you know...

Thank you for your quick replies - its very refreshing to find an open source project with actual activity

@jojo

But I think it's for a very case.

I wouldnt say thats the only use case for this feature. Actually my solution was inspired by several posts in this forum revolving around custom fields usage, like storing internal information in them that should not be visible to website visitors.
From my perpective it brings a big plus in flexibility achieved by minimal changes to the core.

I wrote:

But I think it's for a very case.

Sorry, sometimes my thoughts are too quick. I was trying to say: it's for a very special case.
If you want to share your core hack here, you're welcome and our team will have a look, if and how we can integrate it.
If not then perhaps others will be happy to use the hack.
As more users as they want it, it will be integrated into the core.