Svelte is a very popular JS framework for developing exciting front end applications. It can be used to create standalone apps as well as embedding JS apps into your existing website. Here is how you can include a Svelte app in your Drupal website.

• Add your Svelte app folder to the module/theme folder.
• Declare the svelte JS and CSS in your libraries.yml file

  • svelte: js: sveltejs/public/build/bundle.js: {} css: theme: sveltejs/public/build/bundle.css: {}

• Attach the markup and library inside the render array

  • return [ '#markup' => '<div id="my-application"></div>', '#attached' => [ 'library' => [ 'my_module/svelte', ] ]
    ];

     

DDev is a very nice Docker-based local development tool preferred by many developers especially those using Apple M1 laptops. Setting up a Drupal website is pretty easy and straightforward but using Apache Solr requires users to perform a few additional steps:

1. Based on the documentation here, follow all the steps mentioned under the installation section.

2. Place the following snippet in your settings.ddev.php file

// Apache Solr settings for the DDev environment.
$config['search_api.server.solr']['backend_config']['connector_config']['scheme'] = 'http';
$config['search_api.server.solr']['backend_config']['connector_config']['host'] = 'example-website.ddev.site';
$config['search_api.server.solr']['backend_config']['connector_config']['port'] = '8983';
$config['search_api.server.solr']['backend_config']['connector_config']['core'] = 'dev';

It is very easy to start building a Drupal 9 website in your local once you have got a few things right. Since composer is a recommended way to use Drupal, I have mentioned instructions for a composer-based setup. Here are the steps along with relevant links to help you quickly set things up.

1. Install MAMP or MAMP Pro in your system (https://www.mamp.info/en/mac/)

2. Install composer and command-line PHP in your system. (https://getcomposer.org/download/, https://www.php.net/manual/en/install.macosx.php). You can also use the MAMP provided PHP in your CLI by checking the following link https://www.choosepizzi.net/mamp-lets-make-terminal-use-mamps-php-instead-of-macs-version/.

3. Download the zip file of the latest release from this page https://github.com/drupal/recommended-project/tags.

 4. Extract the content of the zip file to a folder let's say Drupal9 and place that folder in this directory /Applications/MAMP/htdocs/.

5. Go to the terminal and change your directory to '/Applications/MAMP/htdocs/' and run command composer install. This will download the latest code as well as all the dependencies. The codebase fro Drupal is placed in the 'web' directory.

6. Configure the VHost settings as per this blog post https://medium.com/@wilbo/adding-a-virtual-host-in-mamp-for-mac-a6c717cc0475. Make sure it is configured in such a way that the 'web' folder is the root of your application.

7.  Hit the configured URL from the browser and install Drupal.

It is very common to use exposer filters along with the views. By default, Drupal doesn't provide any option to sort out the values shown to a user in an exposed form filter. To overcome this, enable Better Exposed filters  and then you will get an option to sort the options shown in the exposed filter.

Whenever working on a multilingual website you must have noticed that views by default start showing all the translations of available nodes in separate rows. This might be a required behaviour sometimes but most of the time it is very confusing for the users and feels like content duplicacy. This can easily be solved by setting 2 additional settings in the views:

1. Add Filter -> Respective Entity (Translation Language) = Content Language Selected for the Page.

2. Rendering Language = Content Language Selected for the Page.

In case you are using relationships as well in the view (and related entities are marked translatable as well), you might have to set a translation language filter for all the entities. Feel free to set different values for these 2 options to achieve the required behaviour.       

Many times, we add a hook_update_n to change schema, perform relevant options for new release etc. Sometimes running this function manually is required to debug it's working or re run the logic which may not have been implemented because of failed updates. You can use Drush to run any particular function in this way:

drush php-eval "module_load_include('install', 'YOUR_CUSTOM_MODULE', 'YOUR_CUSTOM_MODULE'); YOUR_CUSTOM_MODULE_update_8001();"

You can configure token in this way to achieve this:

[node:source:title]
or
[node:source:field_example]

This will ensure that token will return title or field_example only in the original language in which they were created.

In case you are wondering how you can update Lando in your local system, here are easy steps to do the same:

1. Go to https://github.com/lando/lando/releases/ and check if there is any new release.

2. Go under the assets column and try to find the download link of the .deb release type. Eg: https://github.com/lando/lando/releases/download/v3.1.0/lando-v3.1.0.deb

3. Open the terminal and go to the 'Downloads' directory. (cd ~/Downloads).

4. Enter wget https://github.com/lando/lando/releases/download/v3.1.0/lando-v3.1.0.deb (The link you got from the release section.)

5. Enter sudo dpkg -i lando-v3.1.0.deb (The downloaded file is passed as a parameter to the command).

6. Verify the Lando version in local by entering the command lando version.

You can use the following snippet to load multiple nodes without getting timeout or memory-related issues.

use Drupal\node\Entity\Node; 
$nids = \Drupal::entityQuery('node')->condition('type', 'YOUR_CONTENT_TYPE')->execute();
$nodes = Node::loadMultiple($nids);
foreach ($nodes as $node) {  
  // Perform field-related operations.
  $field_value = $node->field_machine_name->getValue()[0]
}

You can use the following code snippet to change the required attribute of the path field in the node form alter in this way:

/**
 * Implements hook_form_FORMID_alter().
 */
function example_module_form_node_form_alter(&$form, &$form_state) {
  $form['path']['widget'][0]['#open'] = TRUE;
  $form['path']['widget'][0]['alias']['#required'] = TRUE;

}

This will keep the path tab open by default and mark the alias field as required.