Modules

Are my favorite modules ready for D9?

lynette@tag1consulting.com — Wed, 01 Sep 2021 14:49:12 +0000

As everyone in the Drupal community knows, Drupal 8 was a major shift in the way the software was built and will be developed into the future. Prior to Drupal 8, each major release essentially caused major rewrites for core and all of the contributed modules. Drupal 8 aimed to fix this; moving forward, Drupal upgrades will be easy and fast. You get a great return on investment upgrading to D9 because you can seamlessly upgrade to Drupal 10, then 11. Development is looking forward to newer versions, not looking back. This is great news if you want to upgrade to Drupal 9. Over half of the top 50 D7 contrib modules have versions which are Drupal 9 compatible or have compatible releases in progress. Many or all of the features you rely on are ready to go in the new versions. Upgrading modules to Drupal 8 or greater has been an iterative process, like previous versions. Issue trackers, sprints, and focused sessions helped move many of the major modules into readiness for later versions. There aren't many sprints for Drupal 7 development anymore, but there are people working to upgrade D7 modules to D8 and D9. ## What does...

lynette@tag1co… Wed, 09/01/2021 - 07:49

Background Image - A New Drupal 8 Module

markhalliwell — Wed, 29 Nov 2017 01:00:00 +0000

If your site is designed around utilizing background images, then this module is for you! Whether you need a surgical implementation that only administrators/developers can implement or provide the ability to allow users to attach their own background images to entities, this module has you covered. If your site is designed around utilizing background images, then this module is for you! Whether you need a surgical implementation that only administrators/developers can implement or provide the ability to allow users to attach their own background images to entities, this module has you covered.

markhalliwell Tue, 11/28/2017 - 17:00

Nedjo Rogers

dylanclear — Wed, 22 Apr 2015 17:24:55 +0000

Nedjo Rogers is a Senior Performance Engineer with Tag1 based out of Victoria, Canada. He’s been an active Drupal contributor since 2003, has served as an advisory board member of the Drupal Association, and has led Drupal development projects for clients including Sony Music, the Smithsonian Institute, the Linux Foundation, and a number of nonprofit organizations. He’s also the co-founder of Chocolate Lily, where he builds web tools for nonprofits, including the Drupal distribution Open Outreach.

dylanclear Wed, 04/22/2015 - 10:24

How to Maintain Contrib Modules for Drupal and Backdrop at the Same Time - Part 3

david — Thu, 26 Feb 2015 14:54:26 +0000

This is the third in a series of blog posts about the relationship between Drupal and Backdrop CMS , a recently-released fork of Drupal. The goal of the series is to explain how a module (or theme) developer can take a Drupal project they currently maintain and support it for Backdrop as well, while keeping duplicate work to a minimum. In part 1 , I introduced the series and showed how for some modules, the exact same code can be used with both Drupal and Backdrop. In part 2 , I showed what to do when you want to port a Drupal module to a separate Backdrop version and get it up and running on GitHub. In part 3 (this post), I'll wrap up the series by explaining how to link the Backdrop module to the Drupal.org version and maintain them simultaneously. Linking the Backdrop Module to the Drupal.org Version and Maintaining Them Simultaneously In part 2 I took a small Drupal module that I maintain ( User Cancel Password Confirm ) and ported it to Backdrop. In the end, I wound up with two codebases for the same module, one on Drupal.org for Drupal 7, and one on GitHub...

david Thu, 02/26/2015 - 06:54

How to Maintain Contrib Modules for Drupal and Backdrop at the Same Time - Part 2

david — Tue, 17 Feb 2015 16:00:00 +0000

This is the second in a series of blog posts about the relationship between Drupal and Backdrop CMS , a recently-released fork of Drupal. The goal of the series is to explain how a module (or theme) developer can take a Drupal project they currently maintain and support it for Backdrop as well, while keeping duplicate work to a minimum. In part 1 , I introduced the series and showed how for some modules, the exact same code can be used with both Drupal and Backdrop. In part 2 (this post), I'll explain what to do when you want to port a Drupal module to a separate Backdrop version and get it up and running on GitHub. In part 3 , I'll explain how to link the Backdrop module to the Drupal.org version and maintain them simultaneously. Porting a Drupal Module to Backdrop and Getting it Up and Running on GitHub For this post I’ll be looking at User Cancel Password Confirm , a very small Drupal 7 module I wrote for a client a couple years back to allow users who are canceling their accounts to confirm the cancellation by typing in their password rather than having to go...

david Tue, 02/17/2015 - 08:00

How to Maintain Contrib Modules for Drupal and Backdrop at the Same Time

david — Thu, 05 Feb 2015 16:22:40 +0000

Part 1 - Reuse the Same Code In mid-January, the first version of Backdrop CMS was released. Backdrop is a fork of Drupal that adds some highly-anticipated features and API improvements to the core Drupal platform while focusing on performance, usability, and developer experience. When an open-source fork makes the news, it's often because it was born from a fierce, acrimonious battle (example: Joomla forking from Mambo ); the resulting projects compete with each other on the exact same turf and developers are forced to choose sides. Backdrop's goal, however, is not to destroy or replace the original Drupal project. Rather, it aims to be a "friendly fork" that focuses on Drupal's traditional audience of site builders and developers, an audience which the Backdrop founders believe are being slowly left behind by the Drupal project itself. Because of this, I expect that many existing Drupal developers will not want to choose between the platforms, but instead will continue working with Drupal while also beginning to use Backdrop. In this series of blog posts, I will explain how a module (or theme) developer can take a Drupal project they currently maintain and support it for Backdrop as well, while keeping duplicate...

david Thu, 02/05/2015 - 08:22