Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Support native WooCommerce Core Wishlists in Neve classic product templates

Abierto
  • ¿Algo no está bien?
#4,631 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
php, wordpress
Área
frontend, web-dev

Línea de trabajo

Start at Neve's classic single-product template integration and WooCommerce 10.9 native Wishlist hooks. Compare the native Wishlist rendering path with the existing Sparks/Neve Pro Wishlist feature, then verify that active native Wishlists render without overlap and follow Neve's design controls.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

customer report feature-request-triage

Impact: 65 · Confidence: 90 · Complexity: 60

Description

Problem: WooCommerce 10.9+ introduced native Wishlist functionality, but it is currently restricted to block-based product templates using the Add to Cart with Options block. In Neve, which uses classic WooCommerce templates, the native wishlist UI is not rendered.

Desired Behavior: Neve classic templates should support or hook into core WooCommerce Wishlists so users can leverage WooCommerce's native wishlist feature without needing a block theme or third-party/pro plugin.

Acceptance Criteria:

  • Render native WooCommerce Wishlist buttons/hooks on classic single product templates in Neve when WooCommerce Wishlists feature is active.
  • Maintain compatibility with existing Sparks/Neve Pro Wishlist feature without UI overlap or layout conflict.
  • Ensure consistent styling with Neve's theme design controls.

Customer Context

Customer Ethan from Meckeys wants to utilize WooCommerce's new native Wishlist feature (introduced in WooCommerce 10.9+) directly within the Neve theme, but the button does not display on Neve's classic product templates.

Root Cause Analysis

The customer wants to use WooCommerce 10.9's new native core features (Shopper Wishlists and Attribute Color Swatches) with Neve. The underlying problem is that WooCommerce limits these experimental core features to block themes and block-based product templates (such as the Add to Cart with Options block). Neve uses classic WooCommerce templates, causing WooCommerce to hide the Color Swatches setting and prevent native Wishlist buttons from rendering on Neve single product pages. While Neve Pro offers proprietary wishlist/swatch features via Sparks, supporting core WooCommerce native implementations in Neve's classic theme architecture requires net-new compatibility integration in Neve.

Reasoning

The customer is requesting compatibility support in Neve (classic WooCommerce templates) for two newly introduced native WooCommerce core features: (1) core WooCommerce Wishlists and (2) core WooCommerce Color Swatches. Currently, WooCommerce limits these native features to block themes and block-based product templates (e.g., Add to Cart with Options block), making them unavailable or hidden when running Neve's classic WooCommerce templates. Because Neve Pro offers its own standalone wishlist and variation swatches features via Sparks/Booster, supporting WooCommerce core's native implementations in classic Neve templates represents net-new product compatibility capabilities. Each requested native feature compatibility ask is distinct and tracked as its own feature request.

Source: HelpScout #3458698199
Generated by feature-request-triage workflow (ID: feature-request-triage_6ab27bf7ab47a3.89487359)

Lenguaje dominante
PHP
Estrellas
307
Forks
88
Merge medio
1 d 19 h
PR fusionados (30 d)
17

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.