Task #92346
Updated by Alexander Nitsche about 4 years ago
This task should improve the comfort of exporting and importing TYPO3 export presets along with the main export. h1. Status Quo In order to export TYPO3 database and files and the export presets one currently has to h2. A) TYPO3 Source Instance 1) configure export (EXT:impexp) 2) save the export configuration as preset (EXT:impexp) 3) export (EXT:impexp) 4) export the presets separately (phpmyadmin et al) and h2. B) TYPO3 Target Instance 5) import database and files in the new TYPO3 instance (EXT:impexp) 6) import the presets separately (phpmyadmin et al) h1. Quo Vadis This should be reduced to h2. A) TYPO3 Source Instance 1) configure export including database table "tx_impexp_presets" (EXT:impexp) 2) save the export configuration as preset (EXT:impexp) 3) export (EXT:impexp) and h2. B) TYPO3 Target Instance 4) import database and files including presets in the new TYPO3 instance (EXT:impexp) h1. Implementation The export configuration presets are missing a TCA and thus are not listed as exportable table in EXT:impexp. Adding the TCA will provide it there. Side effects are that the export presets become visible and maintainable by admins in the Web->List module (pid=0). The presets currently contain these fields: - title (preset title) - public (preset usable by non-priviledged users?) - user_uid (preset creator) - item_uid (export page root) - preset_data (full export configuration) I would set title and public as editable and the other fields as read only. h1. Question Are there any other (negative) side effects from adding a TCA for tx_impexp_presets?