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.

CommentFileSizeAuthor
activity-batch-load-negate.patch1.07 KBsirkitree

Comments

Scott Reynolds’s picture

Scott Reynolds commented

Instead, can we take an aid, figure out the activity module (node, comment, user, flag etc) and then query that to say, is this a batchable hook?

(and wow, oops that is a bad set of code...)

_shy’s picture

_shy
Primary language Ukrainian
Location Ukraine, Lutsk 🇺🇦
commented
Issue summary: View changes
Status: Needs review » Closed (outdated)

D6 reached its EOL back in February 2016, and there is no active release for D6 for this module anymore.
Development or support is not planned for D6. All D6-related issues are marked as outdated in a bunch.

If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.

Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.