Module Description
Provides a block using the Dropbutton element to switch site language. Rather than the Language Switcher (Language modules basic block) that is an unordered list of links.
*
*
* Block will 'appear' when more than one language is active. Otherwise content is empty.
* Current Language appears at top of list. Otherwise by Language Weight
* Each list item has a class for it's language allowing for background image (flag) attached via theme level. For a great base of icons try: flag-icon-css.
* Options to display language link titles by:
* Language Name (translation UI)
* Language ID
* Native Name
* Custom Labels (per block instance)
* SEO Feature: Option to hide links to untranslated Entities. Sub-option: keep block render in place if no other translation path is available
* Is friends with Bootstrap! v3.8+ #2901106. Bootstrap themes will switch Drupal's native Dropbutton element with Bootstrap Dropdown
* Versions lines 3.1, 3.2 & 4 are Feature Balanced
A Few Mentions:
* About 'hreflang' and Language Blocks: @SEO The hreflang attribute is used with all links within the language block, unlike other 'menu' blocks. This is why dead links to other non-published, or relinking/redirecting to the frontpage: is bad!
* Panels, Views & Other Route Controlling Things These such contrib tools do not conform to building pages that connect as Translated Nodes (or other such Content Entities) do. °This is why they do not have 'translation links'. (*Also possibly the next version of Drupal/Symfony routing may have better translation routing support and such tools could then adopt said tools..). Now that Drupal has it's own Layout tool built ontop of Nodes -- Nodes remain the way to produce such landing pages and attach field/blocks via Layouts while keeping ready for translation. ° See this project Plan Issues as related possible plugins. * In Theory…
* Language Icons…
* flagsarenotlanguages Design vs Communication.
* languageicon.org
Dependencies:
* Language (core)
* Block (core)
* Node (core)
Soft Dependencies:
* (core) Locale and Content Translation
Summary Reminder Nodes (Content Entities) are the base of determining translation children: Views, Panels, Custom Routes have no ability to 'find a translation of'.
Config path:
* /admin/config/regional/dropdown-language-switcher
* /admin/config/regional/language — General Language Setup (core)
Similar As (yet better than):
* Language Switcher Dropdown
* Toolbar Language Switcher
* Language Switcher Extended
* Language Switcher Enhanced
* Language Switch Links
*
*
* Block will 'appear' when more than one language is active. Otherwise content is empty.
* Current Language appears at top of list. Otherwise by Language Weight
* Each list item has a class for it's language allowing for background image (flag) attached via theme level. For a great base of icons try: flag-icon-css.
* Options to display language link titles by:
* Language Name (translation UI)
* Language ID
* Native Name
* Custom Labels (per block instance)
* SEO Feature: Option to hide links to untranslated Entities. Sub-option: keep block render in place if no other translation path is available
* Is friends with Bootstrap! v3.8+ #2901106. Bootstrap themes will switch Drupal's native Dropbutton element with Bootstrap Dropdown
* Versions lines 3.1, 3.2 & 4 are Feature Balanced
A Few Mentions:
* About 'hreflang' and Language Blocks: @SEO The hreflang attribute is used with all links within the language block, unlike other 'menu' blocks. This is why dead links to other non-published, or relinking/redirecting to the frontpage: is bad!
* Panels, Views & Other Route Controlling Things These such contrib tools do not conform to building pages that connect as Translated Nodes (or other such Content Entities) do. °This is why they do not have 'translation links'. (*Also possibly the next version of Drupal/Symfony routing may have better translation routing support and such tools could then adopt said tools..). Now that Drupal has it's own Layout tool built ontop of Nodes -- Nodes remain the way to produce such landing pages and attach field/blocks via Layouts while keeping ready for translation. ° See this project Plan Issues as related possible plugins. * In Theory…
* Language Icons…
* flagsarenotlanguages Design vs Communication.
* languageicon.org
Dependencies:
* Language (core)
* Block (core)
* Node (core)
Soft Dependencies:
* (core) Locale and Content Translation
Summary Reminder Nodes (Content Entities) are the base of determining translation children: Views, Panels, Custom Routes have no ability to 'find a translation of'.
Config path:
* /admin/config/regional/dropdown-language-switcher
* /admin/config/regional/language — General Language Setup (core)
Similar As (yet better than):
* Language Switcher Dropdown
* Toolbar Language Switcher
* Language Switcher Extended
* Language Switcher Enhanced
* Language Switch Links
Module Link
Project Usage
7745
Security Covered
Covered By Security Advisory
Version Available
Production
Module Summary
This module aims to provide a block using the Dropbutton element for switching site language, offering options for displaying language link titles and SEO features like hiding links to untranslated entities.
Data Name
dropdown_language
OPENAI CHATBOT
OPENAI CHATBOT
