Error: React.cloneElement(…): The argument must be a React element, but you pa

  • Resolved Alessio Pellegrini

    (@pointnet)


    2 years, 3 months ago

    Hello,

    This morning I am encountering an issue with my WordPress site when attempting to customize some blocks through the Customize link in the top admin bar. Whenever I try to make changes to blocks , such as modifying titles or paragraphs, an error occurs. Yesterday everything was working as usual

    The error message I receive is as follows:

    Error: React.cloneElement(...): The argument must be a React element, but you passed null.
    at e.cloneElement (https://bottegatoscanaidaho.com/wp-admin/load-scripts.php?c=1&load%5Bchunk_0%5D=heartbeat,customize-base,customize-controls,customize-widgets,react&ver=6.4.3:18:7964)
    at https://site.com/wp-content/plugins/woocommerce/assets/client/blocks/wc-blocks-vendors.js?ver=0b6a0d8207806c01caa1:10:45262
    at wt (https://site.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:47637)
    at dr (https://site.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:54880)
    at js (https://site.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:122633)
    at wl (https://site.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:88659)
    at bl (https://site.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:88587)
    at yl (https://site.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:88450)
    at il (https://site.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:85274)
    at fl (https://site.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0:10:85661)

    Additionally, here is the console output when the error occurs:

    react-dom.min.js?ver=18.2.0:10 Error: React.cloneElement(...): The argument must be a React element, but you passed null.
    at e.cloneElement (load-scripts.php?c=1&load%5Bchunk_0%5D=heartbeat,customize-base,customize-controls,customize-widgets,react&ver=6.4.3:18:7964)
    at wc-blocks-vendors.js?ver=0b6a0d8207806c01caa1:10:45262
    at wt (react-dom.min.js?ver=18.2.0:10:47637)
    at dr (react-dom.min.js?ver=18.2.0:10:54880)
    at js (react-dom.min.js?ver=18.2.0:10:122633)
    at wl (react-dom.min.js?ver=18.2.0:10:88659)
    at bl (react-dom.min.js?ver=18.2.0:10:88587)
    at yl (react-dom.min.js?ver=18.2.0:10:88450)
    at il (react-dom.min.js?ver=18.2.0:10:85274)
    at fl (react-dom.min.js?ver=18.2.0:10:85661)

    I have taken the following steps to troubleshoot the issue:

    1. Disabled all plugins except WooCommerce, but the problem persists.
    2. Verified that WooCommerce is up to date ( and all the rest).
    3. Checked for any JavaScript errors in the browser console, which revealed the error message mentioned above.
    4. Cleared browser cache and disabled browser extensions, but the problem remains.
    5. Ensured that my theme is updated to the latest version and compatible with my WordPress version. I’m using the latest version of GeneratePress.
    6. Disabling only Woocommerce, and in this case the error disappear and I can use the customizer.

    Despite these efforts, the error persists. The only way to modify those blocks, with WooCommerce activated, is to go to /wp-admin/widgets.php and edit them directly without going through the “customize” link.

    Do you happen to know if there are any incompatibilities between the latest WooCommerce and GeneratePress?

    Could you please assist me in resolving this issue? Any guidance or suggestions would be greatly appreciated.

    Thank you for your help.

    P.S. I’ve noticed that the issue occurs on blocks with paragraphs and titles. For example, if I try to edit a menu or the ‘store notice’, or the site title and description, the error does not appear

Viewing 10 replies - 1 through 10 (of 10 total)
  • xmarksthespot

    (@xmarksthespot)

    2 years, 3 months ago

    I am having a similar issue/error, and it also only started today.

    Unlike you I am using the Blocksy theme. I am trying to add attribute filters to the woocommerce sidebar.

    I see the error in the Customiser but also in Appearance/Widgets in the dashboard irrespective of whether I’m using the Block editor or Classic editor.

    I suspect it is a woocommerce issue as I’m not seeing this for other customisations/edits/plug-ins. Perhaps there is a limit as to how many attribute filters or items I can add? – as it is ok initially but seems to get to a point where it falls over. When I start again – having cleared the sidebar, cleared cache and done largely all the things you did – it tends to get to a similar point before falling over with the error again.

    • This reply was modified 2 years, 3 months ago by xmarksthespot.
    Plugin Support Shameem – a11n

    (@shameemreza)

    2 years, 3 months ago

    Hi @pointnet,

    It’s possible that a conflict between WooCommerce and your current theme or another plugin causes the error. However, does this happen with WC 8.6 or an older version?

    Although you’ve mentioned that you’ve disabled all plugins except WooCommerce, and the problem persists, the issue could also be related to your theme. GeneratePress is usually compatible with WooCommerce, but there could be specific settings or customizations causing the issue.

    Could you please temporarily switch to a default WordPress theme like Twenty Twenty-Four or Storefront to see if the issue persists? If the issue is resolved, it will likely conflict with your current theme.

    Looking forward to hearing from you!

    prohumanity10

    (@prohumanity10)

    2 years, 3 months ago

    I have the same error and we can’t edit the widgets, this is a grave error, as its giving an error both in Cutomizer and in Widgets page. I have disabled everything, and the error is from WooCommerce. When disabling WC the error is fixed. Tried on different themes same issue, blocksy, astra, kadence, etc. Thus we are not able to edit the widgets! Please, inform WC to update/fix it as soon as possible, thank you!

    Customizer
    https://prnt.sc/7gKfhojyuGNq
    Widgets
    https://prnt.sc/1j7EBsML_-Hf

    Thread Starter Alessio Pellegrini

    (@pointnet)

    2 years, 3 months ago

    Hi @shameem (woo-hc),
    I’m using the latest version of Woocommerce ( Version 8.6.0 ) and the latest version of GeneratePress (Version: 3.4.0).

    With the default theme , Twenty Twenty-FourVersion: 1.0, the problem disappear.

    carolm29 (woo-hc)

    (@carolm29)

    2 years, 3 months ago

    Hey, @pointnet!

    Thanks for confirming.

    Since the issue is solved with a default theme, than please reach out to your theme’s support so they can assist you further with this.

    Please let us know if there’s anything else we can do to help.

    Have a wonderful day!

    —

    Hey @prohumanity10 and @xmarksthespot!

    Can you please try with a default theme such as Twenty Twenty-Four to see if the issue persists?

    If it does, per WordPress forum guidelines, would you mind opening up a new thread for this so that we can keep things organized and offer more personalized support for you? We’ll be happy to help you out with this over there!

    Have a wonderful day!

    prohumanity10

    (@prohumanity10)

    2 years, 3 months ago

    As I said, the error is from WooCommerce, tried on all themes, even Twenty Twenty Four. https://prnt.sc/cx3zT3S1aDqZ

    Beauty of Code (woo-hc)

    (@beautyofcode)

    2 years, 3 months ago

    Howdy @prohumanity10 👋

    Since WooCommerce 8.6.1 has been released, can you please update WooCommerce to its latest version [8.6.1] and see if this resolves the issue for you?

    If the issue persists, in order to adhere to the forum guidelines, and also better help you in accordance with your own site setup and environment (since these are unique), can you please start your own topic.

    We’ll be happy to help you further there 🙂

    Cheers!

    xmarksthespot

    (@xmarksthespot)

    2 years, 3 months ago

    @carolm29 and @beautyofcode

    I’ve just run a quick check having installed 8.6.1. Initially things looks OK now, but let’s see…

    As I, others posting here and my theme support suspected the issue was with woocommerce. It looks like it was introduced in woocommerce version 8.6.0 on 13 Feb and was resolved in 8.6.1.

    I did smile at the mention of wordpress forum guidelines – my favourite one being that in all circumstances woocommerce support must first always claim that their product is not at fault : – )

    Thread Starter Alessio Pellegrini

    (@pointnet)

    2 years, 3 months ago

    @carolm29 and @beautyofcode
    Hello, with the latest WooCommerce 8.6.1 everything works as expected.

    Plugin Support Shameem – a11n

    (@shameemreza)

    2 years, 3 months ago

    Hi @pointnet,

    That’s great to hear! Thanks for letting us know.

    I will mark this thread as resolved. Should you have further inquiries, kindly create a new topic here.

    Thanks!

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

The topic ‘Error: React.cloneElement(…): The argument must be a React element, but you pa’ is closed to new replies.