Download the PHP package proudcommerce/oxid-console-moduleactivator without Composer

On this page you can find all versions of the php package proudcommerce/oxid-console-moduleactivator. 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?

Informations about the package oxid-console-moduleactivator

OXID Console Moduleactivator

Custom command for the OXID console.

Installation

composer require proudcommerce/oxid-console-moduleactivator

Commands

pc:module:activator

vendor/bin/oe-console pc:module:activator [-s|--skipDeactivation] [-d|--clearModuleData] [--] <yaml-file>

vendor/bin/oe-console pc:module:activator -s ../modules.yml

YML file

Supports either a "whitelist" or a "blacklist" entry with multiple shop ids and the desired module ids to activate (whitelist) or to exclude from activation (blacklist).

If you want, you can also specify a YAML string on the command line instead of a file, e.g.:

Module priorities

With "priorities", you can define the order (per subshop) in which the modules will be activated. You can defined priorities per subshop, see example above.

Installing modules prior to activation

By specifying an "installations" array, you can make sure that the modules are really "installed" in the shop (modules can be installed via Composer or by calling e.g. vendor/bin/oe-console oe:module:install-configuration source/modules/oxcom/ocbcleartmp). If a module of that list is not yet installed, oe:module:install-configuration will be called (please note that you still have to add the Composer namespace for autoloading in the main composer.json e.g.). So this is an "edge-case", if you add e.g. custom project specific modules directly into the "source/modules/" folder and add them manually to the main composer.json (so you don't need to have a separate Composer repository for each module):

A better alternative might be to use the "wikimedia/composer-merge-plugin" plugin, so that your module's composer.json will be used directly.

Arguments

yaml:

Options:

skipDeactivation:

clearModuleData:

All versions of oxid-console-moduleactivator with dependencies

PHP Build Version
Package Version
Requires php Version >=7.1
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 proudcommerce/oxid-console-moduleactivator contains the following files

Loading the files please wait ....