Critical JS Error in Checkout Blocks after updating to WooCommerce 10.7.0

  • Resolved lofersop

    (@lofersop)


    4 months ago

    Hola a todos,

    He detectado un error crítico que deja la página de Finalizar Compra (Checkout) en blanco (cargando infinitamente) tras actualizar a WooCommerce 10.7.0. He tenido que volver a la versión 10.6.2 para que la tienda vuelva a funcionar.

    Detalles del error: En la consola del navegador, aparece el siguiente error de Webpack en el entorno público (frontend), mientras que en el editor de bloques (backend) funciona correctamente: Uncaught TypeError: Cannot read properties of undefined (reading 'call') at c (checkout-frontend.js?ver=fd3b672b3e6033d2fcf3:5:17887)

    Entorno técnico:

    • Versión de WooCommerce: 10.7.0 (Falla) / 10.6.2 (Funciona).
    • Versión de WordPress: 6.9.4.
    • Tema: Divi (Elegant Themes).
    • Servidor: HestiaCP con Nginx como proxy inverso.
    • PHP: 8.3 (con 1GB de memory_limit).

    Pruebas realizadas para el diagnóstico:

    1. Modo de resolución de problemas: Utilicé el plugin Health Check & Troubleshooting para desactivar todos los plugins excepto WooCommerce y cambiar el tema a Twenty Twenty-Three. El error persistió incluso en este entorno puro, lo que descarta conflictos con Divi u otros plugins.
    2. Caché: Se purgaron las cachés de Nginx y del CDN (bunny.net) repetidamente sin éxito.
    3. Archivos: Reinstalé manualmente la versión 10.7.0 descargando el .zip oficial para descartar archivos corruptos, pero el error continuó.
    4. Base de datos: Se ejecutó la actualización de la base de datos de WooCommerce y se limpiaron los transients y las acciones programadas.
    5. Checkout Clásico: Es importante notar que el checkout clásico mediante el shortcode [woocommerce_checkout] SÍ funciona en la 10.7.0, el problema es exclusivo del nuevo Bloque de Finalizar Compra.

    Parece haber un problema con la carga de dependencias o fragmentos (chunks) de JavaScript en la nueva versión de los bloques cuando se sirven bajo ciertas configuraciones de Nginx.

    ¿Alguien más está experimentando este fallo con los bloques en la 10.7.0?

    Agradecería cualquier orientación de los desarrolladores.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    4 months ago

    Hi there!

    Thank you for the detailed report and for outlining all the troubleshooting steps you’ve already taken. I really appreciate the effort you’ve put into isolating the issue, including testing with a default theme, disabling plugins, clearing caches, and confirming the behavior difference between the classic checkout and the Checkout Block.

    I have also tried to replicate this issue on my end using WooCommerce 10.7.0, but everything is appearing fine and I’m not able to reproduce the same behavior with the Checkout Block.

    To assist you further and investigate this more deeply, could you please share the following details:

    • Your site URL so we can try to replicate the issue on your environment
    • System Status Report (you can find this via WooCommerce > Status)
    • Any fatal error logs (if available) under WooCommerce > Status > Logs

    Please use https://pastebin.com/ or https://gist.github.com/ and share the link here in your reply.

    Once we have this information, we’ll be able to investigate further and guide you more accurately.

    Thread Starter lofersop

    (@lofersop)

    4 months ago

    Sistem: https://pastebin.com/wseP2Cq2
    URL: https://ekivitalcentroestetico.com/finalizar-compra/

    JQMIGRATE: Migrate is installed, version 3.4.1
    checkout-frontend.js?ver=fd3b672b3e6033d2fcf3:5 Uncaught TypeError: Cannot read properties of undefined (reading 'call')
        at c (checkout-frontend.js?ver=fd3b672b3e6033d2fcf3:5:17887)
        at 3811 (checkout-frontend.js?ver=fd3b672b3e6033d2fcf3:5:13098)
        at c (checkout-frontend.js?ver=fd3b672b3e6033d2fcf3:5:17887)
        at checkout-frontend.js?ver=fd3b672b3e6033d2fcf3:5:20188
        at c.O (checkout-frontend.js?ver=fd3b672b3e6033d2fcf3:5:18157)
        at checkout-frontend.js?ver=fd3b672b3e6033d2fcf3:5:20202
        at checkout-frontend.js?ver=fd3b672b3e6033d2fcf3:5:20242
    • This reply was modified 4 months ago by lofersop.
    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    4 months ago

    Hi there!

    Thank you for sharing more details. I have checked the site and I am also able to replicate the issue on your site. However, on my site everything is working fine without any issues.

    Before escalating your issue internally, we’ll need the following:

    1. Fatal error logs (if any) under WooCommerce → Status → Logs
    2. Please create a staging site and, instead of using the Health Check & Troubleshooting plugin, manually deactivate all plugins and switch to a default theme like Twenty Twenty-Five. You can use the following plugin to create a staging site. https://wordpress.org/plugins/wp-staging/

    After completing these steps, please share the staging site URL with us. Once we have these details, we’ll be happy to escalate the issue internally.

    In the meantime, I would suggest downgrading to the previous version or using the classic checkout so your live site continues to work properly until the issue is resolved.

    Thread Starter lofersop

    (@lofersop)

    4 months ago

    He creado: https://ekivitalcentroestetico.com/pruebas-error/

    Sin desactivar nada ha funcionado correctamente con 10.7.0.🤔

    Thread Starter lofersop

    (@lofersop)

    4 months ago

    Solucionado, era prblema del cache de bunny añadi la regla para evitar que */wp-json/* se cacheara

    LovingBro (woo-hc)

    (@lovingbro)

    4 months ago

    Hi @lofersop,

    Really glad to hear you were able to track this down and get it resolved, that kind of deep troubleshooting you did here is incredibly helpful and much appreciated. The cache rule for */wp-json/* makes perfect sense in this case and it’s great to see things working again on your end.

    If you have a moment, leaving a review for WooCommerce would go a long way in helping other merchants make informed decisions and also supports the continued improvement of the plugin. You can share your experience here: https://wordpress.org/support/plugin/woocommerce/reviews/#new-post

    If anything else comes up, feel free to reach out anytime 🙂

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

You must be logged in to reply to this topic.