Fatal Error with Polylang Translation

  • Resolved dmwc

    (@dmwc)


    3 years, 5 months ago

    Hello,

    we have a problem with translations. I did a conflict test and the error goes away when deactivating Yoast SEO. We use Polylang. When we create a new translation we got an error message:

    Fatal error: Uncaught Error: Call to a member function is_taxonomy() on string in /homepages/24/d677436263/htdocs/webshop/wp-content/plugins/woocommerce/includes/admin/meta-boxes/views/html-product-data-attributes.php:40 Stack trace: #0 /homepages/24/d677436263/htdocs/webshop/wp-content/plugins/woocommerce/includes/admin/meta-boxes/class-wc-meta-box-product-data.php(46): include() #1 /homepages/24/d677436263/htdocs/webshop/wp-content/plugins/woocommerce/includes/admin/meta-boxes/views/html-product-data-panel.php(51): WC_Meta_Box_Product_Data::output_tabs() #2 /homepages/24/d677436263/htdocs/webshop/wp-content/plugins/woocommerce/includes/admin/meta-boxes/class-wc-meta-box-product-data.php(33): include(‘/homepages/24/d…’) #3 /homepages/24/d677436263/htdocs/webshop/wp-admin/includes/template.php(1389): WC_Meta_Box_Product_Data::output(Object(WP_Post), Array) #4 /homepages/24/d677436263/htdocs/webshop/wp-admin/edit-form-advanced.php(688): do_meta_boxes(Object(WP_Screen), ‘normal’, Object(WP_Post)) #5 /homepages/24/d6774362 in /homepages/24/d677436263/htdocs/webshop/wp-content/plugins/woocommerce/includes/admin/meta-boxes/views/html-product-data-attributes.php on line 40

    The title area looks like this: https://cln.sh/MeDhSx

    Has anyone an idea what causes this?

    Thanks!
    Dirk

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

Viewing 15 replies - 1 through 15 (of 16 total)
1 2
  • Plugin Support Maybellyne

    (@maybellyne)

    3 years, 5 months ago

    Hello,

    Thanks for reaching out about this.

    We see that you have WordPress 5.6.1 and WooCommerce 5.0.0. Can you please confirm what version of Polylang you have and if you are running Yoast SEO 15.8?

    Thread Starter dmwc

    (@dmwc)

    3 years, 5 months ago

    Hi Maybellyne,

    sorry for the late answer! There was an issue with my notifications 🙂

    Polylang Pro Version 2.9.2
    Polylang for WooCommerce Version 1.5.2
    Yoast 15.8 (deactivated atm)

    Thanks!
    Dirk

    Pcosta88

    (@pcosta88)

    3 years, 5 months ago

    Hi,

    We tested this using WordPress v5.6.1, WooCommerce v5.0, Yoast SEO v15.8, Polylang (free v2.9.2) and Storefront v3.5. We were not able to reproduce the issue:

    1. We created a translation (see image: https://ibb.co/rp0n5xV)

    2. We then added data to the translation (see image: https://ibb.co/HCLSNfj)

    3. We then published it. It published as expected, no errors. See image: https://ibb.co/j6dRMyH.

    Unfortunately, we do not have access to the pro version of the add on: Polylang for WooCommerce Version.

    We understand you did a conflict test but we are not sure if it was a complete test.

    We ask that you please perform a complete conflict check. Install the Healthcheck plugin and enable troubleshooting. Then switch to a standard theme like 2020. Does the issue resolve? NOTE: This will not affect how users see your site.

    If there is a conflict with a plugin or a theme, you can create a new GitHub issue for our developers. Please report the issue to a third party developer as well.

    Thread Starter dmwc

    (@dmwc)

    3 years, 5 months ago

    Ok, thanks, I will check again and report!

    Plugin Support devnihil

    (@devnihil)

    3 years, 5 months ago

    @dmwc You’re welcome, and please let us know the outcome once you’ve had a chance to perform those troubleshooting steps.

    Thread Starter dmwc

    (@dmwc)

    3 years, 5 months ago

    Hi there!

    I did a new test and found something new: The error only occurs when Polylang for WooCommerce and Yoast is active. It doesn’t occur when only Polylang Pro is active.

    Can you try to reproduce the error again with:

    WordPress v5.6.1
    WooCommerce v5.0
    Yoast SEO v15.8
    Polylang (free v2.9.2)
    Polylang for WooCommerce v1.5.2
    and Storefront v3.5

    This is not exact the same setup because we use Polylang Pro, but maybe you can reproduce the error this way.

    Thanks
    Dirk

    henrikdamdk

    (@henrikdamdk)

    3 years, 5 months ago

    I have the exact same error. Downgrading to Yoast 15.7 solves the error.

    Hope a solution can be found. Thanks.

    • This reply was modified 3 years, 5 months ago by henrikdamdk.
    • This reply was modified 3 years, 5 months ago by henrikdamdk.
    Plugin Support Suwash

    (@suascat_wp)

    3 years, 5 months ago

    @dmwc Unfortunately, we have no access to the pro addon Polylang for WooCommerce therefore unable to replicate errors on our end. Looks like errors only appear when Polylang addon with WooCommerce and Yoast SEO is activated. Further taking a closer look into those errors you had posted, we don’t see errors generated from Yoast SEO core files but rather from the WooCommerce plugin folder. Thus, it would likely be a compatibility issue of addon with WooCommerce and Yoast SEO working together. We suggest reaching out once to the Polylang pro addon author once for further investigation.

    Thread Starter dmwc

    (@dmwc)

    3 years, 5 months ago

    Ok, thanks so far, I will talk to them!

    Thread Starter dmwc

    (@dmwc)

    3 years, 5 months ago

    And thanks Hendrik!

    Plugin Support devnihil

    (@devnihil)

    3 years, 5 months ago

    @dmwc Can you please confirm whether downgrading to version 15.7 resolved the issue for you?

    Thread Starter dmwc

    (@dmwc)

    3 years, 5 months ago

    Yes this solved the issue. Polylang is investigating now. Keep you posted.

    Plugin Support devnihil

    (@devnihil)

    3 years, 5 months ago

    @dmwc Thanks for confirming that, and please let us know the results once you’ve heard back from Polylang.

    Emmanuel Hesry

    (@manooweb)

    3 years, 5 months ago

    Hi!

    I’m a developer of Polylang team and I investigated the last week about this issue.
    I then propose a fix in the Yoast SEO code because the issue appears since its 15.8 release.

    See https://github.com/Yoast/wordpress-seo/pull/16689

    Regards

    Thread Starter dmwc

    (@dmwc)

    3 years, 5 months ago

    Many thanks, Emmanuel!

Viewing 15 replies - 1 through 15 (of 16 total)
1 2
  • The topic ‘Fatal Error with Polylang Translation’ is closed to new replies.