Planet Drupal

Syndicate content
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 20 hours 8 min ago

Third & Grove: A Sure-Fire Migration Approach to Drupal 8 & Drupal 9

Mon, 10/12/2020 - 02:27

The key to a successful integration to Drupal 8 or Drupal 9 is a solid understanding of your Drupal 7 site, so you know what to migrate over and what to avoid. Here’s what you need to know.

groups.drupal.org frontpage posts: October Seattle Drupal User Group Meeting

Sat, 10/10/2020 - 00:34
Start:  2020-10-22 18:30 - 20:00 America/Los_Angeles Organizers:  rlhawk jcost mortona2k Event type:  User group meeting

We will meet at 6:30 pm on Thursday, October 22. Note that this is the fourth Thursday of the month, not the usual third

Agenda
  • Introductions
  • Announcements
  • Drupal news
  • Reports about what we liked and learned at BADCamp
  • Demos and discussions about debugging with XDebug
Location

Online; the URL for the meeting will be shared in the SeaDUG Slack workspace and with anyone who signs up for the event.

OSTraining: OSTips - E-Commerce Inside Drupal Made Easy

Fri, 10/09/2020 - 16:10
How would you like to be able to set up an ecommerce platform on your drupal site in less than 60 seconds? You can!   In this video, I want to share with you my little frustration with drupal and drupal e-commerce. It's really hard to set up!  However,  there's a fantastic e-commerce platform called ecwid that allows you to set up your store in no time.  Then you can literally have it embedded on your Drupal site in less than 60 seconds. People will never know the difference, because everything stays on your Drupal site!   Let's check it out.

Third & Grove: Acquia Engage 2020 Award Nominations

Fri, 10/09/2020 - 10:26

Third and Grove is honored to have three clients making the final round for the Acquia Engage 2020 awards.

Mateu Aguiló: A standard for progressive decoupled Drupal

Fri, 10/09/2020 - 01:00
In this video I show a set of Open Source tools we have created to manage the whole application lifecycle when embedding JS apps inside of Drupal. You can fork these tools, and with a couple of clicks you will get a demo of progressive decoupling in Drupal in your own site. This works in Drupal 8 and Drupal 9.

Chapter Three: Local Behat Testing with Lando and Pantheon

Thu, 10/08/2020 - 20:06

If you've followed Pantheon's Build Tool Instructions and used Pantheon's Example Drops 8 Composer as the base to take advantage of CircleCI then you've encountered Behat tests. Behat tests are extremely valuable for testing site functionality before new code goes to production or a shared code stream. However, on a custom site these default tests provided by Pantheon are likely to fail if you've made even a benign change like deleting Tags vocabulary on a Drupal standard installation.

Vardot: CMS Buyers Guide

Thu, 10/08/2020 - 14:26
CMS Buyers Guide Type Tool/Template Firas Ghunaim Thu, 10/08/2020 - 16:26

 

At the core of any successful digital transformation is finding the ideal CMS that best fits your enterprise short and long-term digital objectives.

However, this decision making process can take a lot of time and effort.

To simply this process, our team developed this guide to help you identify the CMS that best suits your enterprise and your end-users based on the criteria that is relevant to your business requirements.

The CMS Buyers Guide will feature:

  • Vendor and product viability
  • Budget concerns
  • CMS capabilities
  • Best practices and standards
  • ... and much more.

Download the CMS Buyers Guide by filling out the form to the right.

Form Form title Download Now Solutions by industry Media and Entertainment Healthcare Financial Services High Tech Travel and Tourism Retail Higher Education Government Solutions by need Enterprise CMS Drupal Managed Services E-Commerce On-Site SEO Knowledge Management Social Business Community Related services Web Development Support and Maintenance Drupal Migration and Upgrades DevOps and Engineering Digital Marketing UI/UX Design Digital Strategy Product Varbase Uber Publisher Marketing Automation Open Social

OSTraining: Control Spam in Drupal with Honeypot and/or Antibot

Thu, 10/08/2020 - 05:00

From its conception, the fundamental (ground) idea of the internet was the exchange of information through code snippets of a markup language. This is still the ground principle that moves the internet these days. There are, of course, a lot of other things you can do over the internet, but it all comes down to an exchange of information.

With this kind of freedom, it is not surprising, that people abuse this for their own benefit. Spam comments are a form of abusing this privilege.

The combination of the Drupal modules Honeypot and Antibot will ensure that your site is “almost” 100% protected from spam (at least the ones produced by robots).

Keep reading to learn how to Control Spam in Drupal with Honeypot and/or Antibot!

PreviousNext: Stop your builds failing with git pre commit hooks

Thu, 10/08/2020 - 00:48

Have you ever happily pushed your latest piece of work ready for others to test only to have it fail the build on coding standards? If so, git pre commit hooks could be your friend!

by saul.willers / 8 October 2020

It's pretty standard practice these days for CI build pipelines to include linting steps to ensure things like coding standards pass. Depending on how the build is configured, failing coding standards can result in the entire build failing. 

Because linting is generally not resource intensive, running it locally can be a useful time saver. But it's an easy step to forget. Thankfully it can be automated to run before every git commit with a pre-commit hook.

First we need a script to fire before the commit. This is placed in the project repo somewhere like .git-hooks/pre-commit:

#!/bin/sh

make lint-php
exit $?

We use Makefiles to call our custom lint-php rule, but this could be a Robo command or any other task running which fires your coding standard check.

Next, the script needs to be executable:

chmod +x .git-hooks/pre-commit

Then let git know about this script by running the following command:

git config core.hooksPath .git-hooks

That's it, our coding standards check will now automatically run whenever we do a git commit and stop the commit from proceeding if there is a fail.

If you've got a WIP or something you wish to commit regardless of any errors use git commit --no-verify

Hopefully this saves you from pushing coding standard fails in the future.

Tagged Drupal Development, Git, CI

Promet Source: SEO and Analytics for Zero-Click Searches

Wed, 10/07/2020 - 22:01
Google  has made gigantic leaps in streamlining search results -- to the point that more than 50% of Google searches no longer result in a click-through to a website or other content. More often than not, search queries and question-based searches can now be answered directly from the Search Engine Results Page (SERP). 

Centarro: Commerce Shipping release adds shipment confirmation emails and improved JSON:API support

Wed, 10/07/2020 - 20:29

Several months have passed since we've tagged our first Commerce Shipping release candidate, which added support for "billing same as shipping" address copying and resolved a variety of bugs.

Since then we've kept a close eye on the issue queue. Even though it isn't part of the core Commerce project itself, we consider it an essential contributed module in our ecosystem. We've resolved a few more "last mile" bugs and recently packaged the module's second release candidate.

Shipment confirmation emails

Thanks to the hard work of several community contributors, we now support sending a "shipment confirmation" email to notify customers when their ordered items are shipped.

This behavior is controlled by a setting at the shipment type level:

Similar to order receipts, it's also possible to resend the shipment confirmation from an order's shipments tab:

Read more

BADCamp News: Less than a week away from BADCamp liftoff!!

Wed, 10/07/2020 - 19:29
Less than a week away from BADCamp liftoff!! Wed, 10/07/2020 - 12:00 volkswagenchick Wed, 10/07/2020 - 11:32 We are less than a week away from BADCamp liftoff!! Bay Area Drupal Camp (BADCamp) runs from 9 am - 4 pm PT from Wednesday, October 14 through Saturday, Oct 17. Limited-availability workshops and summits will take place on Wednesday and Thursday. This year we are delivering content in the Hopin platform and separate registration is required for both the workshop and summits block and the sessions. We understand that you may have already registered on the BADCamp website, but we do require folks to register on Hopin as well. Drupal Planet

Mobomo: Debunking 4 CMS Migration Myths

Wed, 10/07/2020 - 18:25

Here’s a dirty secret: most businesses are unsatisfied with their website. Research shows that 34% of website owners are unsatisfied with the amount of business their website generates for them. Loudhouse data suggests that 62% of business owners believe a more effective website would increase their sales. And millions of business websites deal with slow load times, inconsistent customer experiences, and problematic UI/UX issues.

There’s a reason that 36% of small businesses STILL don’t have a website. Creating an amazing, design-driven, customer-centric website is challenging. So, what do you do when your website isn’t making the cut? You look towards the source — your Content Management System (CMS). Every year, thousands of private and public entities migrate their website to a new CMS.

But, unfortunately, thousands more don’t. Migration is scary. It’s easier to stay with your current CMS and focus on redesigns or new templates. Here’s the problem: new coats of paint don’t fix broken engines. If you’re thinking about migrating from WordPress or Joomla to Drupal, you’ve probably heard rumors and myths regarding migrations.

Let’s clear those up. Here are 4 myths about migration that need to be squashed.

Myth #1: I’m Going to Lose All My Content/Data

This is, by far, the most common excuse against migrating. You’re worried all of that precious content and data are going to fall off the ship if you switch ports. And, you’re right to worry. It could… if you don’t migrate correctly. But it’s not inevitable. You can prevent data and content loss. In fact, if you lose data or content, we would consider that a failed migration. In other words, successful migrations keep data and content intact by definition.

Here are some handy-dandy steps you can take to ensure that your precious data doesn’t go overboard during your migration:

  • Crawl your site before migration and use the crawl data to check for URL issues. If you check each URL, you should be able to see any missing content (and fix it!)
  • Keep your existing site stable until you’ve fully migrated.
  • When you migrate, check for duplicate content; plenty of site owners run into the opposite of losing content.
Myth #2: I Have to Invest in a Redesign

You’re migrating; you might as well invest in a redesign, right? Sure! You could. But it’s tricky. When you do a redesign and a migration, you’re no longer just matching URL-to-URL and content-to-content, you’re simultaneously rebuilding your website. Don’t get us wrong; there are advantages. It’s a great time to redesign from an SEO perspective (you’re already going to take a small hit during the migration; more on this in the next section), but it also requires significantly more planning, budget, and time.

If you want to do a redesign-migration, we heavily recommend that you touch base with your design company. You want to work through the kinks and create a best-in-class action plan to tackle any issues that may (or may not) pop up. The entire migration will be structured around the redesign, so it’s important to carefully weigh your options.

Myth #3: Goodbye SEO!

From an SEO perspective, migration sounds like a nightmare. You’ve worked diligently to build up your SEO. What happens when you frolic to a new location? Let’s get this out of the way: your SEO will take a temporary hit. But, it shouldn’t last long. In fact, there’s a good chance you’re moving to another platform because it’s better at handling SEO. For example, Drupal has built-in SEO capabilities (e.g., title-based URL nodes, customizable meta tags, etc.) WordPress does not. Obviously, you can get SEO plugins for WordPress that help you build SEO functionalities, but most of those plugins are also available for Drupal — so Drupal gives you a net gain.

Here’s a secret: migration can help your page rank. After the first awkward week (Google has to recrawl your website, recognize that it’s you, and give you back your ranking), migration can help you build a more powerful SEO framework.

Want to migrate without dumping your SEO overboard? Here are some tips:

  • Update your internal links
  • Benchmark your Google Analytics profile and compare it with your analytics post-migration to look for gaps
  • Keep any old domains and redirect your website
  • Check for broken or duplicate content that could tank your SEO
  • Manage your sitemaps
  • Update any PPC campaigns and ad creatives
Myth #4: You Just Have to “Lift-and-Shift”

There are plenty of myths surrounding the difficulty of migration. But there are also a few myths making migration out to be super easy. And, without a doubt, the most prevalent “easy-peasy-lemon-squeezy” migration myth is the ever-coveted “lift-and-shift.” There is no one-size-fits-all strategy for migrating websites. Sometimes, it can be as easy as lifting content off of one website and putting it onto another website. But that’s seldom the case.

Generally, you need to set up test servers, check to see if website elements function correctly on the new platform, test out and utilize new CMS features, and a variety of other tasks before you can simply drop content from one place to another. In other words, lift-and-shift may work when you’re migrating a cloud environment, but it often doesn’t work with CMS migration.

Remember, just because everything worked perfectly in one environment doesn’t mean it will in another one. You may have to fix some website elements and carefully construct your new website ecosystem. At the same time, you’ll probably be playing around with the new features available to you on Drupal — so the “lift-and-shift” is usually more of a “lift-and-test-and-shift.”

Do You Need Help With Your Drupal Migration?

At Mobomo, we help private and public entities migrate to Drupal environments using proven migration strategies and best-in-class support. So, whether you’re looking to establish your website in a more secure, SEO-friendly environment or you’re looking to do a redesign-and-migrate, we can help you migrate pain-free. Are you ready to move to a brighter future?

Contact us. We’ve got your back.

The post Debunking 4 CMS Migration Myths appeared first on .

Lullabot: Lullabot Podcast: A Look Into the Past, Present, and Future of Lullabot

Wed, 10/07/2020 - 17:10

Matt and Mike have former CEO Matt Westgate on to talk about his transition to Tugboat, and also speak with new CEO Seth Brown to talk about what's upcoming for Lullabot.

The Savvy Few: How to redirect a user after login in Drupal the proper way

Wed, 10/07/2020 - 15:07

Automatically redirecting a user after logging into your Drupal website is a common requirement. In Drupal 7, you would probably have used hook_user_login() to perform this task, but with Drupal 8 came a more robust way to handle this. Our…

Read more

Drupal Core News: Drupal 9.1.0-alpha1 will be released the week of October 19th

Tue, 10/06/2020 - 21:26

Reposted from the Core group on groups.drupal.org

In preparation for the minor release, Drupal 9.1.x will enter the alpha phase the week of October 19th, 2020. Core developers should plan to complete changes that are only allowed in minor releases prior to the alpha release. The 9.1.0-alpha1 deadline for most core patches is October 16. (More information on alpha and beta releases.)

  • Developers and site owners can begin testing the alpha after its release.

  • The 9.2.x branch of core will be created, and future feature and API additions will be targeted against that branch instead of 9.1.x. All outstanding issues filed against 9.1.x will be automatically migrated to 9.2.x.

  • Once 9.2.x is branched, alpha experimental modules will be removed from the 9.1.x codebase (so their development will continue in 9.2.x only). The Config Environment module is an alpha stability module in 9.1.x.

  • All issues filed against 9.0.x will then be migrated to 9.1.x, and subsequent bug reports should be targeted against the 9.1.x branch.

  • During the alpha phase, core issues will be committed according to the following policy:

    1. Most issues that are allowed for patch releases will be committed to 9.1.x and 9.2.x.
    2. Most issues that are only allowed in minor releases will be committed to 9.2.x only. A few strategic issues may be backported to 9.1.x, but only at committer discretion after the issue is fixed in 9.2.x (so leave them set to 9.2.x unless you are a committer), and only up until the beta deadline.
Drupal 8.9.0-beta1 will be released the week of November 2nd

Roughly two weeks after the alpha release, the first beta release will be created. All the restrictions of the alpha release apply to beta releases as well. The release of the first beta is a firm deadline for all feature and API additions. Even if an issue is pending in the Reviewed & Tested by the Community (RTBC) queue when the commit freeze for the beta begins, it will be committed to the next minor release only.

The release candidate phase will begin the week of November 16th. See the summarized key dates in the release cycle, allowed changes during the Drupal 8 and Drupal 9 release cycles, and Drupal 8 and 9 backwards compatibility and internal API policy for more information.

The scheduled release date of Drupal 9.1.0 is December 2nd, 2020.

Bugfix and security support of Drupal 9.0.x, 8.8.x and 8.9.x.

Security coverage for Drupal 8 and 9 is generally provided for the previous minor release as well as the newest minor release. However, Drupal 8.9.x is a Long-Term Support release where support is provided until November 2021. Based on these the following changes are upcoming:

Drupal 8.8.x Security releases will be provided until December 2nd, 2020. Drupal 8.9.x Security releases will be provided until November 2021. Bugfix support will continue into early 2021. Drupal 9.0.x Normal bugfix support ends on December 2nd, 2020. However, security releases are provided until the release of Drupal 9.2.0 on June 2, 2021.

Drupal core announcements: Drupal 9.1.0-alpha1 will be released the week of October 19th

Tue, 10/06/2020 - 20:15

In preparation for the minor release, Drupal 9.1.x will enter the alpha phase the week of October 19th, 2020. Core developers should plan to complete changes that are only allowed in minor releases prior to the alpha release. The 9.1.0-alpha1 deadline for most core patches is October 16. (More information on alpha and beta releases.)

  • Developers and site owners can begin testing the alpha after its release.

  • The 9.2.x branch of core will be created, and future feature and API additions will be targeted against that branch instead of 9.1.x. All outstanding issues filed against 9.1.x will be automatically migrated to 9.2.x.

  • Once 9.2.x is branched, alpha experimental modules will be removed from the 9.1.x codebase (so their development will continue in 9.2.x only). The Config Environment module is an alpha stability module in 9.1.x.

  • All issues filed against 9.0.x will then be migrated to 9.1.x, and subsequent bug reports should be targeted against the 9.1.x branch.

  • During the alpha phase, core issues will be committed according to the following policy:

    1. Most issues that are allowed for patch releases will be committed to 9.1.x and 9.2.x.
    2. Most issues that are only allowed in minor releases will be committed to 9.2.x only. A few strategic issues may be backported to 9.1.x, but only at committer discretion after the issue is fixed in 9.2.x (so leave them set to 9.2.x unless you are a committer), and only up until the beta deadline.
Drupal 8.9.0-beta1 will be released the week of November 2nd

Roughly two weeks after the alpha release, the first beta release will be created. All the restrictions of the alpha release apply to beta releases as well. The release of the first beta is a firm deadline for all feature and API additions. Even if an issue is pending in the Reviewed & Tested by the Community (RTBC) queue when the commit freeze for the beta begins, it will be committed to the next minor release only.

The release candidate phase will begin the week of November 16th. See the summarized key dates in the release cycle, allowed changes during the Drupal 8 and Drupal 9 release cycles, and Drupal 8 and 9 backwards compatibility and internal API policy for more information.

The scheduled release date of Drupal 9.1.0 is December 2nd, 2020.

Bugfix and security support of Drupal 9.0.x, 8.8.x and 8.9.x.

Security coverage for Drupal 8 and 9 is generally provided for the previous minor release as well as the newest minor release. However, Drupal 8.9.x is a Long-Term Support release where support is provided until November 2021. Based on these the following changes are upcoming:

Drupal 8.8.x Security releases will be provided until December 2nd, 2020. Drupal 8.9.x Security releases will be provided until November 2021. Bugfix support will continue into early 2021. Drupal 9.0.x Normal bugfix support ends on December 2nd, 2020. However, security releases are provided until the release of Drupal 9.2.0 on June 2, 2021.

OpenSense Labs: Drupal 9: All questions answered here

Tue, 10/06/2020 - 13:36
Drupal 9: All questions answered here Shalini Rawat Tue, 10/06/2020 - 18:06

“The big deal about Drupal 9 is … that it should not be a big deal” - Dries Buytaert (Founder and Project Lead of Drupal)

June 2020 marked the onset of the long-awaited version 9 of the Drupal CMS. And just like every product, the moment this new CMS rolled out, it raised a lot of interest in the Drupal community as well as among Drupal users. The interest was to understand the new version of Drupal with a view to unlocking the new digital opportunities. Logically this interest gave rise to a number of questions in the head of users, right from the ways to migrate to what this new release actually means to a user.

There are some common concerns about Drupal 9 that every Drupal user is battling with in some way or another way. Therefore, in this blog, we have initiated to unpack the burning questions about Drupal 9 which will put all your questions at peace and will surely help you unleash the best user experience on your website. 


1. What’s new in Drupal 9? 

Drupal 9 is an engine of innovation that has experienced the most straightforward update in the history of Drupal. As a matter of fact, Drupal 9 shares the same new features as Drupal 8.9. Thus, Drupal 9.0 will not include any new features. However, Drupal 9.1 will continue to receive new features biannually (within every six months) with a view to helping enterprises stay up-to-date. Check out the definitive guide to Drupal 9 to know more.

2. Did Covid-19 have any impact on the Drupal 9 release?

Covid-19 has impacted each and every sphere of our lives and the effect of this global pandemic is felt by everyone around the world. Drupal is no different and indeed there were certain challenges that Covid-19 generated against Drupal. However, despite all those hurdles that came across the way, Drupal 9 was released on its planned day i.e. on June 3, 2020. This launch of Drupal 9 is itself a milestone in the history of the open-source community that builds Drupal. 

3. Why was Drupal 9 built in Drupal 8?

Instead of working on Drupal 9 in its own git branch from the scratch, Drupal 9 was built in Drupal 8. Yes, you heard it right. Using the deprecations and optional updated dependency support, Drupal 9 was mostly built in Drupal 8 because of the following reasons:

  • All new (Drupal-9-ready) code was deployed on Drupal 8 sites before Drupal 9 came into existence. 
  • The community worked out the issues in the new code in Drupal 8.
  • Feedback was provided based on the new code so that necessary improvements can be made in Drupal 8.
  • Unlike previous versions of Drupal, building Drupal 9 in Drupal 8 helped the community to avoid ending up with an entirely reworked API.
  • It is important to note here that unlike previous versions of Drupal, Drupal 9 is not a reinvention of Drupal.

4. What will happen to Drupal 7?

Considering a large number of sites that would still be using Drupal 7 in 2020, Drupal 7  was originally decided to receive community support until November 2021. However, in the light of the impact of COVID-19 on the community, the association has now extended Drupal 7 support and moved the end-of-life date to November 28, 2022, which implies that Drupal 7 will be supported for close to 2.5 years after the release of Drupal 9. 

5. What will happen to Drupal 8?

Drupal 8 relies on Symfony 3, and Symfony 3’s end of life is November 2021. As a result, the community support that Drupal 8 receives- including security coverage, will last until November 2021. In other words, no new features will be added to Drupal 8, nor will minor releases be made available. After November 2021 users on Drupal 8 must upgrade to Drupal 9 in order to continue receiving support from the Drupal community.   

6. What are the benefits that Drupal 9 holds over Drupal 8 or even Drupal 7?

Drupal 9 is the culmination of all of the features that are developed over the course of Drupal 8. This updated technology helps Drupal 9 to continue Drupal 8's pattern of continuous innovation along with significant features that are released every six months.

Drupal 9.0 shares the same features as Drupal 8.9 (with the notable exception of updated dependencies). Further,

Drupal 9.1, 9.2, etc. will add new backward-compatible features every six months to Drupal 9.0. 

Drupal 9 platform will be supported with security fixes after November 2021 which makes it more advantageous than Drupal 8. Not to mention, Drupal 9.1 onwards will continue to add new features to Drupal core.

7. What is the best possible way to upgrade from Drupal 7 to Drupal 9?

Migrating from Drupal 7 to Drupal 9 is one of the recent advancements that took place in the world of Drupal. However, before the release of Drupal 9, the best path for Drupal 7 sites to upgrade to Drupal 9 was to upgrade to Drupal 8. This path of migration to Drupal 8 is still a good option for Drupal 7 sites, despite the release of Drupal 9.

Migration from Drupal 7 to Drupal 8

The Drupal 7 to Drupal 8 upgrade includes some pretty significant changes. Migrating Drupal 7 to Drupal 8 can be done in the following ways: 

  • Migrate everything, which includes content and configuration, into an empty Drupal 8 installation (the default method).
  • Manually create a new Drupal 8 site, set the content types and fields up as per the requirement, and then migrate your Drupal 7 content in it. 

Migration from Drupal 7 to Drupal 9

Migrating from Drupal 7 to Drupal 9 can be a possible jump in the world of Drupal. In other words, the Drupal 7 migration ecosystem is still available in Drupal 9, which can help you easily skip Drupal 8 entirely and migrate to Drupal 9. There are three factors that will likely shape this decision-making process that include time and budget, developer skillset and planning a release window. 

8. What is the best possible way to upgrade from Drupal 8 to Drupal 9?

Fortunately, migrating Drupal 8 to Drupal 9 is radically the easiest update that has happened in a decade. However, it is equally important to note here that the path of Drupal 8 to 9 is not a sudden jump, rather it is a compendium of several steps that are much easier to adapt and perform. 

Upgrade to Drupal 8.8 or Drupal 8.9: In order to update your Drupal 8 to Drupal 9, update your site to the most recent version of Drupal 8.x. Drupal 8.8 was a big milestone for API compatibility which is fully compatible with Drupal 9. That is to say, contributed modules that are released prior to 8.8 may not be compatible with Drupal 9.
 
Environment requirements: Ensure that your environment is well suited to Drupal 9’s requirements.  There are new minimum requirements for various databases like MYSQL and MariaDB. Also, your Drush version must be updated to Drush 10. 
 
Audit for conflicting dependencies: If there exist dependencies that are no longer in use, then you will have to find some way to remove those dependencies. This can be done by either rewriting custom code or finding alternative solutions to fix these issues.
 
Check and remove deprecated code: Your site includes deprecated code that needs to be removed. There are a few tools that can be used to check if your site contains deprecated code or not. Some of the common tools include Drupal Check, PhpStan Drupal, Drupal Quality Checker, Upgrade Status and Configuring your test suite. Further, in case your site detects deprecated codes, you can use tools like Rector for Drupal 8 and Upgrade Rector to fix the deprecated codes. 
 
Flag modules as Drupal 9 compatible: Once you have removed the deprecated code from your custom modules, do not forget to flag them as being compatible with both Drupal 8 and Drupal 9.
 
Update contributed modules: Make sure to update all your contributed modules to a Drupal 9-compatible version while your site is still on Drupal 8. This needs to be done before attempting an upgrade to Drupal 9.
 
Once that is done, update your Drupal core to Drupal 9 and run update.php.

9. What are the system requirements to run Drupal 9?

  • In order to run a site built on Drupal 9, your system must comply with the following requirements.
  • If you are planning to run Drupal 9 on Apache, you should have at least version 2.4.7 of the same.
  • PHP 7.3 is the minimum requirement of Drupal 9. PHP 7.4 can be supported too but it is not required. 
  • Despite the fact that Drupal core does not require Drush, many people do use it. However, as of now, Drush will only provide Drupal 9 compatibility in Drush 10. 
  • Besides these requirements, there are some other requirements which include:
  1. Version 5.7.8+is required if using Drupal 9 with MySQL or Percona.·        
  2. Version 10.3.7+ is required if using Drupal 9 with MariaDB.
  3. Version 3.26+ is required if using Drupal 9 with SQLite.
  4. Version 10 is required with the pg_trgm extension if using Drupal 9 with PostgreSQL. 

10. Has theming changed from Drupal 8 to Drupal 9? 

Drupal 9 has updated the Twig templating engine from Twig 1 to Twig 2. This up-gradation of Twig from version 1 to 2 implies that much of the work that has already been done to theme your site using Twig is completely reusable. 

11. Is there any update for third party dependencies in Drupal 9? 

Symfony 3 to 4.4:

The release of Drupal 9 is planned for security support for the most important third party dependency, called Symfony. Since Symfony 3's end of the date is November 2021, Drupal 9 is updated to Symfony 4.4. 

Twig 1 to 2:

Drupal 8 shows a heavy reliance on Twig 1.  Since there is no clear end of life date announced yet, Twig 2 has been launched for years which will be used by Drupal 9 users.

CKEditor 4 (not 5):

CKEditor 4 and 5 are two completely different codebases. Both Drupal 8 and 9 include CKEditor 4. Security support of CKEditor 4 will end around the end of Drupal 9’s life. Therefore, the community has decided to include CKEditor 5 in a future version of Drupal 9, deprecate CKEditor 4 in Drupal 9, and remove it in Drupal 10. 

jQuery and jQuery UI:

Re-evaluation of jQuery UI has resulted in the elimination of most of the components from the core. Only a limited number of components will remain as forked versions that can be used to repair future security issues. Drupal 9 will still be dependent on jQuery itself.

PHPUnit:

Drupal 8 diminished the very own SimpleTest testing system, giving support to PHPUnit. Drupal 9 requires PHPUnit 8 which is responsible for the updates of their PHP requirements strictly according to the support provided by PHP.

Doctrine:

Drupal 8 uses Doctrine's Simple Annotation Parser. However, this has received strong disapproval and will be discarded from a future release without any replacement. The part of the code is divided and included with the Drupal core. 

12. How much time will the contributed module and theme ecosystem take to be ready for Drupal 9?

The process of updating the majority of the top 200 Drupal 9 contributed modules is relatively simple. For this, the contributed project maintainer is required to remove deprecated code from the module or theme and further update the info.yml file in order to confirm compatibility with Drupal 9. Also, patches can be contributed by the developers in the Drupal community to make modules Drupal 9 compatible. 

13. Which modules are no longer supported in Drupal 9? 

The Place Blocks and SimpleTest modules have been removed from core in Drupal 9.

14. Is Drupal 9 difficult to use?

Is Drupal 9 difficult to use? Will I be able to work with Drupal 9? Will I be able to deliver easy access to regular users? You surely have these questions in your head. 

Well, the answer is no. Drupal 9 is an upgraded version of Drupal 8 which is built on the true spirit to provide an improved user-friendly experience. With every update that Drupal undergoes, it comes as a more powerful and user-friendly approach and this is why Drupal has come a long way. Using the tremendous technical power that Drupal offers, Drupal 9 creates an ideal user experience. Regardless of the job profile (content creator, a website developer, or IT support) you hold, you can count on continuous innovation in usability from Drupal.

15. Why choose Drupal 9 over other CMS platforms?

The software should always support your business model and not the other way around. Saying so, Drupal is an ideal CMS that provides a platform to deliver ambitious digital experiences. As the digital landscape continues to extend to more channels and touchpoints, a CMS like Drupal 9 is all you need in your store. Not to mention, Drupal 9 has a hold on the creation of powerful content creation tools, and efficient workflows that can nourish customer journeys. While the true power of Drupal 9 lies in its flexibility and richness, other CMS platforms focus on pre-defined templates or industry-specific solutions. 

16. What ideal tools do Drupal 9 provide to manage content deployment?

Drupal 9 offers the Workflows core module to manage the content deployment as well as editorial workflows in Drupal. The workflows module being an ideal tool is leveraged by major media organizations throughout the world. In addition to this, there are 2 other modules, namely the Content Moderation module and Workspaces module which are responsible to enhance the capability to manage content deployment in different workspaces. 

17. What are the various accessibility features that Drupal 9 will have built-in? 

The Drupal community has always stuck to its root, which means providing the best to its members. The release of Drupal 9 is no different and this is the reason why Drupal 9 is carrying forward the commitment to accessibility which began with the advent of Drupal 7. The existence of Drupal's Core Accessibility Gate feature (responsible for the core changes) in Drupal 9 is itself evidence of dedication to accessibility efforts. Major accessibility features included in Drupal 8 like full keyboard support, voice-to-text for visually impaired users, and media and layout enhancements will continue to be refined and worked on in Drupal 9. 

18. Is there any important security change to expect in Drupal 9? 

One of the main reasons behind Drupal 9 up-gradation lies in security enhancements. Drupal has always shown itself as a secure and ideal choice and the launch of Drupal 9 ensures that Drupal is secure and compatible with modern system requirements. As a matter of fact, Drupal 9 discards deprecated data code, implying working on a smaller codebase, thereby improving security standards and reducing security risks or errors. 

19. Does Drupal 9 offer the same kind of multilingual support that Drupal 8 offers? 

Drupal 9 is graced with all of the robust multilingual features that Drupal 8 has and does not require any re-architecture when updating. 

20. How will Drupal 9 support API-first/headless/decoupled deployments? 

Drupal 9 is built on Drupal 8's API-first architecture and thus it continues to be a leader in headless and decoupled solutions in the CMS market. However, headless//decoupled solutions may differ widely depending on the front-end technology being chosen.

21. Will Drupal 9 enhance movement towards more robust headless support and non-web content? 

With the advancement in technology, there is a huge interest in headless and non-web content with things like chatbots and IoT devices. As of now, there are no plans set to expand into more decoupled features, but the community will always look for change and innovation. There are a myriad of contributed modules that are solely dedicated to decouple and headless support. 

22. How does the new Layout Builder feature allow content editors to build and modify pages?

Drupal's Layout Builder allows content editors to build and modify pages visually using drag-and-drop. Using this feature, a heavy reliance on developers can be eliminated and marketing workflows can be increased. Speaking of the role of Layout builder, this tool lays its entire focus on providing layout tools for non-decoupled Drupal installations. In order to expose Layout Builder components through Drupal's API, a hybrid approach could be used in decoupled implementations.

23. How will Drupal 9 work in combination with disruptive technologies?

Voice, visual search, AR and VR displays are effectively new interaction and presentation models that are responsible for dealing with already existing data. The fundamental content modeling expertise of Drupal and its API-first design makes it a perfect fit to prototype these aforementioned interactions, or to build production applications.

24. What can we expect in Drupal 9 in the upcoming releases?

Making Drupal intuitive is the foremost priority of Drupal 9. Automated Updates Initiatives, adapted during Drupal 8, is being actively worked upon, which would help organizations to keep their sites in a proper and maintained state without requiring a lot of dev resources.

Olivero, a new frontend theme is lined up that can be used optimally for accessibility and front-end experiences. Olivero is being created for people like marketers, site designers, and content editors. 
Besides this, Drupal 9 includes dependency updates and removing deprecated code requirements which were not possible in Drupal 8.9 due to backward compatibility. 

Drupal 9.1 will be open for feature development of all the issues that cannot get into Drupal 9.0. It will also be the place to introduce new deprecations for Drupal 10 and all changes that are only allowed in minor releases. Drupal 9.1 will be released in December 2020.

25. How long will Drupal 9 be supported?

As stated earlier, Drupal 9 heavily relies on Symfony 4 which has an end of life in November 2023. After this, security bugs in Symfony 4 are not possible to get fixed. As a result, all users of Drupal 9 will have to upgrade to Drupal 10 by the end of 2023. 

26. What about Drupal 10?

Drupal 10 is planned to align with the life cycle of third-party projects that are closely integrated with Drupal, for example, Symfony and Twig. Since the Drupal community wants site owners at least one year to upgrade from Drupal 9 to Drupal 10, the community is hoping to jump in and make the next release i.e Drupal 10 in June 2022.

Moreover, new functionality for Drupal 10 is actually added to Drupal 9 releases, implying easy adoption of any new APIs by module developers. Drupal 10 removes all deprecated code providing developers a chance to stay up to date with API changes and thus making the upgrade to Drupal 10 a lot easier. 

Conclusion

The best of the Drupal community has worked hard to produce and deliver this masterpiece to the digital world. Years of hard work and determination have given birth to this higher-performing, robust, and more flexible solution. The change from Drupal 7 or 8 to Drupal 9 is not that easy, however, once you embark on the journey of Drupal 9, life will surely get much easier. 

Skeptical about how to migrate your site to Drupal 9 at ease? Contact us at hello@opensenselabs.com and our experts will help you with the best possible approach towards a successful Drupal 9 migration. 

blog banner blog image Drupal Drupal 9 Blog Type Articles Is it a good read ? On

Specbee: Get Up to Speed with the AMP module for Drupal – A brief Tutorial

Tue, 10/06/2020 - 13:06
Get Up to Speed with the AMP module for Drupal – A brief Tutorial Gurukiran 06 Oct, 2020 Top 10 best practices for designing a perfect UX for your mobile app

As the number of mobile users are increasing rapidly on a daily basis, it is essential to provide a speedy performance and uninterrupted user experiences for mobile users. AMP (Accelerated Mobile Pages) helps in improving the page load time for mobile experiences. Launched in October 2015 by Google, the open-source AMP project has been remarkably successful at expediting content to mobile devices. In this article we will talk about how you can install and configure the AMP module for your Drupal website. The Drupal AMP module supports Drupal 8 and Drupal 9.

AMP is an open-source HTML framework developed by Google’s AMP Open Source Project. AMP Pages provides mobile users with faster loading pages. Because Google is a sucker for speed and high performance, AMP also helps boost your SEO ranking. Google serves the AMP pages directly without going through the website which makes the page load lightning fast. The Drupal AMP Module provides valid AMP markup and a way to match the standards required for an AMP Page. This module converts the CSS into inline CSS. Currently, the AMP module only supports the conversion of the node pages.

Installing the AMP module for Drupal

You can set up the AMP module by downloading it through the composer with the command composer require 'drupal/amp'.
To enable the Drupal AMP module, go to ‘admin/modules’ and enable Accelerated Mobile Pages.
Note: Enable AMP Toolbar If you have the core Toolbar module enabled. Enable AMP RDF If you have the core RDF module enabled.

Configuring the AMP module

Once the module is enabled, you can use the Bartik AMP theme which is provided by the module. In the previous versions of the AMP module, the AMP theme needed to be used as a primary theme and you needed to extend a subtheme to customize how the AMP pages are displayed. However, the latest version gives you the ability to create an AMP theme as a subtheme of the primary theme.

The AMP theme should load the AMP library on every page and remove all the non-AMP JavaScript libraries and CSS. In the AMP theme, you can override the templates which violate the AMP standards.

After the installation, you need to configure the AMP theme and enable the content type for which the AMP subtheme can be applied. Go to ‘/admin/config/services/amp’

Once the Content type is enabled, click on “configure” which will take you to the Manage display page of that particular Content Type. In the Custom Display Settings, enable the AMP view mode.


Once the View mode is selected, use the AMP formatter for image, text, or iframe.

To check the AMP page, insert ‘?amp’ at the end of the page URL. For example:
/node/258?amp’\ . Make sure you replace the blocks with AMP blocks so the page can meet the AMP standards. 

Next, the site needs to be added to the Google search console. Once the website has been indexed, the AMP pages will be served to users in the search results. It is important that the page meets the standards defined by AMP.

Validation

You can use the Google chrome extension AMP Validator to check the validity of the AMP page. It helps in instantly checking if the current page is valid by rolling out a report indicating if there are any errors that need to be fixed. If there are no bugs, it will display a Green icon. If not, you will see a red icon with a list of bugs and warnings that will point out what needs to be fixed by you.
Alternatively, you can also use the Google search console URL inspection to check AMP status and to find out if there are any AMP errors. This tool enables validation for both AMP and non-AMP URLs and provides information on both.

Schema.org Metadata Module for Drupal

The Drupal Schema.org Metadata module is not a must-have module to create Drupal AMP websites but will be necessary to create a valid AMP markup to enhance the AMP site for Google search. It is recommended by Google to comply with the Schema.org standards and use structured data for a rich mobile search experience. By adding structured data in the AMP markup, you will be making your AMP site easier to find and target the right audience. This Drupal module lets you render valid schema.org structured data in the head of the AMP web pages in JSON-LD method. 

Delivering super-fast and high-performance websites is a necessity today regardless of the device the user is operating from. The AMP open-source initiative was a successful move by Google to deliver accelerated experiences from mobile devices. The Drupal AMP module is an extremely useful Drupal module that helps in easy and quick transformation of your Drupal web pages to comply with the AMP standards. Need help creating compelling AMP webpages with Drupal? Contact our Drupal experts today to find out how we can help.

Drupal Planet Shefali ShettyApr 05, 2017 Subscribe For Our Newsletter And Stay Updated Subscribe

Leave us a Comment

  Shefali ShettyApr 05, 2017 Recent Posts Image Get Up to Speed with the AMP module for Drupal – A brief Tutorial Image A Comprehensive tutorial on the ColorBox Module for Drupal 9 (And how to extend it) Image Why the AngularJS and Drupal Combination will make you rethink your web strategy Want to extract the maximum out of Drupal? TALK TO US Featured Success Stories

Know more about our technology driven approach to recreate the content management workflow for [24]7.ai

link

Find out how we transformed the digital image of world’s largest healthcare provider, an attribute that defined their global presence in the medical world.

link

Discover how a Drupal powered internal portal encouraged the sellers at Flipkart to obtain the latest insights with respect to a particular domain.

link