Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The module bootstrap_library is installed with openatrium and the openatrium profile depends on it (it's listed in openatrium.info). However, only the deprecated oa_radix theme lists the module in a make file. This seems odd to me, if openatrium depends on it, it should also have it in its make file, but then again I don't understand make files for profiles that well.
I would like to suggest upgrading bootstrap_library to 7.x-1.4+4-dev (the latest dev at this moment) because it fixes an annoying bug where the status page recognizes 1.10 as less than 1.7. I want to create a patch for a make file but because of the above confusion I have no idea how to do this.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 2916036-oa_core-jquery-version-3.patch | 539 bytes | Jorrit |
| #3 | 2916036-oa_radix-jquery-version-3.patch | 631 bytes | Jorrit |
Comments
Comment #2
mpotter commentedYou are correct. It looks like only oa_radix brings this in via Drush make. That currently works because oa_radix is still installed with Atrium, but definitely needs to be added to the oa_core.make file. So a patch that adds that would be welcome.
However I probably wouldn't update Atrium to use the dev version of bootstrap_library. They really need to get a release. We really try to avoid using dev releases directly when possible. It's usually better to reference a released version and then a patch that fixes the specific issue if the module maintainer is unwilling to make a new release.
Comment #3
Jorrit commentedI have added patches for both oa_core and oa_radix. This makes sure (I hope) that Drush doesn't leave out the patch because it prioritizes the oa_radix configuration over oa_core, like happened with devel and iCalCreator.iCalCreator.
Comment #4
mpotter commentedCommitted to oa_core and oa_radix.