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

WordPress.org support backlog audit (2019–2026)

Aperta
  • Qualcosa non va?
#103 3 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@superdav42 ci sta già lavorando.

Dal 14/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

documentation origin:interactive parent-task status:available tier:standard

WordPress.org support backlog audit, 2019–2026

What

Planning-only: track the deduplicated follow-up work from the maintainer-requested support audit. Implementation belongs to the linked issues, not this index. The audit itself is complete; this tracker remains open until its follow-ups are resolved or explicitly dispositioned.

Coverage and evidence

  • Reviewed 2026-10-14: both unresolved-topic pages and the first two full forum index pages, retrieving 60 distinct thread roots plus the additional reply page for “Stopped working.” All retrievals succeeded.
  • Main window: October 2019–October 2026. The 28 not-resolved threads inside that window were reviewed, plus the September 2019 “Showing Tags When Editing” boundary thread (29 primary unresolved threads). Older June–August 2019 threads visible on page 2 are outside scope.
  • Also inspected resolved/not-a-support-question threads where replies left a feature request or workaround rather than delivering the requested functionality. Forum “closed to replies” is not evidence of a fix.
  • Compared current SCE 3.4.1 source at 4f9308ff02801cca94fdb387a73d5ee247ec34f8 with remote master 68aa5dfa9a24bf1cd87470fb445e52f30d2af2f0: intervening changes affect dependency manifests/lockfile only, not reviewed support code.
  • Read existing open/closed GitHub issues, merged/open PRs, relevant source and changelog; ran scoped collision discovery. PR #57 is an in-flight admin/POT translation change, not a fix for bundled frontend countdown lookup or German Formal/Russian catalogs.
  • Archived forum text was scanned. One Cyrillic-language thread triggered a homoglyph warning; only factual translation evidence was used, and no embedded commands/links/contact requests were executed.
  • This is source/history verification, not a live WordPress reproduction. Third-party theme/add-on, proxy and Akismet-specific conclusions remain unverified where noted.

Follow-up issues

Eleven implementation/documentation issues passed schema-v2 worker-readiness validation and carry auto-dispatch. Three investigation-only issues do not carry auto-dispatch because current reproduction/access and an exact fix are missing.

  • #89 — Duplicate WooCommerce rating controls and review integration.
  • #90 — AJAX-posted and lazy-loaded comments without page reload.
  • #91 — AJAX failure recovery and inline edit/delete endpoint behavior.
  • #92 — Optional Quicktags and external-editor lifecycle.
  • #93 — Moderator comment movement, with optional descendants.
  • #94 — Bundled countdown localization, German Formal and Russian catalog repair.
  • #95 — Nicepage, MasterStudy and WP User Frontend compatibility investigation.
  • #96 — Historical Editing Options conflicts with Jetpack/Max Mega Menu investigation.
  • #97 — Verified custom-field/custom-loop/button/inline-layout examples.
  • #98 — Cache/proxy/migration and failed-controls diagnostic documentation.
  • #99 — Posts-only/no-comments asset-loading policies.
  • #100 — Opt-in edited timestamps/deleted-comment indicators.
  • #101 — Reduced-delay/reduced-motion edit controls.
  • #102 — Historical proxy/migration/cookie/fatal/intermittent/Akismet investigation.

Primary unresolved-thread disposition

Support thread Current code/history result Work captured
Tip No comment-movement operation exists. #93
Edit buttons not shown correctly Already addressed by merged PR #56, SCE 3.4.1. simple-comment-editing.php:475-538 restores pending-comment block markup after Core sanitization. No duplicate fix issue. Existing merged fix
PHP warning about comment_author on null The reported file belongs to mention-comments-authors, not SCE. No evidence establishes an SCE defect. No SCE issue
Rating issue on WooCommerce Duplicate star creation and global selectors remain in current source; associated event/selection faults identified. #89
Using this in static function Current static removal calls self::get_instance()->generate_cookie_data(...) at simple-comment-editing.php:938-943; the reported $this misuse is absent. Already addressed in code
Translation for countdown Countdown is marked for translation, but bundled JSON lookup is not configured. #94
Edit link not unhiding after migration No current console/network reproduction or proven fix. #98, #102
Change language No bundled de_DE_formal catalog exists. #94
Unlimited time Logged-in-author unlimited editing is now an option in 3.4.0; includes/Output.php:140-160 and includes/Functions.php:138-142 implement it. Anonymous indefinite editing was not promised. Already implemented
Nothings apears / MasterStudy No explicit MasterStudy integration; precise renderer/store is unverified. #95
Critical error Only a thrown-file location is supplied, not a full fatal message/stack. Cannot attribute or claim a fix. #98, #102
FancyBox Uncaught Type Error Fancybox admin previews were removed in 3.3.1; current tracked code has no Fancybox calls (changelog mention only). Obsolete integration removed
Alternate Editor Interface? Raw textarea remains; editor adapter/toolbar still missing. #92
Cannot translate the edit button? Current text is translatable and customizable, but bundled catalog discovery needs repair and stored-label behavior needs explanation. #94
Edit link only displays after refresh General dynamic-comment initialization is absent beyond the explicit WP Ajaxify adapter. #90
Not working / WP User Frontend Historical integration unverified; inline action recovery/navigation shortcomings still visible in source. #91, #95
Getting an Ajax error/issue Exact historical JS conflict unknown; current failure-envelope/recovery defects and POST-only navigation exist. #91
SCE clashing with Akismet? Generic approved-comment remoderation was addressed in 3.0.21, but that does not prove the tentative Akismet-specific interaction fixed. Preserve genuine spam decisions. #102
Support for Lazy Load for Comments Single window-load scan and cookie-gated assets leave general delayed initialization missing; 3.0.20 fixed only a timer lookup error. #90
Update compatibility with WP 5.6.1 No behavioral defect reported; current minimum is WP 6.5 and metadata is updated through WP 7.1. Historical metadata request is superseded, not a new bug. No new issue
Not working with Nicepage No explicit adapter; need current template/submit-hook verification. #95, #97
SCE stopped working, WP 5.5.1 Reporter describes recovery and recurrence without enough evidence to identify a current defect. #98, #102
Passing values of added fields Core hooks exist; posted JS is malformed and omits a hook namespace; metadata writer erases values when fields are absent. #97
Displaying edit button and other objects in a row Existing wrapper hierarchy must be retained; layout example missing. Immediate/low-motion presentation request is not implemented. #97, #101
Not working through Cloudflare Proxy-on/off correlation reported, but precise optimization/cache/scheme cause not established. #98, #102
Editing Options conflict with Jetpack Historical Options add-on, not a reproduced standalone SCE failure. #96
Conflict version 2.4.2 / Max Mega Menu Reporter isolated old Options add-on; maintainer could not reproduce. #96
Not working after WP 5.3.1 Maps to historical logged-in regression addressed in 2.4.1; related “Doesn’t work”/“Stopped working” threads confirm recovery. Current ownership-based logged-in path remains. Exact original site not retested. Historical fix, no duplicate issue
Showing Tags When Editing September 2019 boundary: reporter confirmed tags visible again; request evolved into Quicktags toolbar integration. Current textarea escapes raw content correctly. #92

Related requests whose forum status did not mean implementation

Thread Finding Work captured
Using Editor Used by Comment Box Marked resolved as a feature request; still a textarea. #92
Edit link only visible after page reload / BuddyBoss Marked resolved as a feature request; switching to WP Ajaxify is a workaround, not a BuddyBoss fix. #90
A small feature request Edited-time/deleted indicators still missing. #100
Conditional loading, original and 2026 follow-up Developer filter exists; requested built-in policy/setting remains missing. #99
Heads Up W3TC breaks pre-minified JS Explicit exclusion workaround exists; user-facing documentation missing. #98
Right-click of Edit Button Still exposes a POST-only inline endpoint as a navigable link. #91
Translation incident Russian bundled JSON still contains null/English-leading singular/plural arrays despite resolved status. #94

Other checked histories and existing GitHub work

  • Early-textdomain warnings: replies confirm 3.0.32/3.0.33 fixes; current error translation initialization is on init (simple-comment-editing.php:115-140). No duplicate issue.
  • Case-sensitive class-not-found/admin WSOD/PHP-conflict reports: corrected Admin/Tabs paths exist and replies confirm 3.0.14 recovery.
  • Old PHP 5.6/WP 4.9 fatal cases: superseded fixes and explicit current minimums (PHP 7.2/WP 6.5), not requests to restore obsolete runtimes.
  • WP Ajaxify support: confirmed working in replies; native event integration exists. #90 must preserve it.
  • Default gravatars: reporter confirmed spontaneous recovery and likely external Gravatar cause, not an SCE fix request.
  • Existing GitHub #38 custom loop, #29 button HTML and #28 unspecified comment-plugin question were not duplicated. #97/#95/#90 cross-reference their context.
  • Existing GitHub #27 already has three filter arguments in includes/Functions.php:84; #33 now has a built-in compact timer choice. No issue closure or forum response was performed in this audit.
  • Out-of-window 2019 threads about orphaned comments, others’ comments, stop-editing-on-publication and manual approval were discovered but not treated as inside the requested seven-year window.

How and verification

No product code is changed by this index. Its reference/write surface is the linked GitHub issue briefs, plus simple-comment-editing.php, includes/Functions.php, includes/Ajax.php, includes/Output.php, includes/Options.php, includes/WooCommerce.php, includes/Admin/Tabs/Settings.php, src/js/comment-editing/editing.js, src/js/SendCommand.js, src/scss/frontend.scss, languages/, readme.txt and README.md as audit evidence. Implementation issues contain exact scopes and existing-tool/runtime verification contracts. Do not claim a fix shipped merely because a child PR exists; verify the current default branch and actual release/runtime state.

Acceptance criteria

  • Every primary unresolved thread has a source-linked code/history disposition.
  • Remaining bugs/features/documentation gaps are filed as deduplicated, self-contained issues with verification criteria.
  • Unreproduced third-party/environment reports are recorded as investigations rather than invented code defects.
  • Each linked follow-up is implemented and verified, or explicitly dispositioned with evidence.

aidevops.sh v3.39.27 plugin for OpenCode

Lingua principale
PHP
Stelle
19
Fork
10
Merge medio
3h 6m
PR unite (30g)
22

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 Ultimate-Multisite/simple-comment-editing

Tutte le issue di Ultimate-Multisite/simple-comment-editing

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.