Bug #84777
closedException because of non existing form yaml after saving ContentElement
0%
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.
Updated by Gerrit Code Review over 6 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56719
Updated by Ralf Zimmermann over 6 years ago
- Status changed from Under Review to Needs Feedback
- Assignee set to Stefan Froemken
Please abandoned this in favor of https://review.typo3.org/c/56028/
Updated by Gerrit Code Review over 6 years ago
- Status changed from Needs Feedback to Under Review
Patch set 37 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56028
Updated by Gerrit Code Review over 6 years ago
Patch set 38 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56028
Updated by Gerrit Code Review over 6 years ago
Patch set 39 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56028
Updated by Gerrit Code Review over 6 years ago
Patch set 40 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56028
Updated by Gerrit Code Review over 6 years ago
Patch set 41 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56028
Updated by Gerrit Code Review over 6 years ago
Patch set 42 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56028
Updated by Gerrit Code Review over 6 years ago
Patch set 43 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56028
Updated by Benni Mack over 6 years ago
- Has duplicate Bug #84859: Exceptions from Form Configuration files are not caught added
Updated by Gerrit Code Review over 6 years ago
Patch set 44 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56028
Updated by Björn Jacob over 6 years ago
- Sprint Focus changed from On Location Sprint to Remote Sprint
Updated by Patrick Gaumond over 6 years ago
- Category changed from Form Framework to Linkvalidator
Updated by Stefan Froemken over 6 years ago
"Changed to Linkvalidator" What? Why? It has nothing to to with LinkValidator.
Updated by Björn Jacob over 6 years ago
- Category changed from Linkvalidator to Form Framework
- Assignee deleted (
Stefan Froemken)
Why did you change the category? This belongs definitely to the form framework.
Updated by Björn Jacob about 6 years ago
- Status changed from Under Review to New
- Target version deleted (
next-patchlevel) - Sprint Focus deleted (
Remote Sprint)
Updated by Ralf Zimmermann over 5 years ago
- Status changed from New to Closed
This issue is already fixed with #84859 (https://review.typo3.org/#/c/Packages/TYPO3.CMS/+/56797/).