-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to geenrate composer file #3
Comments
Same issue: on first attempt, all composer.json and .lock files are deleted as expected, then the error above. Additional attempts yield the exception below (despite providing a valid Drupal root):
|
Here it is with the stack trace, if that helps:
|
Similar behavior. Lot's of composer.json files are delete, but I end up with these errors: PHP Fatal error: Call to undefined method Symfony\Component\Yaml\Yaml::parseFile() in /Users/.../.composer/vendor/grasmash/composerize-drupal/src/Utility/DrupalInspector.php on line 28 Fatal error: Call to undefined method Symfony\Component\Yaml\Yaml::parseFile() in /Users/.../.composer/vendor/grasmash/composerize-drupal/src/Utility/DrupalInspector.php on line 28 |
Same here. Centos7 PHP 7.1.8
|
I have the same problem. FreeBSD 11.1, PHP 5.6.34 I tried
|
Is there a way to change the title of this issue to include "due to unresloved YAML dependency" (and to correct the spelling of "generate")? |
Same issue here. CentOS 7 / PHP 7.1.11 |
Attempting a global install of Symfony's YAML component with composer didn't work either: Running the composerize command afterward yielded the same result. |
I was getting the same message. I think it fails on the very last step of the process - which is updating Drupal core. I found this still works if you ignore the symfony error message and proceed as follows:
Then run drush updb to update the database. This also doesn't add your modules into your composer.json file - you'll need to run composer require statements for them if you want them tracked. IE: |
Adding
at the start of ComposerizeDrupalCommand.php shows that the former file is found, the latter is not. |
I just let the global composer generate the optimized static classmaps, and it does everything correctly:
I have no idea what is happening :( |
Calling "composer global composerize-drupal --composer-root=asdf --drupal-root=asdf" from some random directory with random values does change anything either: [ReflectionException] |
Resolving any other class works fine though. |
I was not able to solve this. I did work around it though. It's ugly but it works: Go to
at the top after |
Same |
Same here |
Hello, Just installed OS:
This stack trace is displayed twice. |
Did ChristianAdamski 's solution not work for you....? |
Hi there, Was about yo try ChristianAdamski 's solution when I relalised his path refers to a Symfony package inside his home's vendor. Which I don't have. I guess it should use the Symfony/Component from the vendor directory at the root of the Drupal installation. Anyway, after a few rm, require, install, update... manualy checking the content of composer.json at the root of the project I ended up with Drupal 8.5.6 installed. Go figure. XD I'm such in a hury with this project, already lost half a day so I'm gonna focus on building it and I'll come back to this issue later. ;o) Regards |
same issue with php 7.1, any ideas to solve this?
|
I was having the same issue, what helped me was to run the command outside the repository root. The reason for this is that I had symfony/yaml installed in my site and it was using this instead of the global one, and it was an old version that didn't have the |
Hei,
When I run the command, I simply get the error below and it deletes my core and some other files in my docroot:
I have tried setting symfony/yaml as required and re-updating the composerize project to no avail.
The text was updated successfully, but these errors were encountered: