• Resolved luketapis

    (@luketapis)


    Hi. I got this error:

    Deprecated: Function Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry::add() was called with an argument that is deprecated since version 8.9! The $check_key_exists parameter is no longer used: all duplicate data will be ignored if the key exists by default in?/home/xxx/public_html/wp-includes/functions.php?on line?6078

    How this can be fixed?

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Support omarfpg a11n

    (@omarfpg)

    Hi @luketapis,

    I’m reviewing this and it seems WooCommerce 8.8.2 includes?this PR?which deprecates the?$check_key_exists?parameter.

    Please note that the deprecation notice isn’t an error per se, it’s more like a preventive warning, and this should be fixed soon.

    Can you tell us if you’re seeing this message on the front end or back end? And what action are you performing when you see this message? Is it impeding use of the plugin? Are you able to place orders?

    Any details you can share can help us learn more about this to get it fixed quicker!

    Thanks

    Thread Starter luketapis

    (@luketapis)

    Thank you for your fast reply.

    I can see this message on the back end.

    “And what action are you performing when you see this message?” – I ignore it as it doesn’t affect my website dramatically. Just the order website is elongated.

    My customers can make orders normally

    Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @luketapis

    Thanks for confirming and further details.

    Since this warning does not affect your customers’ ability to place orders, you can continue using your site as usual. However, we’ll consider your feedback and work on a solution to remove this warning in future updates of the plugin.

    Meanwhile, I’m going to mark this thread as resolved. If you spot any other problems or if the warning begins to interfere with your site’s functionality, feel free to reach out to us again. If necessary, you can also switch to the legacy checkout block or shortcode instead of the checkout block.

    Should you have further inquiries, kindly create a new topic here.

    Thank you again for your patience and understanding.!

    The third parameter in the call is deprecated, this issue is fixed by removing the 3rd parameter on line 141 in file /wp-content/plugins/woocommerce-payments/includes/multi-currency/Analytics.php

    Current line:
    $data_registry->add( ‘customerCurrencies’, $currency_options, true );

    Fixed line:
    $data_registry->add( ‘customerCurrencies’, $currency_options );

    Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @kbpcit

    Thank you for sharing a solution! However, rather than editing the plugin’s core file, we suggest you wait for the upcoming official update.

    The good news is that our dev already fixed it and merged the changes, and waiting to release it in the next update:

    I hope this provides some clarity. Please let us know if you have any other questions!

    Thread Starter luketapis

    (@luketapis)

    thanks. when the new update will be releasd?

    Hi @luketapis,

    Thanks for getting back to us. The latest version, WooCommerce 8.8.2, was scheduled for release on April 17, 2024. This update includes several exciting new features. If you haven’t received a notification about the update in your WooCommerce dashboard, it’s possible that the update is being rolled out in stages. You can check all the releases of the WooCommerce core plugin here: https://developer.woocommerce.com/releases/

    Let us know if there’s anything else we can help you with.

    Hi @afzalpansuvi,

    Do you have a timeline on the release of the next version of woocommerce-payments? That is the plugin that is throwing the error. The changes to the new version of WooCommerce is what is now causing the error to pop up.

    Thank you @shameemreza for the advise, my apologies.
    I agree that editing the core is not the best solution, however the error was triggering my OCD.

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hello @kbpcit,

    Do you have a timeline on the release of the next version of woocommerce-payments??

    I can confirm that there is already a new update of WooPayments which was released 4 days ago. You can check it out here.

    If you have any further questions, I’d suggest creating your own thread to get personalized assistance.

    All the best.

    Thread Starter luketapis

    (@luketapis)

    The update which was released 4 days ago caused the issue.

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hello @luketapis,

    As confirmed above by my colleague @shameemreza,

    The good news is that our dev already fixed it and merged the changes, and waiting to release it in the next update:

    I hope this provides some clarity. Please let us know if you have any other questions!

    We are not certain of the latest release date, but this issue has already been merged and should be solved in the next WooCommerce update.

    Thanks.

    I have just updated WooCommerce to version 8.8.2 and I have started getting this warning in the backend.
    I have the latest version of WooPayments, version 7.5.1 and the warning it is still there.
    If you think that version 7.5.1 contains the fix to this issue you are mistaken and you are providing misleading information.

    The deprecation warning is thrown when
    WCPay\MultiCurrency\Analytics->register_customer_currencies()
    invokes
    Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->add() with the third parameter $check_key_exists set to true. In my case this happens when EUR/Euro is being registered, but I guess this will happen with any currency other than USD.

    An ETA for the release of a new version of WooPayments with a working solution would be appreciated.

    Just a few minutes after I posted my comment, version 7.5.2 have been released with the aforementioned patch.

    Problem solved.
    Thanks

    Thread Starter luketapis

    (@luketapis)

    confirmed. problem solved. thanks

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Error on line?6078’ is closed to new replies.