Issue Bug Rejected

#89666PersistenceManagerException with two extensions providing a form definition with the same name

Stephan Großberndt 11/13/19, 10:38 updated 11/22/19, 16:23

Description

Usecase:

  • One TYPO3 installation with multiple sites each with its own site extension.
  • Each site extension provides a contact form for the site
  • Path1 is EXT:extension/Resources/Private/Forms/Contact.form.yaml
  • Path2 is EXT:extension2/Resources/Private/Forms/Contact.form.yaml

On installing extension2 the references to the form definitions of extension are no longer valid as they are replaced by the ones of extension2.

The issue is apparently that the name of the yaml is the key for the form definition and the path / extension name is not taken into account.

How to reproduce:

  1. Download extensions.zip from this issue
  2. Install EXT:extension
  3. Add form content element referencing the form definition
  4. Install EXT:extension2
Now there are the following issues:
  • When editing the form content element only the form definition of the second extension is visible
  • When accessing the page containing the form content element in the frontend the following exception is shown:
#1484071985 TYPO3\CMS\Form\Mvc\Persistence\Exception\PersistenceManagerException

The file "EXT:extension/Resources/Private/Forms/Contact.form.yaml" could not be loaded. Please check your configuration option "persistenceManager.allowedExtensionPaths"

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.