README

Form Prefill for TYPO3 Frontend Users – A TYPO3 v13 extension that automatically fills in form fields for logged‑in frontend users (fe_users). Works out‑of‑the‑box with the native Form Framework (EXT:form) and any form that follows the tx_form_formframework[<formIdentifier>][<field>] naming scheme. Field mapping is fully configurable via FlexForm or config.yaml – no TypoScript required.

Features

• Prefills input and textarea fields on the client side via JavaScript.
• Secure PSR‑15 middleware that exposes only whitelisted fe_users fields as JSON (/prefill-user.json).
• Flexible one‑to‑one mapping between fe_users columns and form field keys
• Generic or UID-specific mapping definitions via config.yaml. UID-specific mapping can also be defined per content element (via FlexForm).
• Multiple forms per page supported.
• Implemented as a dedicated CType (formprefill) – ready for TYPO3 v14 (no list_type).
• Zero database changes and no modifications to existing forms.

Requirements

Installation

composer require oliverthiele/ot-formprefill

• Flush caches.

Configuration

Site Configuration (config.yaml)

otFormprefill:
  allowedFields:
    - name
    - email
    - company
    - telephone
  formMappings:
    contactForm:
      name: text-1
      company: text-2
      email: email-1
    contactForm-19022:
      name: text-1
      company: text-3     # Overrides generic mapping
      telephone: text-4   # Adds extra field only for this form UID

Mappings without UID act as default (by persistenceIdentifier). Mappings with UID (e.g. kontaktformular-19022) override or extend the generic mapping.

Extension Configuration (ext_conf_template.txt)

# cat=basic/enable; type=string; label=Allowed FE User fields
allowedFields = username,name,title,first_name,middle_name,last_name,company,address,zip,city,country,telephone,fax,email,www

Used only if no config.yaml is present. These fields are also hard-limited in the middleware.

TypoScript Setup

A full TypoScript setup is provided.

Option 1: Manual import

If you manage TypoScript manually (e.g. in your sitepackage), include it like this:

@import 'EXT:ot_formprefill/Configuration/TypoScript/setup.typoscript'

Option 2: TYPO3 v13 Set autoloading

If you're using TYPO3 v13's new "Site sets" system, you can add the dependency:

name: example/my-site-package
label: 'My Site Package'
dependencies:
  - oliverthiele/ot-formprefill

This automatically includes the setup file and assets.

Usage

1. Add the content element

Insert the Form Prefill content element (CType: formprefill) on the same page as your form.

2. Configure the FlexForm (optional)

If no mapping is configured, automatic mapping is used: fe_users.column → same form field name.

3. Output

After rendering, the ViewHelper will inject the mapping into the page as JavaScript:

<script>
window.formPrefillMappings = {
  "contactForm-42": {
    "email": "email",
    "fullName": "name"
  }
}
</script>

Middleware: /prefill-user.json

If a frontend user is logged in, this endpoint returns a filtered list of their fields:

{
  "name": "Max Mustermann",
  "email": "max@example.com"
}

The list is determined (in order):

1. site/config.yaml → otFormprefill.allowedFields
2. Extension setting (ext_conf_template.txt)
3. Fallback default

Developer Notes

• JavaScript is located in Resources/Public/JavaScript/FormPrefill.js, embedded via <f:asset.script defer="true">
• Middleware route: Configuration/RequestMiddlewares.php
• CType registration: TCA/Overrides/tt_content.php
• Icon: Configuration/Icons.php
• Mapping logic combines persistenceIdentifier and content element UID

Roadmap

• Unit tests for the middleware.

License

GPL‑2.0‑or‑later – see LICENSE

Sponsor

Initial development was sponsored by WWE Media GmbH Agency for digital products

Author

Oliver Thiele – oliver-thiele.de Mail: mail@oliver-thiele.de