- πΊπΈUnited States Jon Pugh Newburgh, NY
This worked for me when updating a Drupal 8 varbase site to Drupal 9.
I was able to test it like this:
Add to your repositories:
"repositories: { "varbase_total_control": { "type": "vcs", "url": "https://git.drupalcode.org/issue/varbase_total_control-3226341.git" },
Require the dev branch, but alias it as a real version so the rest of the composer stack doesn't break:
composer require "drupal/varbase_total_control:dev-3226341-missing-layouts.yml-file as 9.0.3"
After that, "drush updb" worked.
- π―π΄Jordan Rajab Natshah Jordan
Thanks, for following up on the issue.
Better to remove any use of masonry and masonry API when upgrading
Or after upgradeAs #3145800: Remove [Masonry API] module and its related configuration from the 9.0.x branch β
On another subject on Gitlab MR composer require directly for a fork issue branch or diffhttps://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupa... β
If you use the URL to the Gitlab MR directly, your codebase will change without warning, as people work on the merge request.