Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
When I look at the Updates page of my Varbase project, it says I need new updated versions of several modules like Ace Code Editor 8.x-1.0 or Display Suite. Yet when I run "composer update", nothing gets fixed. When I run "composer outdated", I can see the old ones in red. Suggestions?
Comments
Comment #2
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commentedThank you for reporting
Ace Code Editor is having some issues with the composer in the latest version
#3022330: composer installation fail
In Varbase Editor we are requiring the module with a wild card
As we are using ~1.0 so the composer is getting the working one avoiding any errors in the update or install build
Comment #3
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commentedReleased varbase_core 8.x-6.9
https://www.drupal.org/project/varbase_core/releases/8.x-6.9
and varbase_editor 8.x-6.3
https://www.drupal.org/project/varbase_editor/releases/8.x-6.3
We can update a number of modules at this time
But first, we need to remove the following from the project composer.json
And remove from
vendor/vardot/varbase-updater/config/tags.json
tooThen we can run
composer update
Comment #4
bogdog400 CreditAttribution: bogdog400 commented[See #5 below. I didn't delete the lines above.]
Thanks for the quick fix but now I'm getting this error:
Here is the composer run:
And then I reran it perhaps creating this login_destination problem:
Finally, I used drush to update the db and clear the cache.
Comment #5
bogdog400 CreditAttribution: bogdog400 commentedSorry. I didn't read your text closely enough. I went back and deleted the two lines:
Composer fixed my mistake be reinstalling them. I couldn't find the tags.json file because there's no vendor/vardot directory in my version. But at least drupal is running again.
BTW, these three modules are listed as needing updates but composer isn't updating them.
Comment #6
mmjvb CreditAttribution: mmjvb as a volunteer commentedAs a user of this distribution suggest to use https://www.drupal.org/project/varbase/releases/8.x-6.4 instead. It shows whether there is an update on the right. When scrolling down it show the components and whether there is an update for it.
Don't know what this distribution suggests for updating, but according to Semantic Versioning you should be ok when sticking to the same major version. Which is why I suggest to use "composer outdated -mD" instead. It shows more relevant information to your situation. Obviously, it disregards the version constraints of your project. Use "composer update --dry-run" to find out what is going to happen before you do it for real.
When it doesn't mention the expected updates you need "composer prohibits <package>" to find out what prevents it from updating. You might need to change the requirements because of their version constraints. Use "composer require <package:version constraint> --no-update" to change composer.json for each. Use "composer update" or whatever you are told by the release notes and/or maintainer of this distribution.
Comment #7
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commentedReleased Varbase 8.x-6.6
https://www.drupal.org/project/varbase/releases/8.x-6.6
Cleaned up all hash commits so that vardot/varbase-project template and the composer.json looks clean.
https://github.com/Vardot/varbase-project/blob/8.6.6/composer.json
The update should work without issues, But we have to remove all old Hash commits!!!
Comment #8
bogdog400 CreditAttribution: bogdog400 commentedThanks for this. This cleaned up things quite a bit.
I'm still getting update messages for these two modules but I'm guessing that's because there are incompatibilities, right?
Comment #9
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commentedComment #10
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commented