Add WPFTP feedback export: Tools admin page + WP-CLI command

[Piyopiyo-Kitsune]

Context

The two WordPress Facilitator Training Program courses run a survey (a Jetpack Form) asking respondents what role they're in. Being able to later match who enrolled in and completed the course against their reported role requires knowing which logged-in user submitted each survey response.

Jetpack Forms' own CSV export doesn't include the logged-in user who submitted each response, even though Jetpack captures it internally (display name, username, user ID) at submission time. There's no filter/hook exposed by Jetpack to inject that into its own export, so this adds a standalone export path in wporg-learn instead.

What's added

• wp feedback export (WP-CLI) — full export of Jetpack Forms feedback responses: every field Jetpack's own CSV export has (ID, Date, Title, Source, the form's own fields, Consent, IP Address, Country code, Browser), plus the logged-in user, joined by the real feedback post ID (not by row position).
• Tools → WPFTP Feedback (wp-admin) — the same export from the browser, with a form picker, status filters (spam/trash), and a date range — for exporting without shell access. Gated behind the export capability (Administrator-only by default), nonce-protected.

Both share get_rows()/build_csv() in feedback-logged-in-user-export.php; the CLI command lives in its own file (class-feedback-export-cli.php) since this plugin's convention is not to mix function and class declarations in one file.

Testing

• Verified end-to-end in wp-env: real guest + logged-in Jetpack Forms submissions, both the CLI command and the Tools page produce an identical, correctly-joined CSV.
• Verified the "no responses found" admin notice and a distinguishable error (vs. a silent empty result) when Jetpack Forms is deactivated.
• Verified capability gating denies a non-admin (Editor) user, both at the menu level and the form-handler level.
• phpcs clean against this project's phpcs.xml.dist.
• Went through /code-review (5 findings: reuse of Jetpack's own get_all_parent_post_ids(), avoiding a redundant double-fetch of feedback data, replacing a const+reassignment workaround with proper use imports, distinguishing integration failures from genuinely-empty results via WP_Error, and comment-style) — all fixed and re-verified.
• Ran a security review — no findings.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Adds an alternative export path for Jetpack Forms feedback responses in wporg-learn, ensuring each response row includes the logged-in user information Jetpack captures but does not include in its own CSV export.

Changes:

• Adds shared export logic (get_rows() + build_csv()) to assemble Jetpack’s export columns and join logged-in user data by feedback post ID.
• Adds a Tools → WPFTP Feedback admin page to download the CSV with form/status/date filters.
• Adds a wp feedback export WP-CLI subcommand to generate and save the same CSV.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.

File	Description
wp-content/plugins/wporg-learn/wporg-learn.php	Loads the new feedback export and WP-CLI command files.
wp-content/plugins/wporg-learn/inc/feedback-logged-in-user-export.php	Implements shared row building + CSV creation, and adds the Tools page + admin-post handler.
wp-content/plugins/wporg-learn/inc/class-feedback-export-cli.php	Registers the wp feedback export WP-CLI command using the shared export logic.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[maciejpilarski]

Looking into it 👀

[maciejpilarski]

Update after merge: this was reverted in #3660 and re-landed with fixes in #3661.

A full review of the merged code, checked against the Jetpack Forms source, the shared Export_CSV mu-plugin utility and WordPress core, found problems that change what the export contains and let the CLI widen an export silently:

• date_query without inclusive drops both boundary days of a Y-m-d range; a one-day range exports nothing.
• Export_CSV::add_row() runs sanitize_text_field() on every cell and its esc_csv() inserts apostrophes before -, +, @, = mid-text, so free-text answers come out altered.
• An unrecognised --status makes WP_Query drop the status clause (exports spam and trash), an unparseable --after becomes 1970 (exports everything), a non-numeric --post casts to 0 (all forms).
• --dir defaulted to the current directory, so a run from the site root wrote a guessably named file with usernames and IP addresses into the web root.
• Smaller: all-test-response results became a wp_die(); spam/trash rows had no status column; same-day exports overwrote each other; the ID column was matched by the English literal rather than Jetpack's translated key; core's export capability gated the page.

One data caveat that matters for the role-to-completion analysis: Jetpack only began capturing the submitter's account in forms package 7.14.0 (23 March 2026). Responses stored before that have no logged_in_user key at all, so their user columns are blank in exactly the way a guest's are. #3661 adds a "Logged-in user recorded" column so the two cases can be told apart.

The feature and its purpose are unchanged in #3661; @Piyopiyo-Kitsune is credited as co-author there. Thanks for building it.