Repository navigation
Open
Labels
area:analyticsAnalytics & trackingAnalytics & trackingarea:pluginsPlugin configuration/internalsPlugin configuration/internalscomp:wp-adminWP Admin screensWP Admin screenslang:jsJavaScript/TypeScriptJavaScript/TypeScriptlang:phpPHP codePHP codepriority:normalDefault priority for most issues.Default priority for most issues.status:needs-triageNew/ungroomed; needs review by PM/leadNew/ungroomed; needs review by PM/lead
Description
Context
The starter-plugin references in lightspeedwp/.github#3387 are obsolete. Generated plugins must use block-plugin-scaffold as their implementation source. This issue tracks the native replacements that are not yet present on develop.
Scope
- Capability-gated SVG uploads with server-side
enshrined/svg-sanitizevalidation - Configured
PHPMailertransport and sender values from deployment secrets, plus generated sender settings - Environment-aware
pre_wp_mailhandling for non-production environments - Vendor-neutral
dataLayerinitialisation and named analytics events - Capability-checked duplicate-post row action using core post APIs
- Generated-plugin guidance for the approved plugin register and advisories
Acceptance criteria
- Each feature is opt-in or has a safe generated-project default
- Security-sensitive features have capability and sanitisation checks
- Mail credentials are loaded from deployment configuration and never persisted in generated project files or the database
- Generated output includes focused tests and updated scaffold documentation
- No reference to a retired starter repository remains in generated output or guidance
- docs: add versioned plugin advisories for issue 1396 .github#3387 can link each planned replacement to this issue
Non-goals
- Reimplementing WordPress core APIs
- Client-specific analytics or mail configuration
- SMTP transport credentials in generated source or the database
Metadata
Metadata
Assignees
Labels
area:analyticsAnalytics & trackingAnalytics & trackingarea:pluginsPlugin configuration/internalsPlugin configuration/internalscomp:wp-adminWP Admin screensWP Admin screenslang:jsJavaScript/TypeScriptJavaScript/TypeScriptlang:phpPHP codePHP codepriority:normalDefault priority for most issues.Default priority for most issues.status:needs-triageNew/ungroomed; needs review by PM/leadNew/ungroomed; needs review by PM/lead
Type
Fields
Priority
None yet
Activity
eleshar commentedon Sep 27, 2026
This issue is now the tracking reference cited by the published advisory
docs/PLUGIN_ADVISORIES.mdis ondevelop(merged via #3387 in lightspeedwp/.github) and cites this issue as the implementing reference for four rows in its Section 1 table: Safe SVG, WP Mail SMTP / Change Mail Sender, Disable Emails, GTM4WP / Google Site Kit, and Yoast Duplicate Post.Those rows are currently marked
planned, notavailable, which is the correct status while this issue is open. The document's own guidance is to verify the generator branch before trusting a status, and to treat an issue as a tracking reference rather than as evidence the feature ships.Two things to do when this lands:
plannedtoavailable, with a direct source link rather than an issue link, in line with the document's status legendupload_mimeswithenshrined/svg-sanitizeon upload, a configuredPHPMailertransport with sender values from deployment secrets, apre_wp_mailshort-circuit driven bywp_get_environment_type(), vendor-neutraldataLayerevents, and a capability-checked duplicate-post row actionNo action needed from me; flagging the coupling so the advisory is not left stale after this ships.