Hooks & Filters

TableCrafter exposes a small, focused set of extensibility points: two PHP apply_filters hooks for customizing export templates and proxy trust, plus three frontend JavaScript CustomEvents for reacting to mobile card interactions. This page documents every real hook with its exact signature.

Overview

TableCrafter is intentionally lean on server-side hooks. Because the plugin fetches data from external sources rather than storing it in your database, most customization happens through shortcode attributes, CSS custom properties, and the frontend event system rather than through a large hook surface.

At version 3.5.6, the plugin defines exactly two PHP filters and emits three namespaced DOM events. There are no do_action hooks. This page covers all of them.

PHP Filters

Both PHP filters are standard WordPress apply_filters hooks. Register your callbacks with add_filter() from your theme's functions.php or a small companion plugin.

tc_export_templates

Filters the array of export templates returned by TC_Export_Handler::get_export_templates(). Each template is a keyed array describing how the export handler formats dates, numbers, and metadata when generating CSV, XLSX (OOXML), or PDF output. The plugin ships three built-in templates: default, business, and data_analysis.

Add a custom template that includes metadata and uses a European date format:

add_filter( 'tc_export_templates', function( $templates ) {
    $templates['eu_report'] = [
        'name'             => 'EU Report',
        'description'      => 'European report format',
        'include_metadata' => true,
        'date_format'      => 'd/m/Y',
        'number_format'    => '0,00',
    ];
    return $templates;
} );

You can also override a built-in template by reusing its key (for example, changing the default template's date_format):

add_filter( 'tc_export_templates', function( $templates ) {
    $templates['default']['date_format'] = 'F j, Y'; // e.g. June 21, 2026
    return $templates;
} );

tablecrafter_trusted_ip_headers

Filters the list of proxy header keys that TableCrafter's security layer is allowed to trust when resolving the client IP in TC_Security::get_client_ip(). This is used for rate limiting and security logging. For safety, the filter defaults to an empty array, meaning only REMOTE_ADDR is trusted unless you explicitly opt in.

Trust Cloudflare's connecting-IP header when your site sits behind Cloudflare:

add_filter( 'tablecrafter_trusted_ip_headers', function( $headers ) {
    $headers[] = 'cloudflare';
    return $headers;
} );

Frontend JavaScript Events

On the client, the TableCrafter renderer emits native DOM CustomEvents for mobile card interactions. Every event name is prefixed with tablecrafter:, dispatched on the table's container element, and configured with bubbles: true so you can listen on a parent element or document.

The rowData property is the row's data object, rowIndex is its position in the dataset, and (for cardTap) card is the card DOM element. The built-in cardView and cardEdit handlers are deliberate placeholders so you can attach your own behavior.

Listen for card edits anywhere in the document and route them to your own UI:

document.addEventListener('tablecrafter:cardEdit', function (e) {
  const { rowData, rowIndex } = e.detail;
  // Open your custom edit modal with the row data
  openEditor(rowData, rowIndex);
});

document.addEventListener('tablecrafter:cardTap', function (e) {
  console.log('Card tapped at row', e.detail.rowIndex);
});

Styling Hooks (CSS Custom Properties)

Beyond PHP and JS hooks, TableCrafter exposes CSS custom properties so you can theme tables without overriding the stylesheet. Set them on the table container or a parent scope:

.my-page .tablecrafter-container {
  --tc-bg-color: #0f172a;
  --tc-text-color: #e2e8f0;
  --tc-border-color: #334155;
  --tc-focus-color: #38bdf8;
}

What's Not a Hook

To avoid confusion, note the following about TableCrafter's extensibility model:

• There are no do_action hooks in version 3.5.6 — only the two apply_filters filters documented above.
• Per-table configuration (data source, columns, search, sort, pagination, refresh) is controlled through [tablecrafter] shortcode attributes, the Gutenberg block, and the Elementor widget — not through PHP hooks.
• The collaboration features register REST routes under the tablecrafter/v1 namespace; these are internal endpoints, not developer extension points.

Next Steps

To configure tables before reaching for code, see shortcode-reference.html for every [tablecrafter] attribute, and data-export.html to learn how the export templates filtered by tc_export_templates are applied to CSV, XLSX, and PDF output.