#108653Introduction of database storage for forms
Description
*Problem / Motivation*
Currently, form definitions can only be stored in the file system (FAL or extension paths). This creates limitations for new features like workspaces or translations.
Requirements
_Functional:_
- Form definitions can be stored in the database table `form_definition`
- Database storage is only available when `allowedPages` is configured
- Editors can choose between storage options in the Form Manager
- Existing file system-based forms remain fully functional
Technical:
- Implementation of a `DatabaseStorageAdapter` following the Chain of Responsibility pattern
- Implementation of the `StorageAdapterInterface`
- New configuration option `allowedPages` in the PersistenceManager
- Automatic storage adapter selection based on persistence identifier
- Backend permissions for configured pages are enforced
Configuration
persistenceManager:
allowedPages:
- 1
- 23Reviews 6
- 14.3 94189[TASK] Clarify what the storage tests actually verify
- main 94182[TASK] Clarify what the storage tests actually verify
- main 93616[TASK] Add test for database-stored form rendering in frontend
- main 93596[BUGFIX] Render database forms in frontend without BE user requirement
- main 93335[BUGFIX] Perform access check when reading forms from database storage
- main 92241[FEATURE] Introduce database storage for form extension
Related issues 5
- Feature #109191FormPersistenceManager::listForms should work only on database data
- Bug #109528EXT:form > Database storage forms > Access denied: You do not have permission to access forms on page "0".
- Task #109557Functional tests for DatabaseStorage
- Task #109898Clarify what the storage tests actually verify
- Bug #110239Select/Radio/Checkbox option order in DB-stored forms reverts after reload on MySQL (JSON object key order not preserved)