TYPO3中PowerMail表单上传文件重命名问题求助

Got it, let's tackle this PowerMail file naming issue in your TYPO3 job application form. The problem where duplicate filenames get hidden suffixes in emails (but not in storage) is a common one, and you've already nailed the right directions with prefixes or showing the full stored filename. Here's how to implement both solutions properly:

1. Add Purpose-Based Prefixes to Uploaded Files #

This approach ensures files are immediately distinguishable by their purpose (resume vs. certificate) even before they hit storage, which avoids confusion entirely. We'll use PowerMail's hooks to intercept the upload and rename files based on their form field.

Step-by-Step Implementation: #

• Create a custom TYPO3 extension (if you don't have one already) to hold your hook logic.
• Add this hook class to your extension to handle file renaming:

<?php
namespace Vendor\YourExtension\Hooks\Powermail;

use In2code\Powermail\Domain\Model\File;
use TYPO3\CMS\Core\Resource\FileInterface;

class FileUploadPrefixer
{
    public function addPurposePrefix(File $file, FileInterface $originalResource): void
    {
        // Get the form field's marker (e.g., "resume" or "certificate" as you named them)
        $fieldMarker = $file->getField()->getMarker();
        
        // Assign prefix based on field type
        $prefix = match($fieldMarker) {
            'resume' => 'resume_',
            'certificate' => 'certificate_',
            default => ''
        };

        if (!empty($prefix)) {
            $newFileName = $prefix . $originalResource->getName();
            // Rename the actual stored file
            $originalResource->rename($newFileName);
            // Update PowerMail's file record to use the new name
            $file->setName($newFileName);
        }
    }
}

• Register the hook in your extension's ext_localconf.php:

$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['in2powermail']['Domain/Model/File']['manipulateFile'][] =
    \Vendor\YourExtension\Hooks\Powermail\FileUploadPrefixer::class . '->addPurposePrefix';

Now, when a candidate uploads xxx.pdf to the certificate field, it'll automatically become certificate_xxx.pdf—and this renamed version will show up in both storage and the form email, making it crystal clear for your gateway.

2. Display the Full Stored Filename (With TYPO3's Suffix) in Emails #

If you prefer to keep the original filename structure but want the email to show the exact suffix TYPO3 adds for duplicates, you can adjust how PowerMail renders filenames in emails.

Option 1: Modify the Mail Template #

• Locate your PowerMail email templates (default path: typo3conf/ext/powermail/Resources/Private/Templates/Mail/, or your custom template path if you've overridden it).
• In the template file (e.g., Html.html or Text.html), replace instances of {file.name} with {file.originalResource.name}. This pulls the actual stored filename (including TYPO3's duplicate suffix) instead of the user-uploaded original name.

Option 2: Use a Hook to Auto-Replace Filenames #

If you don't want to edit templates directly (to avoid overwrites during PowerMail updates), use a content manipulation hook:

<?php
namespace Vendor\YourExtension\Hooks\Powermail;

use In2code\Powermail\Domain\Model\Mail;

class MailFilenameFixer
{
    public function replaceWithStoredFilename(Mail $mail, string $content): string
    {
        foreach ($mail->getFiles() as $file) {
            $originalUploadName = $file->getName();
            $storedFilename = $file->getOriginalResource()->getName();
            // Swap the original name with the stored name in the email content
            $content = str_replace($originalUploadName, $storedFilename, $content);
        }
        return $content;
    }
}

• Register the hook in ext_localconf.php:

$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['in2powermail']['Domain/Model/Mail']['manipulateMailContent'][] =
    \Vendor\YourExtension\Hooks\Powermail\MailFilenameFixer::class . '->replaceWithStoredFilename';

Quick Tips #

• Test both solutions by uploading duplicate filenames to verify the email and storage match.
• If using custom templates, ensure TYPO3 is configured to use your template path via the extension manager or TypoScript.
• Keep your custom extension updated to align with TYPO3 and PowerMail version changes.

内容的提问来源于stack exchange，提问作者Larkis