Download the PHP package amcgowanca/composer-patches-drupal-patching without Composer

On this page you can find all versions of the php package amcgowanca/composer-patches-drupal-patching. 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 composer-patches-drupal-patching

Patching Drupal 8 core with cweagans/composer-patches

This package provides a work-around for the issue in which Drupal 8 core package patches, applied through the use of cweagans/composer-patches, does not correctly apply patches to Drupal core itself. Instead, a common symptom of incorrectly applied patches is the creation of the directories: docroot/core/b/ or docroot/core/core. This appears to be the result of a composer.json's specification of the drupal/core project's installation path being docroot/core. This is commonly seen in Acquia BLT (and potentially Acquia Lightning) based projects.

This Composer Plugin provides a mechanism to resolve the issue so that patches defined in a composer.json for Drupal core can be applied to docroot vs. docroot/core through modification of the installation path at time of pre-patch apply events that are fired through cweagans/composer-patches plugin. However, this ultimately warrants modifications to the Composer Patches project to allow for the modification of the $install_path value which can be seen through the changes outlined here.

Usage

Related issues & resources

The following is a collection of high-level issues and resources related to the core problem that this plugin (and the modified cweagans/composer-patches) helps address:

Example repository

An example repository has been put together to contain an example of a clean Acquia BLT project setup in which the error that this Composer Plugin aims to resolve, in addition to an example in which the problem at hand is in fact solved. More information can be found at amcgowanca/composer-patches-drupal-patching-proof.

All versions of composer-patches-drupal-patching with dependencies

PHP Build Version
Package Version
Requires php Version >=5.6.0
composer-plugin-api Version ^1.0
cweagans/composer-patches Version 1.x-dev
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 amcgowanca/composer-patches-drupal-patching contains the following files

Loading the files please wait ....