Request path exclusion conditions are not respected

Created on 7 March 2024, over 1 year ago
Updated 8 March 2024, over 1 year ago

Problem/Motivation

I wanted to give some more space to users when adding or editing nodes or their profile page. So I used Context to remove the second sidebar of my theme. This resulted to remove the sidebar on all pages although I think my conditions are correct (see reproduce below)

Steps to reproduce

These are my settings:
Conditions: Request path exclusion
/node/add/*
/node/*/edit/
/user/*/edit
Reaction: Disable a region containing some blocks in selected theme (in my case bootstrap second sidebar)
Result: The region disappears whatever the page is (tested on viewing a user's profile and display front page and a node)
Disabling the context brings back the previously removed region.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

5.0

Component

Code

Created by

🇫🇷France erwangel

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

Comments & Activities

  • Issue created by @erwangel
  • First commit to issue fork.
  • 🇸🇮Slovenia deaom

    I tested this with the default Olivero theme and noticed the Request path exclusion always negates the condition. Meaning if I add the Request path exclusion /node/add/* (the Olivero theme needs to be used in FE - the checkbox not ticked under Apperance to use the admin theme when editin or creating content) and then under Reactions add Region -> Disable Regions in Olivero -> Header, the region is actually removed from all other paths, except the /node/add/* path.
    The /node/*/edit works the same way and user/*/edit is using the admin theme so no effect there (different regions and display).
    I'm not sure if bootstrap is doing something differently, as based on the issue, it just disappears from everywhere, which should not happen. If the issue is still there, could you try with a block as a reaction, just to see if the issue lies with the bootstrap theme?

Production build 0.71.5 2024