Jelenlegi hely

Drupal.org

Feliratkozás Drupal.org hírcsatorna csatornájára
Frissítve: 3 nap 1 óra

drupal 8.4.0

2017, október 4 - 21:44
Release notesDrush users: Update to Drush 8.1.12

Versions of Drush earlier than 8.1.12 will not work with Drupal 8.4.x. Update Drush to 8.1.12 or higher before using it to update to Drupal core 8.4.x or you will encounter fatal errors that prevent updates from running. (Drush 8.1.12 and 8.1.13 will successfully update Drupal 8.3.x to 8.4.0, but users may still see other error messages after updates have run.)

Updated browser requirements: Internet Explorer 9 and 10 no longer supported

In April 2017, Microsoft discontinued all support for Internet Explorer 9 and 10. Therefore, Drupal 8.4 has as well. Drupal 8.4 still mostly works in these browser versions, but bugs that affect them only will no longer be fixed, and existing workarounds for them will be removed beginning in Drupal 8.5.

Additionally, Drupal 8's browser requirements documentation page currently lists incorrect information regarding very outdated browser versions such as Safari 5 and Firefox 5. Clarifications to the browser policy and documentation are underway.

Known Issues

Drupal 8.4.0 includes major version updates for two dependencies: Symfony 3.2 and jQuery 3. Both updates may introduce backwards compatibility issues for some sites or modules, so test carefully. For more information, see the "Third-party library updates" section below. Known issues related to the Symfony update include:

Important fixes since 8.3.x

Translators should take note of several string additions and changes since the last release.

File usage tracking

Drupal 8 has several longstanding file usage tracking bugs. To prevent further data loss, Drupal 8.4 has disabled the automatic deletion of files with no known remaining usages. This will result of the accumulation of unused files on sites, but ensures that files erroneously reporting 0 usages are not deleted while in use. Additionally, an issue with validation errors when saving content referencing these files has also been resolved.

The change record explains how sites can opt back into marking files temporary. If you choose to enable the setting, you can also set "Delete orphaned files" to "Never" on /admin/config/media/file-system to avoid permanent deletion of the affected files.

While the files will no longer be deleted by default, file usage is still not tracked correctly in several scenarios, regardless of the setting. Discussion on how to evolve the file usage tracking system is underway.

Configuration export sorting Revision data integrity fixes Other critical improvements New stable modules

The following modules, previously considered experimental, are now stable and safe for use on production sites, with full backwards compatibility and upgrade paths from 8.4.0 to future releases:

Datetime Range

The Datetime Range module provides a field type that allows end dates to support contributed modules like Calendar. This stable release is backwards-compatible with the 8.3.x experimental version and shares a consistent API with other Datetime fields.

Future releases may improve Views support, usability, Datetime Range field validation, and REST support. For bugs or feature requests for this module, see the core Datetime issue queue.

Layout Discovery

The Layout Discovery module provides an API for modules or themes to register layouts as well as five common layouts. Providing this API in core enables core and contributed layout solutions to be compatible with each other. This stable release is backwards-compatible with the 8.3.x experimental version and introduces support for per-region attributes.

Media

The new core Media module provides an API for reusable media entities and references. It is based on the contributed Media Entity module.

Since there is a rich ecosystem of Drupal contributed modules built on Media Entity, the top priority for this release is to provide a stable core API and data model for a smoother transition for these modules. Developers and expert site builders can now add Media as a dependency. Work is underway to provide an update path for existing sites' Media Entity data and to port existing contributed modules to the improved core API. Both versions cannot be used at the same time, so we also prevent the 1.x version of the contributed Media Entity module from being enabled at the same time as the core Media module.

Note that the core Media module is currently marked hidden and will not appear on the 'Extend' (module administration) page. (Enabling a contributed module that depends on the core Media module will also enable Media automatically.) The module will be displayed to site builders normally once user experience issues with it are resolved. Similarly, the REST API and normalizations for Media is not final and support for decoupled applications will also be improved in a future release.

Inline Form Errors

The Inline Form Errors module provides a summary of any validation errors at the top of a form and places the individual error messages next to the form elements themselves. This helps users understand which entries need to be fixed, and how. Inline Form Errors was provided as an experimental module from Drupal 8.0.0 on, but it is now stable and polished enough for production use. See the core Inline Form Errors module issue queue for outstanding issues.

Workflows

The Workflows module provides an abstract system of states (like Draft, Archived, and Published) and transitions between them. Workflows can be used by modules that implement non-publishing workflows (such as for users or products) as well as content publishing workflows.

Drupal 8.4 introduces a final significant backwards compatibility and data model break for this module, moving responsibility for workflow states and transitions from the Workflow entity to the Workflow type plugin. Read Workflow type plugins are now responsible for state and transition schema for full details on the API and data model changes related to this fix. Now that this change is complete, the Workflows module became stable!

While the module can be installed as-is, it is not useful in itself without either Content Moderation and/or some other module that requires it.

Content authoring and site administration improvements REST and API-first improvements Performance and scalability improvements Developer experience improvements Automated testing improvements Third-party library updates Experimental modules Migrate (beta stability)

Migrate provides a general API for migrations. It will be considered completely stable once all issues tagged Migrate critical are resolved.

  • This release includes numerous developer experience improvements for Migrate and Migrate Drupal, including deprecating outdated references to "CCK", simplifying field type mapping, renaming several plugins to better capture their and many other API and documentation improvements. (Backwards compatibility is provided in each case Migrate is in beta.)
  • Added the ability to provide the source module to migrations to help site owners review what data is being migrating, especially for cases where the source and destination module are not the same (for example if a new Drupal 8 module replaces old functionality.
Migrate Drupal and Migrate Drupal UI (alpha stability)

Migrate Drupal module provides API support for Drupal-to-Drupal migrations, and Migrate Drupal UI offers a simple user interface to run migrations from older Drupal versions.

Content Moderation (beta stability)

Content Moderation allows workflows from the Workflows module to be applied to content. Notable improvements in this release:

As per the experimental module process, there were some backwards-incompatible changes since Drupal 8.3.x. Experimental modules do not offer a supported upgrade path, but an unofficial upgrade path is available.

Field Layout (alpha stability)

This module provides the ability for site builders to rearrange fields on content types, block types, etc. into new regions, for both the form and display, on the same forms provided by the normal field user interface. Field Layout has had several bugfixes since 8.3.0, but no significant changes. See the entity display layout roadmap for the next steps for this module, which needs to become stable by 8.5.0 to remain in Drupal core.

Settings Tray (beta stability)

The Settings Tray module allows configuring page elements such as blocks and menus from the frontend of your site. Settings Tray has improved significantly since Drupal 8.3.0, including numerous user interaction and accessibility fixes, better compatibility with stable core modules like Quick Edit and Contextual Links, added documentation, and a CSS reset for better themer experience.

The module reached beta stability following completion of moving the off-canvas dialog renderer into a core component, and renaming the machine name of the module to settings_tray, to match its user-facing name. We hope to make Settings Tray stable by 8.5.0. To track progress, see the "outside in" roadmap issue.

Place Blocks (alpha stability)

This feature allows the user to place a block on any page and see the region where it will be displayed, without having to navigate to a backend administration form. 8.4.0-alpha1 was the deadline for Place Blocks to stabilize, but the module's roadmap was not completed. Furthermore, the module is not intended as a standalone feature and should instead be a built-in part of the Block system. For these reasons, Place Blocks module has been marked hidden in this release (it can still be enabled with Drush). The Place Blocks module itself will be turned into an empty module in Drupal 8.5.x, since ideally the core Block system will offer the same functionality in 8.5.0 (though this depends on completion of a core patch for the feature.)

Download Size md5 hash drupal-8.4.0.tar.gz 12.76 MB 074795a2f5fc0b599a7dcfb9d1fb03f5 drupal-8.4.0.zip 21.14 MB 60ed1b57a672366eaa54335621ec89fe Last updated: 4 Oct 2017 at 19:44 UTCOfficial release from tag: 8.4.0Core compatibility: 8.xRelease type: Bug fixesNew featuresShort description: The latest minor release includes new features and backwards-compatible API improvements, and is ready for new development and production sites.Packaged Git sha1: abfe77673a5a6194ef13600e05f1ca2c5dd59db8
Kategóriák: Informatika

drupal 8.4.0-rc2

2017, szeptember 20 - 14:48
Release notes

This is a release candidate for the next feature release of Drupal 8. Release candidates are not supported for production sites, but they are intended for widespread testing in preparation for the upcoming stable release. More information on release candidates.

This minor release provides new improvements and functionality without breaking backward compatibility (BC) for public APIs. There may be changes in internal APIs and experimental modules that require updates to contributed and custom modules and themes per Drupal core's backwards compatibility and experimental module policies.

For a full list of other API and feature additions included in the 8.4.0 release candidate compared to 8.3.x, see the 8.4.0-alpha1, 8.4.0-beta1, and 8.4.0-rc1 release notes.

Drush users: Update to Drush 8.1.12

Versions of Drush earlier than 8.1.12 will not work with Drupal 8.4.x. Update Drush to 8.1.12 before using it to update to Drupal core 8.4.x or you will encounter fatal errors.

Known issues Major version updates for dependencies

Drupal 8.4.0-alpha1 includes major version updates for two dependencies: Symfony 3.2 and jQuery 3. Both updates may introduce backwards compatibility issues for some sites or modules, so test carefully.

File usage tracking

Drupal 8 has several longstanding file usage tracking bugs. To prevent further data loss, Drupal 8.4 has disabled the automatic deletion of files with no known remaining usages. This will result of the accumulation of unused files on sites, but ensures that files erroneously reporting 0 usages are not deleted while in use. The change record explains how sites can opt back into marking files temporary. If you choose to enable the setting, you can also set "Delete orphaned files" to "Never" on /admin/config/media/file-system to avoid permanent deletion of the affected files.

While the files will no longer be deleted by default, file usage is still not tracked correctly in several scenarios, regardless of the setting. Discussion on how to evolve the file usage tracking system is underway.

Revision data integrity hotfixes

Drupal 8.4 includes numerous hotfixes for data integrity issues related to revisions, including #2766957: Forward revisions + translation UI can result in forked draft revisions. This issue prevents data loss with multiple draft translations by restricting Drupal to only have one draft translation at a time (so multiple translators cannot have draft translations of the same content in parallel). #2860097: Only having one default revision per entity forces translations to be kept in sync is the issue to allow multiple draft translations again without data loss.

Changes since 8.4.0-rc1: Download Size md5 hash drupal-8.4.0-rc2.tar.gz 12.76 MB 50730355dd1a82d988e484c2b4eff422 drupal-8.4.0-rc2.zip 21.25 MB c7d43354145662cd581e089d51049ea0 Last updated: 20 Sep 2017 at 12:44 UTCOfficial release from tag: 8.4.0-rc2Core compatibility: 8.xRelease type: Bug fixesShort description: Release candidates are not supported for production sites, but they are intended for widespread testing in preparation for the upcoming stable release.Packaged Git sha1: a5e98193108c1a69d536a48e5154aa84fb9e57b6
Kategóriák: Informatika

drupal 8.4.0-rc1

2017, szeptember 6 - 23:19
Release notes

This is a release candidate for the next feature release of Drupal 8. Release candidates are not supported for production sites, but they are intended for widespread testing in preparation for the upcoming stable release. More information on release candidates.

This minor release provides new improvements and functionality without breaking backward compatibility (BC) for public APIs. There may be changes in internal APIs and experimental modules that require updates to contributed and custom modules and themes per Drupal core's backwards compatibility and experimental module policies.

For a full list of other API and feature additions included in the 8.4.0 release candidate compared to 8.3.x, see the 8.4.0-alpha1 and 8.4.0-beta1 release notes.

Drush users: Update to Drush 8.1.12

Versions of Drush earlier than 8.1.12 will not work with Drupal 8.4.x. Update Drush to 8.1.12 before using it to update to Drupal core 8.4.x or you will encounter fatal errors.

Known issues Major version updates for dependencies

Drupal 8.4.0-alpha1 includes major version updates for two dependencies: Symfony 3.2 and jQuery 3. Both updates may introduce backwards compatibility issues for some sites or modules, so test carefully.

File usage tracking

Drupal 8 has several longstanding file usage tracking bugs. To prevent further data loss, Drupal 8.4 has disabled the automatic deletion of files with no known remaining usages. This will result of the accumulation of unused files on sites, but ensures that files erroneously reporting 0 usages are not deleted while in use. The change record explains how sites can opt back into marking files temporary. If you choose to enable the setting, you can also set "Delete orphaned files" to "Never" on /admin/config/media/file-system to avoid permanent deletion of the affected files.

While the files will no longer be deleted by default, file usage is still not tracked correctly in several scenarios, regardless of the setting. Discussion on how to evolve the file usage tracking system is underway.

Revision data integrity hotfixes

Drupal 8.4 includes numerous hotfixes for data integrity issues related to revisions, including #2766957: Forward revisions + translation UI can result in forked draft revisions. This issue prevents data loss with multiple draft translations by restricting Drupal to only have one draft translation at a time (so multiple translators cannot have draft translations of the same content in parallel). #2860097: Only having one default revision per entity forces translations to be kept in sync is the issue to allow multiple draft translations again without data loss.

Important fixes in this release Status of the Workflows and Content Moderation modules

The Workflows module is now stable! By itself, Workflows does not provide new functionality for the site builder, but stabilizing Workflows is an important step toward providing content moderation as a part of Drupal core.

The Content Moderation module is still considered experimental and its status for 8.4.0 is still being reviewed.

Settings Tray module renamed and now in beta

The experimental Settings Tray module's machine name has been changed from outside_in to settings_tray to match user-facing labels. If you have Settings Tray installed on your site, you must uninstall it before upgrading to 8.4.0-rc1 to avoid fatal errors. You can simply re-enable it afterward; since the Settings Tray module does not store any data or configuration, this should not affect your site.) Following this rename, Settings Tray is now considered beta stability.

All changes since 8.4.0-beta1 Download Size md5 hash drupal-8.4.0-rc1.tar.gz 12.74 MB 28f7b802ddf81f6a5f50a1400766d913 drupal-8.4.0-rc1.zip 21.19 MB 528f34f4d7e30361a2bedce12d36ea75 Last updated: 6 Sep 2017 at 21:24 UTCOfficial release from tag: 8.4.0-rc1Core compatibility: 8.xRelease type: Bug fixesNew featuresShort description: Release candidates are not supported for production sites, but they are intended for widespread testing in preparation for the upcoming stable release.Packaged Git sha1: 5046d2c4d8dad7144fead0bc9e61e2ae9788fcd6
Kategóriák: Informatika

drupal 8.4.0-beta1

2017, augusztus 17 - 19:44
Release notes

This is a beta release for the next release of Drupal 8. Betas are good testing targets for developers and site builders who are comfortable reporting (and where possible, fixing) their own bugs. Beta releases are not recommended for non-technical users, nor for production websites. More information on beta releases.

This minor release provides new improvements and functionality without breaking backward compatibility (BC) for public APIs. There may be changes in internal APIs and experimental modules that require updates to contributed and custom modules and themes per Drupal core's backwards compatibility and experimental module policies.

For a full list of other API and feature additions included in the 8.4.0 beta compared to 8.3.x, see the 8.4.0-alpha1 release notes.

The following important issues have been resolved since 8.4.0-alpha1 (in addition to the numerous fixes listed at the end of this post).

Known issues

Drupal 8.4.0-alpha1 includes major version updates for two dependencies: Symfony 3.2 and jQuery 3. Both updates may introduce backwards compatibility issues for some sites or modules, so test carefully. For more information, see the "Third-party library updates" section of the 8.4.0-alpha1 release notes and the "Updated third-party libraries" section below.

Important fixes in this release

The following critical and major bug fixes resolve several problems that affected file usage tracking and translated content, prevented content creation in the Content Moderation module, affected user experience in multiple interfaces, and triggered race conditions in the Batch system, among others.

User and developer experience improvements

The following improvements have been added to this beta (in addition to those that were already included in 8.4.0-alpha1).

Experimental module improvements

This beta release includes several improvements for the experimental modules in 8.4.0-alpha1.

Migrate Workflows and Content Moderation

The Workflows and Content Moderation modules include numerous fixes since 8.4.0-alpha1. Workflows has now entered the release candidate phase. We expect that Workflows may be available as stable modules in Drupal 8.4.0 unless we identify serious bugs or architectural issues. Content Moderation remains beta stability, as we have identified a critical feature gap because there is no way to find moderated content that requires added views integration for Content Moderation as well as a feature addition to Views itself.

Settings Tray

The 8.4.0-beta release includes numerous Settings Tray fixes since 8.4.0-alpha1. Settings Tray remains at alpha stability but only three unresolved issues remain that block beta stability:

Settings Tray improvements since 8.4.0-alpha1 include:

Updated third-party libraries All changes since 8.4.0-alpha1 Download Size md5 hash drupal-8.4.0-beta1.tar.gz 12.72 MB 8df2388ddd79d63d4b506463c1e173f8 drupal-8.4.0-beta1.zip 21.17 MB 95dbf397cd2322fb7025a73225fcbc5d Last updated: 17 Aug 2017 at 17:49 UTCOfficial release from tag: 8.4.0-beta1Core compatibility: 8.xRelease type: Bug fixesNew featuresShort description: Betas are good testing targets for developers and site builders who are comfortable reporting (and where possible, fixing) their own bugs. Beta releases are not recommended for non-technical users, nor for production websites.Packaged Git sha1: 53841f08f1bec76af867f5c473b130913cb81eb4
Kategóriák: Informatika

drupal 8.3.7

2017, augusztus 16 - 19:16
Release notes

Maintenance and security release of the Drupal 8 series.

This release fixes security vulnerabilities. Sites are urged to upgrade immediately after reading the notes below and the security announcements:

No other fixes are included.

No changes have been made to the .htaccess, web.config, robots.txt or default settings.php files in this release, so upgrading custom versions of those files is not necessary.

Known issues Updating from versions older than 8.3.0

We've received reports of the following issues with the 8.3.0 release that may affect those updating from older versions of Drupal 8:

  • A few sites have reported #2869449: PluginNotFound exception after update to Drupal 8.3 where the plugin name mentioned in the exception may vary. Administrators of affected sites should check the issue queues of contributed modules in use. Comment on #2869449 if necessary.
  • Sites that have the HAL module enabled and are upgrading from 8.1.x have encountered #2867444: Configuration schema errors whilst updating to 8.3.0. Possible workarounds include updating to 8.2.7 first and then to 8.3.0, or (for sites using Drush) updating to Drush 8.1.10. (Note that 8.1.x has been end-of-life since September 2016, so we generally do not provide full support for updates that skip minor releases.)
File usage tracking causes unexpected file deletion

Drupal 8 currently has a number of known issues related to incorrect tracking of file usage, which can result in files being unexpectedly deleted from a site. Site owners experiencing unexplained file loss should consider setting "Delete orphaned files" to "Never" on /admin/config/media/file-system until these issues are resolved, and note the following issues:

Search the issue queue for all known issues.

Download Size md5 hash drupal-8.3.7.tar.gz 12.15 MB e7b1f382d6bd2b18d4b4aca01d335bc0 drupal-8.3.7.zip 20.13 MB f006be47ad27f8f1e90bc79bd28e0c35 Last updated: 16 Aug 2017 at 17:18 UTCOfficial release from tag: 8.3.7Core compatibility: 8.xRelease type: Security updateShort description: The next patch release of Drupal 8 is ready for new development and use on production sites.Packaged Git sha1: d86c3b65ee89ad7a2b4e53aafcff12a185aa749b
Kategóriák: Informatika

drupal 8.4.0-alpha1

2017, augusztus 3 - 22:06
Release notes

This is an alpha release for the next feature release of Drupal 8. Alphas are good testing targets for developers and site builders who are comfortable reporting (and where possible, fixing) their own bugs. Alpha releases are not recommended for non-technical users, nor for production websites. More information on alpha and beta releases.

This minor release provides new improvements and functionality without breaking backward compatibility (BC) for public APIs. there may be changes in internal APIs and experimental modules that require updates to contributed and custom modules and themes per Drupal core's backwards compatibility and experimental module policies. Also see the change records for the 8.4.x branch.

Drush users: Update to Drush 8.1.12

Versions of Drush earlier than 8.1.12 will not work with Drupal 8.4.x. Update Drush to 8.1.12 before using it to update to Drupal core 8.4.x or you will encounter fatal errors.

Updated browser requirements: Internet Explorer 9 and 10 no longer supported

In April 2017, Microsoft discontinued all support for Internet Explorer 9 and 10. Therefore, Drupal 8.4 has as well. Drupal 8.4 still mostly works in these browser versions, but bugs that affect them only will no longer be fixed, and existing workarounds for them will be removed beginning in Drupal 8.5.

Additionally, Drupal 8's browser requirements documentation page currently lists incorrect information regarding very outdated browser versions such as Safari 5 and Firefox 5. Clarifications to the browser policy and documentation are underway and we hope to finalize it before 8.4.0-rc1.

Known Issues Important fixes since 8.3.x

Translators should take note of several string additions and changes since the last release.

File usage tracking

Drupal 8 has several longstanding file usage tracking bugs. To prevent further data loss, Drupal 8.4 has disabled the automatic deletion of files with no known remaining usages. This will result of the accumulation of unused files on sites, but ensures that files erroneously reporting 0 usages are not deleted while in use. The change record explains how sites can opt back into marking files temporary. If you choose to enable the setting, you can also set "Delete orphaned files" to "Never" on /admin/config/media/file-system to avoid permanent deletion of the affected files.

While the files will no longer be deleted by default, file usage is still not tracked correctly in several scenarios, regardless of the setting. Discussion on how to evolve the file usage tracking system is underway.

Configuration export sorting Revision data integrity fixes New stable modules

The following modules, previously considered experimental, are now stable and safe for use on production sites, with full backwards compatibility and upgrade paths from 8.4.0 to future releases:

Datetime Range

The Datetime Range module provides a field type that allows end dates to support contributed modules like Calendar. This stable release is backwards-compatible with the 8.3.x experimental version and shares a consistent API with other Datetime fields.

Future releases may improve Views support, usability, Datetime Range field validation, and REST support. For bugs or feature requests for this module, see the core Datetime issue queue.

Layout Discovery

The Layout Discovery module provides an API for modules or themes to register layouts as well as five common layouts. Providing this API in core enables core and contributed layout solutions to be compatible with each other. This stable release is backwards-compatible with the 8.3.x experimental version and introduces support for per-region attributes.

Media

The new core Media module provides an API for reusable media entities and references. It is based on the contributed Media Entity module.

Since there is a rich ecosystem of Drupal contributed modules built on Media Entity, the top priority for this release is to provide a stable core API and data model for a smoother transition for these modules. Developers and expert site builders can now add Media as a dependency. Work is underway to provide an update path for existing sites' Media Entity data and to port existing contributed modules to the refined core API.

Note that the core Media module is currently marked hidden and will not appear on the 'Extend' (module administration) page. (Enabling a contributed module that depends on the core Media module will also enable Media automatically.) The module will be displayed to site builders normally once user experience issues with it are resolved in a future release.

Similarly, the REST API and normalizations for Media is not final and support for decoupled applications will be improved in a future release.

Inline Form Errors

The Inline Form Errors module provides a summary of any validation errors at the top of a form and places the individual error messages next to the form elements themselves. This helps users understand which entries need to be fixed, and how. Inline Form Errors was provided as an experimental module from Drupal 8.0.0 on, but it is now stable and polished enough for production use. See the core Inline Form Errors module issue queue for outstanding issues.

Content authoring and site administration improvements REST and API-first improvements Performance and scalability improvements Developer experience improvements Automated testing improvements Third-party library updates Experimental modules Migrate (beta stability)

Migrate provides a general API for migrations. It will be considered completely stable once all issues tagged Migrate critical are resolved.

Migrate Drupal and Migrate Drupal UI (alpha stability)

Migrate Drupal module provides API support for Drupal-to-Drupal migrations, and Migrate Drupal UI offers a simple user interface to run migrations from older Drupal versions.

Workflows (beta stability)

The Workflows module provides an abstract system of states (like Draft, Archived, and Published) and transitions between them. Workflows can be used by modules that implement non-publishing workflows (such as for users or products) as well as content publishing workflows.

Drupal 8.4 introduces a final significant backwards compatibility and data model break for this module, moving responsibility for workflow states and transitions from the Workflow entity to the Workflow type plugin. Read Workflow type plugins are now responsible for state and transition schema for full details on the API and data model changes related to this fix. Now that this change is complete, the Workflows module has reached beta stability, and it may furthermore be marked stable in time for Drupal 8.4.0!

Content Moderation (beta stability)

Content Moderation allows workflows from the Workflows module to be applied to content. Content Moderation has beta stability in 8.4.0-alpha1, but may become stable in time for 8.4.0! Notable improvements in this release:

Field Layout (alpha stability)

This module provides the ability for site builders to rearrange fields on content types, block types, etc. into new regions, for both the form and display, on the same forms provided by the normal field user interface. Field Layout has had several bugfixes since 8.3.0, but no significant changes. See the entity display layout roadmap for the next steps for this module, which needs to become stable by 8.5.0 to remain in Drupal core.

Settings Tray (alpha stability)

The Settings Tray module allows configuring page elements such as blocks and menus from the frontend of your site. Settings Tray has improved significantly since Drupal 8.3.0. The goal for this release is to get Settings Tray to beta stability. Only two issues remain before that milestone: to move the off-canvas dialog renderer into a core component, and to rename the machine name of the module to settings_tray, to match its user-facing name. We hope to make Settings Tray stable by 8.5.0. To track progress, see the "outside in" roadmap issue.

Place Blocks (alpha stability)

This feature allows the user to place a block on any page and see the region where it will be displayed, without having to navigate to a backend administration form. 8.4.0-alpha1 was the deadline for Place Blocks to stabilize, but the module's roadmap was not completed. Furthermore, the module is not intended as a standalone feature and should instead be a built-in part of the Block system. For these reasons, Place Blocks module has been marked hidden in this release (it can still be enabled with Drush). The Place Blocks module itself will be turned into an empty module in Drupal 8.5.x, since ideally the core Block system will offer the same functionality in 8.5.0 (though this depends on completion of a core patch for the feature.)

Download Size md5 hash drupal-8.4.0-alpha1.tar.gz 12.54 MB 540c951999e8cac74d1d5ff70a81157f drupal-8.4.0-alpha1.zip 21.01 MB 488777cf856c0b767034e6b2b05c35c5 Last updated: 3 Aug 2017 at 20:09 UTCOfficial release from tag: 8.4.0-alpha1Core compatibility: 8.xRelease type: Bug fixesNew featuresShort Description: Alpha releases are good testing targets for developers and site builders who are comfortable reporting (and where possible, fixing) their own bugs. Alpha releases are not recommended for non-technical users, nor for production websites.Packaged Git sha1: 3a50084b2128acc08e350e99c8108c513632ba7b
Kategóriák: Informatika

drupal 8.3.6

2017, augusztus 2 - 17:33
Release notes

This is a patch release of Drupal 8 and is ready for use on production sites. See the CHANGELOG.txt for a summary of changes and improvements since the last minor release. Learn more about Drupal 8.

This release only contains bug fixes, along with documentation and testing improvements. Translators should take note of a handful of minor string changes since the last release.

The following important issues are resolved in 8.3.6 (in addition to the dozens of other fixes listed at the end of this post):

Changes to the update process since Drupal 8.2.3

Beginning with 8.2.3, packaged Drupal releases no longer contain development PHP libraries. See Drupal 8 will no longer include dev dependencies in release packages for more information. See core/UPDATE.txt in the Drupal download for full instructions on how to update.

Known issues

There are no known regressions in this release.

Updating from versions older than 8.3.0

We've received reports of the following issues with the 8.3.0 release that may affect those updating from older versions of Drupal 8:

  • A few sites have reported #2869449: PluginNotFound exception after update to Drupal 8.3 where the plugin name mentioned in the exception may vary. Administrators of affected sites should check the issue queues of contributed modules in use. Comment on #2869449 if necessary.
  • Sites that have the HAL module enabled and are upgrading from 8.1.x have encountered #2867444: Configuration schema errors whilst updating to 8.3.0. Possible workarounds include updating to 8.2.7 first and then to 8.3.0, or (for sites using Drush) updating to Drush 8.1.10. (Note that 8.1.x has been end-of-life since September 2016, so we generally do not provide full support for updates that skip minor releases.)
File usage tracking causes unexpected file deletion

Drupal 8 currently has a number of known issues related to incorrect tracking of file usage, which can result in files being unexpectedly deleted from a site. Site owners experiencing unexplained file loss should consider setting "Delete orphaned files" to "Never" on /admin/config/media/file-system until these issues are resolved, and note the following issues:

Search the issue queue for all known issues.

Changes since 8.3.5: Download Size md5 hash drupal-8.3.6.tar.gz 12.15 MB de7ceedf9391c4b52c1c5a7f66809129 drupal-8.3.6.zip 20.13 MB e973014a096274b2464ac5cbc14874c9 Last updated: 2 Aug 2017 at 15:34 UTCOfficial release from tag: 8.3.6Core compatibility: 8.xRelease type: Bug fixesShort Description: The next patch release of Drupal 8 is ready for new development and use on production sites.Packaged Git sha1: 37cedd6207b31894cf42a371419d38c81a23b0ee
Kategóriák: Informatika

drupal 8.5.x-dev

2017, július 28 - 20:33
Download Size md5 hash drupal-8.5.x-dev.tar.gz 13.67 MB ca894fa7565b7603506837103102b30b drupal-8.5.x-dev.zip 23.02 MB a19928a19502cede4c0fdaa9b60f4404 Last updated: 29 Jul 2017 at 22:14 UTCLast packaged version: 8.5.x-devRelease notes

Development release package for the 8.5.x release.

The 8.5.x branch is open for development and will now include the latest commits. Those interested in testing the development version of Drupal core should continue to work with the 8.4.x branch until the 8.4.0 release on October 5, 2017.

Development release from branch: 8.5.xCore compatibility: 8.xShort Description: Development release package for the 8.5.x release.Packaged Git sha1: 0d6d6736eb3afef399cf6c32ef40da4a751a15c5
Kategóriák: Informatika

drupal 8.3.5

2017, július 5 - 19:13
Release notes

This is a patch release of Drupal 8 and is ready for use on production sites. See the CHANGELOG.txt for a summary of changes and improvements since the last minor release. Learn more about Drupal 8.

This release only contains bug fixes, along with documentation and testing improvements. Translators should take note of a handful of minor string changes since the last release.

Changes to the update process since Drupal 8.2.3

Beginning with 8.2.3, packaged Drupal releases no longer contain development PHP libraries. See Drupal 8 will no longer include dev dependencies in release packages for more information. See UP.TXT in the Drupal download for full instructions on how to update.

Known issues

There are no known regressions in this release.

Updating from versions older than 8.3.0

We've received reports of the following issues with the 8.3.0 release that may affect those updating from older versions of Drupal 8:

  • A few sites have reported #2869449: PluginNotFound exception after update to Drupal 8.3 where the plugin name mentioned in the exception may vary. Administrators of affected sites should check the issue queues of contributed modules in use. Comment on #2869449 if necessary.
  • Sites that have the HAL module enabled and are upgrading from 8.1.x have encountered #2867444: Configuration schema errors whilst updating to 8.3.0. Possible workarounds include updating to 8.2.7 first and then to 8.3.0, or (for sites using Drush) updating to Drush 8.1.10. (Note that 8.1.x has been end-of-life since September 2016, so we generally do not provide full support for updates that skip minor releases.)
File usage tracking causes unexpected file deletion

Drupal 8 currently has a number of known issues related to incorrect tracking of file usage, which can result in files being unexpectedly deleted from a site. Site owners experiencing unexplained file loss should consider setting "Delete orphaned files" to "Never" on /admin/config/media/file-system until these issues are resolved, and note the following issues:

Search the issue queue for all known issues.

All changes since the last release Download Size md5 hash drupal-8.3.5.tar.gz 12.14 MB 23832fcfe0c6398727d24e582042f149 drupal-8.3.5.zip 20.12 MB 65fc6ac9bc72c566dfe259c8255e638c Last updated: 5 Jul 2017 at 17:14 UTCOfficial release from tag: 8.3.5Core compatibility: 8.xRelease type: Bug fixesShort Description: The next patch release of Drupal 8 is ready for new development and use on production sites.Packaged Git sha1: fa8e2513c4b75b13abe331114f6b30f33f846c63
Kategóriák: Informatika

Theme by me