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_formadmin_formemail_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 $fieldlabeldata_typevalue_callbackdonation_formadmin_formshow_in_metashow_in_exportemail_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!

New templates

🤩 New Beacon Campaign Templates w/ “Hero” Block!

With the new Beacon Campaign Templates for Charitable Pro, you can launch a stunning, full-width fundraising page that instantly captures visitor attention above the fold.

Fundraising page header for Save Maple Grove Park with a donation widget and a small square photo of a sunlit tree thumbnail on the left.

🔦 Above-the-Fold Impact: Lead with a full-width hero image, your logo, and your goal with a donation widget locked right on top of the banner so your ask and momentum register instantly without scrolling.

📐 Two Flexible Layouts: Choose between a structured two-column layout for side-by-side storytelling and supporting details, or a clean one-column view designed for uninterrupted long-form narratives.

⚡ All-in-One Hero Field: Powered by the new Campaign Hero field, bringing background media, live progress bars, custom donation amounts, and recurring giving tabs together into a single cohesive block that can be dropped into any layout.

🎨 Automatic Theme Matching: The hero banner and donation widget automatically inherit your campaign theme’s button and accent colors, ensuring your entire presentation stays beautifully on-brand without touching a line of CSS.

Learn more here.

donation form Feature New

📝 Donation Form Block: Embed a Working Donation Form Anywhere

With the new Donation Form Block for Charitable Pro, you can drop a fully working donation form directly onto any page or post in the WordPress block editor. No redirects, no page reloads, and zero friction between reading your story and making a contribution.

📝 Drop Forms Anywhere: Place a working form directly onto your homepage, inside a story-driven blog post, on a dedicated landing page, or within a campaign announcement.

🎯 Dynamic Campaign Binding: Easily choose a specific campaign from the block sidebar or set it to automatically bind to whichever campaign is currently being viewed.

📐 Full vs. Minimal Form Views: Switch between a full layout or a compact minimal view to perfectly fit sidebars, narrow columns, or wide landing pages.

🎨 Scoped No-Code Styling: Customize typography, container spacing, border radius, amount buttons, and accent colors independently for every form instance without touching a line of CSS.

Learn more here.

ambassadors New

👤 Creator Profiles: Put a Face to Every Peer-to-Peer Campaign

Ambassadors 3.3.0 now provies Creator Profiles — giving your supporters a permanent, shareable public home that turns one-time fundraisers into ongoing relationships.

👤 Public Creator Pages: Give every fundraiser an instant, clean landing page at /creator/their-name/ to showcase their custom avatar, bio, and a browsable grid of their campaigns.

📊 Proof of Impact: Boost donor trust by displaying site-wide milestones on the profile—like total funds raised and total donor counts.

💳 Interactive Hover Cards: When donors hover over a creator’s name on a campaign page, a compact card expands with their bio and social handles right at the moment of decision.

📍 Responsible Location Sharing: Allow creators to safely show local supporters where they are based using only city, state, and country details.

🛠️ Self-Serve Customization: Fundraisers can update their own profiles and link up to six social networks directly from the My Campaigns hub, saving you admin time.

Ready to empower your advocates? Update to Ambassadors 3.3.0 and turn on “Enable Public Creator Page” today!

Improvement Payments

📱 Turn Mobile Scrollers Into Donors: Meet Charitable’s Mollie Upgrade

Losing mobile supporters because they hate typing out long card numbers on their phones? Charitable’s updated Mollie integration features:

⚡ One-Tap Wallet Checkout: Enable donors to complete their gifts instantly using Apple Pay or Google Pay with a simple face scan, fingerprint, or tap.

💰 No Extra PCI Burden: Skip complex domain verification and security compliance since all wallet transactions run safely through Mollie’s hosted checkout.

🛠️ Custom Cancel Routing: Keep the experience predictable by automatically sending donors who back out to your cancellation page, or use developer filters to route them to a custom page.

Visit this page to learn more.

ambassadors improved New

Moderation and Directory Screens In Ambassadors 3.0

Ambassadors 3.0 has new features: moderation and directory screens… now easily see those who are earning donations on your peer to peer network – including campaign creators that might need to be verified – all in one place. Generate reports, email ambassadors and campaign creators directly and more.

🚀 See when campaign creators and ambassadors have updated their campaigns, what donors/donation they have brought in and more.

🎉 Manually add ambassadors and campaign creators, and approve them in one-click!

Visit this page to learn more.