Miscellaneous Filters

3 unique filter hooks currently map to this category, across 4 call sites.

Hook Inventory

Hook	Edition	Call Sites	First Source
fluent_community/custom_order_by	Core	1	fluent-community/app/Models/Feed.php:377
fluent_community/max_execution_time	Core	1	fluent-community/app/Functions/Utility.php:596
fluent_community/max_per_page	Core	2	fluent-community/app/Http/Controllers/ActivityController.php:23

fluent_community/custom_order_by

• Type: filter
• Edition: Core
• Call sites: 1
• When it fires: Applies a custom sort to the post query for an order key the built-in sorts do not handle.

Reachable only for keys you have added through fluent_community/post_order_options: the scope rejects anything outside that list before the filter, and each of the seven shipped keys is handled by an earlier branch and returns early. A callback receives the query builder and must return a builder — return nothing and the caller ends up with null where a query is expected. Apply ordering only; adding where clauses here silently changes which posts a viewer sees.

Parameters

#	Name	Type	Description
1	$query	mixed	The post query builder, with no ordering applied yet.
2	$type	string	The requested sort key.

Return: The query builder. Returning anything else breaks the caller, which continues to chain on it.

Call Sites

Edition	Source	Parameters
Core	fluent-community/app/Models/Feed.php:377	$query (mixed) $type (mixed)

Example

add_filter('fluent_community/custom_order_by', function ($query, $type) {
    return $query;
}, 10, 2);

Related: fluent_community/post_order_options

fluent_community/max_execution_time

• Type: filter
• Edition: Core
• Call sites: 1
• When it fires: Filters the number of seconds a batched background job may run before re-scheduling itself.

The default is derived from PHP's max_execution_time: unlimited or unreadable becomes 60, the value is capped at 58, and three seconds of headroom are subtracted — so a typical site sees 27 or 55. Email digests, post and comment notifications and the moderation mailers all compare their elapsed time against it and queue a fresh Action Scheduler task when they exceed it. Returning a value larger than the real PHP limit risks jobs being killed mid-batch, which loses the resume point.

Parameters

#	Name	Type	Description
1	$maxRunTime	int	Seconds of budget for a batch, already capped and reduced by three.

Return: int — seconds. It is not re-clamped, so the cap and the headroom are yours to respect.

Call Sites

Edition	Source	Parameters
Core	fluent-community/app/Functions/Utility.php:596	$maxRunTime (mixed)

Example

add_filter('fluent_community/max_execution_time', function ($maxRunTime) {
    return $maxRunTime;
}, 10, 1);

Related: fluent_community_send_daily_digest

fluent_community/max_per_page

• Type: filter
• Edition: Core
• Call sites: 2
• When it fires: Filters the ceiling on how many items a paginated portal endpoint will return.

Defaults to 100 and is applied identically in the feeds and activities endpoints, where the requested per_page is clamped with min($maxPerPage, max(1, $perPage)). The result is cast with (int) and an effective 0 falls back to 100, so the limit cannot be removed by returning nothing — return a large number instead. It bounds only these two endpoints; other list endpoints use the framework's own pagination defaults.

Parameters

#	Name	Type	Description
1	$maxPerPage	int	The per-page ceiling, 100 by default.

Return: int — cast to an integer; a falsy result reverts to 100.

Call Sites

Edition	Source	Parameters
Core	fluent-community/app/Http/Controllers/ActivityController.php:23	100 (int)
Core	fluent-community/app/Http/Controllers/FeedsController.php:52	100 (int)

Example

add_filter('fluent_community/max_per_page', function ($maxPerPage) {
    return $maxPerPage;
}, 10, 1);