Title: Using the Custom Fields code
Last modified: April 7, 2018

---

# Using the Custom Fields code

 *  Resolved [missbritt](https://wordpress.org/support/users/missbritt/)
 * (@missbritt)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/using-the-custom-fields-code/)
 * Can you clarify –
 * Am I adding the code from [https://github.com/joedolson/plugin-extensions/blob/master/my-tickets/custom-fields.php](https://github.com/joedolson/plugin-extensions/blob/master/my-tickets/custom-fields.php)
   to the existing plugin .php file or installing that file as an extra plugin?

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Author [Joe Dolson](https://wordpress.org/support/users/joedolson/)
 * (@joedolson)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/using-the-custom-fields-code/#post-10158938)
 * There are instructions on how to use those files here:
 * [https://github.com/joedolson/plugin-extensions](https://github.com/joedolson/plugin-extensions)
 * You’d install it as an extra plug-in.
 * Best,
    Joe
 *  Thread Starter [missbritt](https://wordpress.org/support/users/missbritt/)
 * (@missbritt)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/using-the-custom-fields-code/#post-10159047)
 * Thank you!
 *  Thread Starter [missbritt](https://wordpress.org/support/users/missbritt/)
 * (@missbritt)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/using-the-custom-fields-code/#post-10159109)
 * Hmmm… I followed the instructions. Installed the custom cart fields plugin and
   activated – but no additional options are showing up anywhere in my WordPress
   admin.
 *  Thread Starter [missbritt](https://wordpress.org/support/users/missbritt/)
 * (@missbritt)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/using-the-custom-fields-code/#post-10159144)
 * I see what the issue is – this makes the changes to ALL events. Is there a way
   to customize these options for each event? We’re a nonprofit with a few different
   types of fundraisers for different programs throughout the year. So, for example,
   right now I’m trying to build a registration form for a golf outing. Later in
   the year we would like to be able to use the same site/plugins to sell tickets
   to a shopping event (all tickets the same.)
 *  Plugin Author [Joe Dolson](https://wordpress.org/support/users/joedolson/)
 * (@joedolson)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/using-the-custom-fields-code/#post-10159436)
 * The ‘context’ parameter can accept an event ID, so that it only adds that custom
   field to a specific event.
 *  Thread Starter [missbritt](https://wordpress.org/support/users/missbritt/)
 * (@missbritt)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/using-the-custom-fields-code/#post-10159701)
 * To be clear: I’m changing the code in the custom fields.php file of the plugin
   every time I want to customize a cart? Just need to be sure because that’s not
   something that will be sustainable for our organization long-term.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Using the Custom Fields code’ is closed to new replies.

 * ![](https://ps.w.org/my-tickets/assets/icon-256x256.png?rev=1097581)
 * [My Tickets - Accessible Event Ticketing](https://wordpress.org/plugins/my-tickets/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/my-tickets/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/my-tickets/)
 * [Active Topics](https://wordpress.org/support/plugin/my-tickets/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/my-tickets/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/my-tickets/reviews/)

## Tags

 * [custom fields](https://wordpress.org/support/topic-tag/custom-fields/)
 * [mytickets](https://wordpress.org/support/topic-tag/mytickets/)

 * 6 replies
 * 2 participants
 * Last reply from: [missbritt](https://wordpress.org/support/users/missbritt/)
 * Last activity: [8 years, 2 months ago](https://wordpress.org/support/topic/using-the-custom-fields-code/#post-10159701)
 * Status: resolved