hechoendrupal / drupal-console-launcher Goto Github PK

After updating to rc17 the Launcher drupal command returns the message, "Could not find Drupal in the current path.". This should be changed to something that instructs the user to run the command within a Drupal project and reminds them of the documentation page fro the Launcher where we will explain what it is and why you are using it.

The launcher assumes white as the default console color.
Not only this may not be the case, but also colors may not match in different terminals.

Here's what I get when running drupal --version:

As you can see the color is changed to light-grey-bold in my case.

This link: https://drupalconsole.com/installer

Maybe you forget add the "drupal.phar" asset to this release.

https://github.com/hechoendrupal/drupal-console-launcher/releases/tag/1.7.0

Thank you so much for your work!

Hello,
When installed with composer global require drupal/console-launcher, drupal then returns this error:

 Something is wrong with your drupal.phar archive.
 Try downloading again by executing from your terminal:
 curl https://drupalconsole.com/installer -L -o drupal.phar

Would it be possible to support installing it this way? It would be easier to integrate it in our system than using the PHAR.

Using Drupal Console with the drupal-composer project, I can't launch the console from the drupal directory (web), but have to launch it from inside the root directory (where the composer.json is found). Any idea how to fix this?

I'm using the latest version (rc14 as of now) and the problem started with rc9 as far as I know (maybe a problem using Drupal Finder and a multisite (without a default site?)).

The readme only gives these installation instructions:

curl https://drupalconsole.com/installer -L -o drupal.phar
mv drupal.phar /usr/local/bin/drupal
chmod +x /usr/local/bin/drupal

Why doesn't it mention the following?

composer global require drupal/console-launcher

This is much more "composer-style" and it also works much easier for Windows installation.

Hi!

I think the launcher debug output - "Using the Drush script found at [...] using pcntl_exec" - from Drush is very useful. I wasn't able to get similar output from the Drupal Console launcher.

This may not be the best place for this issue. Please close and put in the right place if there's somewhere better.

I needed to update Drupal console to 1.8.0 today. The instructions on https://docs.drupalconsole.com/en/getting/launcher.html about downloading say

`Install Drupal Console Launcher using the phar

curl https://drupalconsole.com/installer -L -o drupal.phar`

This is failing, which means that Drupal console breaks. If instead of curl, you load the URL in a browser you see
The website encountered an unexpected error. Please try again later. Error: Class 'TheIconic\Tracking\GoogleAnalytics\Analytics' not found in Drupal\github_data\Controller\InstallerController->index() (line 63 of modules/custom/github_data/src/Controller/InstallerController.php).

Hello my friends, I keep getting the error:

Something is wrong with your drupal.phar archive.
Try downloading again by executing from your terminal:
curl https://drupalconsole.com/installer -L -o drupal.phar

I have followed the following instructions while in my Drupal root folder:

curl https://drupalconsole.com/installer -L -o drupal.phar
mv drupal.phar /usr/local/bin/drupal
chmod +x /usr/local/bin/drupal

After these steps I type in 'drupal self-update' or 'drupal' in my terminal but keep getting the error message. Am I doing something wrong? I am on WSL.

Thanks

The command formed by line 20 of LauncherContainer.php seems to be causing issues on Windows.

C:\Users\lal65\Sites\wcprospect8-dev>drupal site:install
'C:\Users\lal65\Sites\wcprospect8-dev/vendor/drupal/console/bin/drupal' is not recognized as an internal or external command, operable program or batch file.
Wouldn't it make sense to use DIRECTORY_SEPARATOR instead of '/' as in below?

$command = sprintf( '%s'.DIRECTORY_SEPARATOR.'vendor'.DIRECTORY_SEPARATOR.'drupal'.DIRECTORY_SEPARATOR.'console'.DIRECTORY_SEPARATOR.'bin'.DIRECTORY_SEPARATOR.'drupal --root=%s %s', $options['root'], $options['root'], $this->parseArguments() );

Cross referencing hechoendrupal/drupal-console#3847,

With some debugging, I found that the launcher was starting drupal console with a path argument that was just the name of the directory that contained drupal, but not the full path to it.

I have the launcher installed globally and it works fine (reports it's version) outside of a drupal docroot

docker@cli:/var/www$ drupal --version
Drupal Console Launcher version 1.0.0-rc14

When run in a D8 docroot (without Drupal Console installed in the project) I get the error below, which is expected.

docker@cli:/var/www/docroot$ drupal --version

 [ERROR] Drupal Console is not installed at:                                                                            

 You must execute the following composer commands:
                                                                                                                        
 composer require drupal/console:~1.0 --prefer-dist --optimize-autoloader                                               
 composer update drupal/console --with-dependencies

I then run the commands to get composer installed as a project level dependency:

 composer require drupal/console:~1.0 --prefer-dist --optimize-autoloader                                               
 composer update drupal/console --with-dependencies

Now the launcher is not working inside the docroot:

docker@cli:/var/www/docroot$ drupal --version
[03-Mar-2017 16:55:52 UTC] Error: Call to undefined method Drupal\Console\Core\Utils\ConfigurationManager::loadExtendConfiguration() in /var/www/docroot/vendor/drupal/console-core/src/Application.php on line 284 #0 /var/www/docroot/vendor/drupal/console-core/src/Application.php(95): Drupal\Console\Core\Application->registerExtendCommands()
#1 /var/www/docroot/vendor/drupal/console/src/Application.php(49): Drupal\Console\Core\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#2 phar:///usr/local/bin/drupal/vendor/symfony/console/Application.php(124): Drupal\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#3 /var/www/docroot/vendor/drupal/console/bin/drupal.php(69): Symfony\Component\Console\Application->run()
#4 phar:///usr/local/bin/drupal/src/Utils/Launcher.php(30): include_once('/var/www/docroo...')
#5 phar:///usr/local/bin/drupal/bin/drupal.php(87): Drupal\Console\Launcher\Utils\Launcher->launch('/var/www/docroo...')
#6 phar:///usr/local/bin/drupal/bin/drupal(3): require('phar:///usr/loc...')
#7 /usr/local/bin/drupal(10): require('phar:///usr/loc...')
#8 {main}
Error: Call to undefined method Drupal\Console\Core\Utils\ConfigurationManager::loadExtendConfiguration() in Drupal\Console\Core\Application->registerExtendCommands() (line 284 of /var/www/docroot/vendor/drupal/console-core/src/Application.php).

However the installed version of the console if working fine if executed directly:

docker@cli:/var/www/docroot$ vendor/bin/drupal --version
Drupal Console version 1.0.0-rc16

Notice the versions of the launcher and the console are not the same in my case:

Drupal Console Launcher version 1.0.0-rc14
Drupal Console version 1.0.0-rc16

If I update the launcher to 1.0.0-rc15 or 1.0.0-rc16, then everything works as expected.

Presumably the launcher is supposed to be compatible with an arbitrary version of console. Unfortunately the above shows it's not. Unless the 1.0.0-rc14 release of launcher had a regression and this is not something to expect on a regular basis.

There's one thing I came across during installation with drupal quick:start.

I noticed that for the installation to succeed I had to enter an absolute path during the question "Enter value for directory placeholder".

The value given there is handed over to composer create-project which seems to work as the composer project does gets created but when the chain comes to the drupal site:install command it executes drupal site:install standard --root=testfolder --db-type="sqlite" --no-interaction which throws the following error message:

[ERROR] The command "drupal site:install standard --root=testfolder --db-type="sqlite"
--no-interaction" failed.
                                                                                  
Exit Code: 1(General error)
                                                                                  
Working directory: phar:///usr/local/bin/drupal/bin/../
                                                                                  
Output:
================
                                                                                  
[ERROR] Drupal Console is not installed at:
                                                                                  
testfolder
                                                                                 
                                                                                  
You must execute the following composer commands:
                                                                                  
composer require drupal/console:~1.0 --prefer-dist --optimize-autoloader
                                                                  
Error Output:
================

Perhaps it's more clear for the user to either:
a. make it more clear that one should provide an absolute path during that question or
b. make sure the site:installer will run succesfully when a relative path is given

Hi,

I can no longer use the console-yaml extend plugin, with any launcher from 1.1.1 on... 1.1.0 is the last version that works.

I've been installing the Yaml plugin using these steps:

RUN mkdir ~/.console && cd ~/.console &&   composer create-project drupal/console-extend extend --no-interaction &&   cd extend && composer require drupal/console-yaml

... with DC 1.1.0 drupal list yaml gives a list of Yaml commands, and with DC 1.1.1 I get "[Symfony\Component\Console\Exception\CommandNotFoundException]
There are no commands defined in the "yaml" namespace."