• Hello,
    I have the following error flooding the debug.log. I’ve did a grep to find what is causing it and only place was your plugin: stream/connectors/class-connector-wordpress-seo.php

    PHP Deprecated: Function WPSEO_Metabox::translate_meta_boxes is deprecated since version Yoast SEO 23.5 with no alternative available. in /home/413833.cloudwaysapps.com/hjszqnhuwy/public_html/wp-includes/functions.php on line 6085

    WPSEO_Metabox is a class from Yoast SEO. Its current version is 23.5. Steam is updated to its latest version 4.0.2.

    Thank you.
    Regards,
    al.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Julie

    (@juliejubilee)

    Also getting this error. It causes 500 errors when using the Breakdance page builder plugin, so we’ve had to downgrade Yoast back to 23.4.

    I’m seeing the same thing. I’m using Yoast + Yoast Premium.. I’m up-to-date:

    +------------------------------+-------------+-------------+---------+
    | name | old_version | new_version | status |
    +------------------------------+-------------+-------------+---------+
    | wordpress-seo | 23.5 | 23.6 | Updated |
    | wordpress-seo-premium | 23.5 | 23.6 | Updated |
    +------------------------------+-------------+-------------+---------+

    I can see it runs in file: stream/connectors/class-connector-wordpress-seo.php

    /**
     * Logs WordPress SEO meta activity
     *
     * @param int    $object_id   Object ID.
     * @param int    $meta_key    Meta key.
     * @param string $meta_value  Meta value.
     */
    private function meta( $object_id, $meta_key, $meta_value ) {
        $prefix = \WPSEO_Meta::$meta_prefix;
    
        \WPSEO_Metabox::translate_meta_boxes();

    I’m seeing it mostly in the backend/dashboard. A Google search of the notice shows that it’s apparently coming up on the front end of many sites.

    • This reply was modified 1 month, 2 weeks ago by ereckers.
    • This reply was modified 1 month, 2 weeks ago by ereckers.

    I’m experiencing this as well. Any timeline for a fix? Or a code change we can implement?

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.