### PHP: MuLoaderPlugin::dumpRequireFile() Output

Source: https://context7.com/jengo-agency/wp-muplugin-loader/llms.txt

This PHP code snippet provides an example of the generated `mu-require.php` file content. This file is created by the `dumpRequireFile` method during Composer's install or update process and serves as the bootstrap loader for MU plugins managed by the plugin.

```php
<?php
// This method runs automatically during composer install/update
// Generated mu-require.php content example:

/**
 * Plugin Name: MU Plugin Loader
 * Plugin URI: https://github.com/jengo-agency/wp-muplugin-loader
 * Description: MU Plugin Loader - Autoload your mu-plugin directories.
 * Version: 2.0.0
 * Author: Box UK / Luke Woodward
 * Author URI: https://github.com/jengo-agency/wp-muplugin-loader
 *
 * @since 1.1.0
 */
require_once __DIR__ . '/../../vendor/jen-go/wp-muplugin-loader/src/mu-loader.php';

```

--------------------------------

### Composer Configuration for WP MU Plugin Loader

Source: https://github.com/jengo-agency/wp-muplugin-loader/blob/master/README.md

This JSON snippet shows how to include the WP Must-Use Plugin Loader in your project's composer.json file and define installer paths. It ensures that plugins of type 'wordpress-muplugin' are directed to the correct directory.

```json
{
	"require": {
		"composer/installers": "~1.2.0",
		"johnpbloch/wordpress": "*",
		"jen-go/wp-muplugin-loader": "~1.0"
	},
	"extra": {
		"installer-paths": {
			"app/wp-content/themes/{$name}": [
				"type:wordpress-theme"
			],
			"app/wp-content/plugins/{$name}": [
				"type:wordpress-plugin"
			],
			"app/wp-content/mu-plugins/{$name}": [
				"type:wordpress-muplugin"
			]
		},
		"wordpress-install-dir": "app/wp"
	}
}
```

--------------------------------

### PHP: MuLoaderPlugin::overridePluginTypes() Logic

Source: https://context7.com/jengo-agency/wp-muplugin-loader/llms.txt

This PHP code snippet illustrates the internal logic of the `overridePluginTypes` method within the `MuLoaderPlugin` class. It shows how the plugin intercepts package installation events to identify and reclassify standard WordPress plugins as MU plugins based on the `force-mu` configuration in `composer.json`.

```php
<?php
// This method is called automatically by Composer during package installation
// Example internal behavior when rest-api plugin is installed:

use Composer\Installer\PackageEvent;
use LkWdwrd\MuPluginLoader\Composer\MuLoaderPlugin;

$plugin = new MuLoaderPlugin();
// Composer configuration has force-mu: ["rest-api"]

// When wpackagist-plugin/rest-api is installed:
// 1. Package type is checked: "wordpress-plugin"
// 2. Package name "wpackagist-plugin/rest-api" is extracted as "rest-api"
// 3. Matches force-mu array
// 4. Package type is changed to "wordpress-muplugin"
// Result: Plugin installs to mu-plugins/ instead of plugins/

```

--------------------------------

### Composer Configuration for MU Plugin Loading

Source: https://context7.com/jengo-agency/wp-muplugin-loader/llms.txt

This JSON configuration sets up Composer to manage WordPress themes, plugins, and MU plugins, specifically directing MU plugins to the `app/wp-content/mu-plugins/` directory. It also demonstrates how to force specific regular plugins to be treated as MU plugins using the `force-mu` option and specifies the WordPress installation directory.

```json
{
  "require": {
    "composer/installers": "~1.2.0",
    "johnpbloch/wordpress": "*",
    "jen-go/wp-muplugin-loader": "~1.0",
    "wpackagist-plugin/rest-api": "*"
  },
  "extra": {
    "installer-paths": {
      "app/wp-content/themes/{$name}": [
        "type:wordpress-theme"
      ],
      "app/wp-content/plugins/{$name}": [
        "type:wordpress-plugin"
      ],
      "app/wp-content/mu-plugins/{$name}": [
        "type:wordpress-muplugin"
      ]
    },
    "force-mu": [
      "rest-api"
    ],
    "wordpress-install-dir": "app/wp"
  }
}
```

--------------------------------

### Display MU Plugin Loader Rows in Admin

Source: https://context7.com/jengo-agency/wp-muplugin-loader/llms.txt

Renders additional rows in the WordPress admin MU Plugins list table to display subdirectory plugins loaded by the MU Plugin Loader. This function automatically hooks into the 'after_plugin_row_mu-require.php' action and provides an example of its output in the admin panel, indicating loaded plugins with a '+' prefix.

```php
<?php
namespace LkWdwrd\MuPluginLoader\Util;

// Automatically hooked to 'after_plugin_row_mu-require.php' action
// Displays in WordPress Admin > Plugins > Must-Use section

// Example output in admin panel:
// mu-require.php (the loader itself)
// +  REST API - Provides REST API endpoints
// +  Custom Plugin - Custom functionality
// +  Another Plugin - Additional features

// The '+' prefix indicates plugins loaded via the MU Plugin Loader
// Each row shows full plugin metadata (name, description, version, author)

```

--------------------------------

### Filter MU Plugins Loaded - Modify Plugin List

Source: https://context7.com/jengo-agency/wp-muplugin-loader/llms.txt

Apply custom filtering to control which MU plugins are loaded by intercepting the plugin list before initialization. This is achieved by adding a filter to `lkwdwrd_mupluginloader_get_muplugins`. The filter callback receives the array of plugins and can modify it, for example, by unsetting specific plugins or conditionally removing them.

```php
<?php
// Create file: 00-filter-mu-plugins.php in mu-plugins directory
// Named to load alphabetically before mu-require.php

add_filter(
    'lkwdwrd_mupluginloader_get_muplugins',
    function (array $plugins): array {
        // Remove specific plugin from loading
        unset($plugins['example-plugin/plugin.php']);

        // Or conditionally remove based on environment
        if (defined('WP_ENV') && WP_ENV === 'development') {
            unset($plugins['production-only-plugin/plugin.php']);
        }

        return $plugins;
    }
);

// Load the mu loader
require_once 'mu-require.php';

```

--------------------------------

### Define Custom MU Plugin Source Directory

Source: https://context7.com/jengo-agency/wp-muplugin-loader/llms.txt

Allows overriding the default MU plugins directory to load plugins from alternative locations, such as WordPress VIP client MU plugins. This definition should be placed in `wp-config.php` or an environment configuration file before `mu-require.php` is loaded.

```php
<?php
// In wp-config.php or environment configuration file
// Define before mu-require.php loads

define('MU_PLUGIN_LOADER_SRC_DIR', WPCOM_VIP_CLIENT_MU_PLUGIN_DIR . '/');

// Now mu_loader() will scan and load plugins from the custom directory
// Example: /wp-content/client-mu-plugins/ instead of /wp-content/mu-plugins/

```

--------------------------------

### MU Plugins Loaded Action Hook - Execute Code After Loading

Source: https://context7.com/jengo-agency/wp-muplugin-loader/llms.txt

Execute custom code after all MU plugins have been loaded and registered with WordPress by hooking into the `lkwdwrd_mupluginloader_muplugins_loaded` action. This is the appropriate place to interact with functionality provided by the loaded MU plugins.

```php
<?php
// In a theme's functions.php or another plugin

add_action('lkwdwrd_mupluginloader_muplugins_loaded', function() {
    // All MU plugins from subdirectories are now loaded
    // Safe to interact with MU plugin functionality

    if (function_exists('custom_mu_plugin_function')) {
        custom_mu_plugin_function();
    }

    // Log which MU plugins were loaded
    error_log('MU Plugins loaded: ' . print_r(
        \LkWdwrd\MuPluginLoader\Util\get_muplugins(),
        true
    ));
});

```

--------------------------------

### mu_loader() - Load MU Plugins from Subdirectories

Source: https://context7.com/jengo-agency/wp-muplugin-loader/llms.txt

The main loader function that discovers and requires all MU plugin files from subdirectories in the MU plugins folder. It accepts an optional list of plugins, a directory separator, and a custom MU directory. It registers plugin real paths if the function exists and fires an action hook after loading.

```php
<?php
namespace LkWdwrd\MuPluginLoader\Util;

// Automatically called by mu-require.php
// Loads all MU plugins from subdirectories

function mu_loader(
    $plugins = false,
    string $ps = DIRECTORY_SEPARATOR,
    string $mudir = WPMU_PLUGIN_DIR
): void {
    if (!$plugins) {
        $plugins = get_muplugins(ABSPATH, WP_PLUGIN_DIR, $mudir);
    }
    foreach ($plugins as $plugin) {
        if (function_exists('wp_register_plugin_realpath')) {
            wp_register_plugin_realpath($mudir . $ps . $plugin);
        }
        require_once $mudir . $ps . $plugin;
    }
    do_action('lkwdwrd_mupluginloader_muplugins_loaded');
}

// Example output when executed:
// Loads: mu-plugins/plugin-name/plugin-name.php
// Loads: mu-plugins/another-plugin/index.php
// Fires action: lkwdwrd_mupluginloader_muplugins_loaded

```

--------------------------------

### Modifying MU Plugin Source Directory (PHP)

Source: https://github.com/jengo-agency/wp-muplugin-loader/blob/master/README.md

This PHP code snippet shows how to define a custom source directory for MU plugins. By defining the `MU_PLUGIN_LOADER_SRC_DIR` constant, you can direct the loader to a different path, such as 'client-mu-plugins' on WordPress VIP projects.

```php
define('MU_PLUGIN_LOADER_SRC_DIR', WPCOM_VIP_CLIENT_MU_PLUGIN_DIR . '/');
```

--------------------------------

### Enabling Unix Directory Separators in Composer Config

Source: https://context7.com/jengo-agency/wp-muplugin-loader/llms.txt

This JSON configuration enables the use of Unix-style path separators in the generated loader file. This is particularly useful for developers working on Windows environments who are deploying to Linux-based servers, ensuring path compatibility.

```json
{
  "extra": {
    "installer-paths": {
      "app/wp-content/mu-plugins/{$name}": [
        "type:wordpress-muplugin"
      ]
    },
    "force-unix-separator": true
  }
}
```

--------------------------------

### Forcing Unix Directory Separators

Source: https://github.com/jengo-agency/wp-muplugin-loader/blob/master/README.md

This JSON configuration enables the forcing of Unix directory separators. This is useful for development environments on Windows that use a Linux VM for the server, ensuring correct path resolution for the MU loader script.

```json
{
	"extra": {
		"force-unix-separator": true
	}
}
```

--------------------------------

### Filter MU Plugins Loaded (PHP)

Source: https://github.com/jengo-agency/wp-muplugin-loader/blob/master/README.md

This snippet demonstrates how to filter the list of mu-plugins loaded by the mu-plugin-loader. It uses the 'lkwdwrd_mupluginloader_get_muplugins' filter hook to remove specific plugins from the loaded list. The filtering should be applied before the mu-loader is initialized. Dependencies include the wp-muplugin-loader package.

```php
add_filter(
    'lkwdwrd_mupluginloader_get_muplugins',
    function ( array $plugins ):  array {
        unset( $plugins['example/plugin.php'] );
        return $plugins;
    }
);

// Load the mu loader
require_once 'vendor/jen-go/wp-muplugin-loader/src/mu-loader.php';
```

--------------------------------

### get_muplugins() - Retrieve Cached MU Plugin List

Source: https://context7.com/jengo-agency/wp-muplugin-loader/llms.txt

Retrieves a cached list of all valid MU plugin files in subdirectories, excluding root-level files that WordPress loads automatically. It uses the WordPress transients API for caching, with the cache key being an MD5 hash of directory contents. The cache automatically invalidates when files change.

```php
<?php
namespace LkWdwrd\MuPluginLoader\Util;

// Called internally by mu_loader()
// Returns array of plugin paths relative to mu-plugins directory

$plugins = get_muplugins(
    ABSPATH,
    WP_PLUGIN_DIR,
    WPMU_PLUGIN_DIR,
    DIRECTORY_SEPARATOR
);

// Example return value:
// [
//     'rest-api/plugin.php',
//     'custom-plugin/index.php',
//     'another-plugin/another-plugin.php'
// ]

// Uses WordPress transients API for caching
// Cache key is MD5 hash of directory contents
// Automatically invalidates when files change

```

--------------------------------

### Forcing Plugins to MU Status

Source: https://github.com/jengo-agency/wp-muplugin-loader/blob/master/README.md

This JSON configuration shows how to force regular WordPress plugins to be treated as Must-Use plugins. The 'force-mu' key in the 'extra' section takes an array of plugin slugs to be moved to the MU plugins directory.

```json
{
	"require": {
		"johnpbloch/wordpress": "*",
		"jen-go/wp-muplugin-loader": "~1.0",
		"wpackagist-plugin/rest-api": "*"
	},
	"extra": {
		"force-mu": [
			"rest-api"
		],
		"installer-paths": {
			"app/wp-content/themes/{$name}": [
				"type:wordpress-theme"
			],
			"app/wp-content/plugins/{$name}": [
				"type:wordpress-plugin"
			],
			"app/wp-content/mu-plugins/{$name}": [
				"type:wordpress-muplugin"
			]
		},
		"wordpress-install-dir": "app/wp"
	}
}
```

--------------------------------

### rel_path() - Calculate Relative Path

Source: https://context7.com/jengo-agency/wp-muplugin-loader/llms.txt

Calculates the relative path between two absolute paths, which is useful for generating portable require statements. This utility function is used internally by the loader to determine paths relative to the MU plugins directory.

```php
<?php
namespace LkWdwrd\MuPluginLoader\Util;

// Used internally to generate loader paths
$from = '/var/www/html/wp-content/mu-plugins';
$to = '/var/www/html/vendor/jen-go/wp-muplugin-loader/src/mu-loader.php';

$relative = rel_path($from, $to, DIRECTORY_SEPARATOR);
// Returns: ../../vendor/jen-go/wp-muplugin-loader/src/mu-loader.php

// With custom separator for cross-platform compatibility
$relative_unix = rel_path($from, $to, '/');
// Returns: ../../vendor/jen-go/wp-muplugin-loader/src/mu-loader.php

```

--------------------------------

### Customizing MU Require Filename in Composer

Source: https://context7.com/jengo-agency/wp-muplugin-loader/llms.txt

This JSON configuration shows how to customize the name of the generated MU plugin loader file by setting the `mu-require-file` option within Composer's `extra` configuration. It also illustrates how to completely disable the automatic generation of this file by setting `mu-require-file` to `false`.

```json
{
  "extra": {
    "installer-paths": {
      "app/wp-content/mu-plugins/{$name}": [
        "type:wordpress-muplugin"
      ]
    },
    "mu-require-file": "custom-mu-require-filename.php"
  }
}
```

```json
{
  "extra": {
    "mu-require-file": false
  }
}
```

--------------------------------

### Customizing MU Require File Name

Source: https://github.com/jengo-agency/wp-muplugin-loader/blob/master/README.md

This JSON configuration demonstrates how to customize the name of the generated MU plugin loader file (`mu-require.php`) or disable its generation entirely. This is done via the 'mu-require-file' key within the 'extra' section of composer.json.

```json
{
	"extra": {
		"installer-paths": {
			"app/wp-content/mu-plugins/{$name}": [
				"type:wordpress-muplugin"
			]
		},
		"mu-require-file": "custom-mu-require-filename.php"
	}
}
```

```json
{
	"extra": {
		"installer-paths": {
			"app/wp-content/mu-plugins/{$name}": [
				"type:wordpress-muplugin"
			]
		},
		"mu-require-file": false
	}
}
```

--------------------------------

### plugins_url() Filter - Correct Asset URLs for Symlinked MU Plugins

Source: https://context7.com/jengo-agency/wp-muplugin-loader/llms.txt

This filter callback automatically corrects asset URLs when MU plugins are symlinked into the mu-plugins directory. It ensures that resources like CSS and JavaScript are served from the correct path, preventing 404 errors that can occur with default WordPress URL generation for symlinked files.

```php
<?php
namespace LkWdwrd\MuPluginLoader\Util;

// Automatically hooked into WordPress 'plugins_url' filter
// Fixes URLs when plugins are symlinked into mu-plugins directory

// Example scenario:
// Plugin file: /mu-plugins/my-plugin/assets/style.css (symlink to /vendor/...)
// Without filter: https://example.com/wp-content/plugins/my-plugin/assets/style.css (404)
// With filter:    https://example.com/wp-content/mu-plugins/my-plugin/assets/style.css (200)

// In plugin code:
$url = plugins_url('assets/style.css', __FILE__);
// Filter automatically corrects path if plugin is in mu-plugins via symlink

```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.