DFX Parish Retreat Letters

By David Marín Carreño (DaveFX)

0+ active installationsVersion 26.11.14.1

Manage personal messages in parish retreats: attendants, confidential messages, permissions, and GDPR compliance — all in one place.

Description

DFX Parish Retreat Letters lets your parish manage the full lifecycle of confidential personal messages for retreat attendants — from collecting letters through a public web form to printing them securely in the admin, while keeping every piece of content fully encrypted and every action fully audited.

How it works

  1. Create a retreat and register your attendants.
  2. Share each attendant’s unique, private URL with the people who want to write to them — family, friends, spiritual directors.
  3. Writers fill in the form on a clean public page: they can type a rich-text message, attach images or documents, and agree to a legal disclaimer. A simple arithmetic CAPTCHA protects against bots.
  4. Messages are stored encrypted in the database. Nobody can read them by browsing the admin — they are only revealed at print time.
  5. Authorised staff print the messages from the admin panel. Each print is logged with the user’s name, timestamp, and IP address.
  6. Messages are handed to attendants during or after the retreat.

Retreat management

  • Create retreats with name, location, start and end dates, and a custom welcome message shown on the submission form.
  • Set a legal disclaimer text and an acceptance checkbox label that writers must tick before they can submit.
  • Enable or disable optional Notes and Internal Notes fields per retreat (Notes are exportable; Internal Notes are not).
  • Set custom body CSS classes on the message-form page per retreat, so each retreat can use a different visual style.
  • Choose a custom header block and footer block (any WordPress block or template part) to brand the submission form page.
  • Delete a retreat together with all its attendants and messages in one action.

Attendant management

  • Add attendants individually or import them from a CSV file (supports merge mode to add emergency-contact data without overwriting existing records).
  • Each attendant stores: name, surnames, date of birth, and the following optional fields — notes, internal notes, emergency-contact details (name, surnames, relationship, email), inviting person, and incompatibilities.
  • Export attendants to CSV including their unique message URL, message count, and all standard fields.
  • Sort and filter the attendant list by name, message count, notes, or any other available column.
  • The attendant list shows at a glance how many messages each person has received and how many have not yet been printed.
  • Delete individual attendants, or remove all attendants from a retreat at once.

Confidential message submission (public form)

  • Each attendant has a unique, cryptographically secure URL (based on a random token). Anyone with the link can submit a message without logging in to WordPress.
  • The submission form provides a rich-text editor (with formatting, images, and copy-paste from Word or Google Docs).
  • Writers can attach images and documents (PDF, DOCX, and other common types). If a message has multiple non-image files, they are bundled into a ZIP for printing.
  • An optional legal disclaimer with a configurable acceptance checkbox can be required before submission.
  • A simple arithmetic CAPTCHA prevents automated submissions. Logged-in WordPress users skip the CAPTCHA.
  • The form URL includes the attendant’s initials as a suffix for easy identification when sharing links, without exposing the full name.
  • Rate limiting (20 requests per hour per IP) prevents abuse.
  • The form is multilingual: senders see it in their browser’s language, or choose one from a selector, among Spanish, Catalan, Basque, Galician, English, Portuguese, French, Italian and German. Changing the language does not reload the page, so nothing written is lost. It can be disabled per retreat.
  • The retreat texts (custom message and legal disclaimer) can have a version written for each language, or be translated automatically with DeepL (optional; the free plan, DeepL API Free, is enough; each translation is cached and only those texts are sent to DeepL).

Secure message access and printing

  • The admin interface never displays message content — there is no content-preview panel. This protects confidentiality if a screen is visible to others.
  • Authorised users open a message and click Print. The plugin decrypts the content on the fly, renders it in a print-ready format with the recipient’s name and the sender’s name, and sends it to the printer.
  • Each print action is recorded in a print log (user, timestamp, IP address). The log is visible from the attendant’s message list.
  • Multiple images in a single message are laid out so they do not split across pages.

Permission system

The plugin uses four access levels, each scoped to specific retreats:

Plugin Administrators (WordPress users with the manage_retreat_plugin capability, automatically granted to WordPress Administrators):

  • Create and delete retreats.
  • Manage all attendants and all messages across all retreats.
  • Grant or revoke permissions for any retreat.
  • Access Global Settings and Privacy & Compliance pages.

Retreat Managers (assigned per retreat):

  • Full control of their assigned retreat: edit retreat details, manage attendants, access all messages.
  • Invite and assign Message Managers to their retreat.
  • Cannot access other retreats or global settings.

Message Managers (assigned per retreat):

  • Read-only access to attendant names for context.
  • Can open and print confidential messages for their retreat.
  • Cannot edit attendants, retreat details, or permissions.
  • All print actions are logged.

Read Only (assigned per retreat):

  • Can see the retreat’s attendants, the custom fields open to message managers, the letter counts and the contact log.
  • Can get each attendant’s letters URL and invitation message to share them. An existing URL is never replaced; an attendant without one gets it generated.
  • Can never change anything else: no editing, withdrawing or deleting attendants, no contact log entries, no CSV import or export.
  • Cannot open, print or download letters, and cannot see the retreat settings or permissions.

User invitations

  • Invite any email address to become a Retreat Manager, Message Manager or Read Only user for a specific retreat directly from the retreat’s Access Management tab.
  • The invitee receives an email with a secure, time-limited token link.
  • If the email address already belongs to a WordPress user, they are granted the role immediately on acceptance. If not, a new WordPress account is created for them.
  • Pending invitations can be cancelled at any time. Expired invitations are cleaned up automatically.

Encryption and data security

  • All message content and file attachments are encrypted with AES-256-CBC and authenticated with HMAC-SHA256 before being written to the database or disk.
  • The encryption key is generated automatically on first activation and stored in the database. An admin notice prompts you to move it to wp-config.php by defining the constant DFXPRL_ENCRYPTION_KEY for better security. If the constant and the database key ever differ, the plugin detects the mismatch and offers a one-click resolution.
  • Every sensitive admin action (permission grants, revocations, invitation events) is written to a permission audit log.

GDPR and privacy compliance

  • Right to Erasure (GDPR Article 17): delete all personal data for a specific email address or attendant in one action.
  • Data Portability (GDPR Article 20): export all personal data associated with an email address as a structured file.
  • IP address anonymisation: sender IP addresses are automatically anonymised after a configurable retention period (default 30 days). A daily WordPress cron job handles the cleanup.
  • Configurable data retention: set how long messages and audit log entries are kept before automatic deletion.
  • Spanish privacy law (LOPD-GDD): the plugin was designed with Spanish data-protection requirements in mind, in addition to GDPR.
  • All settings are found under Retreats > Privacy & Compliance.

Global settings

Under Retreats > Global Settings you can configure:

  • Default header and footer blocks for the message submission form (overridable per retreat).
  • Default body CSS classes for the submission form page.
  • Encryption key management (including the option to remove a database-stored key in favour of the wp-config.php constant).
  • The DeepL API key for the automatic translation of the retreat texts (it can also be defined in wp-config.php as DFXPRL_DEEPL_API_KEY). A key of the free plan, DeepL API Free (up to 500,000 characters a month), is enough.

User manual

  • A user manual is built into the admin, with a version for each access level: plugin administrator, retreat manager, message manager and read only. Each user opens the one for their highest access level, and can switch to the others they hold; plugin administrators can read all four, and retreat managers also those of the access levels they give their team. Every page of the plugin has a Manual link at the top right, and the plugin row in the Plugins screen links to it too. The complete manual covers every screen: retreats, access management and invitations, attendants, CSV import and export, the letters form, printing and returning letters, withdrawals and emptying a retreat, global settings, privacy and security, and a step-by-step retreat calendar.
  • It is shown in the language of each user: English, Spanish, Catalan, Basque, Galician, Portuguese, French, Italian or German (other variants of those languages use the closest one, and any other language gets the English manual).

Internationalisation

  • The plugin ships with complete translations into Spanish, Catalan, Basque, Galician, Portuguese (Portugal), French, Italian and German. The Spanish one matches the translation approved on translate.wordpress.org; the others were machine-generated following the wordpress.org glossary of each language and are open to review on translate.wordpress.org.
  • When the site has a language pack from translate.wordpress.org, its translations take precedence, and the files bundled with the plugin fill in any texts the pack does not translate yet.
  • A .pot template file is included so you can add your own language.
  • The public submission form uses informal Spanish (“tú”) for a friendlier tone.

External services

This plugin can connect to the DeepL API to translate the texts configured for each retreat (custom message, legal disclaimer and its acceptance text) into the language of the visitor of the letters form. It is optional and only used when a DeepL API key is configured in the global settings (or in wp-config.php).

  • What is sent and when: the original text of those retreat fields and the target language, the first time a visitor views the letters form in a language for which the retreat has no version written (or when a manager presses “Translate automatically”). The result is cached, so each text is sent once per language and again only if it changes. Letters, names, email addresses and any other personal data are never sent.
  • Service provider: DeepL SE. Terms and conditions · Privacy policy.

Installation

  1. Upload the dfx-parish-retreat-letters folder to /wp-content/plugins/.
  2. Activate the plugin through the WordPress Plugins menu.
  3. The plugin automatically creates all required database tables on activation.
  4. Navigate to Retreats in the WordPress admin sidebar to get started.

Recommended post-installation steps

  1. Go to Retreats > Global Settings and review the default header, footer, and body-class settings for the submission form.
  2. Go to Retreats > Privacy & Compliance and configure data-retention periods to match your local legal requirements.
  3. For production sites, add the following line to wp-config.php to store the encryption key outside the database:
    define( ‘DFXPRL_ENCRYPTION_KEY’, ‘your-long-random-secret-here’ );
    Replace the placeholder with a long, cryptographically random string — for example one generated by wp_generate_password( 64, true, true ) in the WordPress shell, or by an equivalent secure random generator. The plugin will display a notice reminding you to do this if the key is still in the database.
  4. Verify that your site uses HTTPS. The submission form URLs contain sensitive tokens and must be served over a secure connection.

FAQ

Who can see the content of submitted messages?

Nobody can read message content by browsing the admin interface. Content is only revealed at print time, and only to users who have the Retreat Manager or Message Manager role for that retreat. Every print is logged.

How do writers submit messages without a WordPress account?

Each attendant has a unique, cryptographically secure URL. You share that URL (e.g. by email or WhatsApp) with the people who want to write to the attendant. They open the link in any browser, fill in the form, and submit — no login required.

What happens to the submission form URL after the retreat?

The URL remains valid until you delete the attendant or the retreat. If you want to stop accepting new messages, you can delete the attendant’s token by deleting and re-adding the attendant, or by deleting the retreat entirely.

Does the plugin use WordPress Custom Post Types or pages?

No. All data is stored in custom database tables (prefixed {prefix}dfxprl_*, e.g. wp_dfxprl_retreats). The public submission form is served directly by the plugin using a rewrite rule — you do not need to create any WordPress page.

Can I customise the look of the submission form?

Yes. You can set a custom WordPress block as the header and footer of the form page — globally under Retreats > Global Settings, or per retreat on the retreat edit screen. You can also add custom CSS body classes per retreat.

What file types can writers attach?

Common image formats (JPG, PNG, GIF, WebP), PDF, DOCX, and other document types supported by your server. The maximum file size is determined by your PHP and server configuration and is shown on the form. If a message contains multiple files and at least one is not an image, a ZIP archive is generated for printing.

Is the plugin GDPR-compliant?

Yes. It implements GDPR Articles 17 (Right to Erasure) and 20 (Data Portability), anonymises sender IP addresses after a configurable period, and supports configurable data-retention policies with automatic deletion. All settings are under Retreats > Privacy & Compliance.

Where is the encryption key stored?

By default it is generated automatically and stored in the WordPress database (wp_options). The plugin will display an admin notice recommending that you move it to wp-config.php by defining the DFXPRL_ENCRYPTION_KEY constant. The wp-config.php approach is safer because the key is then separate from the encrypted data.

Can I add translations for my language?

Yes. The best place is translate.wordpress.org, so the translation reaches every site as a language pack. A .pot translation template is also included in the languages/ directory.

Changelog

26.11.14.1

  • Change: on computers, the attendants list shows the name and the surnames in a single Name and Surnames column. Each click on its header sorts by name, by surnames, and then the same in reverse order. When not all the columns fit, the surnames go under the name, so the column takes less room.
  • Change: editing the name from the list shows two fields, the name on top and the surnames below it, saved together.
  • Change: attendants who share a name are sorted by their surnames, and the other way round.

26.11.14

  • Fix: on phones, the plugin credits took several lines over the bottom of the screen and hid the fields under them. They now take a single short line, and the page and the save buttons stay above it. On computers they go at the end of the page.
  • Fix: on phones, the attendant filters and the CSV import and export buttons did not show.
  • New: on phones, each attendant is a compact card, with the full name as its title, the total of letters as a big number next to it, every value next to its label, and the empty values left out.
  • New: on phones, the total of letters of the retreat shows as a big number above the attendants, with the physical letters and the letters still to print in the same box.
  • New: on computers, the attendants list scrolls inside its own pane, like a spreadsheet. Each column takes the width it needs (no more words cut in two), and the column headers, the name and the action buttons stay in sight.
  • New: the attendants list fits more columns on the screen: tighter cells, short dates (09/04/1975, with the long date on hover), the unprinted letters under the message count, and a dash for empty values instead of “N/A” or “No notes”.
  • New: the Edit, Messages, Invitation Message and Withdraw buttons of the attendants list carry an icon next to their name, so they are told apart at a glance.
  • Fix: the Copy Message URL button that appears after generating the URL was always in English.
  • New: the save buttons of the attendant page, the retreat page and the global settings stay at the bottom of the screen, so you can save without scrolling down.
  • Fix: the fields of the retreat custom fields, and those of the letters form, ran past the right edge on phones.

26.11.13

  • New: the user manual shows screenshots of each screen it explains, taken in the language of the manual.
  • Fix: in the attendants list, the Copy Message URL button stuck out of the Actions column, and long column headers ran into the next one.
  • Fix: in the contact log, the time an entry was written or changed, and the withdrawal date, showed the month in English.
  • Fix: the access level drop-down in Current Permissions had its arrow over the text.
  • Fix: a capital letter in the Spanish translation of the CSV import button.

26.11.12

  • New: retreat managers can change the access level of the users already assigned to their retreat, from a drop-down in Current Permissions on the retreat page, except their own and that of the other retreat managers. Plugin administrators can change anyone’s but their own. The change is logged like a grant and a revocation.
  • Fix: the Revoke button appeared next to your own permission, although revoking it was always refused.
  • Fix: revoking the same access level from a user a second time (after granting it again) failed with a database error, so the user kept it.

26.11.11

  • New: user manual in the admin, with a version for each access level (plugin administrator, retreat manager, message manager and read only), linked from the top of every page of the plugin and from the Plugins screen, in English, Spanish, Catalan, Basque, Galician, Portuguese, French, Italian and German, shown in each user’s language.
  • New: the attendants list Filters include the retreat’s custom fields each user can see: text by content, options lists and Yes/No fields with a drop-down, and numbers and dates with a From–To range.
  • Fix: the “File upload message” text was untranslated in every language except Spanish.
  • Fix: in the global settings, the translated notice for a DeepL key defined in wp-config.php named the old Google constant instead of DFXPRL_DEEPL_API_KEY.
  • Fix: two typos in the Spanish translation.

26.11.08.1

  • Change: Read Only users can now get each attendant’s letters URL (Copy Message URL, or Generate Message URL when the attendant has none yet) and their Invitation Message, from the attendants list and the attendant page, to share them with family and friends. They never replace an existing URL, so links already shared keep working.

26.11.08

  • New: Read Only access level for a retreat. Read-only users see the attendants list (active and withdrawn), the letter counts, the custom fields open to message managers and the contact log, and can open each attendant’s page with every field locked. They can never change anything, cannot open, print or download letters, cannot export or import attendants, and cannot see the retreat settings or its permissions. It can be granted to existing users or by invitation from the retreat’s Access Management box.
  • Security: the confidential messages page, deleting a letter from it, printing a letter and viewing its print log did not check that the user had access to that retreat’s messages, so a manager of one retreat could reach the letters of another. They now require being a manager or message manager of the letter’s retreat.
  • Change: in the retreats list, the retreat name opens its settings only for retreat managers; for everyone else it opens the attendants list.

26.11.06.3

  • Fix: saving on the Privacy & Compliance page (updating retention or running the cleanup) came back to a blank admin page. The action ran, but no result was shown. The page and its result notice are now displayed.
  • Fix: when adding or editing a retreat, an error (for example an end date earlier than the start date) came back to a blank admin page and lost the whole form. The error is now shown and the form keeps what was entered.

26.11.06.2

  • Fix: when adding or editing an attendant by hand, if a field failed validation the whole form came back empty and every value had to be typed again. The form now keeps what was entered (including the custom fields) and only the offending field needs fixing.

26.11.06.1

  • New: in the attendants list, the header row with the column names now stays fixed at the top while scrolling, so it is always clear which column is which.
  • Fix: after importing a CSV of attendants, the admin page came back blank with no feedback. The import ran, but its result (how many were added, updated or skipped) was never shown. The result notice is now displayed on the import page.

26.11.05

  • Change: the automatic translation of the per-retreat texts now uses DeepL instead of Google Cloud Translation, for noticeably better translations. Set a DeepL API key in the global settings (the free DeepL API plan covers 500,000 characters a month). Only the retreat texts are ever sent for translation, never letters or personal data.
  • New: translations now follow each language’s formality (informal in Spanish, Italian and German; formal in Portuguese and French).

26.11.04

  • New: multilingual letters form. Senders see the form in their browser’s language, or choose one from a selector, among Spanish, Catalan, Basque, Galician, English, Portuguese, French, Italian and German. The choice is remembered, and changing it replaces the texts without reloading the page, so nothing written is lost. Dates and error messages follow the chosen language. It is enabled by default and can be disabled per retreat (Multilingual Form).
  • New: the custom message, legal disclaimer and acceptance text of each retreat can have a version written for each language, with a Translate automatically button to draft it.
  • New: optional automatic translation of those retreat texts with Google Cloud Translation when a language has no version written. Each translation is cached and only redone when the original changes; only those texts are sent to Google, never letters or personal data. The API key goes in Global Settings or in wp-config.php (DFXPRL_GOOGLE_TRANSLATE_API_KEY).
  • New: complete translations into Catalan, Basque, Galician, Portuguese (Portugal), French, Italian and German. The Spanish translation now matches the one approved on translate.wordpress.org.
  • Improvement: the bundled translations fill in the texts that a translate.wordpress.org language pack does not translate yet, instead of showing them in English.
  • Fix: erasing personal data from Privacy & Compliance always failed; it now works, and the field shows the exact text to type.
  • Fix: the CSV import of attendants now always accepts the English column names as well as those of the panel language, as the help says.

26.10.31

  • Fix: wider left margin (about 15 mm) for the From/To header added to the first page of PDF letters, because some printers were cutting the labels.

26.10.27

  • New: Empty retreat button in the attendants page, available to retreat managers once the retreat has finished. It permanently deletes all the attendants of the retreat, active and withdrawn, with their letters, files, print history, contact log and custom field values, and keeps the retreat with its settings, custom fields and managers so it can be reused. It asks to type the retreat name and warns about letters that could still be returned by email.
  • Security: only plugin administrators can delete a retreat (the server now checks it, not only the interface).

26.10.26

  • New: optional sender email in the message form, typed twice to avoid typos. It is stored encrypted and only used to let the sender know about any issue with their letter.
  • New: letters of withdrawn attendants can be returned by email to their senders, one by one or all at once, with the letter attached (an HTML document for text letters, the original files otherwise). After the email is sent, the letter is deleted. The email subject and text can be configured per retreat, with placeholders, and are previewed before sending.
  • New: warning before permanently deleting a withdrawn attendant who still has letters that can be returned.
  • Change: personal data export and erasure also find letters by the sender’s email.
  • Fix: deleting a letter also deletes its print history.
  • Fix: the message form styles for wide screens were partly ignored (including the message received page) because of an unclosed CSS block.

26.10.15

  • Change: withdrawn attendants have a Messages button again, so their letters can be viewed and printed.
  • Fix: Spanish translation wording (“no válido” instead of “inválido”).

26.10.14

  • New: after sending a message, the sender is taken to a confirmation page that only shows that the message has been received, without any form. Previously the form was replaced by a short line of text, which made it look like the sender had been sent to the parish website.

26.10.12

  • New: attendants can be withdrawn (“dar de baja”). Withdrawn attendants leave the regular list and appear in a new Withdrawn attendants tab with their withdrawal date and user, messages, letters and contact log. They cannot be edited, and their public message form no longer accepts messages. The contact log can still be used.
  • New: withdrawn attendants can be reactivated or deleted permanently. Only withdrawn attendants can be deleted. Withdrawing, reactivating and deleting are restricted to retreat managers.
  • Change: “Delete all attendants” is replaced by Withdraw all attendants.
  • Change: the CSV export only includes active attendants, and the import skips rows matching withdrawn attendants. The attendant count in the retreats list only counts active attendants.
  • Fix: deleting an attendant now checks that the user manages the attendant’s retreat.

26.10.01

  • Change: the attendants list is narrower. The column drag handle only appears when hovering a header and no longer takes up space, and the Physical letters, Total letters and Contact log columns are now narrow.
  • Change: the Contact log column shows a notebook icon with the number of entries; the entries are shown in a window when clicking it.

26.09.26.2

  • New: Physical letters column in the attendants list. It can be sorted, reordered and edited inline by retreat managers and message managers; editing it also updates the row’s total letters and the retreat summary. The Total letters column now shows only the total.
  • Change: when a retreat has a saved column order, new columns (such as a newly created custom field) appear next to the column that precedes them by default instead of at the end.

26.09.26.1

  • New: inline editing in the attendants list. Click a cell to edit it; Enter saves and Escape cancels (Ctrl+Enter saves long texts). Retreat managers can edit name, surnames, date of birth, invited by, incompatibilities and notes; retreat and message managers can edit the physical letters from the Total letters column; custom fields follow their edit permission.
  • New: Contact log column in the attendants list, showing the number of entries and the latest one. It opens a window to read, add and edit entries without leaving the list.
  • New: retreat managers can reorder the columns of the attendants list by dragging their headers. The order is saved per retreat and applies to everyone; it can be restored to the default at any time.
  • Spanish translations updated.

26.09.26

  • New: physical letters received per attendant, editable by retreat managers and message managers.
  • New: Total letters column in the attendants list (messages received through the app plus physical letters), sortable.
  • New: contact log per attendant, where retreat and message managers record their contacts and conversations. Authors can edit their entries for 15 minutes and delete them at any time; retreat managers can edit or delete any entry and see the full change history, including deleted entries. Edited entries are marked as such.
  • New: custom attendant fields per retreat, defined in the retreat edit page: name, slug, type (text, long text, number, date, yes/no, options list), whether they are shown and sortable in the list, who can view and edit them, and whether they are imported from / exported to CSV. They can be used as [slug] placeholders in the message request template.
  • Change: message managers can now open the attendant page in a restricted mode, where they can only update physical letters, the custom fields they are allowed to edit and the contact log.
  • Change: CSV import and export buttons are hidden for message managers.
  • Security: the notice showing the database-stored encryption key is now only displayed to site administrators.
  • Security: saving a retreat, adding or editing an attendant and importing attendants now check the user’s permissions on the server.
  • Spanish translations updated.

26.09.25

  • Maintenance: fixed infrastructure tests that overwrote the WordPress table prefix.

26.09.24

  • Change: message managers can now use the Invitation Message, Generate Message URL and Copy Message URL buttons in the attendants list, not only retreat managers.
  • Security: generating a message URL now checks that the current user has message permissions on the attendant’s retreat.

26.09.21

  • Fix: importing an attendants CSV no longer fails on rows whose date of birth is written with a single-digit day or month (e.g. 19/6/1946). Such dates are now parsed correctly while genuinely invalid dates are still rejected.

26.05.20

  • Change: Add PDF Header is now enabled by default on new installations. PDF header generation runs entirely in the recipient’s browser, so there is no server memory cost. Existing sites keep their saved preference.

26.05.19.1

  • Change: when Add PDF Header is enabled, the From/To header is now generated in the recipient’s browser using pdf-lib instead of server-side TCPDF/FPDI. This removes the server memory cost entirely.
  • Fix: when printing a multi-page PDF letter, all pages are now sent to the printer (previously only the first page printed, regardless of whether the header was enabled).
  • Fix: the print tab now closes reliably after the print dialog is dismissed.

26.05.19

  • New: the PDF From/To header page added when printing single-PDF letters is now an opt-in setting in Global Settings → Add PDF Header, and is disabled by default. The previous behaviour relied on FPDI/TCPDF, which is memory-intensive and could fail to print on shared hosts. When disabled, PDF letters are served via a lightweight auto-print page.

26.05.18.1

  • Fix: prevent third-party widgets (notably Google reCAPTCHA badges) from appearing in the letter print preview on sites with security/anti-spam plugins active. The print page no longer fires the global wp_enqueue_scripts action and only prints its own stylesheet and script.

26.05.18

  • New: the “Print Status” cell for a message now refreshes in place right after printing, so the print count and first-print date update without reloading the page.
  • New: Internet Explorer is now explicitly unsupported. The print view no longer decrypts or sends letter content to IE clients (a clean “browser not supported” page is shown instead), and a warning notice appears across all plugin admin screens when an IE browser is detected.

26.05.12

  • New: when printing a single PDF attachment, a From/To header is now added so the recipient knows who sent it. Three fallback methods are used depending on what is available on the server (TCPDF+FPDI scale-down, external pdfunite/Ghostscript merge, or HTML header-only page).
  • New: expanded audit log to record retreat, attendant and letter operations (added, edited, removed, printed). Entries only contain IDs and anonymized initials — no personal data.
  • New: plugin icon and logo assets.

26.04.28

  • Fix: raised rate limits from 10/20 per hour to 30/hour for both form access and message submission. The form access limit was lower than the submission limit, causing users to be locked out of the form before reaching the submission limit.

26.04.10

  • Improvement: all admin tables are now responsive. On narrow screens and mobile, tables are displayed as card lists with labeled fields, and the permissions sidebar moves below the main content.
  • Improvement: attendants and messages lists now have a mobile-friendly “Sort by” dropdown for sorting on narrow screens.
  • Improvement: messages list columns (From, Type, Submitted, Print Status) are now sortable on desktop via clickable table headers.
  • Improvement: messages can now be sorted by print status (unprinted first, then ascending by print count).

26.03.24

  • Improvement: added detailed translator comments for JSON-encoded CSV column header mappings used in attendant import, with format instructions and Spanish examples.
  • Fix: the “Remove Database Key and Use wp-config.php Key” button now works. Script was previously never output because it was registered during the admin_notices hook, which fires after wp_print_scripts. Now uses admin_enqueue_scripts with a proper inline-only script handle and wp_localize_script.
  • Fix: the remove-database-key AJAX handler now also accepts the legacy DFX_PARISH_RETREAT_LETTERS_ENCRYPTION_KEY constant, matching the backward-compatibility logic of the rest of the encryption layer.
  • Fix: tab buttons in the Access Management section are now visually connected to their content panel.

26.03.23.1

  • Fix: a missing bump in the database version caused the databases not to update with new needed fields. Now fixed.

26.03.23

  • Fix: body_classes field now stores only a list of CSS class names instead of arbitrary CSS, with sanitization enforcing valid class-name characters only.

26.03.22

  • Fix: solved JS not loading on the retreat edit page, which prevented the access management feature (user search, grant/revoke permissions, invitations) from working.
  • Fix: corrected nonce mismatch that caused all Access Management AJAX calls to fail the security check.
  • Fix: normalized all internal identifiers from dfx-prl/dfx_prl to dfxprl for consistency with WordPress plugin repo policy.
  • Fix: removed dead code (render_permission_management_section method that was never called).
  • Fix: corrected CSS class mismatches between PHP templates and JavaScript event listeners in the Access Management section.
  • Fix: admin styles now load correctly on all plugin pages, including the add-retreat and privacy pages.
  • Fix: tab buttons in the Access Management section are now visually connected to their content panel.
  • Fix: the “Remove Database Key and Use wp-config.php Key” button now works. Script was never output because it was registered via wp_add_inline_script during the admin_notices hook, which fires after wp_print_scripts. Fixed by hooking to admin_enqueue_scripts with a proper inline-only script handle and wp_localize_script for the nonce.
  • Fix: the remove-database-key AJAX handler now also accepts the legacy DFX_PARISH_RETREAT_LETTERS_ENCRYPTION_KEY constant, matching the same backward-compatibility logic as the rest of the encryption layer.

26.03.21

  • Feature: added the extra class ‘dfxprl-message-form’ to the body tag of the message form screen.

  • Feature: retreats now have a field to set extra classes to the body tag of the message form screen, allowing
    per-retreat customizations.

  • Change: Removed CSS customizations from the plugin, as they are not allowed in WordPress plugins repo.

  • Fix: solved a few JS errors due to renaming several classes and variables.

25.12.10

  • Fix: Now always using enqueue functions to add JS or CSS to the different pages.
  • Fix: Fixed problem affecting CAPTCHA validation when logged in.
  • Fix: Replaced the plugin prefix from dfx-prl to dfxprl to be accepted in WordPress.org repository.
  • Fix: Added a few extra parameter validations

25.12.09

  • Feature: Marked compatibility with WordPress 6.9
  • Fix: Fixing some warnings by Plugin Check

25.12.05

  • Feature: added feature to delete encryption key from the database if there’s a key mismatch between the database and
    the config file.

  • Feature: added feature to remove all the attendants and their messages from a retreat.

25.11.28

  • Fix: if the server wrongly determined that the maximum file size was 0, all file uploads were disallowed.

25.11.27

  • Fix: accepting “0” as a valid answer for security question calculations.

25.11.26

  • Fix: adding URL suffix in the invitation message

25.11.24

  • Feature: add the attendant name in the message placeholder to avoid mistakes when identifying the attentant

25.11.23

  • Fix: to keep confidentiality, the suffix in URLs will now have the initials, not the full name and surnames

25.11.21

  • Feature: Adding attendant name and surnames as URL suffix when copying it from the attendant list

25.11.20

  • Feature: Added global per-retreat message counter.

25.10.30

  • Fix: sorting indicator in messages count column is now fixed
  • Feature: Allow sorting by the notes and internal_notes fields (if they exist)

25.10.29

  • Feature: Adding new internal notes field, not exportable nor importable.
  • Feature: Adding sorting options and filters to the attendant list
  • Feature: Adding message templates to be sent to emergency contacts in order to request letters

25.10.23

  • Feature: Adding three new optional fields for attendants: emergency-contact relationship, inviting-person and incompatibilities.

25.10.21

  • Feature: Display number of non-printed messages in the attendant list
  • Feature: When printing a message, print the recipientname before the sender name
  • Feature: Adding Message URL column when exporting to CSV
  • Fix: When a message has more than one image, fix the first image size so it fits in the first page
  • Fix: If an image or file cannot be uploaded, return an error instead of accepting the partial message with missing files.
  • Feature: Show actual server limits.
  • Change: Corrected CSS and JS prefix from “dfx” to “dfx-prl” or “dfx_prl”. CSS customizations should be adapted

25.10.15

  • Feature: New notes field for retreat attendants, optional. The field can be enabled or disabled per retreat.
  • Feature: The Emergency Contact Surname field is now optional.

25.10.8

  • Feature: Add place holder in the message form Captcha

25.9.30

  • Feature: improved error messages on AJAX calls.
  • Fix: solved problem with messages when pasted from Microsoft Office, and some style information wrongly got into
    the message body.

25.9.28

  • Fix: increased the allowed rate limit to 20 requests per hour, as 3 was too low for real use cases.

25.9.26

  • Fix: messages with multiple images are now printed correctly, without splitting images in two pages.
  • Fix: if a message have multiple attached files, and any of them is not an image, a ZIP file will be generated now.

25.9.24

  • Fix: now correctly generating error 404 when accessing messages form page with wrong token
  • Fix: solved error that prevented the removal of retreats
  • Fix: solved bug with custom headers and footers

25.9.18

  • Fix: Expanding size of mime_type field so DOCX files can be uploaded

25.9.16

  • Fix: Correcting several security issues to include plugin in WordPress.org repository

25.9.12

  • Feature: Added support for custom header, footer, and CSS in letters form page, globally and per-retreat.
  • Feature: Added support to grant global Retreat Manager permissions to specific users.
  • Feature: New emergency contact email field for attendants.
  • Fix: Retreat managers can now edit retreats they manage.
  • Fix: Correcting translation loading issue in old WP versions

25.9.11

  • Fix: Fixing several warnings from WordPress.org
  • Fix: Captcha won’t show calculations with negative numbers

25.9.7

  • Feature: disable submit button if legal disclaimer has not been accepted

25.9.5

  • Feature: added new legal disclaimer fields in letters form
  • Feature: now including sender’s name when printing a letter

25.7.27

  • Fix: Correcting formatting in outgoing mail messages
  • Fix: Adding missing translations
  • Fix: Removed foreign keys from old DB setups

25.7.23

  • Fix: WordPress coding standards violations- security and best practices improvements
  • Fix: Image paste processing in public message submission frontend
  • Fix: Skip rate limits for logged-in WordPress users
  • Fix: rate limiting for unsuccessful message submissions
  • Fix: Change Spanish translations from formal to informal language in public message frontend
  • Fix: admin notices auto-hiding issue by removing automatic fadeOut
  • Feature: Implement CSV import merge functionality for attendant emergency contact data
  • Fix: CSV export pagination issue – handle per_page=-1 correctly
  • Fix: redirect issue by handling form submissions on admin_init hook
  • Fix: attendant creation error handling to prevent header conflicts

25.7.22

  • Fix: solved error in database creation and upgrade processes

25.7.21 (Foundation Release)

Major Features

  • Complete three-tier authorization system
  • Secure confidential message system using AES-256 encryption
  • Advanced attendant management with bulk operations
  • User invitation system with secure token authentication

Security & Privacy Enhancements

  • Full GDPR compliance with automated data retention policies
  • Enhanced encryption for personal information and secure file storage
  • Print-only message access with comprehensive audit trails
  • Forensic-level audit logging
  • IP address anonymization
  • Foundation-level security implementation with modern PHP practices

Architecture & Development

  • Core plugin architecture using OOP and singleton patterns
  • Database schema optimization and integrated migration system
  • Full compliance with WordPress coding standards

Features & Improvements

  • Retreat-attendant association management
  • CSV import/export with data validation
  • Basic retreat and attendant management
  • Responsive admin interface with modern UX/UI

Internationalization

– Complete i18n support, including Spanish translations

DFX Parish Retreat Letters – Enterprise-grade retreat management for the modern parish.