FIX: Ensure upgrader_process_complete fires for bulk updates#9013
FIX: Ensure upgrader_process_complete fires for bulk updates#9013patil-vipul wants to merge 1 commit intoWordPress:trunkfrom
upgrader_process_complete fires for bulk updates#9013Conversation
|
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 Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe 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
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
|
@SergeyBiryukov Can you look at this change, thanks 🙇 . |
Summary
The
upgrader_process_completehook currently only fires for individual plugin updates but is skipped during bulk operations due to anis_multicondition check. This inconsistency breaks plugins that rely on post-upgrade actions like cache clearing, security scans, and configuration updates.Changes Made
upgrader_process_completehook from theis_multicondition in WP_Upgrader::run()Trac ticket: https://core.trac.wordpress.org/ticket/63596