Login Menu

Main menu

You are here

Crează un cont nou

Create a new account

Prenume *

Nume *

E-mail *

A valid e-mail address. All e-mails from the system will be sent to this address. The e-mail address is not made public and will only be used if you wish to receive a new password or wish to receive certain news or notifications by e-mail.

Data nasterii

Date

E.g., 2018-02-22

Verification *Type the characters you see in the picture; if you can't read them, submit the form and a new image will be generated. Not case sensitive. Switch to audio verification.

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. However, this release flags the node access system for automatic rebuild in order to update certain records for certain configurations. If a site includes a contributed or custom access control module and has multilingual functionality, administrators may see a prompt to rebuild node access. Be aware that this can take some time, but is necessary to ensure correct node access grants for all scenarios.

8.4.5 is also the final release of the 8.4.x series. 8.4.x will receive no further releases, so sites should prepare to update from 8.4.x to 8.5.x following the release of 8.5.0 on March 7 in order to continue getting bug and security fixes.

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 release also includes security fixes, so any sites already using 8.5.0-alpha1, 8.5.0-beta1, or 8.5.x-dev should update immediately!

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.

Sites on 8.4.x should update to 8.4.5 instead, which includes the same security fixes without any additional changes.

This release flags the node access system for automatic rebuild in order to update certain records for certain configurations. If a site includes a contributed or custom access control module and has multilingual functionality, administrators may see a prompt to rebuild node access. Be aware that this can take some time, but is necessary to ensure correct node access grants for all scenarios.

If you have a contributed or custom module that deals with pending revisions or loading different revisions, be aware that new validation was introduced to limit the allowed changes for untranslatable fields. See the related change record about this revision API change for details.

Important: If you have not already upgraded to 8.4.0, read the Drupal 8.4.0 release notes before upgrading to 8.5.0-beta1. Drupal 8.4 includes major version updates for Symfony, jQuery, and jQuery UI and is no longer compatible with older versions of Drush. Drupal 8.3 and earlier are no longer supported.

A bug in Symfony 3.4 causes parsing to fail on certain YAML files that contain comments. Drupal core is working around this issue, but custom services.yaml files or other custom YAML formats may need to implement their own fixes until the issue is fixed upstream in Symfony (hopefully before Drupal 8.5.0). See the Symfony 3.4 change record for details.

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:

There are no known regressions in this release.

Major changes since 7.56:

The file_get_file_references() API function has a new $check_access parameter. This defaults to TRUE for backwards compatibility reasons, but it is recommended that most code which calls this function pass in FALSE in order to ensure that all references to the file are returned, regardless of the permissions of the current user.

Release notes

This is a beta release for the next feature 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.

Important update information

8.5.0-beta1 resolves several issues with the upgrade path so site owners who have encountered problems updating to 8.5.0-alpha1 should try updating to this beta release instead. Site owners and module maintainers planning to update to this release should take note of the following important issues:

If you have a contributed or custom module that deals with pending revisions or loading different revisions, be aware that new validation was introduced to limit the allowed changes for untranslatable fields. See the related change record about this revision API change for details.

Important: If you have not already upgraded to 8.4.0, read the Drupal 8.4.0 release notes before upgrading to 8.5.0-beta1. Drupal 8.4 includes major version updates for Symfony, jQuery, and jQuery UI and is no longer compatible with older versions of Drush. Drupal 8.3 and earlier are no longer supported.

A bug in Symfony 3.4 causes parsing to fail on certain YAML files that contain comments. Drupal core is working around this issue, but custom services.yaml files or other custom YAML formats may need to implement their own fixes until the issue is fixed upstream in Symfony (hopefully before Drupal 8.5.0). See the Symfony 3.4 change record for details.

Issue #2941837 by Eli-T, kjay, cehfisher: Move article body out of csv file in to their own text file

Issue #2938185 by tedbow, JayKandari, navneet0693, acbramley, Eli-T, larowlan, webchick, markconroy, andrewmacpherson, David_Rothstein, smaz, ckrina: When installing Umami, only show warning if 'Demo Umami' radio button is selected (and ensure that it is obvious that warning message only applies to the Umami profile)

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.

Release notes

This is a 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 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.

Important update information

Site update and module owners planning to update to this release should take note of the following important issues:

Drupal 8 will officially drop support for PHP 5.5 and 5.6 in one year, on March 7, 2019. In order to give site owners as much notice as possible, users will now see a warning on installation and on the status report page if the host is running a version of PHP older than 7.0. We recommend you plan to update to a host with PHP 7.1 or higher soon, to ensure you have sufficient time to resolve any issues that may impact your Drupal site or other applications. (See the Drupal 8 PHP requirements page for more information on recommended PHP versions.)

A bug in Symfony 3.4 causes parsing to fail on certain YAML files that contain comments. Drupal core is working around this issue, but custom services.yaml files or other custom YAML formats may need to implement their own fixes until the issue is fixed upstream in Symfony (hopefully before Drupal 8.5.0). See the Symfony 3.4 change record for details.

In order to provide secure REST support for file uploads, viewing public files now requires the "access content" permission. This may require changes to automated tests, but should not affect most sites (since "access content" will already typically be granted). Ensure that the "access content" permission is granted to the relevant roles if you have unusual, custom file handling. File download permission is not affected.

Previously, multi-value base fields in views used incorrect field names, which caused numerous bugs for views data, REST support, etc. and also led to duplicate entries in the Views UI. In 8.5.0, the correct field name is used. Most views should be automatically updated for this change by running update.php, but in rare cases this might break existing custom views. In contrib and custom modules that extend views, overridden base field handlers may need to be updated to use the new (correct) name.

Important: If you have not already upgraded to 8.4.0, read the Drupal 8.4.0 release notes before upgrading to 8.5.0. Drupal 8.4 includes major version updates for Symfony, jQuery, and jQuery UI and is no longer compatible with older versions of Drush.

Earlier development versions of Drupal 8.5.x were potentially vulnerable to a timing attack for viewing REST in rare cases. It is unlikely that this could be exploited; however, if your site is running Drupal 8.5.x-dev and uses REST you should update to 8.5.0-alpha 1 immediately. Drupal 8.4.4 and earlier are not affected, nor are sites that do not enable REST support.

A bug in the 8.5.x upgrade path caused updates to fail with an error with certain configuration. This issue is resolved in 8.5.0-alpha1 and should not affect sites that update directly to 8.5.0-alpha1 or later.

Issue #2808217 by Wim Leers, tedbow, YesCT, dawehner, xjm, Berdir, damiankloip, slucero: To be able to view Vocabulary config entities via REST, one should not have to grant the 'administer taxonomy' permission

Issue #2927766 by Wim Leers: Update ResponseGeneratorTest to use the BrowserTestBase base class instead of the deprecated RESTTestBase

Issue #2449143 by damiankloip, tedbow, Wim Leers, dawehner, Pavan B S, Tybor, effulgentsia, larowlan: REST views specify HTML as a possible request format, so if there is a "regular" HTML view on the same path, it will serve JSON

Issue #2912298 by chr.fritsch, phenaproxima: Make media name available on manage display

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.

Release notes

Development release package for the 8.6.x release.

The 8.6.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.5.x branch until the 8.5.0 release on March 7, 2018.

Known issues

There are no known regressions in this release.

Important: If you have not already upgraded to 8.4.0, read the Drupal 8.4.0 release notes before upgrading to 8.4.4. Drupal 8.4 includes major version updates for Symfony, jQuery, and jQuery UI and is no longer compatible with older versions of Drush.