Ckeditor 4 vs 57/30/2023 Backwards compatibility is provided by the new phpass module that will be installed on existing sites via an update. block/ĭrupal now uses the default PHP password_hash() and password_verify() functions in order to store and verify passwords securely. admin/structure/block/block-content is now /admin/content/block and available from the Blocks tab from the Content menu. admin/structure/block/block-content/types is now /admin/structure/block-content and available as Block types from the Structure menu. The paths to manage custom-block types and block content (formerly custom blocks) have changed. Some "notice" level user events are now logged at the lower-severity "info" level. The settings are stored within the state table (as opposed to configuration), so the settings cannot be accidentally committed and uploaded to production environments. Modules or install profiles that provide default editor configurations may need to update their shipped config.Ī new “Development settings” page at /admin/config/development/settings that contains Twig development settings, as well as the ability to disable various caches. The CKEditor code block is now configurable, allowing the list of languages that can be input to be changed in the editor configuration. This allows the date/time to display as a time difference (e.g. The timestamp default formatter has a setting "Display as a time difference. The view that ships with the File module has been updated to include the operations field. An operations field can be added to views on File entities to add a delete button. Users with sufficient permissions can view, revert and delete block content revisions.Ĭontent administrators can be given permission to delete any file, rather than just files they created. The permissions allow for control by custom block type and access to block administration pages.īlock content entities now have a UI for managing revisions. Administrators can delegate the management of custom block content to users without granting the 'administer blocks' permission. New permissions for managing custom blocks. Existing sites will continue to use the public files location.Ī new setting $settings in has been added to configure the behaviour of admin/reports/status/php. It can be set in settings.php via $settings. The file location for Drupal's asset aggregation system is now configurable. Sites using nginx and php-fpm may need to update their nf for changes to CSS and JavaScript aggregation. This is configurable in and site owners should update their copy of the file to include the section. This brings the value in line with industry standards.ĭrupal adds 'Samesite: Lax' as a session cookie attribute by default. htaccess file now caches all files for one year instead of two weeks. htaccess files with this change to avoid duplicate headers. This prevents duplicate headers in some configurations of Apache. htaccess file now unsets the X-Content-Type-Options header before setting it again. The migration paths from Drupal 6 and Drupal 7 to Drupal 10 will remain supported throughout Drupal 10's release cycle. You must review each text format editor condition.ĭrupal 6 and 7 users can continue to migrate to Drupal 10.1. Upgrading from CKEditor 4 to 5 is a manual process. See the recommendations for CKEditor for details. Most Drupal sites using CKEditor 4 should upgrade to CKEditor 5. ![]() Sites using CKEditor 4 should upgrade to CKEditor 5 in Drupal 9.4 or 9.5 before updating to Drupal 10 ![]() In general, sites should update to the most recent release of their current major branch before updating to the next major release. The data upgrade path from CKEditor 4 to CKEditor 5 is not available before Drupal 9.4.4. All core updates added before 9.4.0 have been removed. Sites must update to at least Drupal 9.4.4 before upgrading to Drupal 10ĭrupal sites running 9.3.x or earlier versions must first update to 9.4.4 or later before updating to Drupal 10. Sites on Drupal 8 or a Drupal 9 version earlier than 9.5.x should upgrade to a supported release as soon as possible. ![]() Drupal 10.0.x will continue to have security support until December 2023.ĭrupal 9.4.x no longer receives security support. Translators can review the latest translation status on .ĭrupal 10.1.x contains new features, and should be the target for new site development. This release may include string changes and additions. This is according to Drupal core's backward compatibility and experimental module policies. If so, contributed and custom modules and themes may need updating. It does not not break backward compatibility (BC) for public APIs.There may be changes in internal APIs and experimental modules. This minor release provides improvements and new functionality. Learn more about Drupal 9 and the Drupal core release cycle. This is a minor version (feature release) of Drupal 10 and is ready for use on production sites.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |