Problem/Motivation
When installing Varbase distribution on a clean install, the web UI stops, indicating a issue with the install of modules - indicating an unmet dependency with Varbase Landing Page Layout Builder module (vlplb).
When issuing a drush command to enable the vlplb module, I get the same error. Similarly when trying to enable varbase_demo module (vlplb is a dependency).
[Drupal\Core\Config\UnmetDependenciesException]
Configuration objects provided by <em class="placeholder">vlplb</em> have unmet dependencies: <em class="placeholder">field.field.node.landing_page_lb.layout_builder__layout (field.storage.node.layout_buil
der__layout)</em>
Steps to reproduce
Follow instructions to create a project on a DDEV environment
composer create-project vardot/varbase-project:~10 varbase --no-dev --no-interactionddev launchto launch a browser and start site install- Enter site configuration and Install
Install fails.
Clean DDEV environment to start all over again.
- Recreate project with composer
- Install site with Drush
drush site-install varbase --yes --account-name="webmaster" --account-pass="${password}" --account-mail="webmaster@mysite.com" --db-url="mysql://${mysql_root}:${mysql_pass}@${mysql_host}/${mysql_base}" --locale="en" varbase_multilingual_configuration.enable_multilingual=false varbase_extra_components.varbase_demo=true varbase_extra_components.editoria11y=true varbase_extra_components.vmi=true varbase_extra_components.varbase_heroslider=true varbase_extra_components.varbase_carousels=true varbase_extra_components.varbase_search=true varbase_extra_components.varbase_blog=true varbase_extra_components.varbase_auth=true varbase_extra_components.varbase_ai=true varbase_extra_components.varbase_api=true varbase_extra_components.varbase_editor=true install_configure_form.enable_update_status_emails=NULL -vvv
Same issue.
Rebuild composer by
rm -rf composer.lock bin/ vendor/ docroot/modules/contrib/ docroot/themes/contrib/ docroot/profiles/varbase/ docroot/libraries/
composer install -vvv
cd docroot/
drush cr
Same issue.
- Recreate project with composer
composer update -W
Same issue.
Proposed resolution
I checked if the field mentioned as a unmet dependency was defined under the vlplb and it does seem to be.
Remaining tasks
- ✅ File an issue about this project
- ❌ Addition/Change/Update/Fix to this project
- ❌ Testing to ensure no regression
- ➖ Automated unit/functional testing coverage
- ➖ Developer Documentation support on feature change/addition
- ➖ User Guide Documentation support on feature change/addition
- ➖ UX/UI designer responsibilities
- ➖ Accessibility and Readability
- ❌ Code review from 1 Varbase core team member
- ❌ Full testing and approval
- ❌ Credit contributors
- ❌ Review with the product owner
- ❌ Update Release Notes and Update Helper on new feature change/addition
- ❌ Release
Varbase update type
- ✅ No Update
- ➖ Optional Update
- ➖ Forced Update
- ➖ Forced Update if Unchanged
User interface changes
- N/A
API changes
- N/A
Data model changes
- N/A
Release notes snippet
- N/A
Comments
Comment #2
paddy_deburca commentedFollowing the release of Varbase 10.0.1 - a fresh install completed correctly resulting with a fully function website.
As this issue is no longer appearing in the released version of Varbase, I proposing marking it as closed (outdated).
Comment #3
rajab natshahComment #4
tarikflz commented@paddy_deburca Hello, I tried with 10.0.1 version with fresh install issue still continue, varbase_landing module needs workflows and varbase_page modules to be enabled I'll create patch for it.
Comment #5
rajab natshahThanks, Paddy, for reopening the issue.
Nice tip, Tarık, testing that.
I confirm the issue when using DDEV
Maybe other problems with DDEV as more changes in the latest version
What do we need to change in our .ddev's configs?
Supporting:
Adding Docksal, gitpod, Tugboat too.
A good working config with order is important
To work with many VM environments
Comment #6
rajab natshahI guess it is something on the order of importing configurations using Drupal Recipes.
Maybe a software is missing in our DDEV config ( .ddev )
I run the following command in a .circleci VM
with the following packages.
varbase/.circleci/config.yml
Comment #7
rajab natshahComment #8
rajab natshahI had a round of troubleshooting with
ddev logs --followandddev xdebug on#3472383: Fix Varbase Editor Default Recipe to Import/Update Configs and Follow Schema with Configuration Inspector
Found issues with Composer builds, PHP 8.3 in Docker images, Lando, and DDEV, ...
Composer 2.7.9 - released 2024-09-04
https://getcomposer.org/changelog/2.7.9
Please take a moment to check out a fresh build of the Varbase Demo:
Comment #9
rajab natshahComment #10
rajab natshah✅ Released varbase_editor-10.0.6
Comment #11
rajab natshahComment #12
rajab natshah✅ Released vardot/varbase-project 10.0.1.1 ( Project template )
https://packagist.org/packages/vardot/varbase-project#10.0.1.1
https://github.com/Vardot/varbase-project/releases/tag/10.0.1.1
What's Changed
composer.lockfile after Drupal 10.3.3 was released #252.vscodeandxdebug#2515.93.0to5.94.0by in #246Also Updated the
composer.lockfile after Drupal 10.3.3 was released #47 for Vardot/platformsh-varbase project templateComment #13
bondd commentedSo pity. Distribution targeted on slimplifying instalation and configuration of Drupal, cant be used because after the end of installation process (currently reccomended release) we get "internal server error 500" and in webserwer log "[error] 16003#0: *947 FastCGI sent in stderr: "PHP message: Uncaught PHP Exception Drupal\Component\Plugin\Exception\PluginNotFoundException: "Unable to determine class for field type 'metatag' found in the 'field.field.node.landing_page_lb.field_meta_tags' configuration" at /home/box/www/docroot/core/lib/Drupal/Core/Field/FieldConfigStorageBase.php line 31" while reading response header from upstream"
Seems all 200+ hours saved on configuring new site need to be spent on debugging of install process.
Do not take it close to heart, but I do not understand how release that cant even start after clean install appear as recommended. And no fixed version are released after almost a month.
Comment #14
paddy_deburca commented@bondd, The issue you have experienced is different from the one which I experienced - and which has since been resolved.
I have tried to reproduce this error by creating a new Varbase project and installing and configuring Drupal, without being able to reproduce this error.
Could you please create a new issue, with as much information as possible, and you are comfortable with, regarding your configuration and the steps you took during install of Varbase? This will help the community better look into and follow the issue to resolution.
Comment #15
rajab natshahComment #16
rajab natshah