Customizer controls script throws when WooCommerce is inactive and an Elementor shop template exists (woocommerce_product_catalog section missing)

Cerrado
  • ¿Algo no está bien?
#4,653 3 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@girishpanchal30 ya está trabajando en esto.

Desde el 13/10/2026.

  • #4654 de @girishpanchal30 — fusionado
  • #4656 de @pirate-bot — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

bug-report bug-report-triage customer report

Summary

With WooCommerce deactivated and a leftover Elementor shop (product archive) template on the site, the Customizer, including the Header Builder, fails to finish loading and stays stuck.

Expected: the Customizer loads normally; the Elementor-template warning is only attempted when the WooCommerce section exists.
Actual: a script error stops initialization.
Impact: the Header Builder and Customizer are unusable on affected sites until WooCommerce is re-enabled or the template is removed.

Customer context

  • Product / area: Neve (Pro) Customizer / Header Builder
  • Version: Not provided
  • Environment: WooCommerce disabled; Elementor shop template remains
  • Reported symptom: Customizer/Header Builder stuck loading
  • Impact: Customizer unusable on that site

Reproduction notes

Inferred steps: 1) Create an Elementor product archive template. 2) Deactivate WooCommerce. 3) Open the Customizer. Expected: the script error appears and the UI hangs. Not reproduced at runtime.

Diagnosis

Conclusion

The code path appears to call .notifications on the result of wp.customize.section('woocommerce_product_catalog') without checking that the section exists. That section is registered by WooCommerce, so with WooCommerce off the result is likely undefined and the call would throw. This is inferred from source, not runtime-verified.

Where this likely occurs
  • assets/apps/customizer-controls/src/controls.js — checkHasElementorTemplates() approx. lines 317–345, on the woocommerce_product_catalog and neve_single_product_layout sections; it is called approx. line 406.
  • inc/compatibility/woocommerce.php — add_customizer_options() approx. lines 145–149, which sets hasElementorShopTemplate and hasElementorProductTemplate via Elementor::has_template().
Engineering notes

The elementor flags are set in the WooCommerce compat class. Worth checking whether that class loads when WooCommerce is inactive, and whether the flag is true in that state. A leftover template post is apparently enough to trigger the branch. The product-template block just below uses the same pattern for neve_single_product_layout.

Test coverage status

No relevant coverage was found during inspection.

What to verify or explore next

May be worth verifying the reproduction with WooCommerce off plus an Elementor product_archive template, and checking the browser console for a TypeError.

Unknowns / follow-up

The affected Neve version is unknown. Whether the flag is populated with WooCommerce off was not confirmed.

Confidence

Confidence: 80/100

Source shows the Customizer script dereferences a WooCommerce section without a null check, matching the customer's diagnosis. Not runtime-reproduced.

Source: HelpScout #3480859978
Generated by bug-report-triage (ID: bug-report-triage_6acd668c519742.22923583)

Lenguaje dominante
PHP
Estrellas
307
Forks
89
Merge medio
3 d 8 h
PR fusionados (30 d)
18

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Codeinwp/neve

Todos los issues de Codeinwp/neve

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.