TYPO3 Core

Reload the mirror list in your Extension Manager settings.

re: Reload the mirror list in your Extension Manager settings.

Clicked "reload..." but got same error as above: "The mirror list was not updated, it could not be fetched from http://repositories.typo3.org/mirrors.xml.gz. Possible reasons: network problems, allow_url_fopen is off, curl is not enabled in Install tool."

Also, there is no list of mirrors in the :Mirror list" pane as in previous version (RC2)

To use the curl function, you need to install the libcurl package for php. I get the same error but using curl isn't the solution (for now)

http://php.nederland.net/manual/en/ref.curl.php

I've attached two images. The first is the extention manager that shows the error. The second one is the output from php_info() in the install tool.

The php settings seem correct.

--

Found the error on my side.

I had a custom url in the 'Enter repository URL' field. The url didn't have http:// in front of it. I removed the custom url and using the mirror list now.

@paul: what url do you have in the extentions mirror list?

http://repositories.typo3.org/mirrors.xml.gz

?

I just checked:
URL: http://repositories.typo3.org/mirrors.xml.gz

Note: I've just upgraded to the full release version of TYPO3 4 and I'm continuing to have the same problem. I guess I'm going to manage extensions manually until I can solve this. Seems to be a problem only on the server running Apache/1.3.34 (Unix) PHP/4.3.10 AuthMySQL/2.20 mod_perl/1.29. I'm doing another clean install of full release version of TYPO3 4 on another server. I'll see if that one's OK.

Thanks.

Problem installation is on server with this configuration:
TYPO3 4 (New Full Release 04.07.06) Apache 1.3.34 (Unix) | MySQL 4.1.11 | PHP 4.3.10

Working installation w/ this configuration:
TYPO3 4 (New Full Release 04.07.06) Apache 1.3.34 (Unix) | MySQL 4.1.13 | PHP 4.3.11

So, I'm assuming there's a problem with the server configuration. Unfortunately I only have access to the http-docs root on both servers.

That´s a problem with the php memory.
I have the same problem, the list won´t load, but unfortunately, I cannot change any Apache / PHP-Settings on the server of my provider.

The Extensions-List might be just too big! Looks like it needs 32MB and most servers just give 16.

I hope there will be a solution soon, but the extensions can be installed by importing the files directly. I did that with templavoilá and it worked.

No, loading the mirror list does not neeed much memory.

Btw, code could use is_callable() to see if cUrl is available. Better to add it to Install code of course...

...and about memory. I had a strange situation today. Tried to update kickstarter. Got out of memory with 64K. Refreshed page through browsers pop up menu, it went without errors. It looks strange to me: sometimes it passes, sometimes fails with out of memory...

See this thread for more details, looks like many people have problems with the extension manager. (It´s german language...)

http://www.typo3.net/index.php?id=13&action=list_post&tid=39372&page=3

Do you still experience this issue?

Well, I still get the error 500 when I push "Retrieve / Update" on my 1und1 webhosting in Germany (which is quite spreaded here).

I just switched to another webhoster (all-incl.com) and the extension manager works quite okay, though sometimes I still have session problems.
There is another solution that works with 1und1: there is an extension called ch_lightem - "Light Extension Manager". With this, the list of extensions was displayed correctly for the first time. But it still crashes sometimes.

I´m not familiar with the server technology, but it seems the extensions database is too demanding for the usual webhostings, or the php script takes too much time, so the server quits it.
I have the same problem when starting the templavoila wizard and when I want to export bigger pages to a .t3d-package.

So this probably is rather a problem with the hosting than with TYPO3 in general, but this issue may exclude people who don´t use a root/managed server from running an installation without restrictions and errors.

But anyway, thanks for your help!! Ron

Please don't flame me for closing this one, the memory issue is on our radar, but it's not this bug to deal with it... Thanks.