I faced the same issue when updating from 3.0.3 to 3.2.7
As mentioned in #5, it seems redundant to add 5 additional modules just to satisfy the Trait dependencies.
So I have created a patch for adding this, it applied smoothly and worked well for my website.
Hope this helps for others too!
P.S. I tried to create an MR, but was facing some issues so created this patch instead.
Hi @Sourav_Paul, my apologies, I am new to contributing, so was not aware of the standards.
Will keep this in mind, thanks.
Added the necessary changes, please review.
LGTM, works as expected.
nishtha.pradhan → made their first commit to this issue’s fork.
I agree with #7
But if you still want to keep both drupal/core and drupal/core-recommended, then you try this:
- Make a backup of all your codebase.
- Delete vendor/ folder & composer.lock file
- Now try running just
composer update "drupal/core-*" --with-all-dependencies
nishtha.pradhan → made their first commit to this issue’s fork.
nishtha.pradhan → changed the visibility of the branch 2883195-hide-userone-from to active.
nishtha.pradhan → changed the visibility of the branch 2883195-hide-userone-from to hidden.
Thank you for your feedbacks @guptahemant & @ankitv18.
I have worked upon them and update the MR.
Please do let me know if any other changes are required.
nishtha.pradhan → made their first commit to this issue’s fork.
Added a deprecation notice for use $variables['view'].
nishtha.pradhan → made their first commit to this issue’s fork.
I'm getting the same error as #16 on Drupal 10.2.5
It goes away after invalidation Drupal cache a few times.
But it is indeed a fatal error, the site shows: "The website encountered an unexpected error. Please try again later."
All I did was open the site and try to go to a particular menu from the admin dashboard.