@prefix sioc: . @prefix dc: . @prefix dcterms: . @prefix xsd: . @prefix content: . @prefix rdf: . @prefix rdfs: . a sioc:Post ; dc:title "Background Jobs" ; dcterms:identifier 152529 ; dc:modified "2026-10-26T11:56:54Z"^^xsd:dateTime ; dc:created "2026-10-26T11:56:54Z"^^xsd:dateTime ; sioc:link ; sioc:has_creator ; sioc:has_container ; content:encoded """

The plugin keeps each site’s user records up to date with a user sync: every user with a role on the site gets a last activity date, a BuddyPress blog record and a profile name. Since 1.1.3 the sync is scheduled through LH_Buddypress_Multi_Network_Queue (includes/class-lh-buddypress-multi-network-queue.php). It runs on Action Scheduler when the current site has it, in the lh-buddypress-multi-network group (listed under Tools → Scheduled Actions), and on WP-Cron otherwise. The same hooks are used on both runners, and on Action Scheduler any WP-Cron copy of a job is cleared so it runs once.

  • lh_bmn_wakeup – the daily sync, per site. Created on init (throttled hourly by the lh_bmn_schedule_checked transient) on each site where BuddyPress loads, with up to 1000 seconds of jitter, so sites added later get it too.
  • lh_bmn_single – a one-off sync 30 seconds after a user registers, is added to the site or updates a profile. While one is waiting no other is queued, so a burst of changes runs the sync once.

A user added to a site is handled while WordPress is switched to that site, so that sync goes to the site’s WP-Cron: Action Scheduler is only safe for the site the request is running on. On deactivation the whole Action Scheduler group is cancelled on the current site and every WP-Cron instance of the plugin’s hooks is removed, including the retired lh_bmn_process; on network deactivation WP-Cron is also cleared on every other site.

Filters

  • lh_bmn_wakeup_hook, lh_bmn_single_hook – the job hook names.
  • lh_bmn_uses_action_scheduler – return false to keep every job on WP-Cron.
"""^^rdf:XMLLiteral ; sioc:content """Part of: LH Buddypress Multi NetworkThe plugin keeps each site’s user records up to date with a user sync: every user with a role on the site gets a last activity date, a BuddyPress blog record and a profile name. Since 1.1.3 the sync is scheduled through LH_Buddypress_Multi_Network_Queue (includes/class-lh-buddypress-multi-network-queue.php). It runs on Action Scheduler when the current site has it, in the lh-buddypress-multi-network group (listed under Tools → Scheduled Actions), and on WP-Cron otherwise. The same hooks are used on both runners, and on Action Scheduler any WP-Cron copy of a job is cleared so it runs once. lh_bmn_wakeup – the daily sync, per site. Created on init (throttled hourly by the lh_bmn_schedule_checked transient) on each site where BuddyPress loads, with up to 1000 seconds of jitter, so sites added later get it too.lh_bmn_single – a one-off sync 30 seconds after a user registers, is added to the site or updates a profile. While one is waiting no other is queued, so a burst of changes runs the sync once. A user added to a site is handled while WordPress is switched to that site, so that sync goes to the site’s WP-Cron: Action Scheduler is only safe for the site the request is running on. On deactivation the whole Action Scheduler group is cancelled on the current site and every WP-Cron instance of the plugin’s hooks is removed, including the retired lh_bmn_process; on network deactivation WP-Cron is also cleared on every other site. Filters lh_bmn_wakeup_hook, lh_bmn_single_hook – the job hook names.lh_bmn_uses_action_scheduler – return false to keep every job on WP-Cron.""" ; sioc:topic . rdfs:seeAlso . rdfs:seeAlso .