Suggested Approach to Reduce Price Field Maddness

[sonicthoughts]

I'm supporting a site where the event coordinator often adds a processing fee and an option to make an additional donation.  For these scenarios, she is forced to create a unique price field for each event fee and now has 50+ price fields to manage.

The organization has been very successful in offsetting costs and increasing fees using this approach. A custom field could indicate if there is an "Additional Donation" and/or "$2 surcharge" field.  I have seen some approaches using a patch from several years ago, but wonder if someone could suggest on a more elegant approach using a hook or API call.
S.

[jaapjansma]

My first thoughts when you are developing something is to split the two in two individual contributions. One is the actual event fee contributions another is the actual donation. That way your reporting becomes probably easier too. But it requires some development

[sonicthoughts]

 Yes.  I agree.  I looked at the price set api and could see a way to add 2 fields.  The price set api is a bit tricky though. Ideally they would use the regular price option and no price set. I have not used a hook before but wonder if that might be easier. Tgoughts?