Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
#4,632 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
php, wordpress
Ambito
frontend, web-dev

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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)

Lingua principale
PHP
Stelle
307
Fork
88
Merge medio
1g 6h
PR unite (30g)
10

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Codeinwp/neve

Tutte le issue di Codeinwp/neve

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.