Download the PHP package level-level/ll-plugin-autoloader without Composer

On this page you can find all versions of the php package level-level/ll-plugin-autoloader. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of level-level/ll-plugin-autoloader

Informations about the package ll-plugin-autoloader

Level Level plugin autoloader

When 0-loader.php is inserted into the mu-plugins directory it will load all subdirectory plugin as it would normal plugins.

Configuration options

You have multiple options to manipulate where the Plugin Loader will look for a vendor folder. Define one of the following values in wp-config:

1. Default == wp-content directory

If you define nothing it will load the same as 2. wp-content directory.

2. wp-content directory

Load from the parent directory above mu-plugins (should be the wp-content dir). This is only used when no LL_AUTOLOAD_DIR is set.

3. Child theme

Use the current Child theme via get_stylesheet_directory as the theme folder containing the vendor folder. This is only used when no LL_AUTOLOAD_DIR is set.

4. Parent/default theme

Use the current parent theme via get_template_directory as the theme folder containing the vendor folder. This is only used when no LL_AUTOLOAD_DIR is set.

5. Custom path

Use a specific directory. The script will still append /vendor/autoload.php to this path.

Overview

Setting Result
Nothing wp-content directory
define( 'LL_AUTOLOAD_DIR', '/tmp/' ); /tmp/
define( 'LL_AUTOLOAD_CONTENT_DIR', true ); wp-content directory
define( 'LL_AUTOLOAD_USE_CHILD', true ); Stylesheet directory (child theme)
define( 'LL_AUTOLOAD_USE_PARENT', true ); Template directory (parent theme)

Pre and Post autoload

Pre autoload

Right before the vendor autoload file is loaded, the pre-autoload.php file in the directory specified as the autoload directory is required if it exists.

This file can be used to set environment variables required in composer loaded dependencies.

Post autoload

Right after the vendor autoload file is loaded, but before the mu-plugins are loaded, the post-autoload.php file in the directory specified as the autoload directory is required if it exists.

This file can be used to bootstrap/configure mu-plugin loaded dependencies, or trigger actions that need to happen as early as possible, but autoloading to be set up.

Adding logging is an example of this. You probably require the Monolog composer dependency, but want it to be bootstrapped before we load the mu-plugins.

Force load normal plugins

In some cases, loading a plugin as must-use plugin can cause issues with the plugin. Instead, you have the option to force load plugins like normal plugins.

In the path where also your vendor folder is, create a file called ll-forced-plugins.json. Inside, paste the following content.

The slug references the plugin file to load. Network determines if a plugin should be network activated if it's a multisite installation.

Please note these force activated plugins will only be activated when visiting the WP-admin. This is needed because some plugins want to perform actions like redirects directly after activation.

Upgrading from v2.x to v3.x

In v3, the wp-content directory loads by default, instead of the template directory in v2. To restore behaviour, set define( 'LL_AUTOLOAD_USE_PARENT', true ); in wp-config.php.

All versions of ll-plugin-autoloader with dependencies

PHP Build Version
Package Version
No informations.
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package level-level/ll-plugin-autoloader contains the following files

Loading the files please wait ....