Subscribe to Planet Drupal feed
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 4 hours 47 min ago

Chapter Three: An Experiment: GraphQL in Twig

Thu, 2020/12/03 - 8:27pm

While experimenting with Gatsby + Drupal and doing research for my previous posts here, I came across the GraphQL Twig module.

This module is beta and hasn't had a lot of activity. I'm not sure how it addresses some deep Drupal theme issues, but it presents an interesting idea:

"The GraphQL Twig module allows you to inject data into Twig templates by simply adding a GraphQL query. No site building or pre-processing necessary."

Categories:

Amazee Labs: Why do enterprises trust Amazee Labs and our Open Source Tech Stack over WordPress based solutions?

Thu, 2020/12/03 - 7:23am
<img src="https://www.amazeelabs.com/sites/default/files/styles/leading_image/public/images/current-affairs/Amazee-Labs-Tech-Stack-over-WP.png?h=994a2424&amp;itok=WPKZyXz3" width="1120" height="630" alt="Amazee Labs logo. Why do enterprises trust Amazee Labs and our Open Source Tech Stack over WordPress based solutions?" title="Why do enterprises trust Amazee Labs and our Open Source Tech Stack over WordPress based solutions?" class="image-style-leading-image" /> At their most simple, both Drupal and WordPress are open source PHP based Content Management Systems (CMS) which have evolved from simple beginnings to great prominence. In the early days of the “CMS wars” many web agencies positioned themselves on different sides of the question “which CMS is best?”
Categories:

undpaul: Happy Birthday! 10 years undpaul

Thu, 2020/12/03 - 1:00am
We really zeroed for the first time. undpaul had its 10th birthday yesterday - and that was celebrated! With hot wine, delicious food, party hats, and memories of one or the other highlight with the undpaul team - of course all Corona-compliant in a remote meeting.
Categories:

Lullabot: Decoupled Platforms: Contentful vs. Drupal

Wed, 2020/12/02 - 11:48pm

Many platforms are advertising the ability to manage content in one place while publishing it to multiple channels. They provide a way to model, manage, and create content and then expose that content via an API. 

These are decoupled-only (or headless) back-ends. The only way to present your content is to create an application that consumes the API, interprets it, and renders the content in your desired format.

Categories:

Drupal blog: Drupal 9.1.0 is available

Wed, 2020/12/02 - 8:45pm
What’s new in Drupal 9.1.0?

The first feature release of Drupal 9 includes the new experimental Olivero frontend theme and various additions to the Claro administration theme. Installer performance is improved 20% and full Composer 2 and PHP 8 support is available. Images with known dimensions are set to lazy-load by default to improve frontend performance.

Download Drupal 9.1.0

New experimental Olivero theme

A new beta experimental frontend theme has been added to Drupal core called Olivero. This is a new modern and clear theme that is planned to become the new default Drupal theme later (replacing Bartik). Subtheming Olivero is currently not supported, but formal support may be included in the future.

The theme is named after Rachel Olivero (1982-2019). She was the head of the organizational technology group at the National Federation of the Blind, a well-known accessibility expert, a Drupal community contributor, and a friend to many.

Key additions to the Claro theme

The experimental Claro administration theme introduces designs for various key pages: the extensions administration page, views administration, status report and media library received Claro styled designs.

Composer 2 and PHP 8 support

Drupal 9.1 is fully compatible with Composer 2. If you are using Composer 1, now would be a great time to update. Most plugins used on Drupal sites are compatible and/or obsolete with the new version. The memory and performance requirements reduced dramatically, which should improve your experience.

PHP 8 is also supported in Drupal 9.1, including all of Drupal's dependencies. There may be contributed projects that are not fully compatible though. Drupal 9 is still compatible with PHP 7.3 and older. There are various exciting new features in PHP 8, but the JIT compiler and performance improvements are not likely to affect Drupal. Drupal 10 is planned to require PHP 8 in 2022. It is worth examining the support timelines of PHP versions to schedule your platform updates.

Other improvements

Installer performance is improved 20%, so getting a new Drupal site set up will be faster.

Images rendered by Drupal with known dimensions will be set to lazy-load automatically. This means browsers will only load them when they should appear in the viewport of the user, improving the user experience by making content appear faster.

Drupal 10 is planned for mid-2022. While Drupal 9 keeps requiring Symfony 4, Drupal 9.1 includes adjustments required to support Symfony 5 already.

What does this mean for me? Drupal 8 site owners

Update at least to 8.9.x to continue receiving bug fixes until the end of life of Drupal 8 in November 2021. The next bug-fix release (8.9.11) is scheduled for January 6, 2021. (See the release schedule overview for more information.) As of this release, sites on Drupal 8.8 will no longer receive security coverage.

We suggest that you update from Drupal 8 to Drupal 9 though. Updating is supported directly from 8.8.x and 8.9.x. Of the top 1000 most used drupal.org projects, 85% are updated for Drupal 9, so there is a high likeliness that most of the modules and themes you rely on are compatible.

Drupal 7 site owners

Drupal 7 support was extended to November 28, 2022, and will continue to receive bug and security fixes throughout this time. From November 2022 until at least November 2025, the Drupal 7 Vendor Extended Support program will be offered by vendors.

On the other hand, the migration path for Drupal 7 sites to Drupal 9 is stable. Read more about the migration to Drupal 9.

Translation, module, and theme contributors

Minor releases like Drupal 9.1.0 include backwards-compatible API additions for developers as well as new features.

Since minor releases are backwards-compatible, modules, themes, and translations that supported Drupal 9.0.x and earlier will be compatible with 9.1.x as well. However, the new version does include some changes to strings, user interfaces, internal APIs and API deprecations. This means that some small updates may be required for your translations, modules, and themes. Read the 9.1.0 release notes for a full list of changes that may affect your modules and themes.

This release has advanced the Drupal project significantly and represents the efforts of hundreds of volunteers and contributors from various organizations. Thank you to everyone who contributed to Drupal 9.1.0!

Categories:

Jacob Rockowitz: Webform 6.x is almost here

Wed, 2020/12/02 - 5:55pm

I’d like to begin by saying most people will not notice any significant difference between Webform 8.x-5.x and Webform 6.x because most of the noteworthy changes are happening under the hood to APIs and configuration: there was a bump in the Webform module's road to Drupal 9, which helped fix subclassing and stop the overriding constructors. This change became the initial commit to the Webform module's 6.x branch. Most of the subsequent commits to the Webform 6.x branch addressed the removal of deprecated code plus some minor tweaks to settings and options.

Removing the Webform module's dependency on jQueryUI

The most noticeable change in Drupal 9 and Webform 6.x is most jQuery UI asset libraries are deprecated and moved to contrib modules. The Webform module was using the jQueryUI's Tabs, Tooltip, and Date picker plugins. Although I considered keeping the requirement of these plugins using Drupal's corresponding jQueryUI modules, after some nudging from the Drupal community, I decided to replace the jQueryUI Tabs and Tooltip and make the jQueryUI Date picker an optional dependency.

The jQuery UI Tabs plugin was replaced with Tabby, a lightweight, accessible vanilla JS toggle tabs library. Since tabs only appear within the Webform module's admin UI, I felt that Tabby was the most straightforward solution without having the Webform module provide its own tabs implementation.

Below is a screenshot of Tabby in the Webform module's user interface.

Replacing the Read More

Categories:

Axelerant Blog: Upgrading Drupal to PHP 8

Wed, 2020/12/02 - 12:09pm
Categories:

Agiledrop.com Blog: Keeping control of your project when outsourcing software development

Wed, 2020/12/02 - 10:25am

In this article, we discuss the importance and different options of keeping control of your project when outsourcing development.

READ MORE
Categories:

Lucius Digital: Using Drupal and Bootstrap HTML? An easy snippet for great Toasts instead of boring Drupal messages :)

Wed, 2020/12/02 - 9:47am
So we wanted to implement the great Bootstrap Toasts feature in our social productivity Drupal distro OpenLucius. HTML framework Bootstrap provides Toasts out of the box. After some trial and error, the end result seems fairly easy to use for everybody. So here is how:
Categories:

Promet Source: Visual Impact and Great UX for High-Stakes Objectives

Wed, 2020/12/02 - 12:55am
Early in 2020, as COVID-19 began to seize headlines, counties throughout California were on the front lines as “hotspots,” and citizens of Marin County were paying close attention. 
Categories:

Specbee: A Brief Guide to Node Package Manager (NPM) in Drupal

Tue, 2020/12/01 - 3:55pm
A Brief Guide to Node Package Manager (NPM) in Drupal Shruthi Shetty 01 Dec, 2020 Top 10 best practices for designing a perfect UX for your mobile app

Node Package Manager (NPM) is an open-source software library that has over 800,000 code packages. In simple terms, we can say that NPM is a command-line tool that installs, updates, or uninstalls node.js packages of an application.

Installation

Inside the project theme folder, directly run the npm install command. It will install all the packages that are there in the package.json file.
Once done, you can verify the NPM installation by writing the following command in the command prompt. This will show you the version of the NPM.

npm -v

If you have older version of NPM then you can update it to the latest version using this command:

npm install npm -g

We can use NPM in two different modes: Global and Local mode.
Global mode - It performs operations which affects all the Node.js applications on the computer.
Local mode - It performs operations for a particular local directory which affects an application in that directory only.

How to add Dependency into package.json

NPM packages are all defined in one file called package.json. The content inside package.json must be written in JSON format. The two necessary fields in that file are ‘name’ and ‘version’.
The main goal of this is automated dependency and package management. Here, you can specify all your project/application dependencies within the package.json file.

Here “test” is the name of the Project and version number is given as “1.0.0”.

The dependency packages that are required for “test” project are : Bootstrap, gulp and gulp-sass along with their versions.

Run the below command in the terminal to install the node modules inside your project theme folder.  

npm install

Once you run this command, all the dependency modules will get installed.

Inside the node_modules folder you will see the dependency modules that get installed.

Gulp is a task runner. It can do many things. It uses the JavaScript code and helps run front-end tasks for large scale web applications. It also builds system automated tasks like CSS preprocessing, HTML minification, concatenating library files, compiling the SASS files, and more. Here we are using Gulp to convert .scss files into .css.

Inside the gulpfile.js we are going to assign the tasks that can be done by Gulp.

When using functionalities that are not Drupal, we need to import the CSS or JS files with respect to that module as a library in theme_name.libraries.yml. Next, we need to call the library with respect to that particular twig file to see the required changes. 
This way we can use other NPM packages like slick-carousel, responsive tabs etc. to your project using this command:

This way we can use other NPM packages like slick-carousel, responsive tabs etc. to your project using this command:

npm install

Use this command to update the packages:

C:\MyNodeProj> npm update


To uninstall the package, use this command:

C:\>npm uninstall

Node Package Manager is a very useful tool for developers to automate a lot of front-end tasks. It lets you install and play around with tons of third-party libraries to run difficult and time-consuming tasks. In this brief guide we have discussed about NPM installation and the usage of Gulp in Drupal. If you found this blog useful, don’t forget to sign up to our newsletter so you don’t miss out on our latest insights by our Drupal experts.

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

Leave us a Comment

  Shefali ShettyApr 05, 2017 Recent Posts Image A Brief Guide to Node Package Manager (NPM) in Drupal Image How to Migrate to Drupal 8 from a SQL source in 6 Simple Steps Image How to Configure Faceted Search for Drupal 8 (and 9) – An easy step-by-step tutorial 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
Categories:

Axelerant Blog: It’s Time To Update The Drupal Core

Tue, 2020/12/01 - 2:24pm
Categories:

ADCI Solutions: Why upgrade PHP: a guide without complicated explanations

Tue, 2020/12/01 - 12:32pm

PHP 8 is here! But we bet that many of the Drupal websites you’ve been working on haven’t even upgraded to PHP 7.4 yet. Meanwhile, upgraded software is a great deal when it comes to security and performance. 

We've prepared the article with short and clear explanations about the necessity of updates and the update process itself.

Read Why upgrade PHP

 

Categories:

Drupal core announcements: Feedback needed: Dropping support for Internet Explorer 11 in Drupal 10

Mon, 2020/11/30 - 1:25pm

We are currently planning for Drupal core to drop support for Internet Explorer 11 in Drupal 10 (scheduled to be released in June 2022). Drupal 9 will be supported until late 2023, which means that sites that want to support Internet Explorer 11 can continue using Drupal 9 until then.

Feedback needed from assistive technology stakeholders

WebAIM's survey of screen reader users shows Internet Explorer 11 usage dropping from 23.3% in October 2017 to 10.9% in September 2019. The next edition of their survey is likely to be released at the end of 2021, but we need to finalize our browser support within the next month in order to develop and release Drupal 10 on schedule.

We need feedback from assistive technology users and accessibility stakeholders. Do you or your users still use Internet Explorer 11 with screen readers? Do their screen readers support browsers other than Internet Explorer 11? How feasible is it to upgrade to a different browser for use with your screen reader? We are requesting feedback until December 18th, 2020.

Why would we drop support for Internet Explorer 11?
  • Microsoft stopped developing Internet Explorer 11 in 2015. For that reason it is significantly behind modern browsers that have continued development. Because more and more libraries are adopting the use of those features, there is a significant cost associated with maintaining Internet Explorer 11. For example, the latest major release of CKEditor has dropped support for Internet Explorer 11, which means that Drupal 10 cannot securely support both CKEditor5 and Internet Explorer 11.

  • Microsoft itself has dropped support for Internet Explorer 11 in many of its services, and the rest will drop support in mid-2021.

  • Usage of Internet Explorer 11 has decreased significantly. Drupal doesn’t collect analytics on browser usage from its end users, so we rely on data provided by other projects such as Wikimedia, WebAIM, and Statcounter. For example, in October 2019, Wikimedia had 4.4% of its traffic using Internet Explorer 11. At the same time this year the number had dropped to 1.4%. We assume that the number of Internet Explorer 11 users will continue decreasing before the release of Drupal 10.

  • Supporting Internet Explorer 11 degrades the experience for everyone. We currently supply all users extra code to make Internet Explorer 11 work. This increases the request size and makes page load time slower for everyone.

  • The additional requirements of Internet Explorer 11 demand additional development time that far exceeds the browser's market share. These efforts come at the expense of new features and bug fixes.

What if I need to support Internet Explorer 11?

Even if Drupal 10 drops support for Internet Explorer 11, you can continue using Drupal 9 until late 2023. We recommend advising your users to move to another browser before that. If you believe your users have specific requirements as to why they cannot move from Internet Explorer 11, post them on the Internet Explorer 11 policy discussion.

Would this affect Drupal 7?

No. Drupal 7 remains compatible with Internet Explorer 11. A separate announcement will be issued if that changes.

Categories:

Drupal Core News: Feedback needed: Dropping support for Internet Explorer 11 in Drupal 10

Mon, 2020/11/30 - 1:25pm

We are currently planning for Drupal core to drop support for Internet Explorer 11 in Drupal 10 (scheduled to be released in June 2022). Drupal 9 will be supported until late 2023, which means that sites that want to support Internet Explorer 11 can continue using Drupal 9 until then.

Feedback needed from assistive technology stakeholders

WebAIM's survey of screen reader users shows Internet Explorer 11 usage dropping from 23.3% in October 2017 to 10.9% in September 2019. The next edition of their survey is likely to be released at the end of 2021, but we need to finalize our browser support within the next month in order to develop and release Drupal 10 on schedule.

We need feedback from assistive technology users and accessibility stakeholders. Do you or your users still use Internet Explorer 11 with screen readers? Do their screen readers support browsers other than Internet Explorer 11? How feasible is it to upgrade to a different browser for use with your screen reader? We are requesting feedback until December 18th, 2020.

Why would we drop support for Internet Explorer 11?
  • Microsoft stopped developing Internet Explorer 11 in 2015. For that reason it is significantly behind modern browsers that have continued development. Because more and more libraries are adopting the use of those features, there is a significant cost associated with maintaining Internet Explorer 11. For example, the latest major release of CKEditor has dropped support for Internet Explorer 11, which means that Drupal 10 cannot securely support both CKEditor5 and Internet Explorer 11.

  • Microsoft itself has dropped support for Internet Explorer 11 in many of its services, and the rest will drop support in mid-2021.

  • Usage of Internet Explorer 11 has decreased significantly. Drupal doesn’t collect analytics on browser usage from its end users, so we rely on data provided by other projects such as Wikimedia, WebAIM, and Statcounter. For example, in October 2019, Wikimedia had 4.4% of its traffic using Internet Explorer 11. At the same time this year the number had dropped to 1.4%. We assume that the number of Internet Explorer 11 users will continue decreasing before the release of Drupal 10.

  • Supporting Internet Explorer 11 degrades the experience for everyone. We currently supply all users extra code to make Internet Explorer 11 work. This increases the request size and makes page load time slower for everyone.

  • The additional requirements of Internet Explorer 11 demand additional development time that far exceeds the browser's market share. These efforts come at the expense of new features and bug fixes.

What if I need to support Internet Explorer 11?

Even if Drupal 10 drops support for Internet Explorer 11, you can continue using Drupal 9 until late 2023. We recommend advising your users to move to another browser before that. If you believe your users have specific requirements as to why they cannot move from Internet Explorer 11, post them on the Internet Explorer 11 policy discussion.

Would this affect Drupal 7?

No. Drupal 7 remains compatible with Internet Explorer 11. A separate announcement will be issued if that changes.

Categories:

Web Omelette: New Drupal module: multi-value form elements

Mon, 2020/11/30 - 10:04am

In this short article I want to introduce you to a new module we recently released on Drupal.org, namely Multi-value form element.

This small module provides a form element that allows you to easily define multi-value elements in your custom forms. Much like what field widgets provide with the Add another item Ajax button.

So how does it work? Easy, really. All you have to do is define a form element of the '#type' => 'multivalue' with one or more children, defined like you normally would. So for example:

$form['names'] = [ '#type' => 'multivalue', '#title' => $this->t('Names'), 'name' => [ '#type' => 'textfield', '#title' => $this->t('Name'), ], ];

Would give you this:

And you can also use multiple form element children if you want:

$form['contacts'] = [ '#type' => 'multivalue', '#title' => $this->t('Contacts'), 'name' => [ '#type' => 'textfield', '#title' => $this->t('Name'), ], 'mail' => [ '#type' => 'email', '#title' => $this->t('E-mail'), ], ];

So as you can see, no big deal to use. But all the complex Ajax logic of adding extra values is out of your hands now and can easily build nice forms.

Check out some more examples of how to use this element and what options it has above the Drupal\multivalue_form_element\Element\MultiValue class.

This module is sponsored by the European Commission as part of the OpenEuropa initiative and all the work my colleagues and myself are doing there.

Categories:

Yusef Blog: Auto Deploy a project with leveraging gitlab CI/CD

Sun, 2020/11/29 - 9:40pm
A few days ago Github again, prevents access to my personal private project on Github because I visited my home country last year. I decided to move my private repositories from Github to Gitlab. after migrating my project I noticed I haven't work with Gitlab for a long time and during this time it has added a lot of tools. like Bitbucket and Github it server very convenient CI/CD development that developers easily deploy their projects to servers without any cover.
Categories: