When we updated our Drupal sites to Drupal 11 and also upgraded the DataLayer module to its latest version (2.1.0), we encountered an issue where all DataLayer variables passed to Google Analytics via Google Tag Manager were showing as undefined or not set. Further debugging revealed that this issue arises because the initialization of the DataLayer variables has been moved to the footer of the page and now uses a lazy build approach. Consequently, tags that trigger on the Pageview event in GTM might not have access to these variables, leading to incomplete or missing data in your analytics.
Technical Q&A
| 1
min read
A change introduced in Drupal 10 altered the way RSS feeds are generated. This change involved adding a tag nested within the element of each feed item. While seemingly minor, this change had unintended consequences. The issue has been fixed in Drupal 10.2.1.
Technical Q&A
| 3
min read
In Drupal, the default behaviour of entity reference fields allows us to select unpublished content if the content creator has permission to view unpublished content, which can be useful in specific scenarios where we need to establish relationships even with unpublished content.
However, in many cases, we want to refer only to published content. The problem arises when we add references during content creation without verifying whether the referenced items are published. This can lead to confusion later when we wonder why the referenced contents are not visible when viewing the content.
Here's a step-by-step guide on how to use a Drupal view to filter the values appearing in an entity reference field
Technical Q&A
| 1
min read
A step-by-step tutorial on how to configure Lando with Drupal to use a custom domain in your local development environment.
| 2
min read
A long-standing client in the financial news space in the US wanted to speed up their speed of processing and sending personalized emails from each portfolio holding.The site provided the latest stock market news which
Drupal Technical
| 3
min read
Drupal is a scalable and secure content management framework which help organizations build their digital platforms. In this article I am presenting a situation where Drupal helped implement a feature for one of our client, without affecting the site's scalability and secure nature.
The client’s site went down to maintenance mode for some users unexpectedly. This happens very rarely and there was no immediate visible reason that could point to the cause of it. So it was imperative that we log when the site goes offline in order to debug the issue.
Drupal Technical
| 3
min read
To keep the default values of the step one form after successfully submitting the step 2 form, here is an easy way. Just pass the form state values of step 1 form as query parameters to the same page on submitting step 2 form. Set the default values of step 1 form as, first check whether the form_state value is set. If yes, set the default values of step 1 form fields with the form_state values. Else check the URL query parameters, whether this variable is set. If yes, then set the default value with that value.
Technical Solution
| 3
min read
I was using Domain Access and Domain Variable modules in my project. I have a lot of domain specific variables which have different values on production, staging and development environments. It takes me a lot of time to set these variables with the corresponding staging and development values each time when I reset these environments. So I was thinking of creating a drush command to update all these configuration variables in single step and I did it.