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

Consistent 'Read More' button and styling for manual post excerpts

Aperta
  • Qualcosa non va?
#4,509 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à
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
57/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
php, wordpress
Ambito
frontend, web-dev

Direzione di ricerca

Inizia individuando il rendering degli estratti dell’archivio del blog di Neve e le impostazioni di Customizer per Excerpt Length e il pulsante Read More. Confronta l’output dell’archivio per gli articoli con estratti manuali con quello degli estratti generati automaticamente, quindi verifica che gli estratti manuali ricevano il pulsante configurato e il comportamento di troncamento concordato.

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

Descrizione

customer report feature-request-triage

Impact: 60 · Confidence: 95 · Complexity: 40

Description

Problem

Currently, Neve's Customizer settings for "Excerpt Length" and the "Read More" button only apply to auto-generated excerpts. Posts that use manually written excerpts bypass these settings because native WordPress outputs manual excerpts exactly as written without the excerpt_more string. This causes an inconsistent user interface on blog archives, as posts with manual excerpts skip the excerpt length limits and are missing the "Read More" call to action.

Desired Behavior

The Customizer's "Read More" button and excerpt styling should apply uniformly to all posts on the archive page, regardless of whether the excerpt was auto-generated from content or manually entered.

Acceptance Criteria
  • Detect cases where a manual excerpt is being used on an archive layout (has_excerpt()).
  • Ensure the theme-configured "Read More" button is successfully appended to custom manual excerpts.
  • Enhance excerpt output to gracefully handle trimming manual excerpts when they exceed the Customizer Excerpt Length (or provide clear logic separating visual read more buttons from strict truncation).

Customer Context

The customer is a business plan user complaining that their blog archive has an inconsistent layout. Posts where they have specifically added a manual custom excerpt do not get truncated according to the Customizer settings, and they are completely missing the 'Read More' button, breaking the archive's visual consistency.

Root Cause Analysis

The root cause is a gap between WordPress's native excerpt behavior and user expectation for theme settings. WordPress's the_excerpt() naturally outputs custom (manual) excerpts as absolute, ignoring excerpt_length limitations and failing to trigger the excerpt_more filters (which usually add 'Read More' buttons). The user expects the theme Customizer's excerpt settings to govern ALL archive outputs blindly, leading to frustration when manual excerpts render inconsistently against auto-generated ones.

Alternative Suggestions

Instead of adding a new feature, update the existing blog archive rendering logic to better handle has_excerpt(). The logic should automatically append the Customizer's 'Read More' button HTML to manual excerpts so that the call-to-action is visually consistent across all posts. Additionally, consider introducing a toggle to enforce the Customizer excerpt length limit on manual excerpts as well, unifying the archive layout without removing the user's ability to input manual text.

Reasoning

The issue is caused by standard WordPress behavior where manual excerpts bypass length truncation and the 'excerpt_more' filter used for the 'Read More' button. Since this results in an inconsistent archive layout, we don't need to build a net-new feature, but rather improve existing archive rendering logic so that Customizer 'Read More' and length settings apply consistently to both auto and manual excerpts.

Source: HelpScout #3340953321
Generated by feature-request-triage workflow (ID: feature-request-triage_6a1dc8bd7fed15.02128843)

Lingua principale
PHP
Stelle
307
Fork
89
Merge medio
2g 20h
PR unite (30g)
24

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.