- Issue created by @rgnyldz
- Status changed to Postponed: needs info
over 1 year ago 6:28pm 5 June 2023 - πΉπ·Turkey rgnyldz
Sorry for my late response, I'm not sure actually, because its kind of random. Sometimes when some comfings are imported. sometimes when cache is cleared ans sometimes just when working on the admin area.
I'm also not sure if this is a module issue or incompatibility issue with another module/config.
I ended up removing the module and use regular regions for my project.
But what happens is;
All blocks inside any block group got disabled and moved to my "Header" region. So I have to manually enable and place the plocks to the block groups again.
- πΊπΈUnited States maxstarkenburg Washington, DC
I'm seeing a variation of this phenomenon. I haven't seen it happen upon cache clear or cron run, but what I am seeing is this:
- Block placement looks correct on prod
- I make a DB dump of the prod database (after which block placement still looks correct on prod)
- I import it into my local so I can run
drush cex
to capture other unrelated config differences that have been made directly on prod - I run a diff against config as committed, and see that the blocks in my
blockgroup
have supposedly been ...- disabled
- moved to another region they definitely shouldn't be in (I'm guessing they're getting moved to the top-most theme region, given the other report moving things to a "Header" region, and in my case I've only seen them moved to my theme's first region, called "Alert").