WordPress Plugin
Profile Configuration
Choose which profile fields to show, arrange them via drag-and-drop, and pick a render mode.
The Profile module renders an editable profile form for signed-in visitors. This article covers the configuration under Unidy → Profile.
1. Field selection
Each visitor sees a subset of the available profile fields. Under Profile fields (standalone) and Profile fields (overlay), drag fields between two pools:
- Selected (draggable) — fields rendered in the profile form, in the order shown. Drag to reorder.
- Available (click-to-add) — fields not currently shown. Click to add to Selected.
Standard fields include salutation, first name, last name, email, date of birth, phone number, company name, address (line 1 and 2, postal code, city, country code), and preferred language.
Custom attributes defined on the Unidy instance (custom_attributes.*) appear here too and can be enabled per site.
2. Standalone vs overlay
The two field-selection lists are independent because the two render surfaces have different UX needs:
- Standalone — the
[unidy_profile]shortcode dropped into a dedicated page. Usually shows all fields.
- Overlay — a right-side panel or modal opened from a header link. Usually a shorter, top-priority subset.
If you don't need the overlay mode, set the render mode to inline and only maintain the standalone field list.
3. Render mode
Under Render mode you decide how the profile surface appears:
- Inline (default) — form rendered at the shortcode position.
- Modal — centered dialog opened from a link.
- Panel — right-side drawer opened from a link.
Modal and panel modes use Trigger URL patterns to define which links (typically /profil, /mein-profil) open the overlay.
4. Header text
Header text appears at the top of the overlay (modal or panel mode). Defaults to Mein Profil. Not shown in inline mode.
5. Avatar and autosave
- Show avatar — display a circular avatar at the top of the profile card. Uses the visitor's initials when no picture is uploaded.
- Autosave — automatically save field changes after the visitor stops typing. Toggle off for a classic save-button workflow.
- Autosave delay — milliseconds to wait after the last keystroke before saving. Default: 800.
Autosave uses the SDK's own debounced save — no extra plugin-side polling. Failed saves surface as inline error toasts via the Custom Error Messages system.
6. Container selector
Optional CSS selector that scopes the trigger-link interception. Leave empty to use the global default from the Auth module.