clemens-tolboom deleted branch dependabot/pip/Groep-5/tensorflow-2.5.1 at KennisnetwerkDataScience/Wifi-punten-in-Leeuwarden
Updated Aug 27
Entity types in core come with what is known as handlers: Various smaller classes that carry out a specific task for the entity type. Group copied this system for its own plugins, but quickly found out that there are severe extensibility limitations to how core deals with handler declarations.
Chromatic: Getting Started with Continuous Website Performance Monitoring: Gather and Track Consistent Data
Let's first be honest; this isn't yet a post COVID-19 world and it won't be for some time yet. However, in-person events are beginning to happen and we need to consider what that means, practically.
How do we maintain reasonable levels of safety for those people who attend? What do we do about those who simply cannot attend, either through concerns over their health or the inability to travel? I might not even be allowed into the USA at the moment as the Astra Zeneca vaccine I had isn't recognised there.Rachel Thu, 08/26/2021 - 17:20 Tags
On our theme BizReview and Listiry, now available in Drupal 9, we have to solve the common problem with displaying nodes on maps.
Here are what we have used in our themes and have verified it is working. Please see the result as below:
Now please follow our tutorial on how to display maps on Drupal with Geofield, Address and Geocoder modules:1. Install Drupal and Geofield
Install Drupal core:
Ok, sounds weird, but it’s true.
Imagine for a moment using Next.js as the decoupled front-end of your Drupal site. Imagine it worked well and was transparent to your content editors. Use the power of Drupal, with built-in JSON API’s to feed all the content you can think of to the front-end. Use Next.js to build out hyper-performing front-end experiences. This approach opens up new possibilities for your developers and your website to deliver content quickly, securely, and across multiple platforms.
Chapter Three is excited to introduce our open-source integration of Next.js and Drupal: https://next-drupal.org.
Planning and executing a major software upgrade can be as easy as running some software, to as complicated as a major migration. For the American Productivity and Quality Center, it was definitely the latter. With hundreds of thousands of users, and many thousands of pieces of content, a migration is a detailed and time intensive process that requires careful planning. In part 2 of our Tag1 Team Talk with the APQC, Tag1 Managing Director Michael Meyers talks with John Tesmer, the Executive Director of Information Technology, and Jim Gillilan, Senior Architect and Lead of the Technology team at APQC, about their migration to Drupal 9, and their future plans. Click here for Part 1 For a transcript of this video, see Transcript: APQC: The D9 Migration - approach, challenges, and what’s next. Photo by Pankaj Patel on UnsplashRead more lynette@tag1co… Wed, 08/25/2021 - 07:21
Gábor Hojtsy: Drupal 10 readiness will be hugely automated, 95% of deprecated Drupal APIs already covered
With the Drupal 8 end of life in a little over two months and Drupal 10's release next year, this is the time of transitions again at Drupal. However, while Drupal 7 to 8 (or 9) was a big move, the transitions from 8 to 9 and 9 to 10 are much smaller and mostly automated.
Drupal 10 is planned to be released in June, August or December 2022 and the tools are getting ready to support that. The two key tools will be the same as the previous upgrade: Upgrade Status and Drupal Rector.
Matt Glaman has been doing amazing work recently in the underlying components of both tools. Thanks to his work on updating phpstan-drupal for Drupal 10 support, Upgrade Status checks deprecated API uses on Drupal 9 too. Since my last update on that, I added reporting of deprecated modules and new system requirements as well.
Ryan Aslett at the Drupal Association built the project analysis job on top of Upgrade Status and that is run on Drupal 9 projects now as well. So we have an idea of the extent of work that will need to be done for Drupal 10 compatibility. I've updated the dev.acquia.com deprecation dashboard to show Drupal 10 results. While projects should not be expected to be Drupal 10 ready at this time, the dashboard helps us prioritise work on certain parts of the tooling to help the ecosystem upgrade.
To support that, Palantir.net has been sponsoring Matt Glaman to also bring Drupal Rector up to date for Drupal 10 readiness. The results are already outstanding! Today, of the 22204 Drupal deprecated API uses identified in Drupal 9 compatible projects. These are green and purple on the chart below. Drupal Rector has automations to fix 95% of them (green). There are a further 5391 non-Drupal deprecated API uses (yellow) including Symfony and PHPUnit deprecated APIs. Those themselves have third party rectors, so the coverage will further improve by including those. That is in the works.
The drupal.org Project Update Bot resolves rectorable deprecated API uses (green) and info/composer issues (blue) when posting patches, so this means that it will be able to resolve most deprecated APIs in its suggested fixes already and we expect it will improve more with third party rectors added.
Drupal 10 itself is a moving target, the branch will be open around October/November so the above does not mean that the tools are complete, but we are significantly further ahead this time compared to the Drupal 8 to 9 transition, making the upgrade to Drupal 10 smoother for everyone.
With the Drupal 8 release, we decided upgrades must be easier going forward and thanks to the fantastic work of contributors and sponsors, we are doing it again.
A few core modules are being deprecated in Drupal 9 for removal in Drupal 10. There are a variety of reasons for their removal, but in each case we think moving to a contributed project would serve users better.
To support the continuous upgrade path and provide stability for Drupal 9 users moving to Drupal 10, we are looking for potential maintainers and co-maintainers to keep security support and ensure stability of the codebases moving out from core. The initial scope of maintaining these projects is to keep the Drupal 9 core-compatible branches intact and provide security support. It would be nice if the new maintainers also improve the projects further but that is not part of the initial scope.
Lee Rowlands stepped up to maintain Forum and HAL modules moving to contributed projects, but co-maintainers would be welcome. Lee Rowlands and Andrey Postnikov plan to maintain Aggregator as a contributed project.
Additionally there is discussion about removing the RDF module too, feedback welcome. This is not yet at a stage where we need maintainers, although it may be there in the future.
Your website shows the world who your business is online. Learn how you can make your website pop in an over-saturated market.READ MORE