- Issue created by @katharine_gates
- 🇬🇧United Kingdom scott_euser
If I understand correctly the issue, I believe your composer.json is locking you within an outdated/unsupported version. The easiest way to see this is with
composer outdatedcommand (so if using ddev, thenddev composer outdated).First make sure that in composer.json you have
"drupal/site_settings": "^2.0@RC|^2.0",so it takes the current supported version (which is version 2 if you look at module homepage). It has an update hook to update from 1x (which is 8.x-1.x in the old format). Its a big update so worth checking things, but it is meant to be backwards compatible with new features as "opt-in" essentially.Then you can run composer update
Note: You can watch the update look, or event search
"name": "drupal/site_settings",in the updated composer.lock file (which might be quicker than checking available updates page).If you still have issues updating, sometimes with composer stuff you can even resort to deleting the project from the contrib folder to make sure composer caching (depending on your local env) does not get in the way and it truly updates.
Hope that helps!
- 🇺🇸United States katharine_gates
Thank you so much for your patience and help. I did in fact have to delete the module files from contrib folder, empty caches, and run cron.
Automatically closed - issue fixed for 2 weeks with no activity.