Project

General

Profile

Actions

Bug #84777

closed

Exception because of non existing form yaml after saving ContentElement

Added by Stefan Froemken over 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2018-04-18
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:
Remote Sprint

Description

Hello Core-Team,

I just see that you have changed the default directory of stored form yaml files from 1:/user_upload/ to 1:/form_definitions/.
As all files in 1:/user_upload/ are read-only I have moved (not copied) all yaml files to the new location.
Of cause: All form plugins contains invalid entries now: "1:/user_upload/kontakt.yaml" (no read access).
Now I want to correct all of my form Plugins to use the new location and select: Kontaktformular (1:/form_definitions/kontakt.yaml)
When I save my plugin it will result in following error:

"Oops, an error occurred!
Object with identifier "1:/user_upload/kontakt.yaml" does not exist in storage
More information regarding this error might be available online."

The DataHandler loops through all fields before saving the record. While checking the field "categories" the RefereceIndexer was started which retrieves the "old" record from DB where we have, of cause, the old invalid yaml filename.
The problem seems to be in \TYPO3\CMS\Form\Hooks\SoftReferenceParserHook where you call retrieveFileOrFolderObject() without a try->catch construct.


Related issues 1 (0 open1 closed)

Has duplicate TYPO3 Core - Bug #84859: Exceptions from Form Configuration files are not caughtClosedBenni Mack2018-04-25

Actions
Actions

Also available in: Atom PDF