Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello,
Trying to update my site from beta9 to beta10 I got this error:
Error: Drupal\Core\Config\UnmetDependenciesException: Configuration objects (core.entity_view_display.node.event.default, core.entity_view_display.node.topic.default) provided by social_like have unmet dependencies en Drupal\Core\Config\UnmetDependenciesException::create() (linea 84 de /home/cvantart/public_html/intranet/html/core/lib/Drupal/Core/Config/UnmetDependenciesException.php).
Ideas?
Thanks
Comments
Comment #2
jochemvn CreditAttribution: jochemvn for Open Social commentedHi huma2000,
Can you show me what commands you performed when you did to update?
Jochem
Comment #3
huma2000 CreditAttribution: huma2000 commentedI did:
Composer update
and then went to the update.php page and follow it
Comment #4
tc33133 CreditAttribution: tc33133 commentedI have a similar issue, but with a different UnmetDependency error.
I did
composer update
drush updatedb
and got the following errors:
Comment #5
tc33133 CreditAttribution: tc33133 commentedI've been working through this issue and got some very good support from @ronaldtebrake on IRC chat.
At first, he suggested it was due to a configuration issue that others have been able to solve by increasing the xdebug max_nesting_level
ini_set('xdebug.max_nesting_level', 300);
as referenced here:
https://www.drupal.org/node/2558371#comment-10363649
https://www.drupal.org/node/2594351#comment-10457017
I wasn't using Xdebug, so @ronaldtebrake suggested I apply a core patch which improves the UnmetDependenciesExeception to list the actual dependencies missing. See https://www.drupal.org/node/2655104. After I ran update.php again, it listed that I was missing fields for the default Event Content type and default Profile Entity, which I had removed for some reason. Once I added the missing fields the update.php ran fine and my problem was solved.
Thanks to Ronald for the help and following up with me.
Comment #6
ronaldtebrake CreditAttribution: ronaldtebrake as a volunteer and for Open Social commentedThanks for the kind words, glad we could help.
@huma2000,
Did you by any chance also add your own fields to the event and topic content type?
If you add the missing fields back to the content types as mentioned in the comment above, please let us know if that was the case and if it fixed your issues or not.
Comment #7
huma2000 CreditAttribution: huma2000 commentedÍ will check and get back to you on this tomorrow as I cannot remember from the top of my head.Thanks.
Comment #8
huma2000 CreditAttribution: huma2000 commentedAfter checking I see that I modify both, event and profile to add the custom fields I needed and removed a couple of unneeded fields, re-added them and still same error :(
Comment #9
tc33133 CreditAttribution: tc33133 commentedYou will get the error if you remove fields from the stock event and profile entities. There are dependencies on the specific field types that are created when the modules are installed during installation.
Comment #10
huma2000 CreditAttribution: huma2000 commentedSo after deleting them, even if I recreate them, is going to fail? any way to solve that?
Comment #11
tc33133 CreditAttribution: tc33133 commentedI was able to update fine after I recreated the fields in the content type Manage Fields page.
Comment #12
maikelkoopman CreditAttribution: maikelkoopman as a volunteer and at Open Social for Open Social commented