In some cases, we might want to modify the form submission behaviour to better fit a particular use case. For instance, we would like to offer our own submit handler, and we will contact the original submit handler under specific circumstances.

Here, we'll utilise the module name example to change the way a form submits when its form ID is demo_form, which is provided by demo module. To do this, we'll create the code that follows in example.module file:

Many of use has faced challenges while upgrading Drupal core from 9 to 10 where some of the modules are not compatible with D10, we might have followed the forked issue approach solution which I have described in one of my previous posts (How to use the Drupal 9 module in a Drupal 10 project using Composer if its MR is already ready...).

We have often found that in the Drupal 9 project, multiple modules are not compatible with Drupal 10, and when we check the module issue queue, especially with the term "Automated Drupal 10 compatibility fixes", we can find at least one issue where the project update bot creates this issue automatically against each module and provides a patch with possible fixes except for making changes in module.info.yml.

Sometimes we need to create a pager for custom data sets, such as retrieving specific types of nodes and applying a filter on top of it to get the expected data set.

In this post, I am going to create a custom Drupal module named pager_example, which will create a pager for a custom data set.

Register a path where we will display a page with a pager using a custom data set. For that, I am going to create a routing file with the name "pager_example.routing.yml", which will have the following snippet: