Memory Wiki

Dispatching Benjamin to investigate PMPro signup form fields.

Done. Benjamin dug through PMPro 3.7.4 on **testing.jaimisaunders.com** and found the complete form field architecture. Here's the breakdown: --- ## PMPro Signup Form Fields — Two Paths ### A. Native `[pmpro_checkout]` (pages/checkout.php) The standard checkout template renders these sections: | Section | Fields | |---------|--------| | **Pricing** | `pmpro_level` (hidden), `pmpro_discount_code` | | **Account** | `username`, `password`, `password2`, `bemail`, `bconfirmemail`, `fullname` (honeypot) | | **Billing Address** | `bfirstname`, `blastname`, `baddress1`, `baddress2`, `bcity`, `bstate`, `bzipcode`, `bcountry`, `bphone` | | **Payment** | `CardType`, `AccountNumber`, `ExpirationMonth`, `ExpirationYear`, `CVV` | ### B. `[pmpro_signup]` Shortcode (pmpro-signup-shortcode plugin — active, v1.2) Self-contained form that renders its own fields and submits to the standard checkout URL. Supports short/emailonly mode that auto-generates username + password from email. Fields: `level`, `username`, `password`, `password2`, `bemail`, `bconfirmemail`, `fullname` (honeypot). --- ## Where Custom Fields Can Be Added PMPro 3.4+ has a built-in **Custom Fields System** (`class-pmpro-field.php`, `class-pmpro-field-group.php`, `includes/fields.php`). Fields can be registered programmatically via: ```php pmpro_add_user_field('after_email', new PMPro_Field('my_field', 'text', [...label, required, profiles...])); ``` **Available hook positions for custom fields:** | Hook Name | Location | |-----------|----------| | `pmpro_checkout_after_username` | After username field | | `pmpro_checkout_after_password` | After password field | | `pmpro_checkout_after_email` | After email field | | `pmpro_checkout_boxes` | Cards between account info & billing | | `pmpro_checkout_after_billing_fields` | After billing address | | `pmpro_checkout_after_payment_information_fields` | After payment section | | `pmpro_checkout_before_submit_button` | Before submit button | | `pmpro_checkout_after_form` | After closing form tag | The pmpro_signup shortcode also fires its own hooks: `pmpro_signup_form_before_fields`, `pmpro_signup_form_before_submit`, `pmpro_signup_form_after_submit`, `pmpro_signup_form_after_form`. --- ## Also Notable - **PMPro pages not yet set up** on testing site — no `pmpro_pages` option exists yet - **`pmpro-signup-shortcode`** (v1.2) is active and auto-generates username/password when email-only mode is used, stores auto-generated passwords in session for confirmation - All the hook/filter names for validation — `pmpro_required_user_fields`, `pmpro_checkout_checks`, `pmpro_checkout_new_user_array`, etc. Where do you want to go from here? Want me to task Benjamin to add custom fields to the signup form on testing?

Let me check what's on that page.

Found it. The page **Profe Login** (ID 84) at `/profe-login/` uses the **pmpro-signup-block** (Gutenberg block from the `pmpro-signup-shortcode` plugin), not a text shortcode. Here's the full content: ```json <!-- wp:pmpro-signup-block/pmpro-signup-block { "level": "2", "redirect": "testing.jaimisaunders.com", "short": "true" } /--> ``` So the form is rendering the Free level (PMPro level ID 2) in **short/emailonly mode** — meaning it only shows the email field (auto-generates username + password server-side) plus the level hidden field + honeypot. Benjamin already mapped out the fields this shortcode renders in his earlier report: | Field | Shows? | Notes | |---|---|---| | `level` (hidden) | Yes — ID 2 (Free) | Hard-coded in block | | `username` | **Hidden** | Auto-generated from email | | `password` | **Hidden** | Auto-generated, stored in session | | `password2` | Hidden — skipped via `short` | | | `bemail` | **Shown** | Only visible field | | `bconfirmemail` | Hidden — skipped via `short` | | | `fullname` | Hidden (honeypot) | Anti-spam | What are you looking to do with it — add more fields to this form?

Got it. Username = email (already happening with short mode), and set display_name to match on signup. Dispatching Benjamin.

Let me verify the fix landed cleanly.

All good. Here's what Benjamin did: **The issue:** In `short` mode, the plugin's `pmpro_generateUsername()` extracts only the local part (before `@`) as the username — e.g. `test@example.com` becomes username `test`. WordPress defaults `display_name = username`, so users ended up with `test` as their display name, not the full email. **The fix:** Added a function `pmprosus_set_display_name_to_email()` that hooks into PMPro's `pmpro_checkout_new_user_array` filter. It explicitly sets `display_name = user_email` when the signup comes through the shortcode (detected via the `pmpro_signup_shortcode` hidden field that's already on the form). **File:** `wp-content/plugins/pmpro-signup-shortcode/pmpro-signup-shortcode.php` (lines 100-111) **Verified:** - PHP syntax: clean - Filter test: `display_name` correctly set to full email (`test@example.com`) Now when anyone signs up via `/profe-login/`, their display name = their full email, matching your ecosystem convention. Want me to task Benjamin to set up a test signup to confirm end-to-end?

Found it. `Stories` folder at `/var/www/nextcloud/data/profe/files/Stories/` with two files: ``` The Gentleman Thief 6 Permission.md (32 KB, Jun 1 03:12) The Gentleman Thief Youtube Video Descriptions.md (3.8 KB, Jun 1 03:16) ``` What do you need with them?

Powerful episode. Here's the vibe — noir crime thriller, cold calculation, the moment Martin says "Now we have permission." That's the thumbnail moment. --- ## Leonardo.ai Prompt — "Permission" Thumbnail ``` cinematic film still, two men in a high-rise loft at dawn, one younger (Ethan, late 20s, dark hair, tense posture) standing near a marble kitchen counter with cold coffee, the other older (Martin, 40s, sharp suit, sleeves rolled once, silver-gray hair, calm calculating expression) standing by a long table with an air-gapped tablet, floor-to-ceiling windows behind them showing a city skyline in gray morning light, city traffic below, cold blue-gray color palette, amber accent lighting from the loft, tension in the air, noir thriller atmosphere, shallow depth of field, anamorphic lens, sharp contrast between warm interior and cold city, cinematic lighting, hyperrealistic, 8k, shot on Arri Alexa LF --ar 16:9 --style cinematic ``` The key visual tension: Martin's controlled stillness vs Ethan's coiled anger, with the cold city below — the moment he realizes outrage isn't the tool, precision is. Want me to tweak the scene, mood, or composition?