2026-10-05 ยท CPH Feedback Desk
Improves feedback form text contrast when a WordPress theme supplies its own paragraph colors.
What changed
- Sets explicit, scoped foreground colors for feedback form instructions and notices so a theme paragraph rule cannot make them difficult to read.
- Retains the standalone feedback workflow, FluentCart catalog integration, private 200 MiB upload ceiling, new-product proposals and administrator-only approval from 2026.10.05.005.
Verification
- Passed 36 public markup checks and 23 targeted palette, selector and version checks; PHP syntax validation passed.
- A local browser loaded the actual conflicting theme paragraph rule after the plugin stylesheet. Form instruction, privacy, help and status text retained the intended light colors; tested normal-text palette contrast was at least 9.42:1 against both background gradient endpoints.
- The underlying feedback workflow is unchanged from 2026.10.05.005, whose isolated WordPress/storage/permission tests and ten independent live read-only API checks passed. Live .006 capabilities report uploads enabled at 200 MiB, the served CSS hash matches the release, and browser inspection confirmed readable form instructions, controls and the new-product-name toggle.
Rollout
Installed, active and visually verified on CreatorPublishingHub.com only. The public feedback page and private administrator queue are available, and the standalone .006 installation package is retained. The earlier .005 package and notes remain available. FluentCart supplies the product catalog; its four migrated products retain draft status and therefore remain excluded from the public selector until published. Taylor's existing reader credential successfully read the feeds; no new monitoring schedule was created.
Updating
- Back up the existing cph-feedback plugin before replacing it with this version. Retain all feedback tables and private uploaded files.
- This update changes presentation and release metadata; it requires no database migration and does not alter reader permissions or administrator approval rules.
Scope and limitations
- Reports, uploaded evidence and customer relationships are unverified user submissions. The plugin does not execute report content, fetch submitted URLs, send email, enroll visitors in marketing or publish feedback.
- Approval records an administrator decision; it is not proof that a change was implemented or a promise of delivery. No store migration or payment configuration is included.
- File limits depend on the hosting configuration as well as the plugin ceiling. Basic abuse controls do not constitute CAPTCHA or malware scanning. Private files require an explicitly verified storage location.
- A read-only API and optional polling helper do not by themselves mean Taylor is monitoring or has reviewed a report. Each installation needs its own authorized reader configuration.