| 开发者 |
landtechwebdesigns
brelandr |
|---|---|
| 更新时间 | 2026年5月13日 11:19 |
| PHP版本: | 6.2 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Yes! While tailored for weddings, it works for any event requiring basic RSVP tracking.
Go to Settings and scroll to the bottom danger zone. Click Erase all data & reset plugin (exports first if you need a backup).
Yes. Wedding Party RSVP Pro adds child guests, full menu courses, seating notes, batch email and SMS, and deeper styling. The free plugin covers unlimited guests, adult entrées, dietary options, CSV import/export, and the public RSVP form.
No. Guests use a Party ID (invite code) you assign—no user registration required.
Yes. Add a Shortcode block (or the classic block) and paste [wedding_rsvp_form]. A block pattern is also available in the editor when the plugin is active.
Yes. Keep both plugins active: the free plugin provides the core guest list and RSVP form; Pro extends it with premium features when your license is valid.
Guest records live in your WordPress database (a custom table, usually wp_wedding_rsvps with your site prefix). Typical fields include Party ID, name, RSVP status, meal choice, and anything guests enter on the public form (for example email, phone, dietary notes, allergies, song request, message, address). Only users who can manage the plugin in wp-admin can view or edit that list.
In wp-admin, use Tools → Export Personal Data and Tools → Erase Personal Data (WordPress 4.9.6+). This plugin registers an exporter and an eraser that match guest rows by email address stored on the guest record. Erasing removes all guest rows that use that email from the RSVP table—use only when appropriate for your jurisdiction and event.
Yes. In Settings → Logistics, set event title, start time, and optional venue; when enabled, guests who complete RSVP can download an .ics file (“Add to calendar”).
In Wedding RSVP → Settings (free) use Frontend Display; with Pro, use Settings → Frontend text. Enter an optional heading and one or more link labels with full https URLs (for example Amazon or Zola). Guests see them after signing in with their Party ID.
In Wedding RSVP → Paste Guest List (admin menu), paste names, emails, or phone lines, preview rows, then import. Imports are capped per request and require an administrator; see the on-screen notice after import.
When your site supports the Interactivity API, guests may see a short hint after typing a Party ID. The browser calls the read-only REST route wgrsvp/v1/party-preview, which returns only whether the party exists, a guest count, and up to three first-name tokens (not full PII). Requests are rate-limited per IP to reduce brute-force guessing; adjust with the wgrsvp_party_preview_rate_limit_max filter if needed.
installPlugin uses pluginData (current WordPress Playground schema); landing page opens the public Wedding RSVP demo (/); demo seed merges wgrsvp_general_settings instead of replacing the option; root blueprint.json stays in sync with assets/blueprints/blueprint.json.assets/blueprints/blueprint.json (excludes only the nested assets/blueprints/trunk/ dev tree).wgrsvp_sanitize_redirect_url_setting() and wgrsvp_resolve_stored_redirect_url() for full URLs and root-relative paths; General Settings save, Interactivity/AJAX success payload, and classic form POST all resolve the stored value before wp_safe_redirect() so guests reach your thank-you / custom page when Pro is inactive.wp_ai_client_prompt).wgrsvp_gift_registry_items). Wedding Party RSVP Pro: same fields on Settings → Frontend text; front end uses the shared renderer when the free plugin is active.wgrsvp_admin_module_enabled filter still applies per module. When Wedding Party RSVP Pro is active with a valid license, use Pro’s Settings for the same module keys.SHOW COLUMNS + seated guest count) are cached 24 hours (wgrsvp_vendor_packet_seating_snapshot) and clear when guest data changes.wgrsvp_rsvp_form_success_flash after non-AJAX submit.wgrsvp/v1/party-preview and coordinator wgrsvp/v1/guest-rows routes (preview remains IP rate-limited).load_plugin_textdomain on init); Text Domain and Domain Path in the plugin header unchanged.prepare() argument spread and allowlisted SELECT columns; deadline nudge SQL uses %i + bound IN list; audit log and vendor packet queries use %i where appropriate; PDF/CSV stream helpers use literal text domain wedding-party-rsvp with an ignored optional third argument so Pro call sites keep working; bundled FPDF files gain ABSPATH guards; PHPCS excludes includes/lib/fpdf; misc PHPCS inline docs for nonce/token and DB calls.wgrsvp_pro_live_demo_url. Shown when Pro is not active.pro_bulk_guest_list, pro_import_csv, pro_ai_guest_tags, pro_rest_seating) and tracked columns table_id, wpr_pro_ai_note_tags; QR check-in tokens are no longer included in diff payloads.wgrsvp_guest_audit (dbDelta on activate/upgrade) records insert/update/delete on guest rows with source (public form, admin, imports, day-of desk, setup wizard, Pro edit/REST/check-in where applicable), actor, and JSON field diffs. Wedding RSVP → Audit log (administrators) lists and filters entries. Erase Personal Data deletes audit rows for erased guest IDs; factory reset truncates the audit table. Filters: wgrsvp_audit_trail_should_log, wgrsvp_audit_trail_changes, wgrsvp_audit_trail_tracked_fields; action: wgrsvp_guest_audit_logged.wgrsvp_arrived_at on the guest row; Pro QR check-ins still show as “Checked in (Pro)”). Coordinators can open the screen for lookup; arrival buttons remain admin-only. Schema: wgrsvp_arrived_at on wedding_rsvps (dbDelta).wedding-rsvp-ops without redirect (same capability as the guest dashboard).wgrsvp_client_summary_portal_state; cleared on factory reset.households_total and households_fully_replied; filter wgrsvp_aggregated_rsvp_stats.get_aggregated_rsvp_stats() is now public so WGRSVP_Growth_Checklist can call it (was private).wgrsvp_getting_started_panel_dismissed (cleared on factory reset).wgrsvp_next_steps_notice_dismissed.wgrsvp_gap): no email, no phone, no mailing address, pending with no email/phone; honored by CSV / check-in / caterer exports via export_wgrsvp_gap.id="wgrsvp-logistics-heading" for in-admin deep links.wgrsvp_guest_hub_payload.gift_received, thankyou_card_sent_on on wedding_rsvps.
7.3.23
NEW: Deadline reminder emails — optional WP-Cron daily nudges before the RSVP deadline (wgrsvp_rsvp_deadline_nudge); settings under General Settings → Logistics; filters wgrsvp_deadline_nudge_recipients, wgrsvp_deadline_nudge_skip_guest, action wgrsvp_deadline_nudge_sent_email (Pro may attach Twilio SMS).
NEW: Caterer portal — magic-link read-only meal summary (Wedding RSVP → Caterer portal); Pro maps table_id labels when seating tables exist.
7.3.22
NEW: Guest Hub — post-RSVP summary (meals, dietary, event details) via AJAX payload, thank-you page, shortcode [wgrsvp_guest_hub], and block; optional Open in Google Maps from Logistics venue (documented under External Services).
7.3.18
IMPROVED: When Wedding Party RSVP Pro is active and licensed, the main Wedding RSVP guest list again includes per-guest email (and SMS when the row has a phone) action buttons—same templates as bulk invite, for reminders or guests added later. Administrators only.
7.3.17
IMPROVED: DataViews (admin) — when Wedding Party RSVP Pro is active with a valid license, the read-only table adds Check-in column filter, Checked in at and Planner tags columns, optional Planner tag (slug) text filter (REST wpr_planner_tag), and passes wpr_attended from the UI. Free-only installs see a short note that those options require Pro.
NEW: Guest-rows REST accepts wpr_planner_tag (slug); Pro extends wgrsvp_guest_rows_rest_order_by_map for wpr_pro_attended_at and wpr_pro_planner_tags sorting.
7.3.16
NEW: Thank-you checklist — optional post-event task list in its own database table (name like wp_wgrsvp_thankyou_tasks): Wedding RSVP → Thank-you checklist (Administrators), shortcode [wgrsvp_thankyou_tracker], block Thank-you checklist, and optional public="1" for visibility on planner-only pages (avoid on fully public pages).
NEW: Household prompt — after a successful Interactivity API RSVP save (no redirect), guests may see a short notice when their party still has pending members, with scroll-to-next-pending.
IMPROVED: Privacy Policy suggested text mentions the checklist table.
7.3.15
NEW: Wedding RSVP Form block (wedding-party-rsvp/rsvp-form) — dynamic block matching [wedding_rsvp_form]; block.json enables __experimentalVisibility where the editor supports viewport visibility.
NEW: DataViews (admin) — optional read-only guest table on Wedding Dashboard (?wgrsvp_dataview=1) uses @wordpress/dataviews when build/ is present (run npm run build in the plugin directory), with GET wgrsvp/v1/guest-rows for pagination, search, RSVP filter, and sorting. Falls back to a small vanilla script if the bundle is missing.
NEW: Caterer summary export — on the Wedding Dashboard guest list, export a Caterer summary (PDF or CSV) that aggregates accepted guests by table with meal counts and dietary/allergy notes (optional checkbox to include non-accepted rows). DataViews can filter by meal choice, text in dietary/allergies, and “has table assignment” via REST query args (menu_choice, dietary_contains, allergy_contains, has_table); all processing stays on your server.
7.3.14
NEW: AI wording assistant on General Settings (welcome title, closed-RSVP message, and copy-paste snippets for save-the-date / deadline reminder) when wp_ai_client_prompt is available. Filter: wgrsvp_ai_wording_prompt.
IMPROVED: Interactivity API — optional entrée follow-up field when guests choose Vegetarian/Vegan; debounced email format hint on the RSVP form; watch() syncs a busy state class when WordPress exposes it (7.0+).
7.3.12
NEW: Optional Add to calendar (.ics) after RSVP when event details are set in General Settings; thank-you state uses a secure redirect with query args.
NEW: Export check-in PDF on the guest dashboard (same filters as CSV), using bundled FPDF.
7.3.11
IMPROVED: License / Support field on General Settings masks a stored key when the site is effectively licensed (including the same trusted showcase hostname rules as Pro); saving with a blank field keeps the existing key.
IMPROVED: Email/SMS admin placeholders and Pro communication redirects use effective license state (not only the raw option), matching Pro behavior for licensed co-installations.
7.3.10
Fix: When Wedding Party RSVP Pro is active with a valid license, the free plugin no longer runs its classic RSVP POST handler on init with the wrong nonce, so guests submitting the public RSVP form no longer see “Security check failed.” (Pro owns the shortcode and nonce in that configuration.)
Compatibility: Confirmed “Tested up to” WordPress 6.9.x for this release.
7.3.9
Maintenance: Coordinated release with Wedding Party RSVP Pro; version and metadata alignment for the directory.
7.3.8
NEW: Suggested privacy policy text in Settings → Privacy (via WordPress privacy policy guide) describing stored guest data, export, and erase behavior.
NEW: Personal data eraser (Erase Personal Data) for guest rows matched by email; dashboard stats cache refreshes after a successful erase.
IMPROVED: Readme FAQ for data storage and export/erase; directory tag event added.
7.3.7
NEW: Optional block pattern to insert the RSVP shortcode from the block inserter.
NEW: Plugins screen link to Pro; dismissible post-activation setup checklist; optional dashboard widget for RSVP counts (filterable).
NEW: Optional milestone notice after the first guest RSVP (dismissible).
NEW: CSV export can match the current guest list search and filters; “Copy RSVP link” for Party ID on the guest list; optional custom message when the RSVP deadline has passed; optional grouped-by-party view; optional privacy exporter for guest data; optional one-time sample guest seed for empty sites.
IMPROVED: Works alongside Wedding Party RSVP Pro with both plugins active (merged admin menu when licensed; Pro owns the public shortcode when the license is active).
7.3.6
NEW: Optional frontend RSVP flow using the WordPress Interactivity API (6.5+): data-wp-interactive, data-wp-context, data-wp-on--submit, and live feedback via data-wp-text (no full page reload when the interactivity module loads). Classic POST submission remains for older WordPress or when script modules are unavailable.
7.3.5
Maintenance: Release version bump for coordinated directory update (aligns with Pro licensing documentation release).
7.3.4
Hardening: Addressed WordPress.org checker warnings around nested guest POST handling and custom-table database operations.
Maintenance: Updated tested-up-to metadata formatting for directory compliance.
7.3.3
Maintenance: Release version bump and metadata normalization for directory checks.
Compatibility: Updated 'Tested up to' formatting to WordPress.org-compliant major.minor (6.9).
Hardening: Improved frontend guest POST handling and clarified custom-table DB operations for Plugin Check compliance.
7.3.2
Compatibility: Tested up to WordPress 6.9.
7.3.1
New: Review request notice after 7 days (Enjoying Wedding Party RSVP?) with Yes / No (Support) / Dismiss. AJAX dismissal, nonce-secured, shown only on plugin admin pages.
7.3
Security Update: Implemented late escaping for inline styles and rigorous variable escaping for output.
Cleanup: Removed unused external service references to comply with directory guidelines.
7.2
Security: Updated prefixes, nonce sanitization, and SQL preparation.
Architecture: Moved form processing to init hook for safer redirects.
7.1
Security Update: Fixed escaping and sanitization issues.
Mobile Responsiveness: Updated Admin Dashboard with "Card View".
Performance: Implemented Object Caching.
7.0
Major update with new UI.
1.0
Initial Release.