All Versions
40
Latest Version
Avg Release Cycle
34 days
Latest Release
1252 days ago

Changelog History
Page 4

  • v1.13.1 Changes

    May 23, 2019

    🚀 Maintenance release for Backdrop CMS. This update contains bug fixes and usability improvements only.

    ⚡️ Update information:

    • 🚀 It will be necessary to run the update script (located at /update.php) for this release.
    • 🚀 No changes have been made to the .htaccess, robots.txt or default settings.php files in this release, so upgrading custom versions of those files is not necessary.

    🔄 Changes since 1.13.0

    • ✅ Issue #3728: Replace deprecated format_username() in comment.test with user_format_name().
    • Issue #3658: Replace all instances of 'theming' with a more specific and accurate word.
    • Issue #2536: Fix display of submitted info for node in block.
    • Issue #3716: Add views_clean_css_identifier() as a Backwards-Compatible wrapper function.
    • ⏪ Issue #3809: Revert the static definition added to entityType().
    • 🌲 Issue #3753: Allow the date display to be customized specifically for logging.

  • v1.13.0 Changes

    May 16, 2019

    Backdrop CMS version 1.13 is here!

    🚀 The Backdrop community is proud to release this most recent version following our 4-month release cycle. This version of Backdrop includes great new features including:

    • An administrative Dashboard (and a redirect there on login)
    • More attributes or links added via the Rich-Text editor
    • A 'Reset' button for the filter on the Modules page
    • The addition of a entity_access() function.
    • 🚀 All the changes included in 1.12.7.
    • More!

    ⚡️ Notes for updating:

    • 🚀 It will be necessary to run the update script (located at /update.php) for this release.
    • 🚀 This release does not modify files outside the core directory. Updating customized copies of those files is not necessary.

    🔄 Changes since 1.12.7

    • 🚚 Issue #361: Move default views to their respective modules
    • 🛠 Issue #3745: Fixed: Dashboard menu shows even if user doesn't have dashboard permission
    • Issue #3655: Add number of terms column to vocabulary overview page
    • Issue #3742: Add field_formatter_settings module to backdrop_merged_modules()
    • Issue #495: Add a useful dashboard to backdrop
    • 👍 Issue #1777: Add support for more link attributes in rich-text editor (id, rel, target, title)
    • 🔀 Issue #1376: Port and merge Field Formatter Settings in core
    • Issue #3455: Identify translatable strings in core static config files
    • Issue #3011: Add function to entity: entity_access
    • Issue #3657: Add vertical tabs to the taxonomy term edit form
    • ⚡️ Issue #3453: Enable manual self-updates on new sites
    • 0️⃣ Issue #574: Change default setting for Who can register accounts? to Administrators only
    • Issue #2595: Fix double-clicking "Save" when editing content causes an error
    • Issue #3690: Add $entity->getFieldValue() method to match field_get_value()
    • Issue #461: Add field_get_value() to get single value from field
    • 📚 Issue #3673: Improve the documentation of settings.local.php
    • Issue #3581: Add 'Reset' button to Modules page
    • 🌐 Issue #3505: Move the translation settings for content types to its own vertical tab.
    • ⚠ Issue #3558: Consolidate the warning about theme_debug being enabled in a single place
    • 🌐 Issue #3464: Extend the translation module to include a block that can hold translated content.

  • v1.13.0-preview Changes

    May 04, 2019

    🚀 Backdrop 1.13.0-preview brings new features to core. The official release of 1.13.0 will be May 15. You may use this version to test the functionality of 1.13.0 prior to it's final release. Additional bug fixes and minor UI adjustments may still occur prior to the final version.

    🚀 Further release notes to be added.

  • v1.12.8 Changes

    August 07, 2019

    🚀 Security-only fixes for the Backdrop 1.12.x branch. This bug fix release contains 3 security fixes. These 3 issues are mitigated by an attacker requiring levels of administrative access, but all users are encouraged to update as soon as possible. For more information see the following security announcements:

    🚑 Backdrop core - Moderately critical - Cross Site Scripting - SA-CORE-2019-010
    🚑 Backdrop core - Moderately critical - Cross Site Scripting - SA-CORE-2019-011
    🚑 Backdrop core - Critical - Remote Code Execution - SA-CORE-2019-012

    ⚡️ Update information:

    • ⚡️ The database update script does not need to be run.
    • 🚀 No changes have been made to the .htaccess, robots.txt or default settings.php files in this release, so upgrading custom versions of those files is not necessary.

    🔄 Changes since 1.12.7

    No other changes have been made.

  • v1.12.7 Changes

    May 16, 2019

    🚀 Maintenance release for Backdrop CMS. This update contains bug fixes and usability improvements only.

    ⚡️ Update information:

    • 🚀 It will be necessary to run the update script (located at /update.php) for this release.
    • 🚀 No changes have been made to the .htaccess, robots.txt or default settings.php files in this release, so upgrading custom versions of those files is not necessary.

    🔄 Changes since 1.12.6

    • 🖐 Issue #3685: Allow views_handler_field_date to work with SQL datetime format.
    • Issue #3719: Ensure that we do not end up with broken views data cache entries.
    • ⏱ Issue #3731: Keep scheduled content scheduled for users without permission to edit the date.
    • Issue #3575: Date fields can show timezone twice.
    • 🔧 Issue #3504: Fix RTL icons in CKEditor toolbar configuration.
    • Issue #3537: Fix error using entity functions in install files.
    • Issue #2515: Fix node block template suggestion in existing content block.
    • Issue #3744: Fix resetting of created date by non-administrators.
    • 🔊 Issue #3743: Fix scrolling of fieldsets within dialogs.
    • ⚠ Issue #3699: Fix PHP 7.1 Warning: A non-numeric value encountered in theme_pager().
    • Issue #3633: Improve the help text in the visibility condition form.
    • Issue #3637: Fix RTL in the Manage blocks page.
    • 💻 Issue #3616: Project Browser: Fix RTL in the "Install new themes" page.
    • Issue #3636: Make weight a number field on book node edit form.
    • Issue #3635: Changed 'Edit links' button text to 'Manage links'.
    • 🚧 Issue #2528: Theme the maintenance page in Basis.
    • Issue #3026: Changed $vars to $variables in Date and Link modules.
    • ⚡️ Issue #3608: Updated description text for block class field.
    • 📚 Issue #3713: Fixed typo in batch_set() documentation.
    • 🚚 Issue #3299: Moved custom block delete button to the bottom of the page.
    • 🖐 Issue #3685: Fix views_handler_filter_date cannot filter for NULL.
    • Issue #3685: Fix Numeric Field Handler Converts NULL to Zero.
    • 🔌 Issue #3685: Views: views_plugin_argument_validate_taxonomy_term has ambiguous column tid.
    • ⚡️ Issue #3678: Update Front page link on update complete page.
    • 🌐 Issue #3674: Installer: Allow using .po translation files from b.org without having to rename them.
    • ⚠ Issue #3691: Fixes missing warning message in views theme information when display machine name is changed.
    • ⚠ Issue #3698: Spelling fix in Options Element warning.
    • ✅ Issue #1478: Avoid race-condition in comment-new test checking.
    • Issue #3609: Removing duplicate content on field date description.
    • Issue #1265: Provide code samples in a textarea for easy copy-paste.
    • 📚 Issue #3311: Update the API documentation to include the new 'info' type for messages.
    • Issue #3667: Properly indent in format_xml_elements().
    • 🌐 Issue #3560: Switch translation links in installer from Drupal to Backdrop.

  • v1.12.6 Changes

    April 17, 2019

    🔒 This resolves BACKDROP-SA-CORE-2019-009, a cross-site scripting vulnerability. Several other bug-fixes and usability improvements are also included, see the list below.

    ⚡️ Update information:

    • 🚀 It will be necessary to run the update script (located at /update.php) for this release.
    • 🚀 No changes have been made to the .htaccess, robots.txt or default settings.php files in this release, so upgrading custom versions of those files is not necessary.

    Other Changes since 1.12.5

    • Issue #3628: Fixed Warning: uasort() expects parameter 1 to be array, null given in node_view_multiple().
    • Issue #2690: Fix views contextual links on page displays by treating the same as block displays.
    • 👯 Issue #2673: Fixed Menu settings of custom layouts not cloned properly.
    • Issue #2497: Make comment, path, redirect operations drop-downs consistent.
    • Issue #3075: [UX] Provide a hint that classes can be added to the inner wrapper of a region.
    • Issue #3249: Help Views Wizard connect to vocabulary correctly.
    • Issue #3316: [UX] Add human name to fields list at admin/reports/fields.
    • 🔧 Issue #3345: [UX] Layouts: render the "Configure" link only if the block is not broken.
    • 0️⃣ Issue #3378: [UX] Default text formats are not saved properly without accompanying values.
    • Issue #3485: Add options_element in backdrop_merged_modules().
    • Issue #3533: Add confirmation form for disabling themes.
    • Issue #3613: Add 'type = profile' in .info files.
    • Issue #3573: Fix draggable nested items in RTL being dragged in the opposite direction.
    • Issue #3592: Change the weight field in the taxonomy term form to a number field.
    • Issue #3593: [UX] Views: Change the "Weight" field to for the page menu/tab to a number field.
    • ⚠ Issue #3622: Fix non-numeric warning in Options Element.
    • 🚚 Issue #3623: [DX] Remove the hard-coded parentheses from fieldset summaries.
    • Issue #3649: Color module: Fix call to undefined function admin_bar_suppress().
    • 🚚 Issue #3519: Fix image link class being removed when using image caption.
    • ⚡️ Issue #3542: [UX] Views: use "configuration changes" instead of "automatic updates" in messages.

  • v1.12.5 Changes

    March 20, 2019

    🔒 This resolves BACKDROP-SA-CORE-2019-008, a cross-site scripting vulnerability.

    ⚡️ Update information:

    • The database update script does not need to be run.
    • 🚀 No changes have been made to the .htaccess, robots.txt or default settings.php files in this release, so upgrading custom versions of those files is not necessary.

    Other changes since 1.12.4

    • Issue #3557: Fix docblock in page.tpl.php
    • 💅 Issue #3554: [UX] Basis: Fix RTL breadcrumb style.
    • 💅 Issue #3543: [UX] Fix RTL password field style.

  • v1.12.4 Changes

    March 13, 2019

    🔒 This resolves issues for the following security advisories:

    No other changes are included.

    ⚡️ Update information:

    • The database update script does not need to be run.
    • 🚀 No changes have been made to the .htaccess, robots.txt or default settings.php files in this release, so upgrading custom versions of those files is not necessary.

    Other changes since 1.12.3

    • ⚠ Issue #3557: [PHP 7.3] strpos explicit string needle warnings.
    • ✅ Issue #3557: Crossport Drupal issue #3023066: [PHP 7.3] Fix BootstrapMiscTestCase::testCheckMemoryLimit() notice.
    • Issue #3557: Crossport Drupal issue #1430934: Notice: Undefined index: display_field in file_field_widget_value().
    • 🗄 Issue #3470: Fix PHP Deprecated Warning with Link module.

  • v1.11.9 Changes

    April 17, 2019

    🔒 This resolves BACKDROP-SA-CORE-2019-009, a cross-site scripting vulnerability. No other changes are included.

    ⚡️ Update information:

    • 🚀 It will be necessary to run the update script (located at /update.php) for this release.
    • 🚀 No changes have been made to the .htaccess, robots.txt or default settings.php files in this release, so upgrading custom versions of those files is not necessary.

  • v1.11.8 Changes

    March 20, 2019

    🔒 This resolves BACKDROP-SA-CORE-2019-008, a cross-site scripting vulnerability.

    ⚡️ Update information:

    • The database update script does not need to be run.
    • 🚀 No changes have been made to the .htaccess, robots.txt or default settings.php files in this release, so upgrading custom versions of those files is not necessary.
    • 🔒 No other changes have been made besides this security fix.