Charitable Documentation

Learn how to make the most of Charitable with clear, step-by-step instructions.

Charitable_Donation_Field

The Charitable_Donation_Field class allows you to create new donation fields or edit existing ones.

Table of Contents

Usage

Create a new donation field

If you want to add a new donation field, you will first need to create a new Charitable_Donation_Field instance, and then register it in the Donation Fields Registry.

add_action( 'init', function() {

    /* Create the Donation Field instance. */
    $field = new Charitable_Donation_Field(
        'my_custom_field',
        array(
            'label'          => __( 'My Custom Field' ),
            'data_type'      => 'meta', 
            'value_callback' => false,
            'donation_form'  => array(
                'type'       => 'text',
                'required'   => false,
                'show_after' => 'phone',
            ), 
            'admin_form'     => true,
            'show_in_meta'   => true,
            'show_in_export' => true,
            'email_tag'      => array(
                'description' => __( 'The custom field value' ),
            ),
        )
    );

    /* Register it. */
    charitable()->donation_fields()->register_field( $field );
} );

Get an existing donation field

If you want to edit or change an existing donation field, the best way to do this is by getting the registered donation field object.

You can then use set() or the magic setter to update the field definition, or use the magic getter to get information about the field.

/* Get the Donation Fields Registry. */
$fields = charitable()->donation_fields();

/* Get the Phone field. */
$field = $fields->get_field( 'phone' );

/* Change the label (magic setter). */
$field->label = 'Mobile No.';

/* Change the field to be required. */
$field->set( 'donation_form', 'required', true );

/* Print out the field's label (magic getter). */
echo $field->label;

Properties

field (string)

The field’s key, or identifier. Every field must have a unique key.

label (string)

The field’s label. This is a description of the field. This is what will be used in the donation form (unless you specifically override it in the donation_form argument), in the admin donation details area and in the donations export as the column header.

data_type (string)

The type of data that this field represents. There are two main options, with a third used mostly for internal Charitable purposes:

  • user: This is information that is specific to the donor, and will generally remain true for the donor in subsequent donations. Examples of this would include their name, phone number, etc.
  • meta: This is information that is specific to the donation. An example of this would be the payment gateway used for the donation, or whether the donor would like this donation to be made anonymously.
  • core: This is used primarily for internal purposes and should not be used in most cases. If you do use it, you will need to make sure you write additional code for storing the field value, as well as for getting it back from the database.

value_callback (false|callable)

How the field’s value will be retrieved. If you leave this out or set it to false, the default callback will be used based the field’s data type:

  • For a meta field, the default value callback is charitable_get_donor_meta_value.
  • For a user field, the default value callback is charitable_get_donation_meta_value.

You can specify your own value callback by passing your own function’s name, an array representing an object method [$class_name, $method_name], or an anonymous function.

donation_form (false|array)

How/whether the field will be included in the donation form. If this is left out or set to false, the field will not be included in the donation form at all. When passing an array, the following arguments are available:

  • label (string)
    The label shown in the donation form. If this is left out, the field’s label property will be used.
  • type (string)
    The type of field. Options include:
    • text
    • email
    • password
    • date
    • datepicker
    • checkbox
    • multi-checkbox
    • select
    • radio
    • file
    • fieldset
    • editor (uses the classic WordPress Editor)
    • textarea
    • number
    • picture
    • url
    • hidden
  • required (boolean)
    Whether this is a required field.
  • options (array)
    Provide a set of options. This is required when type is one of select, radio or multi-checkbox. These should be provided in a simple value => label array, where the label is what people see when they select an option, and value is what gets stored in the database.
  • default (mixed)
    The default value for this field.
  • placeholder (string)
    A placeholder shown in the field when it’s empty.
  • min (int)
    Set the minimum allowed number. Only applicable if type is number.
  • max (int)
    Set the maximum allowed number. Only applicable if type is number.
  • attrs (array)
    An array of arbitrary attributes to be added to the input field.
  • section (string)
    The section of the donation form this should appear in. There are two sections by default: user and meta. If this is not set, the section will be based on the field’s data type.
  • show_before (string)
    Sets where the field should be added in the donation form by specifying the field it should appear before.
  • show_after (string)
    Sets where the field should be added in the donation form by specifying the field it should appear after.
  • priority (int)
    Set the position of the field within the form. This is used unless show_after or show_before are set for the field. If priority, show_after and show_before are not set, the field will be shown after the most recently registered form field.
  • value_callback (false|callable)
    A callback function to retrieve the value of the field for a donation. This will override the value_callback setting for the field.

admin_form (boolean|array)

Sets whether the field should be shown in the admin donation form.

  • If this is set to false, the field will not be shown in the admin donation form (not even as a hidden input).
  • If this is set to true, the form field will inherit arguments from the donation_form (if provided), or use default arguments.
  • Alternatively, you can pass an array of values to fine-tune how this field is shown in the admin form (all the same arguments are accepted as for donation_form above).

show_in_meta (boolean)

Whether to include this in the “Donation Details” section of a single donation details admin page.

show_in_export (boolean)

Whether to include this in the Donations export available from Charitable > Donations.

email_tag (boolean|array)

Whether to create an email tag for this field.

  • If this is false, no email tag will be created.
  • If this is true, an email tag will be created, using the field label as the description. No preview value will be set.
  • Alternatively, pass an array for finer control over the email tag details:
    • description (string)
      The description shown for the email tag. If no description is set, the field’s label will be used.
    • tag (string)
      The email tag. If this is not provided, the field key will be used.
    • preview (mixed)
      A value to use in email previews for this field.

Methods

require()

Added in version 1.5.0

Create a new Donation Field instance.

Arguments

  • $field (string)

    The field’s unique key.

  • $args (array)

    An array containing any of the properties shown above, except for $field.

Usage

$field = new Charitable_Donation_Field(
    'my_custom_field',
    array(
        'label'          => __( 'My Custom Field' ),
        'data_type'      => 'meta', 
        'value_callback' => false,
        'donation_form'  => array(
            'type'       => 'text',
            'required'   => false,
            'show_after' => 'phone',
        ), 
        'admin_form'     => true,
        'show_in_meta'   => true,
        'show_in_export' => true,
        'email_tag'      => array(
            'description' => __( 'The custom field value' ),
        ),
    )
);

require()

Added in version 1.6.0

Change a field argument.

Arguments

  • key (string)

    The field argument to change. This can be any of the properties outlined above, except for $field: label, data_type, value_callback, donation_form, admin_form, show_in_meta, show_in_export, email_tag.

  • setting (string)

    This identifies a specific array element within one of the array-compatible arguments: donation_form, admin_form, email_tag. Note: If $key is not one of those three, leave this as an empty string.

  • $value (mixed)

    The new value for this field argument.

Usage

/* Get the State field. */
$field = charitable()->donation_fields()->get_field( 'state' );

/* Change the label to Province. */
$field->set( 'label', '', 'Province' );

/* Change the field to be required. */
$field->set( 'donation_form', 'required', true );

require()

Added in version 1.5.0

Change the field’s parameters. Unlike the set() method described above, this does not allow you to update a single element within an array-like argument (you can’t use it to easily change whether a field is required in the donation form, for example).

It’s the equivalent of calling set() with the $setting argument left as an empty string.

Note: __set() is a magic method in PHP. It is called implicitly when you try to set one of the class properties, other than $field.

Arguments

  • $key (string)

    The field argument to change. This can be any of the properties outlined above, except for $field: label, data_type, value_callback, donation_form, admin_form, show_in_meta, show_in_export, email_tag.

  • $value (mixed)

    The new value for this field argument.

Usage

/* Get the State field. */
$field = charitable()->donation_fields()->get_field( 'state' );

/* Change the label to Province. */
$field->label = 'Province';

require()

Added in version 1.5.0

Get the field’s value for a particular argument.

Note: __get() is a magic method in PHP. It is called implicitly when you try to access a class property.

Arguments

  • $key (string)

    The field argument to retrieve.

Usage

/* Get the State field. */
$field = charitable()->donation_fields()->get_field( 'state' );

/* Print/echo the current label. */
echo $field->label;

Still have questions? We’re here to help!

Last Modified:

What's New In Charitable

View The Latest Updates
🔔 Subscribe to get our latest updates
📧 Subscribe to Emails

Email Subscription

Join our Newsletter

We won’t spam you. We only send an email when we think it will genuinely help you. Unsubscribe at any time!

ambassadors New

🖨️ Introducing Fliers and Posters: Raise Money Away From the Screen!

A lot of peer-to-peer fundraising happens away from a screen: at the finish line of a 5K, on a school noticeboard, in an office kitchen. Charitable Ambassadors 3.4.7 adds 2 printables, a fundraiser flier carrying each fundraiser’s own story and QR code, and a recruitment poster that signs new fundraisers up. Both open as a normal web page and print straight from the browser. Why this is important:

  • 🏁 A flier for every fundraiser: Each one carries that fundraiser’s own photo, story and goal, with a QR code that opens their page rather than your main campaign.
  • 📌 A poster that recruits: It shows “Now Recruiting” above your campaign name with a large QR code that opens your sign-up form, so someone can start fundraising without waiting on a link from you.
  • 🪄 No design tool needed: Both printables render as a normal web page and print from the browser, with no PDF plugin and no designer.
  • 📄 2 flier layouts: Hand out carries the full story for giving to friends and family, and Post up carries a short hook with 5 tear-off tabs for a noticeboard.
  • 🛡️ Off until you switch it on: Fliers stay off after the update until you enable them under Charitable » Ambassadors » Other » Fliers, and only the owner or an administrator can open one.

Check out our announcement here.

Improvement Payments

💸 Introducing Tiered Rates for Fee Relief: Match the Ask to the Gift!

Fee Relief asks your donors one short question at checkout: would you like to cover the processing fee on this gift? Until now that question used a single rate for every donation on a gateway, so a $10 gift and a $500 gift were asked for the same percentage. Fee Relief 1.3.0 lets you set as many donation bands as you like, each carrying its own rate. Why this is important:

  • 🪙 Gentler on small gifts: A fixed transaction cost is a far bigger share of a $10 donation than a $500 one, so bands let you ask for less at the bottom.
  • 🎚️ As many bands as you need: Each band carries its own percentage and its own fixed amount, and the top band runs on with no upper limit.
  • 🛑 An optional ceiling: A Maximum fee field stops any donor being asked for more than a number you choose, however large the gift.
  • 🔌 Set per payment gateway: Stripe can run on four bands while Windcave and Payfast stay on a single rate, because bands belong to a gateway and not to your whole site.
  • 🛡️ Nothing changes until you say so: Your current rates stay exactly as they are until you switch Use Tiered Rates on under Charitable » Settings » Advanced » Fee Relief.

Check out our announcement here.

Donations Improvement

📊 Your Pro Dashboard Can Now Compare, Export, and Score!

Most fundraising dashboards only tell you how much you have raised. Charitable Pro 1.8.19 rebuilds the dashboard and the Reports Overview around the harder questions: whether anything is broken, whether this period beat the last one, and which single change would make the most difference today. Why this is important:

  • 📈 Every figure has a trend: Pick a period and the tiles and the chart move together, with each total shown against the previous period.
  • 🗓️ Charts that stay readable: Short ranges group donations day by day, while longer ranges group by week or month, so a full year reads as a curve instead of a flat line.
  • 🔀 Compare any 2 periods: Not just consecutive ones, so you can ask how this December did against last December. That matters because fundraising is seasonal.
  • 📤 Export the whole summary: Send the full overview out as CSV or PDF, ready for a board pack or a funder report.
  • 🎯 Score your setup for free: Have your fundraising setup scored, so the one change worth making next is the one you can see.

Check out our announcement here.

Feature New

🎟️ Introducing Charitable Events: Sell Tickets Inside Your Campaigns!

Most nonprofits sell event tickets in one tool and collect donations in another, which leaves two sets of reports and a manual match at the end of the year. Charitable Events brings both together, selling tickets through the same donation forms and payment gateways you already run in Charitable. Why this is important:

  • 🎟️ Every ticket is a donation: Ticket sales run through the gateway you already use and count toward the campaign goal, with everything managed under Charitable » Events.
  • 📱 QR check-in from any phone: Each attendee gets their own QR code on the receipt, and volunteers scan at the door through a check-in link that needs no WordPress account.
  • 🧾 Receipts ready for tax time: Give each ticket type a fair market value, and Charitable puts the correct tax-deductible amount on every donor receipt.
  • 📋 Attendee details at checkout: Ask every guest for a meal choice, shirt size, or access needs, with a separate attendee record created for each ticket.
  • 🗓️ Blocks and calendars included: Three editor blocks plus Sugar Calendar and The Events Calendar support put your events where supporters already look.

Check out our announcement here.

ai New

🚀 Unleash AI Power in Charitable!

Your AI assistant can now build, edit, and manage your Charitable fundraising campaigns directly — just by asking. With Charitable Pro adding write support for the WordPress Abilities API, tools like ChatGPT, Claude, and Cursor can handle full administrative actions safely through MCP. Why this is important:

  • 🤖 Campaign creation in plain language: Prompt your assistant with a goal like “Set up a fundraiser for the shelter with a $5,000 goal”, and it builds a real draft campaign complete with suggested donation tiers.
  • 🎨 Instant donation form tweaks: Add custom fields, change button colors, or reorder elements without diving into form settings.
  • 📝 Offline gift logging: Tell your assistant about cash or check gifts, and it will match donor emails and record transactions into your history.
  • 🛡️ Safety and control by default: Write access stays strictly off until turned on in Charitable » Tools » AI MCP, keeping read-only reporting safe by default.
  • 📜 Full audit logging: Every change made by an AI assistant is tracked under Charitable » Tools » Logs, so you always know who (or what) updated your site.

Check out our announcement here.