Bug #15731
closed
Import of extension in TYPO3 3.8.1 ends with error 'No extension key'
0%
Description
This is with the current CVS version.
When I export 'tt_products' from 4.0CVS and reimport it in 3.8.1 I recently get the error message:
Error: No extension key!!! Why? - nobody knows... (Or no files in the file-array...)
This is the file exported with Backup/Delete in the EM from TYPO3 4.0CVS TYPO3_4-0:
http://story-castle.net/fholzinger/development/T3X_tt_products-2_4_6-z-200602271435.t3x
When I export the same files from TYPO3 3.8.1 the import to another TYPO3 works however.
(issue imported from #M2709)
Updated by Franz Holzinger over 18 years ago
Here is the same tt_products dev. version exported from TYPO3 3.81. which works fine for reimport:
http://story-castle.net/fholzinger/development/T3X_tt_products-2_4_6-z-200602271442.t3x
Updated by Axel Jindra over 18 years ago
I got this error everytime I marked "get latest translation" or "download documentation" when either of these were not available
Updated by Karsten Dambekalns over 18 years ago
Axel, this is indeed often the cause of such errors. But I think here the T3X file is uploaded directly, the TER is not involved. Right?
Updated by Franz Holzinger over 18 years ago
Yes, I have exported the T3X file with the Backup function in EM. I did not use the TER for this.
Updated by Karsten Dambekalns over 18 years ago
I just tried installing a CVS-TYPO3-exported nothing extension and one directly from TER2 on 3.8.0 and it worked.
When installing the extension attached to this bug report, it fails, but the real error message (that doesn't get shown due to a bug on old EM versions) is
"Error: MD5 mismatch. Maybe the extension file was downloaded and saved as a text file by the browser and thereby corrupted!? (Always select "All" filetype when saving extensions)"
I then imported 2.4.6 into a CVS-TYPO3, exported it again and could import that file into 3.8.0 without problems.
So it seems that your file got corrupted for whatever reason.
Updated by Karsten Dambekalns over 18 years ago
Please check again carefully(!) and reopen if this really is an issue.