Can you use Drush 9 without a compositor?

I have a Drupal 7 site that was not built with the composer. I've been using Drush 7 with him, but a week ago, wd-show –tail stopped working, I do not get any results. I installed Drush 9, but I have difficulty configuring it.

I created an xml file, according to the example, the instructions say that you have to put an alias in $ PROJECT / drush / sites / self.site.yml but I do not have a project root with composer.json —- I can send this a Work without using composer to build my site? Or is it drush 9 depending on the drupal site using the composer?

I am running the local version of the site in MAMP on my Mac. I created sites / drush / sites / self.site.yml – contains:
local:
root: / Users / pglatz / dev / wdocs / wdocs-code / www
uri: & # 39; https: //www.whiskerdocs-local-qa.pglatz.com/ & # 39;

The command that I am using is:
drush9 @local –alias-path = / Users / pglatz / dev / wdocs / wdocs-code / www / sites / drush / sites –root = / Users / pglatz / dev / wdocs / wdocs-code / www

When I execute it, I get the error:
The wd-show command was not found. Pass –root or an @siteAlias ​​to execute specific Drupal commands.

But I'm passing –root and a site alias. Probably a silly syntax error on my part, but I can not solve it. Thanks for your help.

compositor: do not you re-apply the patches when you need a new module?

I still find the problem that, when a new module with compositor is required, the existing packages are deleted and reinstalled if they have patches defined in composer.json. For example,

λ lando composer requires drupal / media_entity_browser
1/2: https://packages.drupal.org/8/drupal/provider-2019-2$bae9fca7243956d61e44a716bdfb5c872f0f3e1a0b48b1dccfcae53d7e59c86f.json
2/2: https://packages.drupal.org/8/drupal/provider-2019-1$25356ca628b704d49a0ea504e6374f921a2b54d845d142aae1708cb94088516f.json
Finished: success: 2, omitted: 0, fails: 0, total: 2
1/2: http://repo.packagist.org/p/provider-latest$56447e2294826167894155c32ceb596c58b3b2af059facd78694060f8a4d8c1c.json
2/2: http://repo.packagist.org/p/provider-2019-04$a612146345a708aa360ee61a695dd52d8d0faa79e136de5e075c95860af7c956.json
Finished: success: 2, omitted: 0, fails: 0, total: 2
Using the version ^1.0@beta for drupal / media_entity_browser
./composer.json has been updated
Compilation of patches for the root package.
Removing the drupal / core package so it can be reinstalled and patched again.
- Removing drupal / core (8.7.3)
Removing web / core - deleted
> DrupalProject  composer  ScriptHandler :: checkComposerVersion
Loading compositor repositories with package information
Updating dependencies (including require-dev)
1/4: https://ftp.drupal.org/files/projects/media_entity-8.x-1.8.zip
2/4: https://ftp.drupal.org/files/projects/entity-8.x-1.0-rc3.zip
3/4: https://ftp.drupal.org/files/projects/entity_browser-8.x-2.1.zip
4/4: https://ftp.drupal.org/files/projects/media_entity_browser-8.x-1.0-beta3.zip
Finished: success: 4, omitted: 0, fails: 0, total: 4
Package operations: 5 installations, 0 updates, 0 deletions
Compilation of patches for the root package.
Compilation of patches for dependencies. This could take a minute

For something like drupal / core, this is really a problem in my local, since it takes a while to download and reinstall the package. It seems that I can not find a pattern. Sometimes it seems that the repatched package is a requirement of the required, other times they are not related or no package has been sent again.

Has anyone else found this? Is there any way to avoid it? Ideally, we would only re-apply the patches to a package when it is updated.

Magento 2. How can I correctly extend the provider / compositor / installed .json?

  • I assume that installed.json It contains all the necessary dependencies for Magento.
  • How can I extend properly seller / compositor / installed.json?

Context:

  • Magento has a hard dependence on one of the libraries, more specifically a specific version of a third party msp / recaptcha module: 2.0.2. I want to update it to 2.1.2.
  • Now, if it were a softer dependency (~ 2.0.2) it could have done it from composer.json as described in the answer to this question

At this point, it should be clear what I need to achieve and why. Please ask for more details if necessary. Thank you.

compositor – Fatal error: Error not detected: class not found & # 39; Cm_Cache_Backend_File & # 39;

Going through an update from 2.2.6 to 2.3.1 and I have this population in the interface.

Also, on the command line, if I try to run an update or almost anything, even php bin / magento list I throw this error:

Fatal error: error not detected: the class & # 39; Zend  ModuleManager  Listener  ListenerOptions & # 39; it is not found in /srv/public_html/vendor/zendframework/zend-mvc/src/Service/ModuleManagerFactory.php:41
Battery tracking:
# 0 /srv/public_html/vendor/zendframework/zend-servicemanager/src/ServiceManager.php(747): Zend  Mvc  Service  ModuleManagerFactory -> __ invoke (Object (Zend  ServiceManager  ServiceManager), & # 39; ModuleManager & # 39 ;, NULL)
# 1 /srv/public_html/vendor/zendframework/zend-servicemanager/src/ServiceManager.php(195): Zend  ServiceManager  ServiceManager-> doCreate (& # 39; ModuleManager & # 39;)
# 2 /srv/public_html/setup/src/Magento/Setup/Application.php(35): Zend  ServiceManager  ServiceManager-> get (& # 39; ModuleManager & # 39;)
# 3 /srv/public_html/vendor/magento/framework/Console/Cli.php(71): Magento  Setup  Application-> bootstrap (Array)
# 4 / srv / public_html / bin / magento (22): Magento  Framework  Console  Cli -> __ construct (& # 39; Magento CLI & # 39;)
# 5 {main}
released in /srv/public_html/vendor/zendframework/zend-mvc/src/Service/ModuleManagerFactory.php on line 41

I'm desperate here, I feel like I've tried everything.

compositor – How to distribute / share a project / product of drupal 8?

I have a site that I have built with Drupal 8, using compositor and git to manage the base code. It's a pretty simple site that includes a handful of contrib modules, some custom views and a custom theme.

I'm thinking about the best way to share this site as an open solution for others who want to use it for themselves.

Should I consider an installation profile? distribution? How about just a git repository?

Is there any reason why I can not share my drupal project 8 simply by sharing my exporter composer.json and config?

Magento2: How to install an external package without a compositor?

I have some packages installed under seller dir.
Now, I need a way to get one of them out and place it in another place that allows editing the files (like moving a Magento module to application / code, but in this case it is an external library and not a Magento module).
I tried to place it under lib & under lib / internal + some other similar variations, but nothing seems to work and I get a Class ... does not exist error when I use classes from this library.
– Any idea how to make it work (without changing files or other files)?

8 – Change of module from manual to installed compositor

Note: This is not a duplicate of The site has a combination of manually installed modules and through Composer: Can I move all of them to Composer?
As this question below involves different folder locations.

I currently have modules installed through the Drupal user interface (/ admin / modules / install) that have been installed in the / modules directory.

And I also have composer modules installed that are added to the / modules / contrib directory

Homework: To move the modules to Composer.

I have run "composer require drupal / MODULE" that has put the module in the / modules / contrib location. But now there are 2 copies and, when updating and clearing the cache, Drupal is still using the location of the previous module. (I can say that the module installed by the composer is a newer version)

I would prefer not to have to uninstall all the modules that need to be moved, as it can cause problems.

I have tried to simply remove the module from the directory / modules (leaving the new composition module installed in modules / contrib), but I get the WSOD.

Question: How do I change the modules to managed Composer with a different directory location?

patches: the patch can not be applied using the compositor in Drupal core 8.6.4

I can not apply the patch using the composer in Drupal core 8.6.4. Can anyone help me apply the patch using the composer?
Here is the process of what I am doing:

{
"name": "drupal / drupal",
"description": "Drupal is an open source content management platform that powers millions of websites and applications."
"type": "project",
"license": "GPL-2.0 or later",
"demand": {
"compositor / installers": "^ 1.0.24",
"wikimedia / composer-merge-plugin": "^ 1.4",
"drupal / admin_toolbar": "^ 1.25",
"drupal / config_ignore": "^ 2.1",
"drupal / config_split": "^ 1.4",
"drupal / devel": "^ 1.2",
"Drupal / sections": "^ 1.5",
"drupal / pathauto": "^ 1.3",
"drupal / s3fs": "^ 3.0-alpha13",
"drupal / field_group": "^ 3.0-beta1",
"drush / drush": "^ 9.4",
"drupal / backup_migrate": "^ 4.0",
"drupal / restui": "^ 1.16",
"drupal / conditional_fields": "^ 1.0-alpha4",
"drupal / ckeditor_font": "^ 1.0",
"drupal / colorbutton": "^ 1.1",
"library-ckeditor / panelbutton": "^ 4.11",
"library-ckeditor / colorbutton": "4.11.1",
"drupal / migrate_plus": "^ 4.1",
"drupal / migrate_tools": "^ 4.1",
"drupal / migrate_source_csv": "^ 2.2",
"drupal / migrate_file": "^ 1.1",
"drupal / taxonomy_import": "^ 1.0",
"drupal / metatag": "^ 1.7",
"predis / predis": "^ 1.1.1",
"drupal / rabbitmq": "^ 1.1",
"php-amqplib / rabbitmq-bundle": "^ 1.14",
"drupal / ultimate_cron": "^ 2.0-alpha4",
"cweagans / composer-patches": "~ 1.0"
}
"require-dev": {
"asm89 / twig-lint": "^ 1.0",
"dealerdirect / phpcodesniffer-composer-installer": "^ 0.5.0",
"drupal / coder": "^ 8.2.12"
}
"replace": {
"drupal / core": "^ 8.6"
}
"minimum stability": "dev",
"I 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.c/node/2718229"
    ],
"merge-plugin": {
"include": [
            "core/composer.json"
        ],
"recurse": true,
"replace": false,
"merge-extra": false
}
"installation routes": {
"nucleus": ["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 patches": true,
"patches": {
"drupal / core": {
"Search autocomplete from the result of the views": "https://www.drupal.org/files/issues/2019-01-10/2174633-238.patch"
}
}
}
"automatic loading": {
"psr-4": {
"Drupal \ Core \ Composer \": "core / lib / Drupal / Core / Composer"
}
}
"scripts": {
"pre-autoload-dump": "Drupal \ Core \ Composer \ Composer :: preAutoloadDump",
"post-autoload-dump": "Drupal \ Core \ Composer \ Composer :: secureHtaccess",
"post-package-install": "Drupal \ Core \ Composer \ Composer :: vendorTestCodeCleanup",
"post-package-update": "Drupal \ Core \ Composer \ Composer :: vendorTestCodeCleanup",
"drupal-phpunit-upgrade-check": "Drupal \ Core \ Composer \ Composer :: upgradePHPUnit",
"drupal-phpunit-upgrade": "@composer update phpunit / phpunit phpspec / prophecy symfony / yaml --with-dependencies --no-progress",
"phpcs": "phpcs --standard = core / phpcs.xml.dist --runtime-set installed_paths $ ($ COMPOSER_BINARY vendor-dir config) / drupal / coder / coder_sniffer -",
"phpcbf": "phpcbf --standard = core / phpcs.xml.dist --runtime-set install_paths $ ($ COMPOSER_BINARY config vendor-dir) / drupal / coder / coder_sniffer -"
}
"repositories": [
    {
        "type": "composer",
        "url": "https://packages.drupal.org/8"
    },
    {
        "type": "package",
        "package": {
            "name": "library-ckeditor/panelbutton",
            "version": "4.11.1",
            "type": "drupal-library",
            "dist": {
                "url": "https://download.ckeditor.com/panelbutton/releases/panelbutton_4.11.1.zip",
                "type": "zip"
            }
        }
    },
    {
        "type": "package",
        "package": {
            "name": "library-ckeditor/colorbutton",
            "version": "4.11.1",
            "type": "drupal-library",
            "dist": {
                "url": "https://download.ckeditor.com/colorbutton/releases/colorbutton_4.11.1.zip",
                "type": "zip"
            }
        }
    }
]

}

Command: installation of the composer, but nothing happens.

Thanks in advance.

compositor: NGINX 404 error even though the Magento installation was completed in the CentOS 7 terminal

Using my customized version of this command:

bin / magento configuration: install 

I want to be able to use the Magento administration panel as described in my CentOS 7 terminal window.

[SUCCESS]: Complete Magento installation.
[SUCCESS]: Magento Admin URI: / admin
Nothing to import.

I arrived at this result after following Magento DevDocs in the nginx section of this documentation. However, it seems that I came to this page when I entered the window of my browser:

The page you are looking for is not found.

I admit that this is the first time I use nginx. So I have reviewed some sources that claim that they can be used together with Apache, with the hope of being able to finish my configuration and start putting content.

As a way of solving problems, I have gone through /etc/nginx/conf.d/default.conf but I'm not sure what the correct values ​​are that are supposed to be in server_name. I have seen examples of it pointing to apache in some way.

Here is my current configuration so far:

  • centos 7
  • nginx / 1.12.2
  • php / 7.2.16
  • mariadb / 10.3.13 (mysql 15.1)
  • community edition magento 2.3
  • composer / 1.8.4
  • apache / 2.4.6

Mainly, I'm trying to use nginx as a reverse Apache proxy so that it can support higher volumes of traffic and still be able to use the .htaccess file.

I am sure that I am not implementing this correctly, so any idea, comment or suggestion will be much appreciated.

Namespaces – Using FPDF with automatic compositor loading

I can use the FPDF class if I need the correct file from my library:

Add page ();
$ pdf-> SetFont (& # 39; Arial & # 39 ;, & # 39; B & # 39 ;, 16);
$ pdf-> Cell (40.10, & # 39; Hello World! & # 39;);
$ pdf-> Exit ();

Note: the file fpdf.php has no namespace.

The composer should be loading this file automatically for me. A fragment of my autoload_classmap.php generated by the composer:

// autoload_classmap.php @generated by Composer

$ vendorDir = dirname (dirname (__ FILE__));
$ baseDir = dirname ($ vendorDir);

return matrix
& # 39; FPDF & # 39; => $ vendorDir. & # 39; /setasign/fpdf/fpdf.php&#39 ;,
& # 39; File_Iterator & # 39; => $ vendorDir. & # 39; /phpunit/php-file-iterator/src/Iterator.php&#39 ;,

Another library, phpunit is loading well.

How can I automatically load the FPDF library with the compositor and use: use FPDF;?