Technical Blog

The website encountered an unexpected error. Please try again later
| 8 min read
"The website encountered an unexpected error. Please try again later." this is the most common error encountered by a Drupal developer. Usually, errors are logged by Drupal and the logs can be accessed from Admin->Reports->Recent log messages. But when you get "The website encountered an unexpected error. Please try again later." you cannot even access the reports dashboard.
Zyxware default image4
| 2 min read
You can always create a view manually, and change the configuration one by one manually. And, all done. But, still, there is a chance of manual error. Drupal9 allows you to import-export views. You can follow the below steps to Import and Export views
Zyxware default image3
| 2 min read
In pre Drupal 8 era, the global variable $user was available every where, from you can easily get the current logged in user id. For all new version of Drupal, you should use \Drupal::currentUser()->id() Once you have the user id, you can use the User::load to get the user object.
Zyxware default image3
| 2 min read
Have you ever faced problems trying to delete all the contents of a particular content type in a Drupal website? Drupal is a CMS technology and supports Drupal developers/content writers to add content. I think content writers can face problems while trying to delete content. There are two modules in Drupal that help us overcome this issue, they are:
Zyxware default image4
| 2 min read
Clearing cache is something that a Drupal developer do frequently. Here are the 4 most popular ways to clear the cache. 1.Install the devel module which adds a cache clear option for administrators. You'll find a devel block to add to a region for quick cache clearing. 2. If you install the admin menu and get a quick menu in the top left for clearing various caches in Drupal.
Zyxware default image3
| 1 min read
We can install the latest version of drupal9 using the following command. composer create-project drupal/recommended-project my_site_name_dir This will create a project in 'my_site_name_dir' and automatically execute composer install to download the latest stable version of Drupal and all its dependencies. Your 'my_site_name_dir' will contain files that should be outside of your web root and not accessible by the web server. The web root will be 'my_site_name_dir/web'.
Zyxware default image3
| 2 min read
Actually, we can't install an incompatible module with the composer and apply a compatibility patch afterward. However, since issue forks are branches it's possible to install the module using that branch.  Under the repositories section where the composer source is listed, we need to add an exclude key for our module that we're trying to install using the issue fork. In the following example trying to install an issue for the homebox module. Complete repositories key look like  this now:
Zyxware default image1
| 2 min read
  We can use loadByProperties method in the \Drupal\Core\Entity\EntityStorageInterface.it will help us to search the file entity by the given file URI: /** @var \Drupal\file\FileInterface[] $files */ $files = \Drupal::entityTypeManager() ->getStorage('file') ->loadByProperties(['uri' => $uri]); /** @var \Drupal\file\FileInterface|null $file */ $file = reset($files) ?: NULL; In some other cases if you don't know the file URI    We can use the below code to get the URI: