Project

General

Profile

Actions
Copy link

Bug #33765

closed

Extension manager doesn't handle failed downloads (well)

Added by Oliver Salzburg about 12 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extension Manager
Target version:
-
Start date:
2012-02-08
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.6
PHP Version:
5.3
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

Description

I was trying to import an extension, which failed for some reason. So the MD5 sums of the t3x header and the body didn't match (which the EM told me).

Error: The data transfer did not succeed. Error: MD5 hash of downloaded file not as expected:
1b8d154ab055fc7830bffebca1fa5237 !=

This doesn't stop the EM from focusing the "Available Extensions" tab and placing a filter on it with the extension key of the failed extension.
So I click back into the "Import Extensions" tab, now the extension I was trying to import no longer has an import button...

Actions
Copy link
 #1

Updated by Thorsten Kahler about 12 years ago

  • Status changed from New to Needs Feedback
  • Assignee set to Oliver Salzburg

If you could provide the extension key and version it would be easier to reproduce the error.

Did you try to update the extension list? Sometimes extension authors overwrite existing extension versions instead of increasing the patch level when there are minor changes to the extension. So the MD5 error message might be absolutely right, but the further behaviour of the extension manager should be optimized.

Actions
Copy link
 #2

Updated by Dan Kleine (Untenzu) over 11 years ago

I can conform this issue with the extension »html5meta_t3lib_pagerenderer« as use case. In 4.5 everything is working fine (update is possible with old EM), in 4.6 and 4.7 I get this error message:

Extension import results
Error: The data transfer did not succeed. Error: MD5 hash of downloaded file not as expected:
f8877f2cbf0296f40513de29445fed94 !=

(not equal to »empty« is a bit suspicious)

I used to maintain this simple one-liner extension and send version 0.0.4 marked as »obsolete« into the TER. Whenever I tried to import the updated extension somewhere else, I got this error. Upgraded the extension to 0.0.5 and then again to 0.1.0 to avoid the situation as Thorsten described in his last paragraph. Still not working.

Actions
Copy link
 #3

Updated by Christian Weiske over 11 years ago

I have this problem with 4.7.4 and the cc_meta_* extensions: cc_meta_xmp, cc_metaexec, cc_metaexif

Actions
Copy link
 #4

Updated by Jigal van Hemert almost 11 years ago

  • Status changed from Needs Feedback to New
Actions
Copy link
 #5

Updated by Susanne Moog over 9 years ago

  • Status changed from New to Needs Feedback
  • Is Regression set to No

Hi,

is this still an issue in 6.2?

Thanks,

susi

Actions
Copy link
 #6

Updated by Dan Kleine (Untenzu) over 9 years ago

Well…

The bug still exists in version 4.7.
The bug does not exist in version 6.2 however (tested with the extensions mentioned in this ticket).

Actions
Copy link
 #7

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to Closed
  • Assignee deleted (Oliver Salzburg)

As it is fixed in TYPO3 CMS 6.2 and TYPO3 CMS 4.7 is out of maintenance I'll close this issue.

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.

Actions
Copy link

Also available in: Atom PDF