Skip to content

Cron: Make flushing response data and ignore_user_abort optional in wp-cron - #12210

Closed
i-am-chitti wants to merge 1 commit into
WordPress:trunkfrom
i-am-chitti:65474-wp-cron-flush-optional
Closed

Cron: Make flushing response data and ignore_user_abort optional in wp-cron#12210
i-am-chitti wants to merge 1 commit into
WordPress:trunkfrom
i-am-chitti:65474-wp-cron-flush-optional

Conversation

@i-am-chitti

@i-am-chitti i-am-chitti commented Jun 18, 2026

Copy link
Copy Markdown

Fixes https://core.trac.wordpress.org/ticket/65474

On some server configurations (notably LiteSpeed with LSPHP), calling litespeed_finish_request() or fastcgi_finish_request() can prematurely terminate the cron process mid-execution, causing data inconsistencies with plugins like WooCommerce and Action Scheduler.

This PR introduces two opt-out constants, definable in wp-config.php:

  • WP_CRON_DISABLE_FLUSH — skips the fastcgi_finish_request() / litespeed_finish_request() call
  • WP_CRON_DISABLE_IGNORE_ABORT — skips the ignore_user_abort(true) call

Both default to false, so no behavior change for existing sites. The naming follows existing WordPress conventions (DISABLE_WP_CRON, WP_DISABLE_FATAL_ERROR_HANDLER).

Note: The original patch on Trac proposed WP_CRON_FLUSH defaulting to false, which would have been a breaking change. This PR takes the opt-out approach instead.

Use of AI

Assisted by Copilot

…p-cron.

Introduces two opt-out constants for wp-cron.php that can be defined in wp-config.php
@github-actions

github-actions Bot commented Jun 18, 2026

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props iamchitti, aldavigdis.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions

Copy link
Copy Markdown

Hi there! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

Thank you,
The WordPress Project

@github-actions

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@aldavigdis

Copy link
Copy Markdown

I request that this PR is closed until I make my own within a reasonable time frame, based on the original SVN patch at https://core.trac.wordpress.org/ticket/65474.

@i-am-chitti

Copy link
Copy Markdown
Author

@i-am-chitti
i-am-chitti deleted the 65474-wp-cron-flush-optional branch June 18, 2026 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants