Bug #84859

Task #84872: Refactor form configuration handling

Exceptions from Form Configuration files are not caught

Added by Benni Mack over 3 years ago. Updated almost 3 years ago.

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

100%

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

Related issues

Is duplicate of TYPO3 Core - Bug #84777: Exception because of non existing form yaml after saving ContentElementClosed2018-04-18

Actions
#1

Updated by Gerrit Code Review over 3 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/56797

#2

Updated by Benni Mack over 3 years ago

  • Is duplicate of Bug #84777: Exception because of non existing form yaml after saving ContentElement added
#3

Updated by Ralf Zimmermann over 3 years ago

Test:

  • create a form
  • create a content element "Form"
  • select your form
  • delete the form definition from the filesystem
  • save the content element again
#4

Updated by Ralf Zimmermann over 3 years ago

  • Parent task set to #84872
#5

Updated by Gerrit Code Review over 3 years ago

Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56816

#6

Updated by Benni Mack over 3 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
#7

Updated by Benni Mack almost 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF