AndreaDesign Wedding RSVP Manager

Description

Add an RSVP form to a page with [wedding_rsvp]. Guests can accept or decline an invitation. The plugin stores responses locally, notifies the organiser by email and sends a confirmation to the guest.

Quick start

1. Install and activate the plugin, then open Settings > AndreaDesign Wedding RSVP. The “Getting started” panel there shows what is still missing.
2. Create a page (for example “RSVP”) and add the shortcode [wedding_rsvp]. In the block editor use a Shortcode block. The form appears only on pages that contain the shortcode.
3. Create a thank-you page before you share the form. Click “Create the thank-you page for me” in the panel, or select one of your own pages in the settings. If no thank-you page exists, guests stay on the form page and see a short thank-you message, so they never reach an error page.
4. Select your privacy policy page under Settings > Privacy and set the organiser email in the plugin settings.
5. Send one test reply for “Yes” and one for “No”, check the guest list under Tools > AndreaDesign Wedding RSVP, then delete the test guests.
6. Optional: connect Aurea Pro to receive every reply in your wedding management account. See “External service: Aurea Pro” below.

Features

• Attendance, accompanying adult and child names, arrival/departure dates, accommodation, meals, dietary requirements, transport and notes.
• Admin guest list, CSV export, individual deletion and database reset.
• Server-side validation, nonce checks and a short-lived duplicate-submission limit.
• WordPress personal data export and erasure integration.
• Translatable PHP and JavaScript interface.
• Multiple independent forms on a page.
• Optional Aurea Pro synchronisation. Local RSVP functions work without a service account.

Usage

Manage responses under Tools > AndreaDesign Wedding RSVP and configure notifications/integration under Settings > AndreaDesign Wedding RSVP.

When replacing an earlier installation with the renamed package, back up first and deactivate the old plugin; do not delete it, because uninstall deletes its data. Install and activate this package with the old plugin inactive. Do not activate both copies simultaneously. The shortcode, database tables and stored options remain unchanged.

Add [wedding_rsvp] to a page. Configure the organiser email under Settings > AndreaDesign Wedding RSVP. The form requires JavaScript; exclude the form page from long-lived full-page caches so the security nonce does not expire.

Create a published privacy policy and select it under WordPress Settings > Privacy. The policy link uses that selected page, with /privacy-policy/ as a fallback. Adapt the suggested privacy text to your event before collecting data. A reusable Italian customer template and setup notes are included in PRIVACY-POLICY-IT.txt. Complete its placeholders and omit inapplicable sections; it covers RSVP processing rather than the plugin seller’s checkout or support activities.

After a reply, guests are sent to the thank-you page selected in Settings > AndreaDesign Wedding RSVP. Installations that already have a published page with the slug thank-you keep using it. When no thank-you page exists, guests return to the form page and see a short thank-you message instead of an error page. Accommodation options are the five event locations supplied with this plugin. Each response allows 1–50 adults and 0–50 children; adult names are required. A response for the same email is limited to once per five minutes. This basic limit and honeypot do not replace a site spam protection system, and concurrent requests are not guaranteed to be deduplicated.

Multisite: activate separately on each site; network activation is not supported. Settings and responses belong to each site. Deleting the plugin cleans its data across the network.

External service: Aurea Pro

Aurea Pro is an optional wedding management service at https://aureapro.app. A service account, an API key and the ID of one of your events are required; any applicable service charges and terms are determined by its provider. The plugin’s local features do not require this service.

No service request is sent by default. To enable it, configure Settings > AndreaDesign Wedding RSVP and explicitly select Enable Aurea Pro. After upgrading from earlier versions, authorisation must be selected again. Credentials alone, including wp-config.php constants, do not enable transmission.

After each successfully saved response, the plugin sends one HTTPS POST request to https://aureapro.app/api/wordpress/rsvp with these JSON fields: event_id (the event you configured), name, email (only when provided), pax (number of guests, 1 for a decline), rsvp_status (“Confermato” for acceptances, “Rifiutato” for declines), notes and external_id (the number of the local record, so a guest sent twice is updated, not duplicated). The notes field is one text assembled from arrival and departure dates, accommodation, welcome dinner, wedding dinner and pool party answers, transportation, dietary requirements and the guest’s message. The API key is sent in the X-API-Key header. Accompanying guest names and separate adult/child counts remain local and in emails/CSV exports; they are not sent to Aurea Pro. The address is fixed in the plugin and redirects are disabled.

The administrator’s Bulk Sync button sends the same fields for existing response records, including declines, one request per guest and up to 80 guests per click, because the service limits requests per minute. When more guests are waiting, wait one minute and click again: the plugin continues from the next guest. Repeating a sync updates guests already in Aurea Pro. No requests occur on activation or while authorisation is disabled.

Optional configuration constants in wp-config.php:

• WEDDING_SAAS_KEY: API key (starts with wp_).
• WEDDING_SAAS_EVENT_ID: the Aurea Pro event ID.

Constants override the corresponding saved values. The authorisation checkbox is still required. Synchronisation failures do not discard a saved response; there is no automatic retry queue. Use Bulk Sync to send records that failed.

Service links:

• Website: https://aureapro.app
• Terms: https://aureapro.app/terms
• Privacy: https://aureapro.app/privacy

Review the actual service policies before enabling transmission. The site organiser is responsible for disclosing recipients and handling data requests with the provider.

Privacy and retention

The plugin stores guest names (including accompanying adult and child names), email, counts, dates, accommodation and meal choices, dietary requirements, transport, notes, attendance and submission time in a table named {database prefix}wedding_rsvp.

Notifications and confirmations contain response details and are sent using WordPress wp_mail. Your configured mail provider processes these messages. The organiser notification also contains aggregate response counts. RSVP form fields include an acknowledgement of the site’s privacy policy, checked on the server. That checkbox does not establish or guarantee legal compliance.

Responses have no automatic retention expiry. The organiser must choose and implement an appropriate retention period. Data can be removed from the guest list, reset or WordPress Tools > Erase Personal Data. WordPress Tools > Export Personal Data exports responses matching the requester’s email, including accompanying guest details contained in that response. Follow WordPress’s verified-request process and review any third-party personal data before releasing an export.

The duplicate-submission limit stores a keyed digest of the email for five minutes using WordPress transients; the plugin does not store IP addresses or add tracking cookies. Expired transients may remain in the database until WordPress cleanup runs. Personal data and API responses are not written to debug logs by this plugin.

Local erasure does not remove previously sent emails, backups, downloaded CSV files or records held by Aurea Pro. Handle those copies separately. Deactivation preserves records. Deleting the plugin permanently removes its tables, options and database-backed duplicate-limit transients; export any data you need before deletion. Persistent object-cache transients expire after their five-minute lifetime.