Create compatibility with the Context module

Created on 3 November 2023, over 1 year ago
Updated 14 February 2024, about 1 year ago

Problem/Motivation

I believe that, like me, many developers also use the Context module to control the display of their blocks, because it simplifies the block display rules and because it has more rules than the standard display.

I did some tests and Cheeseburger Trigger cannot detect the Cheeseburger Menu for the functionality proposed by the module to work.

Steps to reproduce

Enable the Context and Context UI module, create a new context, and position the blocks in the desired area. When trying to insert the Cheeseburger Trigger block it does not work as it does not detect the Cheeseburger Menu block

Proposed resolution

Include some form of detection using the Context module, or simplify the use of the Cheeseburger Menu module by requiring only one block. I don't understand the need to have the menu block and the trigger, since the display always appears from the side.

Remaining tasks

Review of functionality or adaptation to the Context module.

User interface changes

Reduction in the number of module blocks.

API changes

N/D

Data model changes

N/D

Feature request
Status

Active

Version

5.0

Component

Code

Created by

🇧🇷Brazil tiagohfweb Patos de Minas - MG

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @tiagohfweb
  • 🇷🇸Serbia holo96

    We've decided to separate cheeseburger menu into two blocks based on mistakes we made in <4.x. So there are multiple reasons for this decision.

    Maybe I can add contextual link to trigger

  • 🇷🇸Serbia holo96

    I will leave this issue open because I think it is good Idea to add contextual links to cheeseburger and also maybe we can add contextual links to rendered menus/taxonomies.

    But for me it seems like contexutal links are working as expected.

Production build 0.71.5 2024