InvalidArgumentException in several cases
Under TYPO3 6.2beta 1 loading a new language in the backend raise an error (see included screen hardcopy):
InvalidArgumentException thrown in file /mnt/hgfs/Temp/TYPO3/typo3/sysext/core/Classes/Resource/File.php in line 221.
This worked fine under TYPO3 6.2.0 alpha 3.
My webserver runs PHP 5.3.10 in FastCGI mode.
Updated by Jan Greth over 7 years ago
Pascal Hinz wrote:
Had the same problem with TYPO3 6.2beta1 but i had to deinstall the TYPO3 System Extension "About Modules (aboutmodules)".
I have the same behaviour in a untouched new Installation. Uninstalling "About Modules" makes the language module functional again.
Updated by Stefan Aebischer over 7 years ago
I can confirm this. For me the error ocured on a fresh Install with sources from master at commit abc08c57858c47cf43ee68745f4642404daf7ba0.
But it only occured on the very first time i hit the Language module, afterwards it worked as expected.
Did not need to deinstall about modules.
Updated by Steffen Müller over 7 years ago
confirmed with master 8e1d6bd0e0c70ba0c827d17945d07327472dde75
I get the exception when clicking the about module. But with each click, a different file identifier appears in the stack trace.
After I continued to click several times, the about modules finally loaded.
Updated by Jan Bartels over 7 years ago
I've just installed the latest 6.2 trunk-version, which should include these patches.
If I run "Migrate all RTE magic images from uploads/RTEmagicC_* to fileadmin/_migrated/RTE/" in the Install-Tool, an uncaught exception is thrown (see duplicate #53131):
Uncaught TYPO3 Exception #1321023156: uid property is already set. Cannot merge index record. (More information)
InvalidArgumentException thrown in file
/.../typo3_62/TYPO3.CMS-master/typo3/sysext/core/Classes/Resource/File.php in line 225.
It seems that this issue is still unsolved.
Updated by Alexander Opitz over 7 years ago
- Status changed from Needs Feedback to Closed
- Target version deleted (
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.