Fatal error: Class 'WP_Widget' not found

[Ragid Hallak]

hello , iam the owner of this website : husamorfali.com

iam getting a fatal error : Class 'WP_Widget' not found in public_html/wp-includes/widgets/class-wp-widget-pages.php on line 17

first i opened wp-admin menu and i found 4.4 wp update
so i pressed on " update automaticly " after 5 min i opened the website
and i found first fatal error in Plugin " the social links " u deleted it
then a new error shown " wp-statistics " i didnt delete it beacuse its improtant so i red in forums + google and changed the name of the file so

a new error came :

Fatal error: Class 'WP_Widget' not found in /home/husonline/public_html/wp-content/plugins/wp-user-avatar/includes/class-wp-user-avatar-widget.php on line 9

so i renamed the Plugins file in file manager " Cpanel " to Plugins.disabled
and created a new folder named Plugins " empty folder "
and then a new error came ...

/public_html/wp-includes/widgets/class-wp-widget-pages.php on line 17

so what i can do ?
and is there a way to backup the articles
and put a " Website is under maintenance " ??

Thanks

[Clorith]

Hi, and welcome to Trac.

Trac is meant for tracking features and bugs in the core WordPress component, this sounds like a single incident, we ask that support requests such as this be directed to our forums at ​https://wordpress.org/support

To get things started though, this sounds like a potentially failed update, please try the Manual Update approach from ​https://codex.wordpress.org/Updating_WordPress, and if the problem persists create a post on the forums as mentioned above.

[Ragid Hallak]

do i need to resend the ticket ?
or its already resended to the correct support ?

and if i tryed the manual update , if anything gone wrong my articles will be deleted or what ?

Thanks for the answer

[Clorith]

You will not lose any content from performing a manual upgrade, but we still recommend making backups when possible.

You will have to create a new topic on the support forums, there is no link between them and this issue tracked.

[dd32]

#35727 was marked as a duplicate.