- Issue created by @Liam Morland
- 🇺🇸United States jrockowitz Brooklyn, NY
We could also move this code to the webform_deprecated project.
- 🇺🇸United States jrockowitz Brooklyn, NY
I am realizing that Bootstrap 3.x is still supported. We can keep the code deprecated in the core webform module but tweak the webform_bootstrap.module to only work with Bootstrap 3.x.
- 🇺🇸United States jrockowitz Brooklyn, NY
I think can we assume no one is creating new sites with Bootstrap 3.x, and we should remove the Bootstrap check in hook_requirements. This will allow us to move the webform_bootstrap.module to https://www.drupal.org/project/webform_deprecated → .
- Merge request !578Issue #3492971: Document webform_bootstrap deprecation → (Merged) created by jrockowitz
- c1014a61 committed on 6.3.x
Issue #3492971: Document webform_bootstrap deprecation
- c1014a61 committed on 6.3.x
- c1014a61 committed on 6.x
Issue #3492971: Document webform_bootstrap deprecation
- c1014a61 committed on 6.x
- 🇨🇦Canada joseph.olstad
I'm creating new bootstrap 3 sites including one I just created this week.
- 🇨🇦Canada joseph.olstad
Bootstrap 3.34 is compatible with Drupal 11 and there's no plans to stop at 11.
Drupal 11 is currently planned to be supported until December 2027
- 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
I think support for things like Bootstrap should be in separate projects. There is already webform_bootstrap5 → .
- 🇨🇦Canada joseph.olstad
ok so basically fork webform_bootstrap into a seperate contrib project, this works for you?
- 🇺🇸United States jrockowitz Brooklyn, NY
I am okay with someone creating and maintaining a dedicated webform_bootstrap project.
- Status changed to Needs review
4 months ago 12:28pm 15 February 2025 - 🇮🇷Iran amir jamshidi
Hello every one.
I installed the https://www.drupal.org/project/bootstrap/releases/8.x-3.35 → template but now I have this error
Unable to install theme: 'bootstrap' due to unmet module dependencies: 'jquery_ui_draggable, jquery_ui_resizable'.
- 🇺🇸United States yesct
This doesn't seem like a release blocker to me. (Just noting.) Priority normal seems fine to me also.
- 🇺🇸United States jrockowitz Brooklyn, NY
I think we need to fork the webform bootstrap 3 module into a dedicated project and deprecate the code in the webform module.
- 🇺🇸United States yospyn
Hi - I work on a Drupal 10.4.5 site that's been using Bootstrap 3 for a long time and here's what I observed:
- Upgraded to 6.3@beta from 6.2.9, webforms appear normal with webform_bootstrap still installed
- Uninstalled webform_bootstrap (since deprecated) and webform styling gets a little wackyThus, for the moment, I'm not uninstalling webform_bootstrap on production. So it would be great to have this submodule still available in some way.
- 🇨🇦Canada joseph.olstad
@yospyn, we're using webform_bootstrap with Drupal 11.1.6 and the latest webform module 6.3.0-beta2.
As for deprecating, I think it's too soon to deprecate. Bootstrap 3 will be supported for the duration of jQuery 4 and possibly beyond. There's tens of thousands of installs.
with that said, could fork if needed as mentioned earlier.
- 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
The best thing would be to create a separate
webform_bootstrap
module project. - 🇨🇦Canada joseph.olstad
@liam morland, forking is problematic for a few reasons, mainly the bumpy ride for existing installs and it's not going to be something that automatically happens for those upgrading. People will stumble before they find the solution.