I was also unable to Run Updates after the upgrade. Please add appropriate instructions to the Release Notes page for what to uninstall before upgrade.
I do not know how these things work, but couldn't you tag a new release in order to get the info.yml file updated properly in existing installations? Or am I misunderstanding the situation?
bunthorne → created an issue.
I created a subtheme with hardly any customization in it from a Bootstrap5 version that was 9/10 compatible. Now my Bootstrap5 version is compatible with 11, but the subtheme still kicks out on the Upgrade Status report as incompatible.
Do I just need to manually update the info.yml file, or should I generate a new subtheme and then copy over any changes I made?
bunthorne → created an issue.
I don't know if this is helpful, but from a simplistic perspective of a site builder with minimal needs it would be great to be able to choose just the primary and secondary colors that would generate all of the relevant color choices, or even a third color if that is part of the set. Is that the goal of this issue?
That banner only says that the modules are removed. Release Notes should warn about upgrading without uninstalling.
bunthorne → created an issue.
Thanks, that helps somewhat. The only thing I would suggest would be to provide a sample in the documentation that parallels the documentation at Bootstrap. It could either go in the screenshot (instead of custom-card-class another-custom-card-class) or in the help text.
For example, the Boostrap example under Card#Text alignment showed
<div class="card text-center mb-3" style="width: 18rem;">
I was able to guess that I did not need the card part of the class; I put text-center in the Custom Card Class for the View to center all card elements.
shelane → credited bunthorne → .
It seems to be in the preview of the Bootstrap List Group view. Location for the one of the 5 error messages was:
https://[sitename]/admin/structure/views/view/[viewname]/preview/page_1?_wrapper_format=drupal_ajax
But after this reset, I am getting php errors in the log:
Deprecated function: explode(): Passing null to parameter #2 ($string) of type string is deprecated in template_preprocess_views_bootstrap_list_group() (line 245 of /[path]/web/modules/contrib/views_bootstrap/views_bootstrap.theme.inc)
I had the same error, and followed the suggestion in #2. For each view that had Bootstrap Cards, I opened the Settings for the card, clicked on Apply, and then Save for the View. After completing that for each BS Cards view, the site was able to display again.
I got the same error on my production installation that is using Olivero theme. Link just became available with 8.x-1.8 update.
What configuration do you need to know about? I have UI Patterns installed and many other UI Suite modules:
UI Examples, UI Examples Defaults, UI Patterns (but not UI Patterns Display Suite or Field Group), UI Patterns Layouts, UI Patterns Library, UI Patterns Settings, UI Patterns Views, UI Patterns Views Styles, UI Skins, UI Styles, UI Styles Block, UI Styles CKEditor 5, (not UI Styles Entity Status), UI Styles Layout Builder, UI Styles Library, UI Styles Page, and UI Styles Views.
bunthorne → created an issue.
Default theme is UI Suite Bootstrap.
bunthorne → created an issue.
getbootstrap.org offers a method for downloading the libraries with composer:
Composer
You can also install and manage Bootstrap’s Sass and JavaScript using Composer:
composer require twbs/bootstrap:5.3.2
bunthorne → created an issue.
drupal/bootstrap5 loads 2 versions of the bootstrap library directly into the theme's dist/bootstrap5/[version#] path.
drupal/bootstrap_barrio also has a method of loading the libraries through a composer command as well as using a CDN.
I'll attempt the method described in the installation instructions to update my composer.json.
Thank you for the screenshot. My mistake--the filters are provided by Module Filter.
Here is the issue:
https://www.drupal.org/project/module_filter/issues/3413467
🐛
Radio buttons on Available updates report do nothing
Active
Are we talking about the same page? Please share a screenshot.
Upgraded from 10.2.0.
The radio buttons have been on the Updates page since I first installed Drupal 7.
The radio buttons.
bunthorne → created an issue.
smustgrave → credited bunthorne → .
FYI I reverted to the core Olivero theme and the active accordion header is appropriately reversed to #ffffff.
bunthorne → created an issue.
bunthorne → created an issue.
jQuery UI Accordion 2.0.0
bunthorne → created an issue.
bunthorne → created an issue.
I think I found the problem happening when I used Taxonomy Manager to import terms.
bunthorne → created an issue.
So what is the roadmap for Views Accordion if it uses a component that is reaching end of life?
Mistakenly entered for this theme. It was intended for UI Suite Olivero.
bunthorne → created an issue.
bunthorne → created an issue.
bunthorne → created an issue.
bunthorne → created an issue.
I was going to try the module, but it is not enabled for D10.
I am trying to import a taxonomy that has multiple terms at level 2 with the same name (although with different Level 1 parents), and Level 3 terms for those Level 2 terms. As far as I can tell with the Taxonomy processor, I can only put one parent for a term, so the processor won't find the separate Level 2 terms to use.
Opera1
King
Queen
Chorus
Courtiers
Ladies in Waiting
Opera2
General
Colonel
Chorus
Soldiers
Villagers
I neeed to be able to reference the parent by using its own parent in a hierarchy:
Parent of Soldiers = Opera2/Chorus
Can this also be added to the 5.x version?
bunthorne → created an issue.
Same problem