• Resolved Noruzzaman

    (@noruzzaman)


    woocommerce-gateway-stripe:

    PHP Fatal error: Uncaught TypeError: Unsupported operand types: string + int in /www/insuranceschooloftexas_156/public/wp-content/plugins/woocommerce-gateway-stripe/includes/payment-methods/class-wc-stripe-payment-request.php:368

    I am using the latest version of your plugin. I have faced these issues. our system running WP V 6.3, WooCommerce v 8.1, PHP v 8.0.0

    issues: https://prnt.sc/Pt08mvd5IuqF
    Please help me.

    Thanks
    Noruzzaman

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi @noruzzaman

    From what I understand, you’re running into a PHP Fatal error with the WooCommerce Stripe Payment Gateway, specifically in the ‘class-wc-stripe-payment-request.php’ file. You’ve mentioned that you’re on the latest version of our plugin, using WordPress 6.3, WooCommerce 8.1, and PHP 8.0.0.

    It appears the error is due to a type conflict between a string and an integer in the ‘class-wc-stripe-payment-request.php’ file. There could be several reasons for this, so let’s start with some basic troubleshooting:

    1. Check for updates: Make sure all your plugins, themes, and WordPress are updated. Even though you’re on the latest version of our plugin, there might be new updates for your other plugins, theme, or WordPress.
    2. Disable other plugins: Other plugins can sometimes conflict with the WooCommerce Stripe Payment Gateway. Try disabling all other plugins except WooCommerce and Stripe Payment Gateway to see if the error continues.
    3. Switch themes: Themes can also cause conflicts. Try changing to a default WordPress theme like Storefront to see if the issue persists. Here’s a handy guide on how to test for conflicts: ?? How to Test for Plugin and Theme Conflicts.
    4. Enable Debugging: If the problem persists, turn on debugging in WordPress. This can help identify the root cause. You can enable debugging by adding these lines to your wp-config.php file:
    define( 'WP_DEBUG', true );
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );
    @ini_set( 'display_errors', 0 );

    This will create a debug.log file in your wp-content directory, logging any PHP errors or notices. For a more detailed guide on enabling debugging in WordPress, you can visit this link: ?? Debugging in WordPress

    If the issue continues after trying these steps, please share more details, like the exact error messages you see when debug mode is on. This will help us identify and solve the problem more effectively.

    It would also be helpful if you could share your site’s System Status report. This will give us a clearer picture of your site’s setup and help us identify the problem. You can find it via WooCommerce > Status. Select Get system report and then Copy for support.

    Once you’ve gathered this information, please paste it inside a Code block in your reply, or use https://pastebin.com to paste it and share the link with us.

    Thanks for your patience and cooperation in this matter! We’re here to help you get this sorted.

    Hello Tamrat @bisratlearn ,

    I hope you’re doing well! I need to revisit this thread as I’ve encountered the same issue Noruzzaman reported. Below are the error details:

    2023/10/03 15:34:02 [error] 3247#3247: *159753 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught TypeError: Unsupported operand types: string + int in /www/**********_620/public/wp-content/plugins/woocommerce-gateway-stripe/includes/payment-methods/class-wc-stripe-payment-request.php:368

    This error notification was sent to me by my hosting provider, and I’m at a loss as to how to reproduce it. For your reference, I’m currently running the following versions of the respective software:

    • WordPress: 6.3.1
    • WooCommerce: 8.1.1
    • WooCommerce Subscriptions: 5.4.0
    • WooCommerce Stripe Gateway: 7.6.0
    • PHP: 8.0

    I believe I have conducted most of the relevant checks and updates. The remaining suggestions seem not directly related to this issue. Therefore, I would appreciate if you could kindly investigate this matter on your end and provide assistance. I’m looking forward to your guidance on resolving this fatal error effectively.

    Thank you in advance for your support and cooperation!

    Best regards,
    Nick

    Hi @nicktoot

    Thanks for letting us know!

    Could you let us know how it goes after performing a conflict test? This is likely a plugin conflict. You can find a more detailed explanation of how to do a conflict test here.

    Plugin Support Gabriel – a11n

    (@gabrielfuentes)

    It’s been a while since you responded, so I’m marking this as resolved – we’ll be here if/when you need us.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘PHP Fatal error’ is closed to new replies.