• preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated 

    in file, line 162: wp-content/plugins/woocommerce/includes/libraries/class-wc-eval-math.php:162
    preg_match()

    Related to problems with shipping calculations when using PHP 8.4

    Does not break:

    8 * [qty]

    Breaks:

    ( 8 * [qty] )

    Also breaks:

    4 + ( 8 * [qty] )


    How to reproduce:

    Add a product in your cart that uses a shipping calculation (and it has parentheses in formula)

    Log off.

    Log on.

    Please see unresolved issue here for reference:

    https://github.com/woocommerce/woocommerce/issues/52689

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    Thank you for bringing this to our attention. I have checked this and can confirm that our developers are actively working on this issue here:
    https://github.com/woocommerce/woocommerce/pull/62740

    At the moment, there is no estimated timeframe (ETA) for when the fix will be released. However, please be assured that the team is working to resolve it as soon as possible.

    Thank you for your cooperation and understanding.

    Hi, thanks for the update.

    It’s good to know that the issue has been identified and the developers are already working on a fix. I understand that resolving such problems properly can take time, especially when stability and testing are involved.

    I’ll keep checking for updates and really appreciate the transparency regarding the situation. Hopefully, a stable fix will be released soon without any further issues.

    In the meantime, I might explore some temporary alternatives like free sms bomber. Thanks again for the support and clarification.

    Plugin Support LovingBro (woo-hc)

    (@lovingbro)

    Hi @kashifaziz12,

    Thanks for jumping in and for your thoughtful follow-up here, it is great to see you have reviewed the earlier update shared by my colleague and that it provided clarity on the current status of the issue.

    You are absolutely right, cases like this can take a bit of time as the fix needs to be properly tested to ensure stability across different setups. At the moment, the issue has already been identified and is actively being worked on by our development team, so the best next step is to keep an eye on upcoming WooCommerce releases where the fix will be included.

    In the meantime, if you notice any additional patterns or have more details to share from your setup, feel free to let us know as that can sometimes help with ongoing investigations.

    We appreciate your patience and understanding while this gets resolved.

    Hi @lovingbro,

    Thanks for the detailed update, really appreciate you taking the time to explain the situation so clearly. It’s good to know that the issue has already been identified and is being actively worked on by the development team.

    I completely understand that proper testing takes time to ensure everything runs smoothly across different environments, so I’m okay with waiting for the official fix in upcoming WooCommerce releases.

    If I come across any additional patterns and useful details from my setup, I’ll definitely share them here to help with the investigation.

    Thanks again for the support and transparency 👍

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    Thank you for your kind words and understanding it’s truly appreciated!

    We’re glad the information was helpful, and thank you for your willingness to share any additional findings from your setup, as that can be valuable for the ongoing investigation.

    Any updates regarding the fix will be shared on the related GitHub issue, so I recommend keeping an eye on that link for the latest progress.

    Please feel free to reach out if you notice anything new or have further questions in the meantime. Thanks again for your patience!

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.