PHPackages                             thefrosty/wordpress-mu-loader - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. thefrosty/wordpress-mu-loader

ActiveWordpress-muplugin[Utility & Helpers](/categories/utility)

thefrosty/wordpress-mu-loader
=============================

Loads regular plugins from the plugins directory as must-use plugins, enforcing their activity while maintaining the typical update flow.

1.2.1(4mo ago)35.4k[1 PRs](https://github.com/thefrosty/wordpress-mu-loader/pulls)GPL-2.0+PHPPHP ^8.0CI passing

Since Jul 4Pushed 2mo ago1 watchersCompare

[ Source](https://github.com/thefrosty/wordpress-mu-loader)[ Packagist](https://packagist.org/packages/thefrosty/wordpress-mu-loader)[ Docs](https://github.com/thefrosty/wordpress-mu-loader)[ RSS](/packages/thefrosty-wordpress-mu-loader/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (5)Dependencies (7)Versions (9)Used By (0)

WP Plugin MU Loader
===================

[](#wp-plugin-mu-loader)

Installation
------------

[](#installation)

```
composer require thefrosty/wordpress-mu-loader:^1.1
```

Loads regular plugins from the plugins' directory as "must-use plugins", enforcing their activity while maintaining the typical update flow. This file will take care of all necessary logic, including preventing activation/deactivation/deletion of those plugins as regular plugins.

#### Benefits

[](#benefits)

- Enforce plugins to be active throughout the entire installation.
- Continue receiving automated update notifications.
- Be able to comfortably update those plugins from the WordPress dashboard.
- The plugin activation, deactivation, and uninstallation routines are executed as usual.

#### Requirements

[](#requirements)

- WordPress >= 6.3
- PHP >= 8.0

#### Usage

[](#usage)

- You can then pass basenames of the plugins you would like to load as MU plugins to the constructor call in the `wp_plugin_mu_loader()` function, as an array.
- A plugin basename consists of the plugin directory name, a trailing slash, and the plugin main file name, for example wordpress-seo/wp-seo.php, jetpack/jetpack.php, or woocommerce/woocommerce.php.
- Alternatively, if you don't want to tweak the code of the function itself, you can also access the loader from the outside: Retrieve the instance via wp\_plugin\_mu\_loader() and then call its load\_plugin() method, passing a single plugin basename string to it.

#### Example

[](#example)

```
wp_plugin_mu_loader()->loadPlugin( 'custom-login/custom-login.php' );
```

OR, create a git managed mu-plugin:

```