The upgrade to Drupal 10 is moving forward successfully as the new version approaches its final stages. The Drupal Config Split module produced unexpected results during our testing phase because of an identified software defect. Our Google Analytics data showed only a minor data gap because of this problem. The business operations of various organizations face significant risks because of such small disruptions. Your website displays outdated content to users while development modules that affect user experience negatively remain active and payment systems encounter the most severe disruptions. As Drupal 9 reached its end-of-life milestone in November 2023, we were proactive in transitioning our sites to Drupal 10. The transition period allowed us to acquire essential knowledge which would help us develop our client's platforms for Drupal 10 migration because we believe in continuous learning.
In Drupal 10, Google Analytics has some issues and thankfully we now know how to fix it! Here’s how.
How to use Drupal Config Split on your websites
The Drupal Configuration Management system operates as a fundamental tool which manages all administrative settings that determine how a Drupal website functions. The Drupal Config Split module functions as an essential extension which allows users to separate configurations for different scenarios or platforms. This module's functionality depends on companion modules such as Config ignore and Config Filter, essential components that extend beyond Drupal Core and necessitate manual installation and maintenance to ensure operational efficiency. The integration of these modules allows Drupal administrators to enhance their website management capabilities which results in improved website performance and greater flexibility for operational needs.
On your websites, use Drupal Config Split to separate out different settings for Google Tag Manager (GTM):
Non-production / local sites: GTM is not available at all in local environments.
Staging sites: are utilizing a staging GTM environment instead of the same GTM container as on live, which enables us to test GTM settings and any changes before deploying them to the live environment.
Production / Live Sites: The primary live GTM container is always on.
Our extensive work with Drupal client projects has shown that Config Split functions as an essential component for handling complex situations. The system operates through multiple advanced methods which enable it to detect and solve problems at the beginning stages of development which results in improved development process efficiency and effectiveness.
Deploying the Drupal 10 upgrade to production
Upon completing the upgrade of Drupal 10 to the production environment, an unexpected obstacle arose: the tracking of traffic by Google Analytics was not functioning as intended. The problem occurred because the system treated the live and production environments as if they were local environments. The problem occurred because Config Split prevented Google Tag Manager (GTM) from activating on the live site which resulted in a temporary loss of GA tracking. To fix this difference the configuration needed a manual activation in the production environment which quickly restored both GTM and GA services. The Drupal Config module contained a particular bug which prevented settings from being properly applied across different environments thus demonstrating the necessity for exact configuration management when building and maintaining websites.
Finding a permanent is a definite fix for the Drupal Config Split issue
In our examination of the Config Split, Config Ignore, and Config Filter modules, we discovered their high level of interdependence. Consequently, we decided to delve into the availability of known patches to enhance their functionality. It was observed that by updating Config Split along with its dependencies, automatic upgrades to the latest 1.x version of config_filter were facilitated. The Drupal 10 upgrade period determined that the latest version available at the time was 1.7. The development of these modules shows their essential connection while demonstrating the need for ongoing maintenance to reach peak operational efficiency and system integration.
Summary and Major takeaways
In conclusion, during our transition to Drupal 10, an oversight occurred when we failed to update the dependencies within the Config split module.The Config Split module stopped working properly because we did not coordinate the upgrade process and it requires config_filter version 1.6 or above. The system stopped functioning because Config Split module does not have a specific version requirement for config_filter which needs version 1.6 or higher.
Migrating from Drupal 9 to 10 highlights the vital necessity of paying close attention to every single detail. Your Config Filter modules must be thoroughly checked for version compatibility with 1.6 or above before performing any migration. Performing comprehensive testing of your Config settings in all environments represents a strong recommendation to detect any possible upgrade-related issues.
