Project

General

Profile

Actions

Feature #87816

open

Allow form configuration by rootline

Added by Cyril Janody over 5 years ago. Updated about 5 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2019-02-28
Due date:
% Done:

0%

Estimated time:
PHP Version:
7.1
Tags:
Complexity:
Sprint Focus:

Description

In the documentation, it's implied that we can define configurations via TypoScript templates, but that does not work.

See https://docs.typo3.org/typo3cms/extensions/form/8.7/Concepts/Configuration/Index.html#yaml-registration-for-the-backend -> option C


Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Bug #89460: Form module does not recognize form setups in other than 1st root-pageNew2019-10-20

Actions
Actions #1

Updated by Cyril Janody over 5 years ago

  • Description updated (diff)
Actions #2

Updated by Gerrit Code Review over 5 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/c/Packages/TYPO3.CMS/+/59816

Actions #3

Updated by Björn Jacob about 5 years ago

  • Subject changed from On multidomain instance, we should be able to make custom configuration by rootline as implied in the documentation (EXT:form) to Custom configuration by rootline
  • Description updated (diff)
  • Status changed from Under Review to New
Actions #4

Updated by Susanne Moog about 5 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from Custom configuration by rootline to Allow form configuration by rootline

As stated in the now abandoned patch: we need to rethink configuration handling in general concept wise as the concepts currently used differ from other TYPO3 concepts and some sort of streamlining would make sense.

Actions #5

Updated by Mathias Brodala over 4 years ago

  • Related to Epic #89731: Configuration streamlining added
Actions #6

Updated by Mathias Brodala over 4 years ago

  • Related to deleted (Epic #89731: Configuration streamlining)
Actions #7

Updated by Mathias Brodala over 3 years ago

  • Related to Bug #89460: Form module does not recognize form setups in other than 1st root-page added
Actions

Also available in: Atom PDF