Bug #21194
closedTranslation update broken
0%
Description
#21079: "dynamic update of translation status im EM is broken"
makes Translation handling submodule broken.
A few seconds after hitting "Check status against repository" or "Update from repository" only a blank page appears.
No PHP error, but anything with output buffers for sure.
This affects 4-2 and trunk (as #21079 was committed to both).
It's reproducible for me with both versions on different servers, als jweilandnet mentioned the problem on twitter.
(issue imported from #M12129)
Files
Updated by Steffen Gebert about 15 years ago
I've attached a patch (12129.diff), which solves the problem on my mac - but on a production server it doesn't work (the whole status indicators (green bar + table) doesn't show up).
There seem to be two levels of output buffering, which all have to be flushed.
What the remaining problem on the production server is, I don't know.
Help welcome! This is an important issue!
Updated by Oliver Hader about 15 years ago
Is there something in the webservers error log or PHP log?
On updating the translations I get a
"Warning: unpack() [function.unpack]: Type V: not enough input, need 4, have 0 in /Users/olly/Development/typo3/trunk/typo3/mod/tools/em/class.em_unzip.php on line 951"
Updated by Steffen Gebert about 15 years ago
No, nothing in error_log - there's no error (also not the unpack()-error).
It's a problem of output buffering.
As soon as I remove zlib-extension, everything works fine. It seems to do additional OB, although it's always set to off (PHP's value and zlib.ouput_compression).
Even the following output is shown at once, not bit by bit. (using XAMPP on MacOS, PHP5.2):
echo "1";
sleep(1);
echo "2";
sleep(1);
echo "3";
?>
This additional OB which is done by default seems to cause the problems.
I debugged it local and so found a solution, but I'm not able to debug on production server, but I think the output buffer there is just thrown away and not sent to the browser (as it takes some time until the buttons are shown).
Updated by Steffen Gebert about 15 years ago
The bug is gone after setting $TYPO_CONF_VARS['BE']['compressionLevel'] = ''
Updated by Oliver Hader about 15 years ago
Thanks for narrowing this down to the compression level!
Updated by Rupert Germann about 15 years ago
FYI: committed attached v3 patches to
4_2 branch rev 6131
trunk rev 6132