The Action Scheduler library currently bundles an outdated version of the WP Background Processing library, specifically the WP_Async_Request class. This older version can cause issues if a plugin extends the WP_Async_Request class and relies on methods that exist only in newer versions (e.g., WP_Async_Request::maybe_wp_die). If the version from Action Scheduler is loaded first, it can result in a fatal error.
While this issue can technically be resolved on the vendor/plugin side, addressing it within the Action Scheduler library itself seems like the more appropriate and future-proof solution. It would be very helpful if you could update the bundled WP Background Processing library to the latest version or consider a more flexible integration strategy (e.g., namespacing) to prevent these types of conflicts.
The Action Scheduler library currently bundles an outdated version of the WP Background Processing library, specifically the WP_Async_Request class. This older version can cause issues if a plugin extends the
WP_Async_Requestclass and relies on methods that exist only in newer versions (e.g.,WP_Async_Request::maybe_wp_die). If the version from Action Scheduler is loaded first, it can result in a fatal error.While this issue can technically be resolved on the vendor/plugin side, addressing it within the Action Scheduler library itself seems like the more appropriate and future-proof solution. It would be very helpful if you could update the bundled WP Background Processing library to the latest version or consider a more flexible integration strategy (e.g., namespacing) to prevent these types of conflicts.