Releases for Bootstrap

This is the 8.x-4.x development branch for version 4.x of the Bootstrap framework.

Use at your own discretion (i.e. not recommended for use on production sites).

Changes since 8.x-3.0-beta2 (32 commits):

Changes since 7.x-3.3 (2 commits):

Bug Fixes

• #2637924 by markcarver: Bootswatch API URL is broken
• #2635140 by szecsodimlaszlo: Page 'Bootstrap Settings' has fallen apart

Changes since 7.x-3.2 (1 commits):

Changes since 7.x-3.2 (1 commits):

Bug Fixes

• #2633924 by gge: Notice: Undefined offset: 1 in drupal_group_functions_by_prefix()

Changes since 7.x-3.1 (4 commits):

Changes since 8.x-3.0-alpha2 (25 commits):

Initial port release for Drupal Bootstrap 3 (7.x-3.x -> 8.x-3.x).

Note that this is an ALPHA release and does not claim to be 100% stable.

There will undoubtedly be bugs, please create issues and create patches.

Change Records

Changes since 7.x-2.x (170 commits by 20 contributors):

Major Change

#2098175: Clean up files
This issue alone has impacted the Bootstrap base theme the most. A huge effort was put in to help organize and optimize the Bootstrap base theme.

Major Change: #2098175: Clean up files

This issue alone has impacted the Bootstrap base theme the most. A huge effort was put in to help organize and optimize the Bootstrap base theme.

The file structure has been completely re-organized. While the base theme may now contain a lot of extra files (seemingly unnecessary at first), it was done in an effort to leverage Drupal's theme system architecture.

By leveraging Drupal's ability to include files only when a specific theme hook is implemented, we have reduced the PHP memory footprint of the Bootstrap base theme. Another advantage to implementing this automated file structure is: organization. We are now organizing [pre]process functions, theme function and template implementations in an easy to find folder structure. How that file structure is determined depends on module they originated from.

Over time this base theme has grown exponentially and this type of change will help ensure it's future growth, without sacrificing performance.

Sub-themes, you can rest assured that you inherit this performance enhancement automatically. There is no need to structure your sub-theme this way, so feel free to continue using your existing workflow :)

Changes since 7.x-2.x:

Changes since 7.x-2.0-beta3:

• Issue #1451510 by natted, nagiek : Exclude bootstrap control-label for radio elements.
• Issue #1863232 by andregriffin: Add isset check before testing value.
• Issue #1483918 : consolitdate preprocess functions
• Issue #1460508 by natted : fix the the previous implementation of the main menu to be more robust
• Issue #1860428 by cpliakas: Change style of status messages
• Issue #1860142 by natted, cthiebault : Reintroduce default menus with navigation region as optional.
• Issue #1706180 by natted, zmove, frankbaele, tchopshop : add dropdown and submenu menu support
• issue #1858418 by andregriffin : make set location of the bootstrap library more easily modified
• Issue #1854036 by andrgriffin, frankbaele, danharper : Fix css include order
• Issue #1857374 by hyrod : fix pager ellipsis
• Issue #1850872 by cpliakas : rearrange includes and optimise incude code
• Issue #1809948 by xcono, avr : Preprocess tables string to array conversion
• Issue #1794682: node delete form buttons wrapper not closing
• Issue #1851390 by jstamper : better fieldgroup support
• Issue #1850934 by cpliakas : Dropdown on tabs for menu local tasks causes UX issue when switching between tabs

Changes since 263a5c1: