diff --git a/core/CHANGELOG.txt b/core/CHANGELOG.txt index 9d30bc4bfd..6ebe20488a 100644 --- a/core/CHANGELOG.txt +++ b/core/CHANGELOG.txt @@ -1,10 +1,14 @@ -Drupal 8.4.x, xxxx-xx-xx +Drupal 8.4.0, 2017-10-05 ------------------------ ### Drush users: Update to Drush 8.1.12 -[Versions of Drush earlier than 8.1.12 will not work with Drupal 8.4.x](https://www.drupal.org/node/2874827). -Update Drush to 8.1.12 before using it to update to Drupal core 8.4.x or you - will encounter fatal errors. +[Versions of Drush earlier than 8.1.12 will not work with Drupal +8.4.x](https://www.drupal.org/node/2874827). 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](https://www.drupal.org/node/2907224).) ### Updated browser requirements: Internet Explorer 9 and 10 no longer supported @@ -14,10 +18,11 @@ 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](https://www.drupal.org/docs/8/system-requirements/browser-requirements) +Additionally, Drupal 8's [browser requirements documentation +page](https://www.drupal.org/docs/8/system-requirements/browser-requirements) currently lists incorrect information regarding very outdated browser versions -such as Safari 5 and Firefox 5. [Clarifications to the browser policy and documentation](https://www.drupal.org/node/2390621) -are underway and we hope to finalize it before 8.4.0-rc1. +such as Safari 5 and Firefox 5. [Clarifications to the browser policy and +documentation](https://www.drupal.org/node/2390621) are underway. ### Known Issues @@ -25,19 +30,15 @@ are underway and we hope to finalize it before 8.4.0-rc1. 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. -* @todo: One such issue is with Drush https://www.drupal.org/node/2907224 -* [Modal tour tips provided by the Tour module are not displayed correctly](https://www.drupal.org/node/2898808) - because the third-party Joyride library has an incompatibility with jQuery 3. - Tour tips are no longer centered and may be displayed entirely off-screen for - many screen sizes. Work is underway on an upstream bug fix. -* Some sites that have files with 0 recorded usages may encounter - [validation errors when saving content referencing these files](https://www.drupal.org/node/2896480). - If your site's users report errors when saving content, you can - [set the `file.settings.make_unused_managed_files_temporary` setting to `true`](https://www.drupal.org/node/2891902), - but make sure you also set "Delete orphaned files" to "Never" on - `/admin/config/media/file-system` - to avoid permanent deletion of the affected files. -* @todo Some Symfony file handling thing https://www.drupal.org/node/2906030 + Known issues related to the Symfony update include: + * [Incompatibility with Drush 8.1.11 and earlier](https://www.drupal.org/node/2874827). + * [Other error messages with Drush 8.1.12 and higher](https://www.drupal.org/node/2907224). + * [Certain file uploads may fail silently](https://www.drupal.org/node/2906030) + due to a Symfony 3 backwards compatibility break if they used the `$deep` + parameter (which was already deprecated in Symfony 2.8 and is removed + in Symfony 3.0. *Check any custom file upload code* that may have used + the deprecated parameter and [update it according to the API change + record](https://www.drupal.org/node/2743809). ### Important fixes since 8.3.x @@ -49,7 +50,10 @@ Drupal 8 has several longstanding [file usage tracking bugs](https://www.drupal.org/node/2821423). To prevent further data loss, Drupal 8.4 has [disabled the automatic deletion of files with no known remaining usages](https://www.drupal.org/node/2801777). 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. +files erroneously reporting 0 usages are not deleted while in use. Additionally, +an issue with [validation errors when saving content referencing these +files](https://www.drupal.org/node/2896480) has also been resolved. + [The change record explains how sites can opt back into marking files temporary](https://www.drupal.org/node/2891902). 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 @@ -96,18 +100,18 @@ is underway. #### Other critical improvements -When nodes got deleted, Menu UI module deleted their menu items. However menu -items may exist if Menu UI module is not enabled and could also be attached -to entities other than nodes. Menu item deletion when referenced entities -are deleted [is now performed by the Custom Menu Links module](https://www.drupal.org/node/2350797) -covering the previously missing cases. - -A race condition occured in the Batch API when using fastcgi. The Batch API now -ensures that [the current batch state is written completely to the database before starting the next batch](https://www.drupal.org/node/2851111). - -When uninstalling modules, empty fields were left behind to be purged. However -without the field definitions, it was not possible to purge them anymore. -[Empty field deletion is now performed immediately](https://www.drupal.org/node/2884202). +* When nodes were deleted, Menu UI module deleted their menu items. However, menu + items may exist even whenm Menu UI module is not enabled and can also be attached + to entities other than nodes. Therefore, menu item cleanup on entity deletetion + [is now performed by the Custom Menu Links module](https://www.drupal.org/node/2350797) + instead, covering the previously missing cases. A related issue that [broke module uninstallation + for some modules providing menu items for certain entity forms](https://www.drupal.org/node/2907654) has also been resolved. +* A race condition occured in the Batch API when using fastcgi. The Batch API now + ensures that [the current batch state is written completely to the database before + starting the next batch](https://www.drupal.org/node/2851111). +* When uninstalling modules, empty fields were left behind to be purged. However, + without the field definitions, it was not possible to purge them anymore. + [Empty field deletion is now performed immediately](https://www.drupal.org/node/2884202). ### New stable modules @@ -243,13 +247,12 @@ either Content Moderation and/or some other module that requires it. ### Performance and scalability improvements -* Drupal 8 aims to do effective caching at various levels, however this - resulted in exessively growing cache tables with many tens of thousands of - entries (even hundreds of thousands), and gigabytes in size. +* Drupal 8 caches at various different levels for more effective caching. However, this + resulted in exessively growing cache tables with tens or hundreds of thousands of + entries, and gigabytes in size. [A new limit of 5000 rows per cache bin was introduced to limit this growth](https://www.drupal.org/node/2526150). * The internal page cache now [has a dedicated cache bin](https://www.drupal.org/node/2889603) - distinct from the rest of the render cache (a significant scalability - improvement). + distinct from the rest of the render cache for improved scalability. * The service collector pattern instantiates all services it collects, which is expensive, and unnecessary for some use cases. For those use cases, a [new service ID collector](https://www.drupal.org/node/2472337) pattern was added. The theme negotiator was updated to use it. [See the change record for information about how to use the service ID collector](https://www.drupal.org/node/2598944) for improved performance. @@ -259,8 +262,8 @@ either Content Moderation and/or some other module that requires it. a particular site's usecase. [See the change record to learn how to access this new setting](https://www.drupal.org/node/2886836). * If there are no status messages, the corresponding rendering - [is now skipped](https://www.drupal.org/node/2853509). On simple sites, this - can result in a 10% improvement when there are no messages! + [is now skipped](https://www.drupal.org/node/2853509). On simple sites that use the + Dynamic Page Cache (on by default), this can result in a 10% improvement when there are no messages! * [Optimized the early Drupal installer](https://www.drupal.org/node/2872611) to check whether any themes are installed first before invoking an unnecessary function, which improves Drupal install time measurably for @@ -314,8 +317,11 @@ either Content Moderation and/or some other module that requires it. features numerous improvements, including better error reporting. See the [jQuery Core 3.0 Upgrade Guide](https://jquery.com/upgrade-guide/3.0/) for information on jQuery 3 backwards compatibility breaks that might affect the - JavaScript code in your modules, themes, and sites. Note that we may consider - rolling back this library update if the [bug affecting tours](https://www.drupal.org/node/2898808) is not resolved in time for Drupal 8.4.0-beta1. + JavaScript code in your modules, themes, and sites. +* The zurb/joyride library (used by the Tour module) has been + [updated to a development version higher than 2.1.0.1](https://www.drupal.org/node/2898808) + to resolve an upstream incompatibility with jQuery 3. We will update to Joyride 2.1.1 once + it is available with the needed fix. * [zendframework/zend-diactoros has been updated from 1.3.10 to 1.4.0](https://www.drupal.org/node/2874817). * [jQuery UI has been updated from 1.11.4 to 1.12.1](https://www.drupal.org/node/2809427). * [jQuery Once has been updated from 2.1.1 to 2.2.0](https://www.drupal.org/node/2899156). @@ -360,22 +366,15 @@ Drupal versions. [Drupal Upgrade](https://www.drupal.org/project/migrate_upgrade) contributed module. (See the [pull request to add support to Drush](https://github.com/drush-ops/drush/issues/2140).) -* [Added field plugin](https://www.drupal.org/node/2814949) to handle - migration of node reference field values from Drupal 6 to Drupal 8. -* [Added date field plugin](https://www.drupal.org/node/2566779) to handle - migration of CCK date fields in Drupal 6 to Drupal 8. -* [Renamed migration field plugins and classes](https://www.drupal.org/node/2683435) - referring to custom fields provided by the Drupal 6 CCK module, which was - replaced in Drupal 7 by the core Field API. [See the change record for more information about how this impacts your migration plugins](https://www.drupal.org/node/2751897). - The migration [classes extending from CCKFieldPluginBase are also deprecated - in favor of field migration classes](https://www.drupal.org/node/2833206). -* Field type mapping became easier with - [default implementations of getFieldFormatterMap() and processFieldValues()](https://www.drupal.org/node/2896507). -* Conflicting text field processing settings [are now identified and logged](https://www.drupal.org/node/2842222). - To support this change, [a new ProcessField plugin was added](https://www.drupal.org/node/2893061) - to dynamically compute the migrated field type. -* [The field instance source plugin got refactored](https://www.drupal.org/node/2891935), - resulting in changed migration template keys. +* This release includes numerous developer experience for Migrate, including [deprecating outdated references to "CCK"](https://www.drupal.org/node/2751897), + [simplifying field type mapping](https://www.drupal.org/node/2896507), and many other API improvements. +* Conflicting text field processing settings [are now identified and + logged](https://www.drupal.org/node/2842222) to avoid security + or data integrity issues with the migration of plain and formatted text fields. +* Automatic redirects are now + [added for node paths that are not valid anymore due to translation merges](https://www.drupal.org/node/2850085). +* @todo [Migration for forum and article comments: duplicate comment types and incorrect comment_entity_statistics](https://www.drupal.org/node/2853872) +* @todo [File migration from D6 to D8 version using Migrate Drupal UI](https://www.drupal.org/node/2907233) #### Content Moderation ([beta stability](https://www.drupal.org/core/experimental#beta)) @@ -449,7 +448,6 @@ 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](https://www.drupal.org/node/2739075).) - Drupal 8.3.0, 2017-04-05 ------------------------ - Added modules: