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: compare
appears 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
We can no longer add contrib projects in the Tugboat sandboxes that we use for core PR's? Can this be fixed or is there a reason for this? We can add contrib projects to demo...
Apr 25th Weekly Meetings
The Mail System and MimeMail modules are now installed. I'll let you know if they solve the problem. Edit: Using Mail System with MimeMail I was able to send plain text emails. There is...
HTML Email treated as plain text
If you haven't already I recommend installing Mail System and MimeMail. The latter will help format emails as HTML and first helps with configuring which module will handle the formatting...
HTML Email treated as plain text