Are you a Drupal Developer? Check out my new Online test for Drupal Developers page on this site.
This quiz is useful for Drupal devs with preparing for the technical interviews, and in general, it helps to refresh the knowledge in Drupal 8 modules development.
It is free and has no registration required.
Try to pass this Drupal exam online and share your results with friends!
When it comes to monetizing traffic on your websites, placing the Google Adsense code snippets has always been easy. Usually, the process is simple: the ad's code snippet has to be put into content block and then placed anywhere on site, or just hardcoded directly into site's templates.
However, if you have a list of posts built with a regular view and you want to periodically show some ad between them, the task requires some coding. As for me, it has always been a case, because I could not find any suitable simple Drupal module that would resolve this task.
So after all, in order to get rid of routine coding, I created a module called Views Row Insert.
Some specific tasks on Drupal-based API development which involves processing third party data like incoming ajax calls or POST requests may require that you will have to deal with these POST params directly somewhere within your drupal code but they might be not be available at the point due to other modules acitions or whatever.
By default, when data flow containing POST or GET values comes to page callback function defined in hook menu, those variables are usually available and accessible.
In some cases, you may want to dynamically insert a new row into your view results, or replace an existing one with the different entity.
Once working on the Drupal project, I faced a situation when I had to access the current loaded node fields in Rules. To be more specific, the content type had an email field and attached entity form. The task was to send the email using Rules to the email address which was set in a node field after submission the attached entity form.
The problem is that the only available fields I had were entity form fields and no fields from the node. So I came up to some custom and quick solution of creating custom Token which would contain the data from the node field.