This was causing a problem where we had multiple contexts in the same region. On placing a custom views box or other item in one of these regions, two contexts would become active and the box appeared to be added to both contexts. It also caused an issue from the users perspective on making sure the correct context is active when they are editing the layout.

Comments

alphageekboy’s picture

Assigned: alphageekboy » Unassigned
Status: Active » Needs review
StatusFileSize
new444 bytes

Here is a patch that comments out the trigger for the default context. In our case it works around the issue of two context being active at once and adds the box to the correct context.

tirdadc’s picture

Assigned: Unassigned » tirdadc
Status: Needs review » Fixed

I changed it so that it only automatically triggers the edit if there's only one context. Committed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.