agaric/agaric-coop
10
1
Fork 0
Code Issues 102 Pull requests Projects Releases Packages Wiki Activity

Error when trying to install Drutopia Case Study #94

New issue
Closed
opened 2018-10-15 16:34:33 +00:00 by cedewey · 13 comments
cedewey commented 2018-10-15 16:34:33 +00:00 (Migrated from gitlab.com)
Copy link

When I try to install Drutopia Case Study, I get the following error:

Unable to install Drutopia Case Study due to unmet dependencies:  
core.entity_form_display.node.case_study.default  
(field.field.node.case_study.field_case_study_technologies,  
field.field.node.case_study.field_license, field.field.node.case_study.field_services),  
core.entity_view_display.node.case_study.small_card  (field.field.node.case_study.field_case_study_technologies,  
field.field.node.case_study.field_services),  
core.entity_view_display.taxonomy_term.license.default (taxonomy.vocabulary.license),  
search_api.index.case_study (field.storage.node.field_services,  
field.storage.node.field_case_study_technologies)
When I try to install Drutopia Case Study, I get the following error: ``` Unable to install Drutopia Case Study due to unmet dependencies: core.entity_form_display.node.case_study.default (field.field.node.case_study.field_case_study_technologies, field.field.node.case_study.field_license, field.field.node.case_study.field_services), core.entity_view_display.node.case_study.small_card (field.field.node.case_study.field_case_study_technologies, field.field.node.case_study.field_services), core.entity_view_display.taxonomy_term.license.default (taxonomy.vocabulary.license), search_api.index.case_study (field.storage.node.field_services, field.storage.node.field_case_study_technologies) ```
cedewey commented 2018-10-16 18:08:31 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in issue #88

mentioned in issue #88
cedewey commented 2018-10-17 15:57:32 +00:00 (Migrated from gitlab.com)
Copy link

closed

closed
cedewey commented 2018-10-17 15:57:35 +00:00 (Migrated from gitlab.com)
Copy link

unassigned @cedewey

unassigned @cedewey
cedewey commented 2018-10-17 19:40:19 +00:00 (Migrated from gitlab.com)
Copy link

reopened

reopened
cedewey commented 2018-10-17 19:43:06 +00:00 (Migrated from gitlab.com)
Copy link

@mlncn I'm stuck on this. I see each of these missing dependencies in drutopia_case_study/config/install

What do I need to do to address this error?

@mlncn I'm stuck on this. I see each of these missing dependencies in drutopia_case_study/config/install What do I need to do to address this error?
cedewey commented 2018-10-17 19:43:10 +00:00 (Migrated from gitlab.com)
Copy link

assigned to @mlncn

assigned to @mlncn
mlncn commented 2018-10-18 01:18:35 +00:00 (Migrated from gitlab.com)
Copy link

changed the description

changed the description
mlncn commented 2018-10-18 01:20:03 +00:00 (Migrated from gitlab.com)
Copy link

changed the description

changed the description
mlncn commented 2018-10-18 01:39:16 +00:00 (Migrated from gitlab.com)
Copy link

@cedewey you need to include the configuration export of these precise field dependencies in Drutopia Case Study, and make a requirement of the module you've alluded to that's the source of the license vocabulary and possibly the license field.

That's... what i've been asking you to do for two days. At this point i'm afraid you may have lost the configuration, unless it's stashed in some branch?

As the error message indicates, web/modules/custom/drutopia_case_study/config/install/core.entity_form_display.node.case_study.default.yml does indeed call for field.field.node.case_study.field_case_study_technologies as a dependency. The first item listed in each series is the one that is there; the following ones in each series are what the first one is missing. The problem is there is NOT any:

  • web/modules/custom/drutopia_case_study/config/install/field.field.node.case_study.field_case_study_technologies.yml
  • web/modules/custom/drutopia_case_study/config/install/field.field.node.case_study.field_license.yml
  • web/modules/custom/drutopia_case_study/config/install/field.storage.node.field_services.yml
  • web/modules/custom/drutopia_case_study/config/install/field.field.node.case_study.field_services.yml
  • web/modules/custom/drutopia_case_study/config/install/taxonomy.vocabulary.license.yml

All of those files need to exist (with proper configuration in them!) for the import to work.

@cedewey you need to include the configuration export of these precise field dependencies in Drutopia Case Study, and make a requirement of the module you've alluded to that's the source of the license vocabulary and possibly the license field. That's... what i've been asking you to do for two days. At this point i'm afraid you may have lost the configuration, unless it's stashed in some branch? As the error message indicates, `web/modules/custom/drutopia_case_study/config/install/core.entity_form_display.node.case_study.default.yml` does indeed call for `field.field.node.case_study.field_case_study_technologies` as a dependency. The first item listed in each series is the one that is there; the following ones in each series are what the first one is *missing*. The problem is there is NOT any: * `web/modules/custom/drutopia_case_study/config/install/field.field.node.case_study.field_case_study_technologies.yml` * `web/modules/custom/drutopia_case_study/config/install/field.field.node.case_study.field_license.yml` * `web/modules/custom/drutopia_case_study/config/install/field.storage.node.field_services.yml` * `web/modules/custom/drutopia_case_study/config/install/field.field.node.case_study.field_services.yml` * `web/modules/custom/drutopia_case_study/config/install/taxonomy.vocabulary.license.yml` All of those files need to exist (with proper configuration in them!) for the import to work.
mlncn commented 2018-10-18 01:41:58 +00:00 (Migrated from gitlab.com)
Copy link

@cedewey OK as hoped the two license-related configurations above field.storage.node.field_license.yml and taxonomy.vocabulary.license.yml do exist in your drutopia_creative_license module, so to take care of them all you need to do is add it as a dependency in drutopia_case_study.info.yml

For the other fields, if you still have it working locally you should be able to drush -y cex and copy them from config/sync into the install directory. If you don't have them working locally still, and you haven't exported them somewhere that you can retrieve them (put into the config install of another Drutopia module maybe?) then you'll have to recreate the fields locally and export them. Or try your hand at copying and tweaking similar config files to create the missing ones...

@cedewey OK as hoped the two license-related configurations above `field.storage.node.field_license.yml` and `taxonomy.vocabulary.license.yml` **do** exist in your `drutopia_creative_license` module, so to take care of them all you need to do is add it as a dependency in `drutopia_case_study.info.yml` For the other fields, if you still have it working locally you should be able to `drush -y cex` and copy them from `config/sync` into the install directory. If you don't have them working locally still, and you haven't exported them somewhere that you can retrieve them (put into the config install of another Drutopia module maybe?) then you'll have to recreate the fields locally and export them. Or try your hand at copying and tweaking similar config files to create the missing ones...
cedewey commented 2018-10-18 17:03:28 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in merge request !25

mentioned in merge request !25
mlncn commented 2018-10-18 21:31:27 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 2c4c2fdcd1

mentioned in commit 2c4c2fdcd14d794ef61e4b2fa8e3f828bfcf3cd3
mlncn commented 2018-10-18 21:31:27 +00:00 (Migrated from gitlab.com)
Copy link

closed via merge request !25

closed via merge request !25
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
bbb-test
D9-upgrade
drush-9-aliases
provision-dewey
No results found.
Labels
Clear labels   
A11y

Accessibility-related issues

  
Automated Testing

   
Contributable

Issues with work that can (potentially) be contributed back to Drupal or other FLOSS projects.

  
Contributed

Tag issues where we have contributed work back to FLOSS projects (replace Contributable tag; the Contributed tag can be removed once the contribution is recorded in a blog or something.

  
Decision

An issue that requires a decision be made.

  
Design

Issues that should include a UX/design work or review.

  
Development

   
Drutopia

Issues related to Drutopia features or infrastructure, or are potential Drutopia enhancements (with tag Contributable).

  
Feature Request

   
IndieWeb

Anything related to interlinking web sites in a broadly IndieWeb fashion, see https://indieweb.org/

  
Infrastructure

   
Marketing

   
Needs documentation

When an issue has uncovered something that should be documented in a user guide or the project wiki or anywhere else outside the issue queue.

  
status::Abandoned

An issue that has been abandoned and will not be completed.

  
status::Blocked

An issue that is blocked for a reason outside Agaric's control.

  
status::Deploy

An issue that has been tested and is ready to be deployed.

  
status::Doing

   
status::Done

   
status::In Review

An issue that has been completed and is ready for a code and/or design review.

  
status::Needs Clarification

   
status::Test

An issue that has been completed and is ready to be tested.

  
status::To Do

An issue that is an agreed priority and has all information needed to be completed.

  
type::Bug

   
type::Task

   
type::User Story
No labels
A11y
Automated Testing
Contributable
Contributed
Decision
Design
Development
Drutopia
Feature Request
IndieWeb
Infrastructure
Marketing
Needs documentation
status::Abandoned
status::Blocked
status::Deploy
status::Doing
status::Done
status::In Review
status::Needs Clarification
status::Test
status::To Do
type::Bug
type::Task
type::User Story
Milestone
Clear milestone
No items
No milestone
Sprint 2
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: agaric/agaric-coop#94
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?