Download the PHP package tivwp/tivwp-force-deactivate-plugins without Composer
On this page you can find all versions of the php package tivwp/tivwp-force-deactivate-plugins. 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:
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.
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?
Informations about the package tivwp-force-deactivate-plugins
TIVWP\Force Deactivate Plugins
Automatically disables plugins on production server.
If the WP_LOCAL_DEV define is NOT true, disables plugins that you specify.
This is the reverse logic of the CWS_Disable_Plugins_When_Local_Dev by Mark Jaquith (@markjaquith).
To install
-
Make sure you have the following settings in your project's
composer.json: -
Run this in your project's root folder:
- The plugin files will be installed in the
path/to/mu-plugins/tivwp-force-deactivate-pluginsfolder. However, WordPress ignores subfolders in themu-plugins. Therefore, you need to copy thetivwp-force-deactivate-plugins.phpone level up, to themu-plugins.
Settings
-
Put this to a local config file (excluded from the repo):
- and this - to the
wp-config.php(edit, of course):
Author
- Gregory Karpinsky (@tivnet)
License
GPL-3.0
All versions of tivwp-force-deactivate-plugins with dependencies
PHP Build Version
Package Version
The package tivwp/tivwp-force-deactivate-plugins contains the following files
Loading the files please wait ...