Feature #94941
open
Exports via export tools sometimes contain previous exports
Added by Lina Wolf almost 3 years ago.
Updated 12 days ago.
Category:
Import/Export (T3D)
Sprint Focus:
On Location Sprint
Description
When I used the export tool to make an export the exported data was saved at public/fileadmin/user_upload/_temp_/importexport
On the next export all files from public/fileadmin/user_upload/_temp_ and their sys_file entries also got exported. Therefore the export contained the previous export as files and grew bigger and bigger...
Related issues
1 (1 open — 0 closed)
- Description updated (diff)
- Related to Story #92526: Concept for improved EXT:impexp added
In addition, previous exports are often deleted manually in the file system, and leave the sys_file record point to a non-existing file which can break the next export, e.g. when exporting the root of the page tree, with:
(1/1) #1551950301 TYPO3\CMS\Core\Resource\Exception\InvalidHashException
Hash has to be non-empty string.
The outdated sys_file records get even included into the export dump, if they are marked as missing. This is due to a missing match in
\TYPO3\CMS\Impexp\Export::exportAddRecord
=>
\TYPO3\CMS\Impexp\ImportExport::isRecordDisabled
which checks, if the record got disabled according to its TCA disabled column definition. In most tables this is column "hidden" but table "sys_file" does not have any disabled column configuration. Is this a bug? Check for the requirement to prevent inclusion of missing sys_file dataset into the export dump.
- Sprint Focus set to On Location Sprint
- Tracker changed from Feature to Bug
- PHP Version set to 8.3
- TYPO3 Version set to 12
I don't know if this is related.
I have got a fresch TYPO3 12.4.17 Version.
If I try to export from Root (ID:0) I also get the same Error
(1/1) #1551950301 TYPO3\CMS\Core\Resource\Exception\InvalidHashException
Hash has to be non-empty string.
- Tracker changed from Bug to Feature
- TYPO3 Version deleted (
12)
- PHP Version deleted (
8.3)
Also available in: Atom
PDF