composer – Drush Site-install – Drupal Answers

I am having an issue on a new mac on Terminal that works with Composer and Drush that is fine. However when I’m on the /david/Sites/animals I go to the Terminal and I’m unable to make the “drush site-install” work.

For example

drush site-install --db-url=mysql://david:root@localhost:3306/animals

I get the following Terminal

In SiteInstallCommands.php line 152:
                                                                                                                                                                      
Drush was unable to drop all tables because `mysql` was not found, and therefore Drupal threw an AlreadyInstalledException. Ensure `mysql` is available in your PATH. 

Am I somehow not typing this correctly.
It is also running MAMP.

Thanks.

8 – How can you have Composer install the site in the project root not in web/?

If the server you are using uses public_html as document root, and not web as drupal/recommended-project expects, you need to follow what reported in Using Composer to Install Drupal and Manage Dependencies.

If you want to modify some of the properties of the downloaded composer.json before composer install is executed, use the --no-install flag when running composer create-project. For example, it is possible that you want to rename the subdirectory ‘web’ to something else.

To do that:

  1. Run composer create-project drupal/recommended-project my_site_name_dir --no-interaction --no-install
  2. Change directories to my_site_name_dir and edit the composer.json file to suit your needs
  3. Run composer install to download Drupal 8 and all its dependencies.

magento2 – Problem when install any thing using composer in magento 2.4.1

am trying to install any module using composer v.1 and v.2 but I get this error all the time

 Problem 1
    - The requested package laminas/laminas-servicemanager (locked at 2.7.11, required as ^3.6) is satisfiable by laminas/laminas-servicemanager(2.7.11) but these conflict with your requirements or minimum-stability.
  Problem 2
    - magento/magento2-base 2.4.1 requires laminas/laminas-servicemanager ^2.7.8 -> satisfiable by laminas/laminas-servicemanager(2.7.10, 2.7.11, 2.7.8, 2.7.9) but these conflict with your requirements or minimum-stability.
    - magento/magento2-base 2.4.1 requires laminas/laminas-servicemanager ^2.7.8 -> satisfiable by laminas/laminas-servicemanager(2.7.10, 2.7.11, 2.7.8, 2.7.9) but these conflict with your requirements or minimum-stability.
    - magento/magento2-base 2.4.1 requires laminas/laminas-servicemanager ^2.7.8 -> satisfiable by laminas/laminas-servicemanager(2.7.10, 2.7.11, 2.7.8, 2.7.9) but these conflict with your requirements or minimum-stability.
    - magento/magento2-base 2.4.1 requires laminas/laminas-servicemanager ^2.7.8 -> satisfiable by laminas/laminas-servicemanager(2.7.10, 2.7.11, 2.7.8, 2.7.9) but these conflict with your requirements or minimum-stability.
    - Installation request for magento/magento2-base (locked at 2.4.1) -> satisfiable by magento/magento2-base(2.4.1).


Installation failed, reverting ./composer.json to its original content.

composer – upgrade_status – unexpected error about PHP version

I’m doing preparatory work for upgrading a site from D8 to D9…

The Drupal dev site (macOS 10.14.6 served with Laravel Vagrant) is running PHP 7.3.28, both on command line and php-fpm, and I’m seeing the correct version with php –version and at /admin/reports/status

And yet, whenever I scan my custom modules via the upgrade_status UI, I consistently get:

PHPStan command failed:

/Users/wt/Sites/sitename/vendor/bin/phpstan analyse --error-format=json -c /tmp/upgrade_status/deprecation_testing.neon /Users/wt/Sites/sitename/web/modules/custom/snape 2> /tmp/upgrade_status/phpstan_error_output

Command output:

Empty.

Command error:

Fatal error: Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 7.3.0". You are running 7.1.33. in /Users/wt/Sites/sitename/vendor/composer/platform_check.php on line 24

If I run phpstan manually using the first command, it works (though annoyingly the JSON output is truncated).

I’ve been going through this question as well, but aside from disabling the version check completely – I’d prefer to fix it – nothing works.

I’ve installed drupal/core-dev and phpunit.

Composer memory limit error on update ( AWS Lightsail)

I’m running an AWS lightsail server for a Drupal 8 qa site. I’m getting an out of memory error when running update. I created a new server with 2GB of memory, and was able to run updates for a few weeks, now I’m getting this:

Fatal error: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 4096 bytes) in phar:///opt/bitnami/php/bin/composer.phar/src/Composer/DependencyResolver/RuleWatchGraph.php on line 52

I set the env var COMPOSER_MEMORY_LIMIT=-1, didn’t help.

The only major change I made since the last time it worked was using display suite for one content type, but ds had already been enabled previously. Seems like 2GB should be plenty, any suggestions on what to try?

8 – How can we just apply the updates to a single module using composer without apply patches for other modules?

We have the following composer.json file. When we want to update a module such as Environment Indicator, we run the suggested composer command composer require drupal/environment_indicator:^3.7'.

In doing so it also applies the patches for core and other modules because the patches is defined in our composer.json file.

What we tried this as well but it had the same results.

composer update drupal/environment_indicator --with-dependencies

composer.json

{
    "name": "drupal/drupal",
    "description": "Drupal is an open source content management platform powering millions of websites and applications.",
    "type": "project",
    "license": "GPL-2.0-or-later",
    "require": {
        "composer/installers": "^1.0.24",
        "drupal/core" : "^8.6",
        "wikimedia/composer-merge-plugin": "^1.4"
    },
    "minimum-stability": "dev",
    "prefer-stable": true,
    "config": {
        "preferred-install": "dist",
        "autoloader-suffix": "Drupal8"
    },
    "extra": {
        "_readme": [
            "By default Drupal loads the autoloader from ./vendor/autoload.php.",
            "To change the autoloader you can edit ./autoload.php.",
            "This file specifies the packages.drupal.org repository.",
            "You can read more about this composer repository at:",
            "https://www.drupal.org/node/2718229"
        ],
        "merge-plugin": {
            "include": [
                "core/composer.json"
            ],
            "recurse": true,
            "replace": false,
            "merge-extra": false
        },
        "installer-paths": {
            "core": ["type:drupal-core"],
            "modules/contrib/{$name}": ["type:drupal-module"],
            "profiles/contrib/{$name}": ["type:drupal-profile"],
            "themes/contrib/{$name}": ["type:drupal-theme"],
            "drush/contrib/{$name}": ["type:drupal-drush"],
            "modules/custom/{$name}": ["type:drupal-custom-module"],
            "themes/custom/{$name}": ["type:drupal-custom-theme"]
        },
        "enable-patching": true,
        "patches" : {
            "drupal/core": {
               "issuenumber1" : "path/to/patch.patch",
             }, 
            "drupal/eck": {
               "issuenumber2" : "path/to/patch.patch",
             },
        }
    },
}

All In One Addons for WPBakery Page Builder (formerly Visual Composer)

Admin submitted a new resource:

All In One Addons for WPBakery Page Builder (formerly Visual Composer) – All In One Addons for WPBakery Page Builder (formerly Visual Composer)

View attachment 14361

Included:

Timeline Card…

Read more

.(tagsToTranslate)nulled(t)nulled sites(t)nulled forum(t)nulled script(t)nulled scripts(t)nulled script forum(t)best nulled scripts site(t)xenforo nulled(t)xenforo 2 nulled(t)xenforo nulled themes(t)seo xenforo 2(t)xenforo themes(t)seo for xenforo(t)vbulletin nulled(t)vbulletin 5 nulled(t)whmcs nulled(t)hexa whmcs(t)whmcs addons nulled(t)whmcs templates nulled(t)whmcs template nulled(t)whmcs modules nulled(t)whmcs themes nulled(t)cs-cart nulled(t)xfilesharing pro nulled(t)blesta nulled(t)arrowchat nulled(t)multi vendor ecommerce script nulled(t)seo providers(t)adsense alternative

updating – Composer Updates Drupal to Beta Version

I’m trying to update Drupal from 9.1.8 to 9.1.9. However, running a composer update jumps to 9.2-beta2. I’m not sure how to fix it so that it sticks to the recommended version.

My composer.json has this…

"drupal/core-composer-scaffold": "^9.1.0",
"drupal/core-project-message": "^9.1.0",
"drupal/core-recommended": "^9.1.0",

enter image description here

How can I prevent my sites from updating past 9.1.x? It used to be a bit simpler with drupal/core but I know that’s not the recommended package to use anymore.

magento2 – Magento 2 EE: Running composer update is giving error

I am trying to run composer update and want to push the changes to magento cloud but is giving the following error:

Problem 1

  • magento/product-enterprise-edition 2.3.4 requires ext-bcmath * -> the requested PHP extension bcmath is missing from your system.
  • magento/product-enterprise-edition 2.3.4 requires ext-bcmath * -> the requested PHP extension bcmath is missing from your system.
  • Installation request for magento/product-enterprise-edition 2.3.4 -> satisfiable by magento/product-enterprise-edition[2.3.4].

Maybe because it is conflicting with my local PHP environment?
I am running the command outside the docker container. Is it necessary to run the commands inside a docker container?