Use the frm_exclude_spam_entries filter to include spam entries in an entry query that normally leaves them out. Return false to keep spam entries in the results.

Spam entries are saved so they can be reviewed in the Spam tab of the entries list. Everywhere else, Formidable leaves them out of entry queries, such as entry counts, Views, graphs, and exports.

Requirements

• Formidable Forms 7.0 or later. The hook is part of Formidable Forms Lite.

When it runs

The filter runs when Formidable builds an entry query that doesn't already choose an entry status. In Formidable Forms Lite, queries that filter by status, such as the one behind the Spam tab, skip it.

Formidable Forms Pro runs it for each query it builds, such as for graphs and Dynamic fields, with $exclude set to true. Formidable Views leaves spam entries out of Views on its own and doesn't run this filter.

When a Lite query selects specific entries by ID or key, spam entries stay in the results. For a query built as an array, the filter still runs with $exclude already false. For a query built as an SQL string, it doesn't run.

Usage

add_filter( 'frm_exclude_spam_entries', 'my_function_name', 10, 2 );

Parameters

• $exclude (bool): Whether to leave spam entries out of the query. Return false to include them.
• $where (array|string): The query conditions, as an array or an SQL string.

Examples

add_filter( 'frm_exclude_spam_entries', '__return_false' );
$total_entries = FrmEntry::getRecordCount( 5 ); // Change 5 to the ID of your form.
remove_filter( 'frm_exclude_spam_entries', '__return_false' );

Limitations

• Returning false for every query adds spam entries to entry counts, graphs, and exports across the site. Add the filter only around your own query, as in the example.
• The filter doesn't change Views. To show spam entries in a View, filter the View by Entry status equals Spam.

Related developer hooks

• Decide whether a flagged submission is saved as a spam entry with the frm_save_spam_entry hook.
• Run code when an entry is marked as spam with the frm_entry_marked_spam hook.

Related articles

• Add Spam Protection
• Manage Entries from the Back-End