Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.From OKV...
<ul class="toggle-wrapper"><li><a class="toggle-menu" href="#">Meny <span>☰</span></a></li><li><a class="toggle-search" href="#">Sök</a></li></ul>
class: mobile-menu-links
placed in Navigation bar region
| Comment | File | Size | Author |
|---|---|---|---|
| mobile_menu_links.png | 137.48 KB | kreynen |
Comments
Comment #1
kreynen CreditAttribution: kreynen commentedComment #2
kreynen CreditAttribution: kreynen commentedThis block needs to be defined and placed in the Navigation bar region by default.
Comment #3
libkuman CreditAttribution: libkuman commentedComment #4
libkuman CreditAttribution: libkuman commentedComment #5
kreynen CreditAttribution: kreynen commentedComment #6
kreynen CreditAttribution: kreynen commentedAfter trying the normal hook block in the .theme for an hour and not seeing the block I finally checked to see if that was even possible. According to http://drupal.stackexchange.com/questions/24333/can-i-use-hook-block-inf..., it's not.
Unfortunately blocks can't be generated by themes, so this has to go in a module. I suggest we put it in cm_starter_blocks along with any other blocks we end up needing and enable that starter module by default.
Does that make sense?
Comment #7
kreynen CreditAttribution: kreynen commentedThe logo and credit blocks we are using are the .profile http://cgit.drupalcode.org/cm_starterkit_easy/tree/cm_starterkit_easy.pr...
We could also put this block in that file.
Comment #8
libkuman CreditAttribution: libkuman commentedif there are no shortcoming to the .profile approach, i think its cleaner as it doesn't mean creating a whole new module for just one block
Comment #9
kreynen CreditAttribution: kreynen commented