Problem
When migration calls add_to_outbox() (e.g., for Move activities), the post_activitypub_add_to_outbox action fires but the scheduler hooks (schedule_outbox_activity_for_federation, schedule_announce_activity) aren't registered yet because:
Migration::init() runs at init priority 1
Scheduler::init() runs at init priority 10 (default)
This causes activities added during migration to go to the outbox but never get scheduled for federation.
Proposed Solution
- Change
Scheduler::init() priority from 10 (default) to 0, so it runs before Migration::init() (priority 1)
- This ensures that the
post_activitypub_add_to_outbox hooks are registered before any migration code calls add_to_outbox()
Testing Instructions
GitHub Issue: #2771
Problem
When migration calls
add_to_outbox()(e.g., for Move activities), thepost_activitypub_add_to_outboxaction fires but the scheduler hooks (schedule_outbox_activity_for_federation,schedule_announce_activity) aren't registered yet because:Migration::init()runs atinitpriority 1Scheduler::init()runs atinitpriority 10 (default)This causes activities added during migration to go to the outbox but never get scheduled for federation.
Proposed Solution
Scheduler::init()priority from 10 (default) to 0, so it runs beforeMigration::init()(priority 1)post_activitypub_add_to_outboxhooks are registered before any migration code callsadd_to_outbox()Testing Instructions
add_to_outbox())activitypub_db_versionoptionactivitypub_process_outboxcron events)GitHub Issue: #2771