• Please look into this error stack trace and fix the issue. The issue appears to be related to the WC Blacklist Manager plugin during the checkout/PayPal payment process.[error] 39838#39838: *4444523 FastCGI sent in stderr: “PHP message: is_internal_meta_key was called incorrectly. Generic add/update/get meta methods should not be used for internal meta data, including “_shipping_phone”. Use getters and setters. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->create_order, do_action(‘woocommerce_checkout_update_order_meta’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Blacklist_Manager_Checkout_Verification_Coordinator->persist_order_evidence, WC_Blacklist_Manager_Checkout_Verification_Coordinator->context_from_order, WC_Blacklist_Manager_Checkout_Verification_Coordinator->order_value, WC_Data->get_meta, WC_Data->is_internal_meta_key, wc_doing_it_wrong. This message was added in version 3.2.0″ while reading response header from upstream, client: 98.97.36.143, server: familylocket.com, request: “POST /?wc-ajax=checkout HTTP/2.0”, upstream: “fastcgi://unix:/var/run/php8.3-fpm-familylocket.sock:”, host: “familylocket.com:29462“, referrer: “https://familylocket.com/checkout/

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

Viewing 1 replies (of 1 total)
  • Plugin Support Jacob

    (@jacobb26)

    Hi,

    Thanks for providing the detailed stack trace. We’ve reviewed it, and it gives us a useful indication of where the issue is occurring during checkout.

    Since you’re using the Premium version of Blacklist Manager, please open a support topic through our official Premium Support portal at:

    https://workspace.yoohw.com/

    WordPress.org requires support for commercial versions of plugins to be handled through the plugin developer’s official support channel.

    Once you open the topic there, we can investigate this against the Premium version you’re running and, if necessary, provide you with a hotfix build directly so you can test the fix as quickly as possible.

    Please include a link to this WordPress.org topic when submitting the request so we can continue from the information you’ve already provided.

    Thanks!

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.