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.
i see this error when i run the update.
Strict warning: Declaration of views_handler_filter_user_relationships_type::value_submit() should be compatible with that of views_handler_filter_in_operator::value_submit() in _registry_check_code() (line 3046 of ../includes/bootstrap.inc).
Comment | File | Size | Author |
---|---|---|---|
#11 | ur-strict_warning-1551792-11.patch | 685 bytes | Shawn DeArmond |
#4 | views_handler_filter_user_relationships_type.inc-Strict_warning-1551792-.patch | 516 bytes | azovsky |
Comments
Comment #1
fraweg CreditAttribution: fraweg commentedHello,
I have this issue:
Strict warning: Declaration of views_handler_filter_user_relationships_type::value_submit() should be compatible with that of views_handler_filter_in_operator::value_submit() in _registry_check_code() (line 3047 of C:\xampp\htdocs\testsite\includes\bootstrap.inc).
Dis you solve the problem?
Best regards
Frank
Comment #2
funature CreditAttribution: funature commentedi'm still waiting for somebody to help me.
Comment #3
fraweg CreditAttribution: fraweg commentedHello euroba,
for me the Problem was in the views filter. There was an filter where I check the relationship name. Here was the problem. I change the filter from "User relationships: Relationship type" to "User relationship types: RTID" and use the RTID instead of the name. With this workaround it works for me.
Best regards
Frank
Comment #4
azovsky CreditAttribution: azovsky commentedHere is the solution.
Comment #5
fraweg CreditAttribution: fraweg commentedThanks! #4 works for me.
Best regards
Frank
Comment #6
supadroopa CreditAttribution: supadroopa commentedI'm having the same issue with the latest dev version... any solutions?
Comment #7
tobiberlinSame here with 7.x-1.0-alpha5
#3 solved the issue
Comment #8
nedjoThe patch correctly resolves the strict warning by setting the signature to match that in the class being extended.
Comment #10
glynster CreditAttribution: glynster commentedFailed as well even manually trying. Did you find a resolve?
Comment #11
Shawn DeArmond CreditAttribution: Shawn DeArmond commentedHere's an updated patch that works for me.
Comment #12
glynster CreditAttribution: glynster commentedPerfect patch worked seamlessly and no more errors :)
Comment #13
mrf CreditAttribution: mrf commentedClosed #1567000: Strict warning as a duplicate of this issue.
Comment #14
mrf CreditAttribution: mrf commentedPatch looks good to me and I see a lot of confirmations about it working manually as well as passing tests.
Comment #15
ergophobe CreditAttribution: ergophobe commented#11 seems to have fixed it for me too.
Comment #16
deanflory CreditAttribution: deanflory commentedPatch #11 worked for me when applied to 2013-Oct-19 dev. It removed (I think):
Comment #17
cha0s CreditAttribution: cha0s commentedYes, it's the correct patch.
Comment #18
AnybodyIssue is still open and already 2 years old. It shows ugly notices.
Newer PHP versions don't like the current state :P
Is there an active maintainer in this module who could take this into .dev? That would be cool :)
Comment #19
heylookalive CreditAttribution: heylookalive commented+1 for getting this committed please!
Comment #21
heylookalive CreditAttribution: heylookalive commentedThanks @azovsky and @Shawn DeArmond! Committed to dev branch.
Comment #23
deanflory CreditAttribution: deanflory commentedNow if only this issue can get some love:
#2167883: Strict warning: Declaration of userpoints_ranking_handler_filter_last_period::init() should be compatible with views_handler_filter::init(&$view, &$options) in _registry_check_code() (line 3138 of /.../includes/bootstrap.inc