Linchpin by Creaholik Pro

It loads before the plugin and takes over a declaration the plugin guards, so the plugin skips its own copy and the conflict never happens. Nothing inside the plugin is changed, and deleting this file returns everything to how it was.

It was checked before it was written — it parses, it declares nothing unguarded, it runs no dynamic code, and your site was loaded once with it active to prove it does not break anything.

<?php
/**
 * Compat overlay: protect the "jquery" script handle from being silently
 * re-registered by arprice / migrate-guru / ocean-extra / updraftplus.
 *
 * None of these plugins should ever *register* jquery with a custom src -
 * WordPress core already provides it (as a dependency group pointing to
 * jquery-core + jquery-migrate). UpdraftPlus contains a legacy code path
 * (only meant for WP < 3.3) that calls wp_deregister_script('jquery') and
 * then wp_register_script('jquery', <cdn url>, ...). If that path is ever
 * triggered (or any other plugin does something similar), it silently
 * clobbers the handle for every plugin that runs after it, and whichever
 * plugin enqueues last "wins" with no error logged.
 *
 * This overlay does not touch any plugin file. It simply verifies, very
 * late on wp_enqueue_scripts / admin_enqueue_scripts / login_enqueue_scripts,
 * that the "jquery" handle still points at core's dependency-group
 * definition (src === false). If some plugin swapped it for a real URL,
 * we restore the core definition so the platform stays consistent
 * regardless of plugin load order.
 */

if ( ! function_exists( 'linchpin_restore_core_jquery_handle' ) ) {
	function linchpin_restore_core_jquery_handle() {
		if ( ! did_action( 'wp_default_scripts' ) && ! function_exists( 'wp_scripts' ) ) {
			return;
		}

		$scripts = wp_scripts();

		if ( ! isset( $scripts->registered['jquery'] ) ) {
			return;
		}

		$jquery = $scripts->registered['jquery'];

		// Core's own registration always uses src === false and relies on
		// jquery-core + jquery-migrate as dependencies. If src is truthy,
		// some plugin has replaced the handle with its own copy/CDN URL.
		if ( ! empty( $jquery->src ) ) {
			// Make sure the underlying pieces core relies on still exist;
			// if a plugin also clobbered those, leave things alone rather
			// than guessing at a version/URL.
			if ( isset( $scripts->registered['jquery-core'] ) && isset( $scripts->registered['jquery-migrate'] ) ) {
				wp_deregister_script( 'jquery' );
				wp_register_script( 'jquery', false, array( 'jquery-core', 'jquery-migrate' ), null );
			}
		}
	}
}

if ( ! function_exists( 'linchpin_reenqueue_jquery_if_needed' ) ) {
	function linchpin_reenqueue_jquery_if_needed() {
		linchpin_restore_core_jquery_handle();

		// If jquery was already queued for output before we fixed the
		// registration above, re-enqueue it so the corrected definition
		// (with proper deps) actually gets printed.
		if ( function_exists( 'wp_script_is' ) && wp_script_is( 'jquery', 'enqueued' ) ) {
			wp_enqueue_script( 'jquery' );
		}
	}
}

if ( ! function_exists( 'linchpin_guard_jquery_handle_boot' ) ) {
	function linchpin_guard_jquery_handle_boot() {
		// Run after every plugin's own enqueue callbacks have had a chance
		// to (mis)register the handle, but still before scripts are printed.
		add_action( 'wp_enqueue_scripts', 'linchpin_reenqueue_jquery_if_needed', PHP_INT_MAX );
		add_action( 'admin_enqueue_scripts', 'linchpin_reenqueue_jquery_if_needed', PHP_INT_MAX );
		add_action( 'login_enqueue_scripts', 'linchpin_reenqueue_jquery_if_needed', PHP_INT_MAX );
	}
}

add_action( 'init', 'linchpin_guard_jquery_handle_boot' );

It loads before the plugin and takes over a declaration the plugin guards, so the plugin skips its own copy and the conflict never happens. Nothing inside the plugin is changed, and deleting this file returns everything to how it was.

It was checked before it was written — it parses, it declares nothing unguarded, it runs no dynamic code, and your site was loaded once with it active to prove it does not break anything.

<?php
/**
 * Overlay: fix duplicate script handle "iris".
 *
 * heartbeat-control ships a bundled copy of CMB2 which, on the front end,
 * re-registers the "iris" script pointing at admin_url( 'js/iris.min.js' )
 * instead of the core copy at wp-includes/js/iris.min.js. WooCommerce's
 * admin screens depend on wp_enqueue_script( 'iris' ) resolving to the
 * real WordPress core Iris color-picker library. Depending on hook order,
 * CMB2's registration can silently clobber the correct one (or vice
 * versa), leaving either WooCommerce's color pickers or CMB2's color
 * pickers broken with no error in the logs.
 *
 * This overlay does not edit either plugin. It simply re-asserts the
 * correct core registration for the "iris" handle after both plugins
 * have had a chance to register their scripts, so the handle always
 * points at the genuine core file regardless of load order.
 */

if ( ! function_exists( 'linchpin_fix_iris_script_handle' ) ) {
	/**
	 * Ensure the "iris" script handle points at the real WordPress core
	 * Iris library, no matter which plugin registered it last.
	 */
	function linchpin_fix_iris_script_handle() {
		if ( ! function_exists( 'wp_scripts' ) ) {
			return;
		}

		$scripts = wp_scripts();

		if ( ! isset( $scripts->registered['iris'] ) ) {
			return;
		}

		$registered = $scripts->registered['iris'];
		$src        = isset( $registered->src ) ? $registered->src : '';

		// Core's own registration lives under wp-includes/js/iris.min.js.
		// If the currently registered "iris" handle points anywhere else
		// (e.g. admin_url( 'js/iris.min.js' ) from a bundled CMB2 copy),
		// restore the correct core registration.
		$core_path = 'wp-includes/js/iris.min.js';

		if ( false !== strpos( $src, $core_path ) ) {
			return; // Already correct.
		}

		$suffix = defined( 'SCRIPT_DEBUG' ) && SCRIPT_DEBUG ? '' : '.min';

		wp_deregister_script( 'iris' );
		wp_register_script(
			'iris',
			includes_url( "js/iris{$suffix}.js" ),
			array( 'jquery-ui-draggable', 'jquery-ui-slider', 'jquery-touch-punch' ),
			get_bloginfo( 'version' ),
			1
		);
	}
}

if ( ! function_exists( 'linchpin_reassert_iris_frontend' ) ) {
	function linchpin_reassert_iris_frontend() {
		linchpin_fix_iris_script_handle();
	}
}

if ( ! function_exists( 'linchpin_reassert_iris_admin' ) ) {
	function linchpin_reassert_iris_admin() {
		linchpin_fix_iris_script_handle();
	}
}

// Hook late (priority 9999) so this runs after both heartbeat-control's
// CMB2 bundle and WooCommerce have registered their own copies of the
// "iris" handle via wp_enqueue_scripts / admin_enqueue_scripts.
add_action( 'wp_enqueue_scripts', 'linchpin_reassert_iris_frontend', 9999 );
add_action( 'admin_enqueue_scripts', 'linchpin_reassert_iris_admin', 9999 );

It loads before the plugin and takes over a declaration the plugin guards, so the plugin skips its own copy and the conflict never happens. Nothing inside the plugin is changed, and deleting this file returns everything to how it was.

It was checked before it was written — it parses, it declares nothing unguarded, it runs no dynamic code, and your site was loaded once with it active to prove it does not break anything.

<?php
/**
 * Compatibility overlay: DONOTCACHEPAGE constant collision.
 *
 * updraftplus (class-updraftplus.php:783) defines DONOTCACHEPAGE without
 * checking defined() first, while litespeed-cache and
 * woocommerce-gateway-stripe both guard their own definitions. Depending on
 * load order, updraftplus's unguarded define() can run after another plugin
 * has already defined the constant, triggering a duplicate-definition
 * warning/fatal under strict error handling.
 *
 * Fix: define the constant here, as early as possible (mu-plugins load
 * before regular plugins), guarded by defined(). This guarantees the
 * constant already exists by the time any plugin tries to (re)define it, and
 * since our own definition is guarded, it never causes a duplicate
 * declaration itself.
 */

if ( ! defined( 'DONOTCACHEPAGE' ) ) {
	define( 'DONOTCACHEPAGE', true );
}