TYPO3 Core

Are you sure the install tool shows this error? It is completely independet of that part of the infrastructure...

Hi Karsten,

the installtool is not independent of that part of the infrastructure because it include init.php which itself loads class t3lib_userauth. And class.t3lib_userauth starts with:
require_once(t3lib_extMgm::extPath('sv').'class.tx_sv_authbase.php');

no chance ;-)

but however: Sönke, does it work if you include the "requiredExt" line in your localconf manually?

$TYPO3_CONF_VARS['EXT']['requiredExt'] = 'cms,version,lang,sv';

for me this error looks like you have a somewhat screwed up installation. Are you shure you removed the old symlinks?
see: http://wiki.typo3.org/index.php/TYPO3_4.0

Hi Rupert, thanks for pointing that out. I didn't check this, and one never stops learning... :)

Definitely looks like a screwed update, I agree.

Hi all,

yesterday the same error appeared on a development server using TYPO3 3.8.0. The hints about the changing the localconf.php didn't have any effect at all. I was able to track the problem down to a simple fact - there was no space left on the device of the webroot. Making some new space solved the problem for me.

can I close this bug?

Hi... I just downloaded the latest stable version (4.1.2) and uploaded it to a client's web server. This is completely new install, but I get this error too. I am not out of disk space (not by well over 30gb). None of the tips here worked.

2 Tor de Vries: and there is no quota for your user..?

The user has a quota of 50gb, and has consumed less than 20gb, leaving more than 30gb available. I said "disk space" but I meant "quota"; the server itself has somewhere around 400gb free.

For whatever it's worth, I ended up deleting Typo3 from the server (code files, MySQL database, everything). Then I uploaded v4.1.3, and it works. Same server, same user, same directory names and permissions. Other than 4.1.2 versus 4.1.3, I see no difference in these installations, but it works now.

I had similar problems in (yep, outdated) 4.1.1 today, after saving a new template and, while I guess it was still saving, clicking icon "Clear cache in typo3conf/". At this point first the top frame showed "TYPO3 Fatal Error: Extension key "sv" was NOT loaded! (t3lib_extMgm::extPath)". Investigating showed that now both FE, BE and install tool all failed.

In typo3conf/ I found some zero-byte temp files. Manually removing the temp files in /typo3conf/ solved my issue.

Changing and saving a template and, while the frame is still reloading, clicking icon "Clear cache in typo3conf/" (which is in my top frame) I can easily reproduce this problem, always getting me this zero-byte files. This is a www.dreamhost.com account with plenty of disk space.

When the cause cannot be found: maybe TYPO3 can check the file length of cached files and ignore zero-byte files?

Details:

ls -la typo3conf/
... 1465 2007-03-05 16:54 extTables.php
... 11594 2007-12-14 16:07 localconf.php
... 37211 2007-12-14 13:43 temp_CACHED_psb152_ext_localconf.php
... 88842 2007-12-14 13:43 temp_CACHED_psb152_ext_tables.php
... 0 2007-12-15 04:25 temp_CACHED_psba8d_ext_localconf.php
... 0 2007-12-15 04:25 temp_CACHED_psba8d_ext_tables.php

www.mydomain.tld/
Error: The main frontend extension "cms" was not loaded. Enable it in the extension manager in the backend.

www.mydomain.tld/typo3/
TYPO3 Fatal Error: Extension key "sv" was NOT loaded! (t3lib_extMgm::extPath)

www.mydomain.tld/typo3/install/
TYPO3 Fatal Error: Extension key "sv" was NOT loaded! (t3lib_extMgm::extPath)

I had the same issue today. While simply trying to load http://www.domain.tld/typo3/ it would show this error. This fixed the issue:
domain/typo3conf# rm temp_CACHED*

There were also 2 zero byte temp_CACHED files in typo3conf folder.

The comment from Patrick Rodacker has been solved in 3.8.1 (according to #14753).

I do not think a zero byte temp_CACHED file could happen in typo3conf/ if php, webserver and rights are properly set up. Please provide a procedure to reproduce this bug in latest trunk or 4.2 branch, or this issue should be set to closed (no change required).

Of course this can happen that the size on the filesystem will get too small after some time.

See the related case at
http://bugs.typo3.org/view.php?id=7739

You run an import script with much data and at the same time you install a TYPO3 extension which will delete the temp_CACHED... files.

See notes in the bug reports. There are also numerous answers in the mailing lists for this question.

Closing the bug as nothing can be done here.