TYPO3 Form Finisher问题：后台可选但无字段加载，前端报错

Hey there, let's break down this issue step by step. That error message—"The finisher preset identified by 'EmailPdf' could not be found, or the implementationClassName was not specified"—is pointing us to two core problems to fix, and we'll start with your YAML configurations since that's where most setup issues happen.

1. Verify Your BaseSetup.yaml Configuration #

This file is where you register the finisher preset and link it to your actual PHP implementation. Double-check these critical details:

• Make sure the EmailPdf preset exists under finishers.presets, with a valid implementationClassName that matches your finisher's namespace and class name. Example correct setup:

  Neos:
    Form:
      finishers:
        presets:
          EmailPdf:
            implementationClassName: 'YourVendor.YourExtension:Finishers\EmailPdfFinisher'
            label: 'Email with PDF Attachment'
            description: 'Sends an email including a generated PDF of the form submission'
  

  • Key checks:
    • The class namespace/path must exactly match the file location (e.g., if your class is in Classes/Finishers/EmailPdfFinisher.php, the class name should be YourVendor\YourExtension\Finishers\EmailPdfFinisher).
    • The preset ID (EmailPdf) is case-sensitive—keep this consistent across all config files.

2. Validate FormEditorSetup.yaml #

This file controls what finishers show up in the backend form editor. Ensure the EmailPdf preset is added to the finisher preset options:

Neos:
  Form:
    Builder:
      formElements:
        'Neos.Form.Builder:Finisher':
          properties:
            finisherPreset:
              options:
                presets:
                  EmailPdf: 'Email with PDF Attachment' # Match the label from BaseSetup

• A common mistake here is a typo in the preset ID—if it doesn't match exactly what you used in BaseSetup.yaml, the backend might let you select the finisher but fail to load its config fields.

3. Check FormEngineSetup.yaml for Config Fields #

This file defines the configuration fields that appear when you select the finisher in the backend. Make sure you've mapped the EmailPdf preset to its form fields:

Neos:
  Form:
    finishers:
      presets:
        EmailPdf:
          formElements:
            recipientAddress:
              type: string
              label: 'Recipient Email Address'
              defaultValue: ''
              validation:
                'Neos.Flow:NotEmpty': []
            pdfTemplatePath:
              type: string
              label: 'PDF Template Path'
              defaultValue: 'resource://YourVendor.YourExtension/Private/Templates/Form/PdfTemplate.html'

• Without this setup, even if the preset is registered, the backend won't know what fields to render for your finisher.

4. Fix Common Pitfalls #

• Clear the cache: After modifying any YAML configs, run ./flow cache:flush (or use the backend cache clearing tool). Flow caches configuration heavily, so old settings might still be loaded.
• Check class autoloading: Ensure your finisher class is in the correct directory (Classes/Finishers/) and follows PSR-4 naming conventions. Test if the class can be instantiated with:

  ./flow php -r "new YourVendor\YourExtension\Finishers\EmailPdfFinisher();"
  

  If you get a "class not found" error, your namespace or file path is wrong.
• Preset ID consistency: Everywhere you reference the finisher (BaseSetup, FormEditorSetup, FormEngineSetup), use the exact same ID (case included—EmailPdf vs emailpdf are different!).

5. Debug the Registered Presets #

To confirm if the EmailPdf preset is actually being registered, run this Flow command to list all active finisher presets:

./flow configuration:show Neos.Form finishers.presets

If EmailPdf doesn't appear in the output, your BaseSetup.yaml is either in the wrong location (it should be in Configuration/ at the root of your extension) or has syntax errors.

内容的提问来源于stack exchange，提问作者Michael Müller