Bug #43151
closed
Unable to import/export .t3d
Added by maarten about 12 years ago.
Updated almost 12 years ago.
Description
Version: TYPO3 6.0.0.RC1
You are unable to enter the import/export module through the right-click menu on the root-icon.
Fatal error: Class '\TYPO3\CMS\Impexp\ImportExport' not found in /home/sharedcore/typo3_src-6.0.0rc1/typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 4157
Issue still persist in 6.0.0RC2, slightly different error:
Fatal error: Class '\TYPO3\CMS\Impexp\ImportExport' not found in /home/sharedcore/typo3_src-6.0.0rc2/typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 4155
- Assignee set to Oliver Hader
- Target version set to 6.0.0-RC2
I have some errors related to that line 4155, it seems the building of the class name for $fullyQualifiedClassName goes wrong in some places in the core,
i.e. I get also error like Class '\TYPO3\CMS\Extbase\Reflection\Service' not found in /home/sharedcore/typo3_src-6.0.0rc2/typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 4155.
So please check, if at all places in the core the namespace'd class-names are built correct, it seems that even in RC2 it is NO stable transition from the old class-name model without namespaces ! With this being unstable, there is no use of making or even declaring it final or an RC !
- Assignee deleted (
Oliver Hader)
- Priority changed from Must have to Should have
Frank Gerards wrote:
So please check, if at all places in the core the namespace'd class-names are built correct, it seems that even in RC2 it is NO stable transition from the old class-name model without namespaces ! With this being unstable, there is no use of making or even declaring it final or an RC !
First, please don't assign issues and tasks to people directly. Never! Unless you pay something for working on several issues - as far as I can speak for me, that's not the case!
It looks like you already digged into the problem, however gave up for what ever reasons. So, I kindly like to ask you to continue and maybe come up with a patch if you've gone that far already.
Besides that, I or anybody else being involved in the release of TYPO3 CMS 6.0 is willing to investigate for any bug that is reported.
- Status changed from New to Closed
duplicate; has been resolved in original issue
Also available in: Atom
PDF