Description of the bug
When creating a User compare context (to compare my user account to the user account for the profile page I am viewing, for example) I noticed that even though contexts were marked as required, the visibility condition is still visible in the drop-down menu.
This new visibility condition has two required user contexts, so should not be available on any path without a user context (the second user context is global $user and is always available). Yet it appears in the select list for the home page layout.

Steps To Reproduce
To reproduce the behavior: 1. Apply the patch from https://github.com/backdrop/backdrop-issues/issues/4029 2. Manage blocks on the home page layout 3. Attempt to add a visibility condition
Actual behavior
- Confirm that
User: compareappears in the list
Expected behavior
Since User: compare appears in the list has required contexts that are not present, User: compare should NOT appear in the list of available visibility conditions
Recent comments
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists