TYPO3 Core

Please check if your setup has short_open_tag enabled, and try switching it off.

Sorry, I tried that, and it did not change anything.
additional info:
when I "check status aginst repository" it gives:
Check done.
""""""""""""""""""here is a green bar"""""""""""""""""""""""""""""""
This table shows the status of the loaded extension's translations.

|Empty document||Empty document||Empty document||Empty document||Empty document||Empty document||Empty document||Empty document||Empty document||Empty document||Empty document||Empty document||Empty document||Empty document||Empty document||Empty document||Empty document||Empty document|
Extension key Danish
cms OK
version OK
lang OK
sv ?
css_styled_content ?

Hello,

As a last resort I downloaded "typo3_src-4.0" again, and unfolded it out instead of the old one, and to-day I could go throuh all the translation, so please close this bug-report.

I do not know what were wrong, but now it works, and this is the most important for me.

med venlig hilsen
Niels Søndergaard

I experience exactly the same problem.
There seems to be an issue with the XML parser ("|SYSTEM or PUBLIC, the URI is missing|" is a php-libxml message).

Exactly the same problem here (with the german language).
Please do not close this bug until resolved.

Here's my workaround (it's magic):
- First of all delete all the already installed language stuff
shell> cd typo3temp
shell> rm l10n.zip
shell> rm llxml/*
shell> cd ../typo3conf/l10n
shell> rm r *
Now press the button 'Update from repository' (Ext.-Manager -> Translation handling)

If (there occur no Problems like hanging at 'Updating translation for extension "sv" ...') {
    feel happy
  } else if (hanging at 'Updating translation for extension "sv" ...') {
     Do ONLY delete the following:
     shell> rm l10n.zip
     ... now try again the button 'Update from repository' -> now it should work
  } else {
     ... no ideas anymore
  }

Ok, I suspect another issue here. The code does not check for the result of the fetching of the remote translation status.

The attached patch adds a check for the return value of fetchTranslationStatus() and thus avoids errors when the remote data cannot be fetched.

The patch bug-3637.diff works perfect. No problems anymore.
(we use curl, allow_url_fopen is Off in php.ini)
Thanks a lot.
Could someone test this patch with allow_url_fopen=On (without curl)?

In Typo3 4.0.1 the problem still exists.

In Typo3 4.0.2 the problem still exists.
The patch bug-3637.diff still works for Typo3 4.0.2.

Sorry, the patch got lost in the core list... I resubmitted for approval and will put it into SVN as soon as possible. 4.0.3 should be fixed, then...

Note that the error on getting the ZIP files from the Ext-Manager can be caused by yet another bug if you are using curl.

With this fix (of #16220) you will get rid of the enigmatic warnings for not existing translations, but instead a nicer warning ("Could not fetch translation status").

The fix for the origin of the problem with curl has been located and the fix approved by the Core Team, so I'm going to submit it now to Trunk and 4.0, so it should be available on 4.0.3. With this fix you should not get warnings or errors when updating translations with curl enabled (only "N/A" for not existing translations).

Fixed in SVN.