• Resolved ajna667

    (@ajna667)


    Hello there is conflict with thenewsletterplugin and problem come from your plugin, look error log, thenewsleter plugin support say It looks like it is triggered when we extract the excerpt from a product, probably they do not check the values before using them, and you should just add a check on the WP_DOING_CRON constant and/or on the valid value of the data you receive.

    error log:

    2024/05/16 11:39:28 [error] 63880#63880: *827833 FastCGI sent in stderr: “PHP message: PHP Warning: filemtime(): stat failed for /www/webiste/public/wp-content/uploads/2022/05/xxx-roche-scaled.jpg in /www/webiste/public/wp-content/plugins/newsletter/includes/helper.php on line 332PHP message: PHP Fatal error: Uncaught TypeError: method_exists(): Argument #1 ($object_or_class) must be of type object|string, null given in /www/webiste/public/wp-content/plugins/easy-table-of-contents/easy-table-of-contents.php:1338

    Stack trace:

    #0 /www/webiste/public/wp-content/plugins/easy-table-of-contents/easy-table-of-contents.php(1338): method_exists(NULL, ‘is_block_editor’)

    #1 /www/webiste/public/wp-content/plugins/easy-table-of-contents/easy-table-of-contents.php(1376): ezTOC::maybeApplyTheContentFilter()

    #2 /www/webiste/public/wp-includes/class-wp-hook.php(324): ezTOC::the_content(‘<p>GxC3xA9ode de cr…’)

    #3 /www/webiste/public/wp-includes/plugin.php(205): WP_Hook->apply_filters(‘<p>GxC3xA9ode de cr…’, Array)

    #4 /www/webiste/public/wp-includes/formatting.php(3992): apply_filters(‘the_content’, ‘GxC3xA9ode de crist…’)

    #5 /www/webiste/public/wp-includes/class-wp-hook.php(324): wp_trim_excerpt” while reading response header from upstream, client: 37.66.152.53, server: webiste.fr, request: “POST /wp-admin/admin-ajax.php HTTP/2.0”, upstream: “fastcgi://unix:/var/run/php8.1-fpm-webiste.sock:”, host: “webiste:x4977”, referrer: “webiste.fr/wp-admin/admin.php?page=newsletter_emails_composer&id=119

    • This topic was modified 6 months, 1 week ago by ajna667.
Viewing 1 replies (of 1 total)
  • Hi ajna667

    The issue has been fixed in very next v2.0.66.1 and many users have confirmed the same. Please update to it and clear log and check new log.

Viewing 1 replies (of 1 total)
  • The topic ‘fatal error’ is closed to new replies.