PK's Diary - few pages from Purushotam Rai's Diary

Accessing Translated Entity in Views Twig | Drupal 8

purushotam — Mon, 12 Jul 2021 23:49:18 +0000

Accessing Translated Entity in Views Twig | Drupal 8 purushotam Tue, 07/13/2021 - 01:49

Though ideally if we use the views correctly and override them well, Drupal Views itself take care of getting the translated version as per configurations of the view. For details check this: EntityField::getValue

But if somehow we wanna get translated version of the entity in a views twig, we will have to get the current language and then call ContentEntityBase::getTranslation on the entity of the views row. And there are various ways of getting the current language in the views-view.html.twig:

#1 Use preprocess to add current language

Storing extra information for any entity in Drupal

purushotam — Sat, 03 Apr 2021 21:20:04 +0000

Storing extra information for any entity in Drupal purushotam Sat, 04/03/2021 - 23:20

A lot of times we come across a requirement where we need to manage some additional data for the Drupal entities. Now, if we think simply, the solution is to create fields .. right... easy and best, that's what Drupal is all about, entities and their properties as fields. But, there can be scenarios where the entity is not fieldable (as of now).

We will be specifically focusing on them in this post, though this can be implemented for any entity, the key is to understand what we want to solve and how, it's a kind of trade-off that we need to do while making any decision. As I always say Drupal has a lot of ways to solve a problem statement, it's you who decide which is the efficient one. You may not find the below solution as most efficient or scalable for you, but definitely, you would draw some important knowledge/information from this post.

Making a variable available (as global) in all twig files in Drupal

purushotam — Tue, 30 Mar 2021 23:28:39 +0000

Making a variable available (as global) in all twig files in Drupal purushotam Wed, 03/31/2021 - 01:28

Most of us know, the ideal way of making a variable available in a specific twig file is to use hook_preprocess_HOOK. But what if we have a requirement that we need a kind of global variable that should be accessible in any twig file. So, that we are able to use it wherever we want to, without additional pain.

The best part of Drupal is, everything is possible. But at the same time, there is a trick, you always have more than one way of doing things. And now it's in your hands to pick up the best suitable performant way for your solution.

So, over here you have the following solutions (which I can instantly think for this problem statement):

Acquia Backend Specialist Certification Guide

purushotam — Sat, 27 Feb 2021 21:49:22 +0000

Acquia Backend Specialist Certification Guide purushotam Sat, 02/27/2021 - 22:49

Recently completed Acquia Backend Specialist Certification thought to share my thoughts around this certification exam that might help the aspiring ones. While preparing for this exam, I had heard that this is the toughest exam out of all the Acquia Drupal Certifications and in my opinion, this rumour is true.

Actually, these certifications might be easy for others but were not for me, as, since last 1.5 yrs I have been working in Drupal 7 only. When I started preparing for this exam, I followed the same preparation pattern which I used while preparing for Acquia Drupal 8 Developer Certification Exam.