x

Show the favicon in bootstrap barrio sub theme

  Andrew Fletcher     published: 20 June 2023         1 minute read

Having a situation where I'm running a sub theme based on Bootstrap Barrio, but I want to be able to see the favicon in the sub theme.  Like many situations, once you know where to look the solution is quite simple.  Yet the path of discovery can take time.

In hunting down a solution, I looked into the theme settings yaml file.  But to no avail.

 

Solution

In your config > sync directory, find your {theme}.settings.yml file.  It will look something similar to the following

_core:
  default_config_hash: {some hash}
favicon:
  use_default: 1
features:
  comment_user_picture: 0
  comment_user_verification: 0
  favicon: 0
  node_user_picture: 0
logo:
  path: themes/custom/{theme}/assets/images/theme-Logo.svg
  use_default: 0
bootstrap_barrio_library: production
bootstrap_barrio_source: bootstrap_barrio/bootstrap_cdn
bootstrap_barrio_fluid_container: 1
bootstrap_barrio_region_clean_top_header: 0
bootstrap_barrio_region_class_top_header: row
bootstrap_barrio_region_clean_top_header_form: 0
bootstrap_barrio_region_class_top_header_form: row
/...

Change the favicon reference to true, as follows

  favicon: 1

So the file now becomes

_core:
  default_config_hash: {some hash}
favicon:
  use_default: 1
features:
  comment_user_picture: 0
  comment_user_verification: 0
  favicon: 1
  node_user_picture: 0
logo:
  path: themes/custom/{theme}/assets/images/theme-Logo.svg
  use_default: 0
bootstrap_barrio_library: production
bootstrap_barrio_source: bootstrap_barrio/bootstrap_cdn
bootstrap_barrio_fluid_container: 1
bootstrap_barrio_region_clean_top_header: 0
bootstrap_barrio_region_class_top_header: row
bootstrap_barrio_region_clean_top_header_form: 0
bootstrap_barrio_region_class_top_header_form: row
/...

 

Clear your cache and the favicon is visible in your sub theme.

Related articles

Andrew Fletcher • 25 May 2024
Connecting AWS S3 with Docker for Drupal 10
Recently, I encountered an issue where my local Docker environment refused to connect to AWS S3, although everything worked seamlessly in AWS-managed environments. This challenge was not just a technical hurdle; it was a crucial bottleneck that needed resolution to ensure smooth Drupal deployments...
↑