Bug #68791
closed
t3d export with FAL images not possible
Added by d.ros no-lastname-given over 8 years ago.
Updated over 5 years ago.
Category:
Import/Export (T3D)
Description
- Summary
I export a single page with several content elements. No Problem.
As soon as a FAL image is within any element the export has not the file included and the import breaks with an error message.
TBH: This must be changed.
- error message
Fatal error: Uncaught exception 'TYPO3\CMS\Core\Resource\Exception\FileDoesNotExistException' with message 'No file found for given UID.'
in /var/www/web1/html/subdomains/foo4/TYPO3.CMS/typo3/sysext/core/Classes/Resource/ResourceFactory.php:347
Stack trace: #0 /var/www/web1/html/subdomains/foo4/TYPO3.CMS/typo3/sysext/core/Classes/Resource/FileReference.php(91): TYPO3\CMS\Core\Resource\ResourceFactory->getFileObject('3190')
#1 /var/www/web1/html/subdomains/foo4/TYPO3.CMS/typo3/sysext/core/Classes/Utility/GeneralUtility.php(4436): TYPO3\CMS\Core\Resource\FileReference->__construct(Array)
#2 /var/www/web1/html/subdomains/foo4/TYPO3.CMS/typo3/sysext/core/Classes/Utility/GeneralUtility.php(4415): TYPO3\CMS\Core\Utility\GeneralUtility::instantiateClass('TYPO3\\CMS\\Core\\...', Array)
#3 /var/www/web1/html/subdomains/foo4/TYPO3.CMS/typo3/sysext/core/Classes/Resource/ResourceFactory.php(586): TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('TYPO3\\CMS\\Core\\...', Array) #4 /var/www/web1/html/subdomains/foo4/TYPO3.CMS/t in /var/www/web1/html/subdomains/foo4/TYPO3.CMS/typo3/sysext/core/Classes/Resource/ResourceFactory.php on line 347
- Additional note
Originally I blamed flux for that.
https://github.com/FluidTYPO3/fluidcontent/issues/259
Files
- Status changed from New to Needs Feedback
TBH: your are invited to improve current behaviour ;)
Did you select sys_file and sys_file_reference to be included in your export? Do you see the files in the preview below the export settings?
Gr. Frans
I included every table.
BTW: Got some voices on slack that FAL export just does not work.
Hi d.ros,
does this issue still exists in latest (6.2.15) version? Maybe, did you test this issue already with one of the TYPO3 7.x versions?
- Status changed from Needs Feedback to New
I can confirm the issue also for CMS 7, but it is really hard to tell if the mistake is a wrong selection of tables to include, or if it's really an import issue.
Nevertheless, an exception must not hit the user.
- Sprint Focus set to On Location Sprint
Are your files located in a sys_file_storage which is not the default "/fileadmin" ? If this is the case: Does the directory of the sys_file_storage already exist on the target? Because a target directory for sys_file_storage will not get created automatically.
- Status changed from New to In Progress
- Assignee set to Bernhard Kraft
- % Done changed from 0 to 30
Hello Bernhard,
thanks for your effort. IIRC it was located in a subdirectory of "~/fileadmin" . IMHO target directory should get created though.
Cheers
- Status changed from In Progress to Under Review
The attached T3D files can get used for testing this issue. Without the patch applied there will be no error message prior to import. After import there will be an error message in the "Messages" tab. The file "Lagerfeuer.jpg" will not get imported and is missing then.
In the "media" field (Tab "Resources") of the newly imported page "Media page" there will only be one image which resides in the default storage. The other image will be missing.
The second T3D "test-patch-68791-ext.t3d" will show an additional error message about the non-installed extension "taskcenter". Of course only if it really is not installed.
The error message will get shown until there is a directory "fileadmin/sub" which is the target for the newly imported sys_file_storage.
- Status changed from Under Review to Resolved
- % Done changed from 30 to 100
- Status changed from Resolved to Under Review
- Status changed from Under Review to Resolved
- Status changed from Resolved to Under Review
- Status changed from Under Review to Resolved
- Sprint Focus deleted (
On Location Sprint)
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by