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

Add compatibility for core WooCommerce native Color Swatches in Neve classic templates

Abierto
#4,632 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
52/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 by tracing Neve's WooCommerce compatibility declarations and hooks for classic single product and archive templates, then inspect how WooCommerce exposes the Color swatches for attributes setting under Settings > Advanced > Features. Verify the setting remains available and that native swatches render on both classic product views; the issue's acceptance criteria define done.

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: 65

Description

Problem: WooCommerce core introduced native attribute Color Swatches, but WooCommerce currently restricts this setting/feature to block themes. When Neve is active, WooCommerce hides 'Color swatches for attributes' under WooCommerce > Settings > Advanced > Features.

Desired Behavior: Neve should provide necessary theme support declarations or template compatibility hooks so WooCommerce core native Color Swatches can be enabled and rendered on classic product attribute selections.

Acceptance Criteria:

  • Declare compatibility/support for WooCommerce core native attribute color swatches in Neve.
  • Ensure color swatch options under WooCommerce > Settings > Advanced > Features remain visible and functional when Neve is active.
  • Correctly display native color swatches on Neve classic single product and archive pages.

Customer Context

Customer Ethan from Meckeys wants to use WooCommerce core's native Color Swatches feature without relying on third-party plugins or paid add-ons, but the setting is unavailable under WooCommerce Settings while Neve theme is active.

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 6 h
PR fusionados (30 d)
10

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.