I installed 7x.1.0-beta10 and 6.x-1.0-beta4 several times, mostly only installing the Dutch language. Each time when I try to download and import the core language file (i.e. drupal-7.10.nl.po) for the first time using www.example.com/admin/config/regional/translate/update it takes hours to import the file (this morning I waited the first time over 2 hours). Only when I break the import halfway (?) by resubmitting the page and repeat this two - three times (each with enough time to complete) the status is "translation completed".
I still am not sure the whole import has been completed (difficult to check).
Translations of additional modules don't have this problem.
I have this problem on three different servers and with different languages (in the D6 version).

Comments

Gábor Hojtsy’s picture

Interesting. How powerful do you think are those servers?

PROMES’s picture

1. My own test pc with WAMP. It has an Intel Dual CPU E2180 2GHz with 4GB internal memory 32 bit Vista. PHP 5.3.1 and PHP memory-limit 128 MB.
2. an older shared hosting server with PHP 5.1.6 and PHP memory-limit 128 MB.
3. a new shared hosting server with PHP 5.3.2 and PHP memory-limit 128 MB. This issue happened on this server.
None have the PECL upload library or APC installed.
About servers 2 and 3 I don't have more info (both from a hosting company).
Recently I changed for one site from server 2 to server 3 because of very long runtimes of inserts of nodes with up to 1 million bytes: server2: about 5 minutes, server 3: less then 20seconds response time. Server 2 is a very busy server, I presume server 3 doesn't have much hostings yet. So server 3: less hostings and much faster.
If you need more detailed info, please state what info you need, then I can ask the hosting company.

Thanks for your help.

PROMES’s picture

Update.
Today I tried to update the core language file on my pc several times. Every time I got a timeout.
The current number of translations at admin/config/regional/translate didn't change after each try.

denjell’s picture

Category: bug » feature
Priority: Normal » Minor
Status: Active » Needs review

Gábor is right. Your php-memory is set WAY to low for drupal. up it to 512mb and see what happens.
here is more info if you need it: http://drupal.org/node/29268#comment-2931556

however, it might be __nice__ to add this to the codebase: (it will probably throw an error if there is neither enough memory available - like on a shared host - or if the current user doesn't have permission)

ini_set("memory_limit","512M");

BTW: This is not a bug which is why I have changed it to a feature request with minor priority and needing review.

PROMES’s picture

Status: Needs review » Closed (fixed)

Thanks for your help and input.
I changed in all three D7 sites the memory limit to 512M.
The site on my pc with WAMP still gives this error on the d7 po file:
An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /spelen/batch?id=21&op=do StatusText: OK ResponseText: Fatal error: Maximum execution time of 240 seconds exceeded in G:\xampp\htdocs\spelen\includes\database\database.inc on line 2135
However the "max_execution_time = 3000" in php.ini in the php map (3000 <-> 240 ?).
But since this is a testing site, I don't care that much.

PROMES’s picture

Version: 7.x-1.0-beta10 » 7.x-1.0-beta11
Status: Closed (fixed) » Active

I installed a new site today with 7.x-1.0-beta11. The import of the default language po file started after creating the settingspage. I followed the import in the database, looking how many entries were created. After 4671 new entries in the locale_target table the creation stopped but the import didn't stop. I waited another 5 minutes: no new entries. So I stopped the import en restarted the import. It ended saying something as 4671 entries imported.
So I presume the import indeed was succesfull, but the import module wasn't aware of it.
Maybe this is helpfull for you.

asrob’s picture

It's interesting. I've just installed 7.x-1.0-beta11 in Hungarian, "max_execution_time = 600", "memory_limit = 256M" and everything is fine.
Here is the translation status: "magyar 4758/4768 (99.79%)"

asrob’s picture

Issue summary: View changes

PROMES, can you confirm that this bug still exists?

PROMES’s picture

Status: Active » Closed (works as designed)

Since the upgrade to own servers (august 2012), with the PECL upload library installed, the problem doesn't exists anymore.
I think the problem was in the hosting servers / ability to change default PHP settings.