WordPress.org
Get WordPress

Plugin Directory

Changeset 3489900


Ignore:
Timestamp:
03/24/2026 11:08:15 AM (4 days ago)
Author:
DaveFX
Message:

Update trunk via GitHub Actions

Location:
dfx-parish-retreat-letters/trunk
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • dfx-parish-retreat-letters/trunk/dfx-parish-retreat-letters.php

    r3489012 r3489900  
    44 * Plugin URI: https://github.com/davefx/dfx-parish-retreat-letters
    55 * Description: A WordPress plugin for managing parish retreat letters.
    6  * Version: 26.03.23.1
     6 * Version: 26.03.24
    77 * Author: David Marín Carreño
    88 * Author URI: https://davefx.com
    … …  
    2828 */
    2929if ( ! defined( 'DFXPRL_VERSION' ) ) {
    30     define( 'DFXPRL_VERSION', '26.03.23.1' );
     30    define( 'DFXPRL_VERSION', '26.03.24' );
    3131}
    3232

  • dfx-parish-retreat-letters/trunk/includes/class-admin.php

    r3488281 r3489900  
    20052005        // Define field mappings for English and Spanish
    20062006        $field_mappings = array(
    2007             /* translators: JSON string with list of allowed headers for field name. */
     2007            /* translators: JSON array of CSV column headers that map to the "name" field when importing attendants.
     2008               Translate each value to the equivalent column header in your language. Keep the JSON format: ["value1", "value2"].
     2009               Example for Spanish: ["nombre", "nombre de pila"] */
    20082010            'name' => json_decode( __('["name", "first name"]', 'dfx-parish-retreat-letters' ), true ),
    2009             /* translators: JSON string with list of allowed headers for field surname */
     2011            /* translators: JSON array of CSV column headers that map to the "surnames" field when importing attendants.
     2012               Translate each value to the equivalent column header in your language. Keep the JSON format: ["value1", "value2"].
     2013               Example for Spanish: ["apellido", "apellidos"] */
    20102014            'surnames' => json_decode( __('["surname", "surnames", "last name"]', 'dfx-parish-retreat-letters' ), true ),
    2011             /* translators: JSON string with list of allowed headers for field date_of_birth */
     2015            /* translators: JSON array of CSV column headers that map to the "date of birth" field when importing attendants.
     2016               Translate each value to the equivalent column header in your language. Keep the JSON format: ["value1", "value2"].
     2017               Example for Spanish: ["fecha de nacimiento", "nacimiento"] */
    20122018            'date_of_birth' => json_decode( __('["date of birth", "birth date", "dob", "birthdate"]', 'dfx-parish-retreat-letters' ), true ),
    2013             /* translators: JSON string with list of allowed headers for field emergency_contact_name */
     2019            /* translators: JSON array of CSV column headers that map to the "emergency contact name" field when importing attendants.
     2020               Translate each value to the equivalent column header in your language. Keep the JSON format: ["value1", "value2"].
     2021               Example for Spanish: ["nombre del contacto de emergencia", "nombre de emergencia", "nombre del contacto"] */
    20142022            'emergency_contact_name' => json_decode( __('["emergency contact name", "emergency name", "contact name","emergency contact first name", "emergency first name", "contact first name"]', 'dfx-parish-retreat-letters' ), true ),
    2015             /* translators: JSON string with list of allowed headers for field emergency_contact_surname */
     2023            /* translators: JSON array of CSV column headers that map to the "emergency contact surname" field when importing attendants.
     2024               Translate each value to the equivalent column header in your language. Keep the JSON format: ["value1", "value2"].
     2025               Example for Spanish: ["apellido del contacto de emergencia", "apellido de emergencia", "apellido del contacto"] */
    20162026            'emergency_contact_surname' => json_decode( __('["emergency contact surname", "emergency surname", "contact surname", "emergency contact last name", "emergency last name", "contact last name"]', 'dfx-parish-retreat-letters' ), true ),
    2017             /* translators: JSON string with list of allowed headers for field emergency_contact_phone */
     2027            /* translators: JSON array of CSV column headers that map to the "emergency contact phone" field when importing attendants.
     2028               Translate each value to the equivalent column header in your language. Keep the JSON format: ["value1", "value2"].
     2029               Example for Spanish: ["teléfono de emergencia", "teléfono del contacto", "teléfono"] */
    20182030            'emergency_contact_phone' => json_decode( __('["emergency contact phone", "emergency phone", "contact phone", "phone"]', 'dfx-parish-retreat-letters' ), true ),
    2019             /* translators: JSON string with list of allowed headers for field emergency_contact_email */
     2031            /* translators: JSON array of CSV column headers that map to the "emergency contact email" field when importing attendants.
     2032               Translate each value to the equivalent column header in your language. Keep the JSON format: ["value1", "value2"].
     2033               Example for Spanish: ["email de emergencia", "email del contacto", "email"] */
    20202034            'emergency_contact_email' => json_decode( __('["emergency contact email", "emergency email", "contact email", "email"]', 'dfx-parish-retreat-letters' ), true ),
    2021             /* translators: JSON string with list of allowed headers for field emergency_contact_relationship */
     2035            /* translators: JSON array of CSV column headers that map to the "emergency contact relationship" field when importing attendants.
     2036               Translate each value to the equivalent column header in your language. Keep the JSON format: ["value1", "value2"].
     2037               Example for Spanish: ["parentesco del contacto de emergencia", "parentesco", "relación"] */
    20222038            'emergency_contact_relationship' => json_decode( __('["emergency contact relationship", "relationship", "contact relationship"]', 'dfx-parish-retreat-letters' ), true ),
    2023             /* translators: JSON string with list of allowed headers for field invited_by */
     2039            /* translators: JSON array of CSV column headers that map to the "invited by" field when importing attendants.
     2040               Translate each value to the equivalent column header in your language. Keep the JSON format: ["value1", "value2"].
     2041               Example for Spanish: ["invitado por", "invitador"] */
    20242042            'invited_by' => json_decode( __('["invited by", "invited", "inviter"]', 'dfx-parish-retreat-letters' ), true ),
    2025             /* translators: JSON string with list of allowed headers for field incompatibilities */
     2043            /* translators: JSON array of CSV column headers that map to the "incompatibilities" field when importing attendants.
     2044               Translate each value to the equivalent column header in your language. Keep the JSON format: ["value1", "value2"].
     2045               Example for Spanish: ["incompatibilidades", "incompatibilidad", "no puede estar con"] */
    20262046            'incompatibilities' => json_decode( __('["incompatibilities", "incompatibility", "cannot be placed with"]', 'dfx-parish-retreat-letters' ), true ),
    2027             /* translators: JSON string with list of allowed headers for field notes */
     2047            /* translators: JSON array of CSV column headers that map to the "notes" field when importing attendants.
     2048               Translate each value to the equivalent column header in your language. Keep the JSON format: ["value1", "value2"].
     2049               Example for Spanish: ["notas", "nota", "comentarios", "comentario"] */
    20282050            'notes' => json_decode( __('["notes", "note", "comments", "comment"]', 'dfx-parish-retreat-letters' ), true ),
    20292051        );

  • dfx-parish-retreat-letters/trunk/languages/dfx-parish-retreat-letters.pot

    r3489012 r3489900  
    33msgid ""
    44msgstr ""
    5 "Project-Id-Version: DFX Parish Retreat Letters 26.03.23.1\n"
     5"Project-Id-Version: DFX Parish Retreat Letters 26.03.24\n"
    66"Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/dfx-parish-retreat-letters\n"
    77"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"

  • dfx-parish-retreat-letters/trunk/readme.txt

    r3489012 r3489900  
    44Requires at least: 5.0
    55Tested up to: 6.9
    6 Stable tag: 26.03.23.1
     6Stable tag: 26.03.24
    77Requires PHP: 7.4
    88License: GPLv3 or later
    … …  
    174174
    175175## Changelog
     176
     177### 26.03.24
     178
     179- Improvement: added detailed translator comments for JSON-encoded CSV column header mappings used in attendant import, with format instructions and Spanish examples.
     180- 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.
     181- 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.
     182- Fix: tab buttons in the Access Management section are now visually connected to their content panel.
    176183
    177184### 26.03.23.1
Note: See TracChangeset for help on using the changeset viewer.