#28843 closed defect (bug) (fixed)
Fatal error: Call to protected method ... on PHP 5.2.5
| Reported by: | Ipstenu | Owned by: | wonderboymusic |
|---|---|---|---|
| Priority: | high | Milestone: | 4.0 |
| Component: | General | Version: | 4.0 |
| Severity: | blocker | Keywords: | |
| Cc: | Focuses: |
Description
Reported here: https://wordpress.org/support/topic/fatal-error-1264?replies=12&view=all
Errors:
Fatal error: Call to protected method WP_List_Table::get_pagenum() from context '' in C:\wamp\www\wordpress\wp-admin\plugins.php on line 16
and
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'WP_Comments_List_Table::_js_vars' was given in C:\wamp\www\wordpress\wp-includes\plugin.php on line 488
there are no errors on PHP 5.4
Attachments (1)
Change History (12)
#2
@
12 years ago
That's what I thought, but when I asked, she did a totally fresh install:
"On a new install on WAMP server 2.0 with PHP 5.2.5 there is the error :
Warning: Wrong parameter count for array_unique() in C:\wamp\www\wordpress4\wp-includes\taxonomy.php on line 2348"
I don't have an (easy) way to test PHP 5.2.5 but the user swears it didn't happen on 5.4 so ... I;m thinking derpy PHP?
#4
@
12 years ago
- Keywords reporter-feedback removed
- Priority normal → high
- Severity normal → blocker
I can reproduce all the issues mentioned here on a clean install on PHP 5.2.4 (minimal required version).
Introduced in [28493] and [28583].
28843.patch fixes the access modifier issues for me. Doesn't touch the array_unique() issue.
#7
@
12 years ago
Per user report, the user_func_array issue is still happening
https://wordpress.org/support/topic/warning-call_user_func_array-22?replies=5
Sorry for the bad report, I'm on my phone.
#8
@
12 years ago
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'WP_Comments_List_Table::_js_vars' was given in C:\wamp\www\wordpress4\wp-includes\plugin.php on line 488
On dashboard with PHP 5.2.5 on a new install and on an update
If I disable the dashboard_activity widget with the function unset, there are no errors:
unset ($ wp_meta_boxes dashboard normal core dashboard_activity);
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Any weird plugins or themes installed? My hunch is that someone is calling this method statically, which I have little sympathy for. Worst Case Scenario: I'll remove the access modifier, but this sounds a like a busted install or whack code.