Increase time limit when doing batched .po imports

Please increase the max_execution_time in php.ini.

max_execution_time = 180     ; Maximum execution time of each script, in seconds

Agreed that's likely to fix it.

If this is a common error, we should consider having Drupal itself try to increase the maximum execution time while the language import is running (like we already do during cron runs). Although that won't work in all hosting environments.

Looks like there was an issue related to this at #569004: Add support for seek based batch import of .po files that was originally filed against core but then moved to contrib. I'm not sure why.

@David_Rothstein: we already up the limit exactly like we do in the cron operations (same code).
@alexpua: this is not solvable in Drupal core since it would require substantial API changes in locale module. For Drupal 7, you can use the new (and still stabilizing) http://drupal.org/project/gettextapi module to be able to read big files. It just replaces core locale module functionality at places, so it will not have any new UI component visible.

Marking duplicate of #569004: Add support for seek based batch import of .po files.

This issue is about the installer, and I don't see where set_time_limit() is called when a language is being imported during installation.

Actually, even post-installation, it's not clear that it gets called everywhere it needs to be. (It happens at admin/config/regional/translate/import but doesn't seem to at other places in which a batch import is run.)

Either way, we need to fix this issue in Drupal core, not just contrib. If the set_time_limit() solution is the only one that's safe to backport, we could do that here and then have a separate D8-only issue for the more comprehensive fix.

Oh, yes, you are right, it does not increase the time limit when in batch import.

With #1848490: Import translations automatically during installation being committed now, the situation on importing po files has completely changed. Translations are imported using a batch process php max execution time problems will no longer occur.
Marking the issue fixed in full confidence. Feel free to re-open if the error still occurs with the latest 8.x release.

Well, even if it does not apply to Drupal 8, it would still apply to Drupal 7.