Watchdog page load impact on Drupal websites
In Drupal, the Watchdog module (or the logging system) is responsible for logging messages, errors, and other information related to the operation of your Drupal site. This data is useful for monitoring and troubleshooting, but it can potentially impact page load times if not managed properly.
Lando setup running Drupal 10
Create a Lando setup running Drupal 10.
The command you provided appears to be a Lando configuration command for initialising a new Lando environment for a Drupal 10 project. Following is a breakdown of the command and what it does:
Twig\Error\SyntaxError: Unexpected "spaceless" tag
Adding Open AI to a Drupal site
Twig\Error\SyntaxError: Unknown "filter" tag
Twig error
Twig\Error\SyntaxError: Unknown "filter" tag. in Twig\Parser->subparse() (line 6 of themes/custom/{theme}/templates/views/views-view-field--products--field_product_type.html.twig).
Line 6 of the views-view-field--products--field_product_type.html.twig file is
{% filter upper|escape('html') %}
The actual Twig file code
TypeError: Cannot assign null to property Drupal\views\Plugin\views\argument\ArgumentPluginBase::$operator
Post upgrading from Drupal 9.5.10 to Drupal 10.1.3, I was seeing the following error when viewing a view page:
Drupal managing a patch to composer.json
To get Flysystem S3 ready for Drupal 10, I needed to apply the latest patch to the contrib module - Flysystem S3 (https://www.drupal.org/project/flysystem_s3).
Rather than using the current RC (2.0.0-rc5) release, which was released 25 March 2022. Instead, I'll be using the dev release - 2.0.x-dev updated 14 Aug 2023.
Drupal 9 to 10 upgrade an example of the actual steps taken
Continuing on from the Drupal 9 to Drupal 10 upgrade outline written earlier... Upgrading Drupal 9 to Drupal 10. However, the point of difference is this article works through the actual action steps of the upgrade.
Planning and testing is critical for the Drupal to version 10 process to work successfully. As some of the environments that I work in are deployed via CD/CI pipelines.
Could not delete /var/www/html/content/vendor/composer/
Attempting to run a composer update command, you know the one used regularly
composer update
I ran into a 'could not delete' response
Drupal - where has the Google ID disappeared?
On most of the sites I'm running the Google analytics ID is appearing. Therefore, tracking and capturing data. All except one!
Discovering where Google ID and Google Tag ID were on a client's site... or not in this situation. Yes that's correct, for some reason the analytics IDs aren't appearing. Zip, zero... nothing.
Looking on this site, Google tag Manager positions the tag ID in the following lines of code