qTranslate и maximum execution time проблеми с по-нов WordPress

September 9, 2009 wordpress

На последния сайт, по който работих, започна да ми се появява много сериозно нон стоп error за Maximum execution time exceeded.

Fatal error: Maximum execution time of 60 seconds exceeded in

Вината не е в сървъра на ICN, нито в сървъна на NS1, където е сайта. Явно има проблем със самия плъгин и това как актуализира езиковите си файлове. Както и да е, ако още някой има този проблем, надявам се да се реши, понеже постнах тема в съпорт форума им. Въпросът гласи следното:

Hello,
I’ve read a lot of topics about this problem, in the past I’ve made one website using qtranslate which works all right, but the version number of WP and qtranslate there are lower. A month ago I was developping another website, when suddenly I started getting a blank screen and then “Maximum execution time exceeded” and error in mo.php or streams.php, as probably a lot of people do. First I thought it was me that was doing something wrong with the configuration. And I searched what was causing this error. I found that something replaces my bulgarian .mo file in wp-content/languages, which is usually around 370KB big, with a file that was then 270B big. I re-replaced that file with the original and things went on well again. But not for long. A week later the file broke again. The website was about to launch and I had to find a quick solution. What I did is I edited the mo.php in wp-includes/pomo with commenting this lines:

for ($i = 0; $i < $total; ++$i) {
$reader->seekto($originals_lenghts[$offset($i)]);
$original = $reader->read($originals_lenghts[$length($i)]);
$reader->seekto($translations_lenghts[$offset($i)]);
$translation = $reader->read($translations_lenghts[$length($i)]);
if ('' == $original) {
$this->set_headers($this->make_headers($translation));
} else {
$this->add_entry($this->make_entry($original, $translation));
}
}

This, along with deleting the bulgarian .mo file solved temporarily the problem, but it caused some drawbacks, because I couldn’t use the load_theme_textdomain(); of the template, which I needed.
So now I uncommented those lines and I’m still keeping the bulgarian .mo file deleted. This is the original website: http://www.venquity.eu/en/ However I mirrored it on my server to trace the progress of this problem. There I replaced an original bulgarian .mo file in the wp-content/languages folder today with updated WordPress 2.8.4 and qTranslate 2.4.3 and now I’m waiting to see if this problem persists – the beta server is at http://beta.wh1sp.com/venquity/en/ (don’t pay attention to phpThumb’s errors – it’s because it doesn’t find its cache)
I tried to searched in the changelog of 2.4.3 whether this problem is solved because I can’t give up from this plugin – it has so many features and is so integrated in WordPress. I was wondering if someone knows something about whether this issue is solved in 2.4.3 because I couldn’t find official information from the developper about it here in this forum.
Thanks again, apart from this problem the plugin is awesome and works fantastic.
EDIT: It did it again on the real site, now I found out that the replaced .mo file contains this html:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /wordpress-i18n/bg_BG/tags/2.8.3/messages/bg_BG.mo was not found on this server.</p>
</body></html>

I blanked it, so the system could work. Then I unchecked Automatically check for .mo-Database Updates of installed languages. ,because it seems that caused it now. I really don’t know what to do now… :(

ЕДИТ: Последната версия като че ли оправя проблема, поне засега не се е появил отново.

 

2 коментара

  1. Mylena says:

    ънчека на настройката за “Automatically check for .mo-Database Updates of installed languages.” оправи ли проблема?

  2. whisp says:

    Да, както и новата версия на плъгина. Досега сайтът не е крашвал, надявам се да не крашва повече.

Вашият коментар