Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This problem is the same as in #2501751: Visibility rules aren't saved for unlimited multiple value fields.
When visibility rules for panes are edited, they are not saved in some cases. Please see the full description in the issue mentioned above.
Comment | File | Size | Author |
---|---|---|---|
#1 | panels-access_settings_saving-2504465-1.patch | 638 bytes | maximpodorov |
Comments
Comment #1
maximpodorov CreditAttribution: maximpodorov commentedThe patch fixes the problem in the same manner as in the CTools' issue.
Comment #2
maximpodorov CreditAttribution: maximpodorov commentedComment #3
osopolarThanks maximpodorov, this works for me.
Comment #4
crmn CreditAttribution: crmn commentedpatch #1 works for me
Comment #5
ian_v CreditAttribution: ian_v commentedThanks, patch #1 works for me.
Comment #6
DamienMcKennaThis seems to be a safe bet.
Comment #7
DamienMcKennaComment #8
dsnopekMoving to 3.8 so we can get 3.7 out quicker!
Comment #9
osopolarMaybe this time.
Comment #10
philsward CreditAttribution: philsward commentedThis yet again, fixed an issue with an empty "entityreference" field that failed to save the "NOT" declaration. I'm not 100% sure if this fixes issues with the "multivalue" fields, however, this patch in combination with #2501751: Visibility rules aren't saved for unlimited multiple value fields DOES fix the problem described in #2503509: Make Visibility Rules Validate Against Null Field Values . I will note that my entityreference field IS a multivalue field though...
In my case, I was trying to validate a NOT against an empty (null) entity reference field. In other words, if it's empty, do not show it.
After applying both patchs:
#2504465: Visibility rules aren't saved for unlimited multiple value fields & #2501751: Visibility rules aren't saved for unlimited multiple value fields
my issue (being able to save it as "NOT" against a null entity reference field) is resolved..
Moving to RTBC, if for anything to get the functionality included that will recognize and save against the empty / null values.
At the very least, we NEED the patch from #1 included in order to fix the issue described in #1188466: Add a simple selection rule for checking if a field is empty. So, this patch will allow you to save the visibility rules, however it won't perform the desired selection. You need the other patch (1188466 #42) in order for the visibility rule to work against an empty value.
If the 'multivalue' issue still isn't resolved, I suggest that we rename this issue to denote it as a fix for the empty/null problem and create a new issue that solely targets saving visibility rules on multivalue fields.
Comment #11
AnybodyI can confirm this is still needed and works. Confirming the 2 years old RTBC.
Comment #12
joseph.olstadretriggered tests
Comment #13
izmeez CreditAttribution: izmeez commented1+ RTBC hoping for commit.
Comment #14
joelpittetThanks @maximpodorov, I've committed this for the next release.