Jelenlegi hely

Hírolvasó

drupal 8.7.13

Drupal.org - 2020, április 2 - 22:19

This is a patch release of Drupal 8 and is ready for use on production sites. Learn more about Drupal 8.

If you are upgrading to this release from 8.6.x, read the Drupal 8.7.0 release notes before upgrading to this release.

Further bugfixes are available in Drupal 8.8. Drupal 8.7.x will receive security coverage until June 3rd, 2020 when Drupal 9.0.0 and 8.9.0 are released.

Important update information

This release resolves several upgrade path critical bugs that may have prevented sites from updating from Drupal 8.6 or earlier:

Known issues

Search the issue queue for known issues.

All changes since 8.7.12 drupal-8.7.13.tar.gzRelease file SHA-1 hash: a778c68ff987eeb9bd0ea4573498d7653a39ef00Release file SHA-256 hash: 87bc9cbd19c10eae3418bed0b12a486c4294bca53a7989b499fa586b1b502e4dc602aed82b1047cca97486b604f9f44b drupal-8.7.13.zipRelease file SHA-1 hash: 5b1d93d16cce633a9e14431b4cf53e9045577fdeRelease file SHA-256 hash: 8441967acd5896ab3eaadb6119afa63e3f2988b0b13c89a33b3d3ba7c8a18313782d88829b3f59a34744b322669783da VCS Label: 8.7.13Core compatibility: 8.xRelease type: Bug fixesPackaged Git sha1: 5360d9ece38465a40401de4bbbb839eb37eeb639
Kategóriák: Informatika

drupal 8.8.5

Drupal.org - 2020, április 2 - 22:17

This is a patch release of Drupal 8 and is ready for use on production sites. Learn more about Drupal 8.

If you are upgrading to this release from 8.7.x or earlier, read the Drupal 8.8.0 release notes before upgrading to this release.

Drupal 8.8.x will receive security coverage until December 2, 2020 when Drupal 9.1.0 is released.

Important update information

This release resolves several upgrade path critical bugs that may have prevented sites from updating from Drupal 8.7 or earlier:

Known issues

Search the issue queue for known issues.

All changes since 8.8.4 drupal-8.8.5.tar.gzRelease file SHA-1 hash: 3ac94168d38f97984fadc1bdd96f815564b60748Release file SHA-256 hash: 8cbb0df82d1a19c085e785952d28bcfe5105b895940fb3cc28846b9c422fc58611e595f6aa42fca4ab4423bff0b09c28 drupal-8.8.5.zipRelease file SHA-1 hash: 0482c8bc06061b785d9281dc72f71e6a7883ed5bRelease file SHA-256 hash: 5dae6ba8f8515089caf91334788bfe3248e22d106421276d8ad668c2bd2611f900160756dddebef13d9f10df34f2b640 VCS Label: 8.8.5Core compatibility: 8.xRelease type: Bug fixesShort description: Actively maintained with new features and backwards-compatible improvements every six months. Use this version for the best compatibility with future releases.Packaged Git sha1: cb0cd8079ede8b953ff282eab82aeb2c1f0e667f
Kategóriák: Informatika

drupal 8.9.0-beta2

Drupal.org - 2020, április 2 - 22:16

This is a beta release for the final, long-term support minor version 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 release fixes security vulnerabilities present in 8.9.0-beta1. Sites are urged to upgrade immediately after reading the security announcement and notes below:

This minor release provides new improvements 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.

Minor releases may include string changes and additions. Translators can review the latest translation status on localize.drupal.org.

Drupal 8.9 is the final minor release of the 8.x series. It is a long-term support (LTS) version, and will be supported until November 2021. It also provides the same public API as Drupal 9.0 aside from deprecated code. For more information on the upcoming Drupal 9 release, read the Drupal 9.0.0-beta1 release notes.

Important update information
  • Drupal core's minimist JavaScript development dependency requirement has been updated from 1.2.0 to 1.2.2.

Known issues

Search the issue queue for known issues.

All changes since 8.9.0-beta1 drupal-8.9.0-beta2.tar.gzRelease file SHA-1 hash: fb3e64b39c0b49e779c58a839c6d265bd87a36f5Release file SHA-256 hash: 3d30dbf5f61a71064febf449b3c23baa260d7698271dc3e434082792ec7075b6c4ff64852b7f4cf2997e70939fdf725c drupal-8.9.0-beta2.zipRelease file SHA-1 hash: a8c00fa1c00164d0bde56c9db3d979ad55f534d0Release file SHA-256 hash: a06d91e858f24ea2f8a87a9e50af9277d250daee2ec3d1ba54c38e9dfdd872f101492c70e7fd51a81535580d9bc45b79 VCS Label: 8.9.0-beta2Core 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: 07b36f592d2cc4d6f16ed2d76cd7a01ab44542dd
Kategóriák: Informatika

Újabb szög a TLS 1.0 és 1.1 koporsójába

HUP.hu - 2020, április 1 - 10:16
Újabb szög a TLS 1.0 és 1.1 koporsójába Titkosítás, biztonság trey 2020. 04. 01., sze - 10:16

Plan for change: TLS 1.0 and TLS 1.1 soon to be disabled by default https://t.co/YeafaP8JOf

— Windows Blogs (@windowsblog) March 31, 2020

TLS 1.0 and TLS 1.1 will soon be disabled by default in all supported Microsoft browsers, starting with Microsoft Edge version 84.

Learn more on the Microsoft Edge blog: https://t.co/GDvAGofuGK

— Microsoft Edge Dev (@MSEdgeDev) March 31, 2020

A Microsoft (is) folyamatosan száműzi a TLS 1.0-t és 1.1-et. Korábban megkezdődött az Office 365-tel, most folytatódik a böngészőkkel. Részletek itt.

Kategóriák: Informatika

PostgreSQL JDBC 42.2.12 Released

PostreSQL.org - 2020, április 1 - 02:00

The JDBC team has released version 42.2.12

We have released 42.2.12 to correct regressions in this version: Specifically - PR 1729 was reverted as this is a breaking change - PR 1719 has been reverted as it introduced errors in the PgType Cache

We suggest not using 42.2.11

JDBC Team

Kategóriák: Informatika

PostgreSQL Community Code of Conduct Committee Annual Report for 2019

PostreSQL.org - 2020, április 1 - 02:00

The PostgreSQL Community Code of Conduct Committee has delivered their Annual Report summarizing the complaints received and actions taken in the calendar year 2019.

All complaints and actions are anonymized to protect the identities of all parties involved.

You can view a copy of the report here:

https://www.postgresql.org/about/policies/coc/reports/2019/

Kategóriák: Informatika

Hack the Crisis Hungary - 48 órás online hackathon és ötletverseny

HUP.hu - 2020, március 31 - 14:02
Hack the Crisis Hungary - 48 órás online hackathon és ötletverseny HUP hup 2020. 03. 31., k - 14:02

Az új típusú koronavírus okozta helyzetben soha nem látott ipari összefogás mellett fog megrendezésre kerülni a HWSW által kiírt, Hack the Crisis Hungary nevű programozói verseny. A hackathon célja, hogy a fejlesztők ötleteikkel és azokból megvalósított megoldásaikkal hozzájáruljanak a világjárvány és karantén okozta krízishelyzet könnyebb elviseléséhez, átvészeléséhez. A verseny ötlete Észtországból ered, a magyar esemény a globálissá duzzadt kezdeményezéshez csatlakozik, amihez immár 30 ország csatlakozott.

Kategóriák: Informatika

FreeBSD Office Hours #1

HUP.hu - 2020, március 30 - 21:51
FreeBSD Office Hours #1 FreeBSD trey 2020. 03. 30., h - 21:51

#BSDSec [FreeBSD-Announce] FreeBSD Office Hours: April 1, 2020 18:00 UTC...
#FreeBSD https://t.co/BJjiXTGISD

— BSDSec.net (@BSDSec) March 30, 2020

A FreeBSD április elsején megtartja az első FreeBSD Office Hours-t, ami egy olyan online esemény, ahol a felhasználók, közreműködők és fejlesztők kérdéseket tehetnek fel, tanácsokat kaphatnak stb. A formátummal még kísérleteznek, egyelőre úgy néz ki, hogy Google Meet lesz. Részletek a bejelentésben.

Kategóriák: Informatika

drupal 9.0.0-beta2

Drupal.org - 2020, március 30 - 21:21
drupal-9.0.0-beta2.tar.gzRelease file SHA-1 hash: a78a8d99e2963f4fc90d0e9c8e867b9a08b1149aRelease file SHA-256 hash: aeefad0d1df318762b6e3842916d17c112b00c45a71e6b38c07c656714e3c27b8c45d8abb2a6f09326de40ae845a4435 drupal-9.0.0-beta2.zipRelease file SHA-1 hash: 1212d9d184753e7d04eefad0ef3c8c88a56ccd5dRelease file SHA-256 hash: e95f4b454a31cf7334674c706ccd9cf95bbcbf9f8974c3d3572ec1d17c3b25a733568e2d009a166c54ae862fda2a8823

This is a beta release for the next major version of Drupal. Drupal 9 beta releases are intended for site owners and module or theme authors to test compatibility and upgrade paths for Drupal 9.0. Beta releases are not intended for production.

This release fixes security vulnerabilities present in 9.0.0-beta1. Sites are urged to upgrade immediately after reading the security announcement and notes below:

Note that Drupal 8 is not affected by the Symfony vulnerabilities above.

Refer to How to prepare your Drupal 7 or 8 site for Drupal 9 for tools you can use to check the Drupal 9 compatibility of modules, themes, and sites. For more information on 9.0.x development, see #3007300: [META] Release Drupal 9 on June 3 2020.

The 9.0.x branch also includes all the latest commits that will be backported to 8.9.x and earlier branches. 9.0.x and 8.9.x have the same APIs and features. The key changes in 9.0.x are:

  1. Deprecated code will be removed.
  2. Dependencies will be updated to new major versions as appropriate.
  3. Platform requirements (supported PHP and database versions) will be increased.

For all other changes, refer to the 8.9.x branch.

Important update information Known issues

Search the issue queue for known issues.

All changes since 9.0.0-beta1 VCS Label: 9.0.0-beta2Release type: Security updateBug fixesShort description: Drupal 9 betas are for testing sites and projects with the upcoming Drupal 9.0 release. They are not for production.Packaged Git sha1: 772aa3faa0ec9da0b8627a4359044cfce6e1999f
Kategóriák: Informatika

Jön a OnePlus 8 sorozat

HUP.hu - 2020, március 30 - 19:26
Jön a OnePlus 8 sorozat PDA, Mobil, Tablet trey 2020. 03. 30., h - 19:26

Start: április 14.

Kategóriák: Informatika

E-Vent - nyílt forrású lélegeztetőgép projekt az MIT berkeiből

HUP.hu - 2020, március 30 - 19:17
E-Vent - nyílt forrású lélegeztetőgép projekt az MIT berkeiből Hardver trey 2020. 03. 30., h - 19:17

The team, called MIT E-Vent (for emergency ventilator), was formed on March 12 in response to the rapid spread of the Covid-19 pandemic. https://t.co/cmFqei96Gf pic.twitter.com/8lpQeJ1XQS

— Massachusetts Institute of Technology (MIT) (@MIT) March 29, 2020
The team, called MIT E-Vent (for emergency ventilator), was formed on March 12 in response to the rapid spread of the Covid-19 pandemic. [...] Students and faculty working in consultation with local physicians designed a simple ventilator device that could be built with about $100 worth of parts, although in the years since prices have gone up and the device would now cost $400 to $500 in materials. They published a paper detailing their design and testing, but the work ended at that point. Now, with a significant global need looming, a new team, linked to that course, has resumed the project at a highly accelerated pace.

Részletek: MIT Emergency Ventilator (E-Vent) Project

Kategóriák: Informatika

Office 365 -> Microsoft 365

HUP.hu - 2020, március 30 - 19:03
Office 365 -> Microsoft 365 Microsoft, Windows trey 2020. 03. 30., h - 19:03

Office 365 -> Microsoft 365 - https://t.co/HIVdVTiK8m pic.twitter.com/jCrd3F8Ina

— HUP (@huphu) March 30, 2020 #onhup
Today, we are delighted to announce that on April 21st, Office 365 will become Microsoft 365,

Részletek: Introducing the new Microsoft 365 Personal and Family subscriptions

Kategóriák: Informatika

Linus kiadta az 5.6-os Linux kernelt

HUP.hu - 2020, március 30 - 17:45
Linus kiadta az 5.6-os Linux kernelt Kernel trey 2020. 03. 30., h - 17:45

5.6: mainline Version: 5.6 (mainline) Released: 2020-03-29 Source: linux-5.6.tar.xz PGP Signature: linux-5.6.tar.sign Patch: full https://t.co/92ScQXt9Ou #linux #kernel

— Linux Kernel Releases (@LinuxKReleases) March 30, 2020

Kicsit vacillált, hogy újabb -rc következzen inkább, vagy a végleges, végül a végleges mellett döntött. Annak ellenére is, hogy több változás érkezett a múlt héten, mint amennyit a fejlesztés ezen szakaszában látni szeretett volna. Részletek a bejelentésben. A KernelNewbies Linux_5.6 oldala még nem frissült. A kiadással kapcsolatos részletekért érdemes ellátogatni az LWN idevágó oldalára.

Kategóriák: Informatika

[KV] Nem kellene már az egészségügyben dolgozók bérét most megemelni?

HUP.hu - 2020, március 28 - 17:41
[KV] Nem kellene már az egészségügyben dolgozók bérét most megemelni? Kérdés kantal 2020. 03. 28., szo - 17:41

Egyre-másra találkozom a neten és a médiában az egészségügyi dolgozók felé kinyilvánított köszönettel. Másrészt sokat hallani a gazdaságot élénkítő csomagokról, hogy kik kapjanak és mennyit. Persze a bankok, meg bizonyos vállallkozói szektorok kapni fognak. Bőven. Van, ahol egyszeri alkalommal még dollárt is osztogatni terveznek. Nem kellene a "mi gazdaság-élénkítő csomagunkat" azzal kezdeni, hogy felemeljük az egészségügyi dolgozók bérét?

Kategóriák: Informatika

Hivatalos COVID-19 alkalmazást hoz ki a WHO Androidra és iOS-re

HUP.hu - 2020, március 28 - 14:00
Hivatalos COVID-19 alkalmazást hoz ki a WHO Androidra és iOS-re Egyéb trey 2020. 03. 28., szo - 14:00

World Health Organization @WHO to launch an official app on iOS and Android https://t.co/n8tcw1nabJ

— Tedros Adhanom Ghebreyesus (@DrTedros) March 27, 2020

Tedros Adhanom Ghebreyesus WHO-igazgató bejelentette, hogy szervezete hivatalos alkalmazást ad ki Androidra és iOS-re. A kiadás hétfőre várható. A kezdeti kiadás főbb céljai:

Kategóriák: Informatika

Gyakorlatilag vége a TrueOS (egykori PC-BSD) fejlesztésének

HUP.hu - 2020, március 28 - 12:43
Gyakorlatilag vége a TrueOS (egykori PC-BSD) fejlesztésének FreeBSD trey 2020. 03. 28., szo - 12:43

It's Official But Sad: #TrueOS Is Over As Once The Best Desktop #BSD #FreeBSD OShttps://t.co/ESDWEnThSa pic.twitter.com/cAB34AyB6f

— Phoronix (@phoronix) March 28, 2020

A TrueOS (egykor PC-BSD) nevű, FreeBSD-alapú desktop gyakorlatilag halott. Ezt Kris Moore alapító erősítette meg az iXsystems fórumán:

Kategóriák: Informatika

Végül a OnePlus-nál is jön az Always-On Display

HUP.hu - 2020, március 28 - 09:05
Végül a OnePlus-nál is jön az Always-On Display Android trey 2020. 03. 28., szo - 09:05

The top IDEA is Always-On Display. We hear you, and our OS Product team has replied: it's on our roadmap.

— OnePlus (@oneplus) March 27, 2020

A Samsung sok évvel ezelőtt bevezette, más gyártók szépen lemásolták és szállítják. Kivéve a OnePlus-t. Eddig. A vállalat jelezte, hogy meghallotta a hangokat, amelyek kérték. Jön.

Kategóriák: Informatika

CentOS Blog: Git Forge decision

CentOS.org - 2020, március 27 - 18:01

After evaluating over 300 user stories from multiple stakeholders we have aligned on a decision for the Gitforge that CPE will operate for the coming years. We are opting for Gitlab for our dist git and project hosting and will continue to run pagure.io with community assistance.

Analysis and recommendation:

A lot of comments and concerns were raised about the suitability of Github as a forge of choice. The preference from all stakeholders (Fedora, CentOS, RHEL, CPE)  is that Github is not a contender and not a preference, with that in mind, we have decided to not analyse it as an option and respect the wider wishes of our stakeholders. Therefore the rest of this analysis focuses on Pagure versus Gitlab as our choice.

Looking at the user story list, we have a picture of a standard set of practices that users expect to have from a Gitforge. The basics of storing code, accessing it, merging, forking and the traditional git workflow are satisfied by both Forges under investigation. 

A key requirement coming to us is security. The need for HTTP/S pushes, the need for more stringent branch control via protected and private branches is a key operating requirement of the CentOS stakeholders. The need to interface with internal and external users in a private capacity whereby embargoed content can be worked on in private is a necessary requirement. 

Another key requirement is usability and accessibility. It is clear that our current forge solution is used as a mixture of ticket tracker, work planning, code repository and storage of documents and other artifacts. The barrier to usage needs to be low to attract drive by users and a strong representation was made for the need to have more accessible ways to interface with the system from a GUI to a command line client.

Developer centric needs came from multiple sources. Integrations with daily workflow, integrations within the IDE, integrations in an always ready and always on approach (SLA requirements were high) as well as the ability to use the forge as a means to improve the codebase (auto notifications of issues, interactive PR reviews etc.) and way of working by providing analytical output was also raised.

A big factor in a decision here needs to be both the immediate usability to meet stakeholder needs that includes an immovable deliverable for CentOS Stream which CPE must deliver by the end of the year. 

Another major factor is the stability, availability and responsiveness of the platform chosen. While no Forge meets the full suite of requirements, the issue of stability, availability and some of the richer features that were requested are currently not available in Pagure. Gitlab provides the most feature rich experience out of the box and the recommendation of the CPE Management is to opt for Gitlab as our chosen Forge for dist-git and general project hosting. For pagure.io we want to offer it to the community to maintain. CPE would provide power and ping and the rest of it will be up to the community willing to do the work. If no-one steps up to pick the maintenance of pagure.io, it will be a candidate application to sunset. Some top level requirements which helped us arrive at this decision:

  • There is a need for CentOS Stream to integrate with a kernel workflow that is an automated bot driven merging solution (merge trains). This allows for richer CI capabilities and minimizes the need for human interaction
  • Gitlab provides subgroups allowing for more granular permissions for repos
  • Gitlab allows for project planning capability which could make multiple trackers such as Taiga redundant, allowing for the planning and tracking to reside within the repo. It would enrich the current ticket based solution that Pagure has evolved into for some groups
  • 24/7 availability in an SLA model and not hosted by the CPE team freeing up resourcing and removing the need to staff a dedicated team for a Gitforge SLA which would necessitate a follow- the- sun Ops model and a heavy investment in stability and observability of the Pagure solution.

The opportunity cost to invest our finite resources into bringing Pagure up to the minimum standard that we require by the end of the year would mean feature starving both Fedora and CentOS for the next 18-24 months as we strive for the optimal standard. As a team, we spend 40% of our available resources on keeping the lights on day to day with a very small amount of that improving our technical debt situation. We are spending 30% of our team on delivering CentOS Stream. The available bandwidth for the team is not at a point that we could safely and with confidence deliver the required features to make Pagure work as our Forge of choice. It additionally would have a longer term impact with our lights on work needing to expand to move Pagure to an SLA, tilting our resourcing plan for that body of work towards 60% of our capacity. We feel this is not a responsible decision that we can make as the inward investment in a Forge is not something that we can do at the expense of planned initiatives that are on our backlog. Some of them include a better packager workflow, more investment in CI/CD to remove CPE from manual work and empower the community to do more things in our infrastructure, more observability and monitoring of our infra and services, movement of services towards the Cloud to make use of a modern tech stack and that's before we consider immovable service progression that we simply have to undertake, for example, the new Auth / AAA system.

However, we do not want to abandon Pagure and our plan going forward is thus.

  1. Offer the maintenance of pagure.io to anyone in the community interested in leading it.
  2. Engage with Gitlab on the possibility of a SaaS offering so that CPE can attain key requirements of uptime, availability and throughput as well as ensuring tooling integrations (such as Fedora Messaging among others) are preserved. Legal considerations with respect to control of code will be our first discussion point with them enabling us to make a SaaS Vs self hosted decision.
  3. Keep Pagure running with our oversight while we analyse a sunset timeline which will give a minimum of 12 months notice once we have a plan firmed up. We will fix blocker bugs, address critical vulnerabilities and keep the lights on in the same manner that we have committed to over the last 14 months where Pagure has not been a staffed and supported initiative.
  4. Where possible, when we have to update our tooling, we will attempt to refactor our tooling to be forge agnostic, allowing our Communities the choice of storing their code on Gitlab or continuing to use pagure.io
  5. Watch closely for collaboration with other Communities on Pagure and provide them with guidance and oversight to help the Pagure Community grow. We recognise that this is a growing and unique ecosystem and we genuinely want to see it succeed and will do our best to support it in that capacity. To that end we will publish the roadmap difference between Pagure and Gitlab to allow the Community to focus on feature enhancements to bridge that gap.
  6. Facilitate our Communities and assist them in standing up a version of Pagure that can be driven and maintained by the Community allowing a pure Open Source principles approach for those who seek it.

We recognize how difficult a decision this is and we empathize with the emotional attachment to Pagure. It is why we want to have a mutually beneficial approach to ultimately allow Pagure to grow and flourish and allow our community members to setup and work with any Forge they wish. This ultimately allows the CPE team to focus on adding value to a greater scale of initiatives  . This approach allows us to focus on value added services and initiatives that will benefit a large percentage of our communities instead of focusing on a singular foundational service which would ultimately consume our finite resourcing and limit our impact on both Communities.

-- Jim and Leigh

Kategóriák: Informatika

Az OTRS Group bemutatja szolgáltatásmenedzsment szoftverének 8-as verzióját (x)

HUP.hu - 2020, március 27 - 11:45
Az OTRS Group bemutatja szolgáltatásmenedzsment szoftverének 8-as verzióját (x) Hirdetés hup 2020. 03. 27., p - 11:45

Új ügyintézői felület és számos beállítási lehetőség az egyedi felhasználói élmény biztosítására

Új, modern és biztonságos. Az OTRS Group március 27-én, a folyamat- és kommunikációmenedzsment megoldások egyik vezető gyártója kiadta szoftverének új verzióját, az OTRS 8-at. A szolgáltatásmenedzsment megoldás legutóbbi verziója az egyedi felhasználói igényekre fókuszál, a folyamatokat és munkafolyamatokat még hatékonyabbá változtatva a jobb felhasználói élménnyel.
 

Kategóriák: Informatika

drupal 8.9.0-beta1

Drupal.org - 2020, március 26 - 23:41

This is a beta release for the final, long-term support minor version 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 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.

Minor releases may include string changes and additions. Translators can review the latest translation status on localize.drupal.org.

Drupal 8.9 is the final minor release of the 8.x series. It is a long-term support (LTS) version, and will be supported until November 2021. It also provides the same public API as Drupal 9.0 aside from deprecated code. For more information on the upcoming Drupal 9 release, read the Drupal 9.0.0-beta1 release notes.

Important update information
  • Theme functions were deprecated prior to Drupal 8.0.0's release in favor of Twig templates. However, the deprecation did not use Drupal's deprecation APIs to notify module and theme developers. Starting with Drupal 8.9.0 the use of theme functions will start to trigger deprecation notices. (In Drupal 9, this error will also be logged because theme functions bypass the sanitization functionality provided by Twig.)

  • The shortcut module disabled the cache for Dynamic Page Cache for users with access to shortcuts. These pages will now be cached which should result in a performance improvement. In rare cases, cache coherency (invalidation) bugs which were previously hidden by the disabled cache may now be surfaced. If content for authenticated users with access to shortcuts is cached incorrectly after upgrading to this release, the module that provides the incorrectly cached content might need a fix to its cache handling code (for example, cache tags or contexts).

Update system improvements and upgrade path fixes
  • Drupal now shows a more user-friendly warning when a site tries to upgrade to a new version without having run required intermediate database updates first.

    If you see 'Unsupported schema version' when attempting to run updates, you should:

    1. Back up your site and codebase.
    2. Locate an older version of the contributed module which contains the updates you missed.
    3. Downgrade the module to that version in your code base, and attempt to run updates again.

    When this error is shown, it will now also prevent any updates from proceeding, so may make a persistent issue on an existing site more obvious.

    Ideally, you should always attempt updates of contributed modules and core on a backup of your site (such as a local development environment) prior to running them on production.

  • Additionally, module developers may now specify when they have removed post-update hooks, using the new hook_removed_post_updates(). See the change record on hook_removed_post_updates() for more details.

  • Previously, corrupt menu link or taxonomy term data could cause fatal errors when sites attempted to update to Drupal 8.7 from 8.6 or earlier, due to two separate issues with the upgrade path.

    Some of this data will now be repaired automatically on upgrade. In some cases, this could result in content that was not displayed reappearing. If you previously encountered this upgrade path issue, review the change notice on the fixed menu and taxonomy upgrade path for more details on how to check for possible side effects from this change.

    Other data integrity issues that cannot be automatically repaired will result in an error message when update.php is run. If you were unable to update to 8.7 due to issues with menu link or taxonomy term data, Drupal 8.8.4 now adds instructions for resolving this issue. Try installing 8.8.4 and running update.php again. If you see an error that there are "Integrity issues detected" for your site data, follow the instructions in this change record to attempt to repair the data so that updates can be run.

Migrate system changes
  • Multilingual migrations are now stable and have been moved into the main Migrate Drupal module. The experimental Multilingual Drupal Migrate module is therefore no longer required, and will be uninstalled automatically on upgrade..

  • A new complete node migration, d7_node_complete.yml (for Drupal 7) and d6_node_complete.yml (for Drupal 6) is now available. This migration will migrate all nodes and node revisions, including translated nodes and translated node revisions. The complete node migration will eventually replace the existing trio of node migrations. See change record on the new 'complete node migration' for more information on the new migrations.

Dependency changes
  • jquery.cookie has been deprecated in Druapl 8.9 and removed in Drupal 9.0 in favor of js-cookie version 2. A core/js-cookie library has been introduced, and a backwards-compatible shim is provided as core/jquery.cookie for Drupal 9. We may upgrade to js-cookie 3 if it is available before 9.0.0-rc1 and 8.9.0-rc1.

  • Drupal is now using stable releases for behat/mink (1.8.0) and behat/mink-selenium2-driver (1.4.0). These were previously pinned to development versions because a critical bug affecting Drupal core had not been resolved in any stable release.

  • Since the Zend Framework has become Laminas, Drupal 8.9 now uses the Laminas components for several dependencies in place of the previous Zend Framework components. Code should be updated to use the new Laminas classes. A backwards compatibility layer is provided by laminas/laminas-zendframework-bridge. See the change record on updating to the Laminas components for examples of how to change your code.

  • The Sortable library updated to 1.10.2. If your module or site depends directly on Sortable, review the changes listed here: Sortable 1.10.2 changelog

Other important bug fixes Known issues

Search the issue queue for known issues.

All changes since 8.8.0

Browse the commit log for 8.9.x.

drupal-8.9.0-beta1.tar.gzRelease file SHA-1 hash: 21d3edab69b622657c1546b87501b43c1a393756Release file SHA-256 hash: 04ff39b4fd26599652c5f3cbc46e5d014936e1ade027ebf4051884f9cb84560ea1e8f17527ba1edd52ecae2d88cbdf9c drupal-8.9.0-beta1.zipRelease file SHA-1 hash: 0b3f969847b7f4b986ba44eb063bf3bb6d380fb7Release file SHA-256 hash: 2d2d4eb957ab89b89a4094834a809345079949bfe0d855b2621536fe2ea8a8778bf79a4ec8c53ed4f68c895721947913 VCS Label: 8.9.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: 1e0e0e09cbe8cfb5113f3b32f15f84aa0cda38be
Kategóriák: Informatika

Oldalak

Theme by me