don't run activity_batch_load() on admin/build/activity

Created on 17 February 2011, over 14 years ago
Updated 29 October 2025, 6 days ago

Currently there is logic in theme_activity_settings_actions_list() which runs activity_batch_load() just to determine if we're able to regenerate the activities for that particular action. This is really intensive if the purge setting is high, and in reality, just more intensive than it should be altogether.

I'd like to change this to some stricter checking logic, only supporting the hooks and ops we currently include with activity.

πŸ› Bug report
Status

Closed: outdated

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States sirkitree

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

No activities found.

Production build 0.71.5 2024