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
You can edit images and load them back to the same folder with the same name and extension, this will not create a problem. Replace directly in the file system, without the use of CMS, for CMS...
Image manipulation on server?
I was under the impression you could not do that - don't know where I got that idea from... thought it had to do with the way Backdrop manages image files.
Image manipulation on server?
I think given the warning on the source site: At this time, if your new project can afford to require PHP 5.5+, which it should, please use PHP's native password_hash() /...
July 31, 2025