Support » Fixing WordPress » Fatal error: Uncaught Error: Call to undefined method stdClass::render() in

  • Eric

    (@erajgayurov)


    SOS!!! I need your help! After migrating from one hosting to another I got this issue –

    Warning: Creating default object from empty value in /home/h007366887/schiever.tj/docs/wp-includes/class-wp-block.php on line 236
    
    Fatal error: Uncaught Error: Call to undefined method stdClass::render() in /home/h007366887/schiever.tj/docs/wp-includes/class-wp-block.php:241 Stack trace: #0 /home/h007366887/schiever.tj/docs/wp-includes/blocks.php(901): WP_Block->render() #1 /home/h007366887/schiever.tj/docs/wp-includes/blocks.php(939): render_block(Array) #2 /home/h007366887/schiever.tj/docs/wp-includes/class-wp-hook.php(309): do_blocks('<!-- wp:paragra...') #3 /home/h007366887/schiever.tj/docs/wp-includes/plugin.php(191): WP_Hook->apply_filters('<!-- wp:paragra...', Array) #4 /home/h007366887/schiever.tj/docs/wp-includes/widgets/class-wp-widget-block.php(78): apply_filters('widget_block_co...', '<!-- wp:paragra...', Array, Object(WP_Widget_Block)) #5 /home/h007366887/schiever.tj/docs/wp-includes/class-wp-widget.php(393): WP_Widget_Block->widget(Array, Array) #6 /home/h007366887/schiever.tj/docs/wp-includes/widgets.php(835): WP_Widget->display_callback(Array, Array) #7 /home/h007366887/schiever.tj/docs/wp-content/themes/oceanwp/partials/footer/widget in /home/h007366887/schiever.tj/docs/wp-includes/class-wp-block.php on line 241

    How to solve it???

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Moderator bcworkz

    (@bcworkz)

    The empty value is assigned to $inner_block just before the referenced code line, so I think there’s an issue with the HTML structure of one of your widgets, causing $inner_block to have an empty value.

    Try moving select widgets to inactive to try and isolate which widget is causing the issue. Once found, you may need to redefine that widget from scratch to eliminate the error. Also ensure the code responsible for that widget is fully up to date. I’m not 100% confident this is the problem, but it’s my best guess.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.