Ticket #11168 (closed defect (bug): fixed)
Fatal error: Call to undefined method WP_Error::__destruct()
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.9 |
| Component: | Administration | Version: | 2.9 |
| Severity: | normal | Keywords: | has-patch |
| Cc: |
Description
This is in several of the widgets in the dashboard. the sqldump contains a 2.8 site's data, which then gets upgraded to 2.9.
the RSS feeds, which worked fine in 2.8, no longer do. I suppose that's no big deal, since they get refreshed eventually. but mentioning it in the event it's related to the other problems:
- Fatal error: Call to undefined method WP_Error::destruct() in /Users/denis/Sites/wp/wp-admin/includes/dashboard.php on line 627
- Fatal error: Call to undefined method WP_Error::destruct() in /Users/denis/Sites/wp/wp-includes/default-widgets.php on line 775
- Fatal error: Call to undefined method WP_Error::destruct() in /Users/denis/Sites/wp/wp-admin/includes/dashboard.php on line 745
Attachments
Change History
- Keywords has-patch added
Thank God PHP usually has garbage collection. :-)
comment:4
follow-up:
↓ 8
miqrogroove — 2 years ago
- Keywords needs-patch added; has-patch removed
- Status changed from closed to reopened
- Resolution fixed deleted
- Milestone changed from 2.9 to 2.9.1
Missed WP_Widget_RSS and possibly others. See http://wordpress.org/support/topic/343166
comment:5
miqrogroove — 2 years ago
This is related, but might need a separate ticket (?) http://wordpress.org/support/topic/342975
- Keywords has-patch added; needs-patch removed
11168.2.diff fixes this error:
Fatal error: Call to undefined function: __destruct() in /home/content/.../wp-includes/default-widgets.php on line 735
The "could not be converted to UTF-8" error should be handled in a separate ticket.
comment:7
miqrogroove — 2 years ago
xref #11219
- Status changed from reopened to closed
- Resolution set to fixed
- Milestone changed from 2.9.1 to 2.9
Replying to miqrogroove:
Missed WP_Widget_RSS and possibly others. See http://wordpress.org/support/topic/343166
Please don't reopen tickets from previous milestones where a fix was made during that release.
It makes it much harder to keep track of the remaining issue - a new ticket should be created for an issue once the release the original ticket was closed against has shipped.
I have created a new ticket to track the remaining issue: #11518

