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 patch prevents the submit and form_id array elements being saved to the data column on user registration.
Comment | File | Size | Author |
---|---|---|---|
#6 | unset_0.patch | 449 bytes | chx |
#3 | unset.patch | 427 bytes | chx |
user.module_23.diff | 852 bytes | drumm | |
Comments
Comment #1
moshe weitzman CreditAttribution: moshe weitzman commentedgosh, this bug again. we've seen it with system_settings and one other place. there are a few more system variables which might need to be unset() see http://drupal.org/node/41170. maybe we can do the unset() in a central place and then both of these issues will use that code?
Comment #2
Dries CreditAttribution: Dries commented+1 for fixing this in a central place.
Comment #3
chx CreditAttribution: chx commentedComment #4
Dries CreditAttribution: Dries commentedCan we clean up some code in system.module too?
Comment #5
NaX CreditAttribution: NaX commentedI was looking in the PHP manuals at the unset function just before reading this issue and I would like to know if you want to unset these variables globally or locally.
If you in a function and you use unset() it only destroys the local version of the variable even if it is passed by reference.
To unset the global version of the variable you need to unset it using the $GLOBALS array. So my question is how do you want to unset these variables. Globally or locally, or is that unimportant.
Comment #6
chx CreditAttribution: chx commentedNaX is right. Dries, there is nothing to clean up in system. This fixes (partially) the issue moshe talks of.
Comment #7
Dries CreditAttribution: Dries commentedCommitted. Thanks.
Comment #8
(not verified) CreditAttribution: commented