Patch does not apply on new version
The documentation was updated for latest version on Drupal.org a few days ago
Enable twig debug on your services.yml and try to find if the div was injected by template.
If not, will need to trace javascript trying to find if a module js is injecting that div.
I can assure Barrio is not responsable for that piece of HTML
Please enable twig debut and inspector the origin of the a tags
Bootstrap 5 has no dependency on jquery.
Please check on your Bootstrap versión.
DEV version for bootstrap_library is ready for D11 with one simple code change comming from automated bot.
After some test will push to stable version.
This is a mature module 10 years old, one of the few still going from D7 to D11.
Never had a major issue or mantainance problems.
Please feel free to post any code upgrade to module if you feel it can solve an issue or generate any kind of improvement.
@sarigaraghunath please create the patch against 2.0.x
@aswathyajish
For the upgrade at last the following steps required:
- Match your subtheme regions with Bootstrap 5 regions.
- Copy page.html.twig from B5 base theme version and update regions previous B3.
- On your subtheme change twig markup to B5 markup.
- Requiere drupal/jquery if your js depends on it.
- Start troubleshooting
jQuery version upgrade on D11 breaks slick.js
Closed with more than 6 months inactive.
Reopen only if patch or fix proposed.
Set as critical, it breaks the site upon installing breaking the database if enabled with other modules leaving installation half the way.
Please activaste the twig debbuging mode and inspect to find where is Drupal looking for the page.html.twig template
Harmless
For a quick guide use this
Bootstrap SASS Straterkit →
.
The documentatio works for the Bootstrap SASS subtheme you are working on.
To install dependencies run npm install
This is minor issue as it did not affect end result on site.
Furthermore the theme is not the one who generates the links as they are generated on core
@xmacinfo
There were over 200 tickets on versions 8.x-3.x and 7.x sited for months or years.
Just did a cleanup for all over 6 months last interaction expexcting that if any of this tickets were still alive someone was going to pick it up and make it live again, like in this case.
Just for the record, this is the only one at the moment alive again.
For css subtheme there is no 100% working definition as it will depend os specific folder structures.
On scss subthemes a variable is set to allow customizations.
In your case and any other folder structures different from theme's "standard" path should be customized on subtheme's css
Details is added only for multiple values field is set, otherwise it is loaded as a regular field
There is really no need to add weights (if bootstrap library is called before global styling library), but for styles and colors weight is harmless and with the new weights applied bootstrap call will occur always before, avoiding any overrides.
Suggestios applied, always room for improvements specially on styles.
Just taking note that this is a base theme, so just basic styles applied to base components
colors.css sets css vars, order is not an issue.
Core styles should be disabled, so no risks on them.
styles.css if no Sass should overrite bootstrap styles, bootstrap as dependency should load first.
Module css loads before themes css.
Furthermore, your custom theme styles order could be set on the subtheme.
So, what styles are overwriten and by who?
@joseph.olstad
We are just openning new choices, not closing any.