• Resolved dyin

    (@dyin)


    Hello WooCommerce Team,
    With PHP 8.4, I’m seeing several deprecation notices originating from the sabberworm/php-css-parser library bundled with WooCommerce:

    1. PHP Deprecated: Sabberworm\CSS\Parser::__construct(): Implicitly marking parameter $oParserSettings as nullable… in /path/to/wp-content/plugins/woocommerce/vendor/sabberworm/php-css-parser/src/Parser.php on line 24
    2. PHP Deprecated: Sabberworm\CSS\CSSList\Document::render(): Implicitly marking parameter $oOutputFormat as nullable… in /path/to/wp-content/plugins/woocommerce/vendor/sabberworm/php-css-parser/src/CSSList/Document.php on line 158
    3. PHP Deprecated: Sabberworm\CSS\RuleSet\RuleSet::addRule(): Implicitly marking parameter $oSibling as nullable… in /path/to/wp-content/plugins/woocommerce/vendor/sabberworm/php-css-parser/src/RuleSet/RuleSet.php on line 105

    These parameters need to be explicitly marked as nullable for PHP 8.4 compatibility. This might require updating the bundled version of the sabberworm/php-css-parser library or applying patches.

    Could you look into this for a future WooCommerce update?
    Thanks!”

Viewing 1 replies (of 1 total)
  • Hi @dyin,

    Thanks for reaching out and for sharing these deprecation notices!

    What you’re seeing are warnings related to PHP 8.4 compatibility, specifically about parameters that need to be explicitly marked as nullable in the sabberworm/php-css-parser library bundled with WooCommerce.

    The good news is these are not critical errors, just deprecation notices. Our developers are aware of this and will address them in future updates as part of ongoing compatibility improvements.

    Thanks again for flagging this we really appreciate it!

Viewing 1 replies (of 1 total)

The topic ‘PHP 8.4 depreciation notices’ is closed to new replies.