Rename 'Published' tab to 'Saved' in form list pages

[arifulhoque7]

Related Free PR, Close issue

• Updated tab label from 'Published' to 'Saved' in wpuf_get_forms_counts_with_status()
• Changed status badge text in FormsList.vue
• Clarifies that forms are stored in the database rather than published content

Summary by CodeRabbit

• Style
  • Replaced the “Published” badge with “Saved” when a form’s status is publish, ensuring consistent terminology across the forms list and status summaries.
  • Other statuses (“Pending”, “Private”, “Draft”) remain unchanged.
  • No functional changes—this is a visual/wording update aimed at clearer status presentation in the UI.

[coderabbitai]

Walkthrough

UI and backend labels for the "publish" post status were changed from "Published" to "Saved". The Vue component adjusts the displayed badge text, and the PHP helper updates the status label mapping. No logic, styling, or public APIs were modified.

Changes

Cohort / File(s)	Summary of Changes
UI status badge text assets/js/components/FormsList.vue	When post_status is publish, the rendered badge label now displays "Saved" instead of "Published". Other statuses unchanged; no structural or styling changes.
Backend status label mapping wpuf-functions.php	In wpuf_get_forms_counts_with_status, the label for publish was changed from "Published" to "Saved". No changes to logic, counts, or function signatures.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A carrot-tipped quill in my fluffy paw,
I nudge a word and heed the law:
“Published” hops to “Saved,” neat switcheroo,
Front to back, the labels coo.
I twitch my nose—small change, well-braved,
One hop closer to forms well saved. 🥕🐇

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly and accurately summarizes the primary change: renaming the "Published" tab to "Saved" on form list pages. It is a single, clear sentence that focuses on the main user-facing change and aligns with the PR objectives and file-level edits. The title contains no extraneous details or ambiguous phrasing.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

assets/js/components/FormsList.vue (1)

551-553: Localize the new 'Saved' badge (and other statuses).

Wrap these strings with __() to keep i18n consistent across the UI.

-                    {{ form.post_status === 'publish' ? 'Saved' :
-                       form.post_status === 'pending' ? 'Pending Review' :
-                       form.post_status === 'private' ? 'Private' : 'Draft' }}
+                    {{ form.post_status === 'publish' ? __( 'Saved', 'wp-user-frontend' ) :
+                       form.post_status === 'pending' ? __( 'Pending Review', 'wp-user-frontend' ) :
+                       form.post_status === 'private' ? __( 'Private', 'wp-user-frontend' ) : __( 'Draft', 'wp-user-frontend' ) }}

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1d7b9b1 and 3392753.

📒 Files selected for processing (2)

• assets/js/components/FormsList.vue (1 hunks)
• wpuf-functions.php (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: Inspections

wpuf-functions.php

[warning] 1-1: The method parameter $post_id is never used.

---

[error] 1-1: Processing form data without nonce verification.

🔇 Additional comments (1)

wpuf-functions.php (1)

5607-5611: LGTM: backend label switched to ‘Saved’.

Status mapping now returns “Saved” for publish, matching the UI badge change.

Please confirm that no other forms list UI strings still render “Published” (e.g., any legacy PHP-rendered list views). If needed, we can scan templates using a quick grep for “Published” within forms-related contexts.

[Rubaiyat-E-Mohammad]

Post Status should be published @arifulhoque7 vai

[arifulhoque7]

done @Rubaiyat-E-Mohammad vai