Contrib.social

Block are visible only in the content region when front page per domain is set

Open on Drupal.org →
Created on 23 February 2023, almost 2 years ago
Updated 14 June 2023, over 1 year ago

Drupal Version 9.5.3

Domain module version 8.x-1.0-beta6

Domain theme switch 8.x-1.5

Expected Behavior

Show blocks from any region in a theme.

Actual Behavior

Blocks from other regions other that "content" are not shown.

Steps to reproduce

1. Setting a front page per domain ex. /node/195
in admin/config/system/site-information

2. Setting blocks visibility per node again /node/195

3. Accessing the domain.com shows only the blocks in the content region.

If we haven't set a front page and we redirect via .htaccess or apache redirect to domain.com/lang/node/185 then blocks in all regions are visible.

Deleting the domain record and creating it again does not solve the issue. Front page remains the same and blocks are still not visible when placed outside the main content.

💬 Support request
Status

Postponed: needs info

Component

- Domain Content

Created by

🇧🇬Bulgaria joro78

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

Comments & Activities

  • Issue created by @joro78
  • Status changed to Postponed: needs info almost 2 years ago
  • Comment almost 2 years ago →
    🇺🇸United States agentrickard Georgia (US)

    Due to the use of .htaccess, no mention of Domain Config, and the use of an unsupported module, there really isn't enough information here to tell how to reproduce this issue.

    Make sure that "required cache contexts" are set according to the documentation:

        required_cache_contexts: ['languages:language_interface', 'theme', 'user.permissions', 'url.site']

    Also note that the DomainBlockVisibilityTest.php uses sidebar_first as the region.

    As a result, I suspect this may be coming from Domain Theme Switch. You may get a better answer in that queue.

    Ideally, Domain Theme Switch would extend the above test to confirm it works as expected.

  • Comment over 1 year ago →
    🇺🇸United States bsnodgrass

    Reviewing for 📌 Documentation for 2.0.x Active ...

    Has this issue been resolved? Can you duplicate after updating to the 2.0.0-beta1 release?

    Per the project description, "The 2.0.0-beta1 release is a code-only update from 8.x-1.0-beta8. Upgrading should only require a cache clear. The 8.x-1.x branch is now deprecated and will receive no new commits or releases."

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024