Download the PHP package ojohnny/wp-fallback-plugins-dir without Composer

On this page you can find all versions of the php package ojohnny/wp-fallback-plugins-dir. 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 ojohnny/wp-fallback-plugins-dir

Informations about the package wp-fallback-plugins-dir

wp-fallback-plugins-dir

Load all WordPress plugins in a specified directory, unless they are loaded elsewhere.

Why?

Look, I'm not saying that you should bundle other plugins with your theme/plugin, but if your deployment process only handles theme deployment rather than a full WordPress deployment then you could give it a try.

  1. Users can't disable the bundled plugins. They can still install another version of the same plugin and load it instead, which may be useful in case of security updates after the theme is no longer being developed.
  2. The fallback plugins are still visible in the Admin interface. This can help future developers (including your future self) figure out what is going on.
  3. If a user would install some incompatible plugin, the first action can now be to bulk-deactivate all plugins. The bundled plugins are still active after this operation, so it should not break vital site functionality.
  4. Reduce the amount of clicking around in admin panels after deploys or when setting up a new development environments.

Installation

Using composer:

Usage

Assuming you are using composer and have installed composer/installers and a couple of WordPress plugins (possibly from wpackagist), then your functions.php could look something like this:

If you want to use this inside a plugin, perhaps it is better to do this inside an appropriate add_action(), such as plugins_loaded.

All versions of wp-fallback-plugins-dir with dependencies

PHP Build Version
Package Version
Requires php Version >=7.4
matthiasmullie/path-converter Version ~1.0
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 ojohnny/wp-fallback-plugins-dir contains the following files

Loading the files please wait ....