Bug #105566
closed
FormPersistenceManager::ensureValidPersistenceIdentifier called with empty $formSettings on saving
0%
Description
On saving a form in the backend editor, FormPersistenceManager::ensureValidPersistenceIdentifier is called with an empty $formSettings. Therefore checks for $this->isFileWithinAccessibleExtensionFolders() always fails.
The same method is also called on listing the forms in the backend module and on opening a form in the backend and in both cases $formSettings contains the data set in the yaml.
Therfore the form can be opened and edited but not saved.
Updated by Lina Wolf 11 days ago
In UniqueFieldHandler->setExistingFieldStateBeforeSave FormPersistenceManager::load is called with both empty formSettings and $typoScriptSettings wondering if this error is related to https://review.typo3.org/c/Packages/TYPO3.CMS/+/85669
Updated by Garvin Hicking 11 days ago
- Related to Task #104667: Do not use ext:form ConfigurationManager in FormPersistenceManager added
Updated by Lina Wolf 11 days ago
ยท Edited
- Status changed from New to Closed
Sorry, my bad, I was in a third party extension and didn't notice. See here: https://gitlab.com/lavitto/typo3-form-to-database/-/issues/118