• Resolved fruitbat

    (@fruitbat)


    Looking for help unravelling a fatal type=1 error, spotted in Woo today. The site was down earlier this morning, unsure how long for. Asked Namecheap, they could not tell me or offer a reason why. Once back up it Woo had meanwhile done a strange new thing – and duplicated the store notice, set to ‘above’. Duplication option not available in the store notice customizer. This has since been switched to ‘below’ – which interestingly does not duplicate. Theme = Kadence.

    ERROR EXTRACT:
    Uncaught Error: Call to undefined function php_uname() in /var/www/wptbox/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version2/class-wc-rest-system-status-v2-controller.php:990

    This is a Namecheap hosted site on their EasyWP package. Namecheap support have informed me that they cannot disable php_uname() something that searching indicated could be a solution. They suggested asking Woo support and provided this link. I’d like to find out the following:

    a) How fatal is this fatal error?
    b) Is php_uname disablement the solution / or only solution?
    c) To ignore it or deal with it?
    d) If deal with it, then how?

    Thank you

    • This topic was modified 11 months, 3 weeks ago by fruitbat. Reason: Extra info

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi @fruitbat,

    It sounds like you’re facing a couple of frustrating issues after your WooCommerce update. Let’s tackle that fatal error first, as it’s the more critical one.

    The “Uncaught Error: Call to undefined function php_uname()” means a function WooCommerce needs (php_uname()) isn’t available in your PHP environment. This error is critical; it can crash your site or stop features from working, so it definitely needs fixing for site stability. The function being disabled is the cause; the solution is a workaround.

    You’re not alone with this EasyWP issue. Another user on EasyWP faced the exact same php_uname() error after an update and found a workaround, as seen in this ww.wp.xz.cn thread: https://ww.wp.xz.cn/support/topic/critical-uncaught-error-after-9-9-3/#post-18505205

    To resolve it, add this code to your theme’s functions.php file:

    if ( ! function_exists( 'php_uname' ) ) {
      function php_uname( $mode = 'a' ) {
        return 'n/a';
      }
    }
    

    Always back up your functions.php before editing, or use a child theme.

    The duplicated store notice (when set “above” but not “below”) suggests a theme or plugin conflict, likely with Kadence. It’s common for themes to handle notice display differently. Once the fatal error is fixed, if the notice duplication continues, we recommend temporarily switching to a default WordPress theme (e.g., Twenty Twenty-Four) to see if the issue disappears. You might also consider contacting Kadence support, as they may have specific guidance for this interaction with WooCommerce.

    Let us know if the php_uname() workaround resolves your critical error!

    Plugin Support Chris Moreira – a11n

    (@chrism245)

    I’m closing this as resolved due to no further updates from you. If you need additional help in the future, feel free to reach out anytime.

    If you have a few minutes, we’d love if you could leave us a review: https://ww.wp.xz.cn/support/plugin/woocommerce/reviews/

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

The topic ‘Call to undefined function php_uname()’ is closed to new replies.