Bug #24843
closed
ter not loading when clicking on "update"
0%
Description
When you click on update in the Repository Tab the TER Extension list does not get updated!
It says
Error parsing Json response null
We tested it in all our sites it is impossible to update extensions.
(issue imported from #M17347)
Files
Updated by Henrik Ziegenhain almost 14 years ago
I can confirm this error, but it seems that the new EM fetches the extensions
Updated by Oliver Hader almost 14 years ago
Does this bug occur with the old (regular) Extension Manager or with the new grid view?
Updated by Henrik Ziegenhain almost 14 years ago
Hi Oli,
the error occurs in the new EM
Updated by Oliver Hader almost 14 years ago
Sorry, I was not able to reproduce on my system. However I attached a screenshot on how to get further information with the Firefox plugin "Firebug".
Please open the AJAX request there and post the information that was responded by the server (note: the accordant request contains the string "namespace=TYPO3.EM").
Updated by Henrik Ziegenhain almost 14 years ago
Hi Oliver,
I checked it on 3 Installations. 2 are accessed via https and the third one normally over http protocol.
http woks fine. https throws the above mentioned Json error at the first time I update the remote repository. A second update works fine, the response in firebug says something like "No update needed".
Updated by Henrik Ziegenhain almost 14 years ago
Strange, its not always reproducable. I think it has nothing to do with the protocols.
I cleared the table cache_extensions and updated the remote repository and got the following message in firebug:
<br />
<b>Fatal error</b>: Allowed memory size of 67108864 bytes exhausted (tried to allocate 31981894 bytes) in <b>/path/to/sources/typo3_src-4.5.0/t3lib/utility/class.t3lib_utility_debug.php</b> on line <b>335</b><br />
I cleared and updated a few times more, everything worked fine and i got this message:
[{"tid":8,"action":"ExtDirect","method":"repositoryUpdate","type":"rpc","result":{"success":true,"data":{"count":"4889"},"rep":1},"debug":""}]
Updated by Steffen Kamper almost 14 years ago
This is improved with #24974. So there is a good way to see the real reason for this error.
Updated by Alexander Opitz almost 11 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
0) - Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.1.7)?
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
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.