- Issue created by @finnsky
- Status changed to RTBC
7 months ago 12:03am 21 June 2024 - 🇵🇹Portugal jcnventura
Because this theme requires Bootstrap 3, which is no longer supported, and in turn Bootstrap 3 requires a version of jQuery less than jQuery 4 which is shipped with Drupal 11, this theme will become end-of-life when Drupal 10 itself reaches end-of-life (currently scheduled for mid-2026).
This should be clearly documented in the module homepage, moving the recommendation of Bootstrap 5-based themes from the bottom of the homepage to the top, and acknowledging both the fact that Bootstrap 3 is no longer supported, and that the theme will never support any version of Drupal greater or equal to 11.
- 🇷🇸Serbia finnsky
I would say it differently.
At one time, Bootstrap 3 was an excellent framework that greatly moved the industry forward.
But now some of his decisions are slowing down this movement.
Such as a font size of 10 pixels for the root element for example.It's time to say goodnight sweet prince...
- 🇵🇹Portugal jcnventura
@finnsky, I agree with you but Bootstrap 3 has been EoL already for 5 years. The real news for those wanting to upgrade to Drupal 11 when it is released in about 1 month, is that this theme is simply not compatible with that version of core.
The theme needs to clearly document that, and say that anyone still using this theme (which still works) will now be locked into Drupal 10 until they can migrate away to another theme. The fact that Bootstrap 3 has been EoL is not in the same level of importance.
- Status changed to Fixed
7 months ago 4:55pm 25 June 2024 Automatically closed - issue fixed for 2 weeks with no activity.
- 🇨🇦Canada joseph.olstad
Bootstrap 3 is no longer EOL
We're now using the entreprise7pro/bootstrap instead of twbs/bootstrap
I've stubbed an issue to investigate possible approaches to deal with the font preferences.
https://github.com/entreprise7pro/bootstrap/issues/3
Investigating providing an optional override for those who wish to shim in a solution on top of bootstrap 3. An additional CDN with the shim could be provided as an option. We could include this option by default for new installs.
Either way, I'm sure there's a pragmatic low or no disruption solution for everyone going forward.