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'm receiving this error:
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 /.../v02/includes/bootstrap.inc
That's all the info I have. I don't specifically recall, but this could have come up when updating to Drupal 7.24, not sure, or it was when I updated to the 2013-Oct dev release.
Comment | File | Size | Author |
---|---|---|---|
#12 | userpoints-strict_warning-2167883-12-D7.patch | 571 bytes | Sagar Ramgade |
Comments
Comment #1
deanflory CreditAttribution: deanflory commentedComment #2
deanflory CreditAttribution: deanflory commentedThis could have something to do with an update to PHP 5.4 which is supposedly more strict about things.
Comment #3
pimok3000 CreditAttribution: pimok3000 commentedsubscribing with PHP 5.5 and the latest dev
Comment #4
JohnLi CreditAttribution: JohnLi commentedI'm receiving the similar error below. Any suggestion/advice please? Thank you.
Strict warning: Declaration of CourseObjectMoodleQuestionnaire::getReport() should be compatible with CourseObject::getReport($key) in _registry_check_code() (line 3146 of C:\xampp\htdocs\junhai\includes\bootstrap.inc).
Comment #5
deanflory CreditAttribution: deanflory commentedJohnLi, you need to create your separate issue in the Course / Moodle Questionnaire module's issue queue. This issue is for userpoints.
Comment #6
deanflory CreditAttribution: deanflory commentedSo, anyone have any ideas on this? This issue has been in the queue for some time now.
Comment #7
deanflory CreditAttribution: deanflory commentedMarking as "Needs work" to garner more attention to the issue.
Comment #8
deanflory CreditAttribution: deanflory commentedI'm still getting this after an update.php run.
Comment #9
deanflory CreditAttribution: deanflory as a volunteer commentedKeeping this issue alive.
Comment #10
deanflory CreditAttribution: deanflory as a volunteer commentedNot sure why this is being overlooked...a rather annoying error.
Comment #11
deanflory CreditAttribution: deanflory as a volunteer commentedComment #12
Sagar Ramgade CreditAttribution: Sagar Ramgade as a volunteer commentedPlease review this patch. It might solve your problem.
Comment #14
deanflory CreditAttribution: deanflory as a volunteer commentedSagar, any chance you can correct the failed patch so we have a chance to review?
Comment #15
Sagar Ramgade CreditAttribution: Sagar Ramgade as a volunteer commentedHi Dean, The above patch is failing due to some other functions like Userpoints update 7200. My patch is safe to apply and it wont add any additional trouble to the module. You may first try on your local environment to verify this.
Comment #16
deanflory CreditAttribution: deanflory as a volunteer commentedThanks Sagar! I ended up using your patch over the "userpoints_views-fix-strict-warnings-2193507.patch" patch as it would no longer apply fully and they both seemed to have some similar parts. I'm going to leave the issue open as I don't know whether this patch actually fixes the issue or just hides the error notices. I'll leave that for more codeily-inclined folk to determine.