Project

General

Profile

Actions

Bug #17960

closed

Unsuccessful update of extension list not recognized

Added by Franz Holzinger over 16 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extension Manager
Target version:
-
Start date:
2007-12-31
Due date:
% Done:

0%

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

Description

I have pressed 'Retrieve/Update' This has ended in a timeout error message. But the date of the last retrieval has been updated.
Now I want to fetch the recently uploaded div2007 and it says that it would not be available. I cannot repeat the 'Retrieve/Update' because it says that nothing had changed.

(issue imported from #M7068)


Files

bug_0007068.patch (570 Bytes) bug_0007068.patch Administrator Admin, 2010-11-08 12:39
Actions #1

Updated by Chris topher over 14 years ago

So this is fixable by making the Core set the internal "Update successful"-flag after the update has successfully completed (and not before as it obviously is done now).

Actions #2

Updated by Kevin Ulrich Moschallski over 13 years ago

Hi,

i think i found the problem:

in line 1723 of class.em_index.php the new md5hash file is written and in line 1724 the xml is parsed. So if the xml parsing stops i.e. because of a timeout the md5hash is already written. I just swapped those lines to get rid of this problem. I'll attach the patch.

Actions #3

Updated by Gone With the Wind about 12 years ago

  • Target version deleted (0)

This is still a problem on TYPO3 4.5.x, especially on servers that run php5 only in cgi mode (activated via htaccess; like allinkl.com). TYPO3 4.5 should be the target since that is an LTS...

Actions #4

Updated by Susanne Moog almost 10 years ago

  • Description updated (diff)
  • Status changed from New to Needs Feedback
  • Is Regression set to No

Hi,

does this still occur on TYPO3 6.2?

Regards,

Susi

Actions #5

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing 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

Also available in: Atom PDF