Doesn't import translations [#949238]

Not sure if this issue belongs here, or somewhere else... as it appears to be a problem with translation imports?

Anyway, I have tried this basic process three times now:

- Extracted Localized Drupal install profile into webroot
- created fresh DB & DB user
- copied default-settings.php to settings.php and set permissions
- ran through install script

Everything looked good until the final step. After the "configure site" step, I get a white screen when it should be doing the translation imports. When I refresh the page, it tells me the site is configured. But then when I go to the homepage everything is in English, not the language I selected. Clearly, nothing imported.

I tried going to admin/build/translate/import/package to reimport the packages, but it also accomplishes nothing.

Little help?

[frustrated side note]
If you guys are going to no longer link to the old translation files and force everyone to move to a entirely new method for deploying sites in a different language, you should have better documentation on how to accomplish it. The only documentation at all that you provide is (a) for D7 and (b) in Japanese. I have no idea if I am doing something wrong, or this just plain doesn't work... but it's taken me quiet a few hours to get as far as I have. The old method, while tedious, at least worked and was well explained across the web :(
[/frustrated side note]

Comments

Comment #1

bbenone CreditAttribution: bbenone commented 22 October 2010 at 04:46

Title:

Doesn't do anything....

» Doesn't import translations

Sorry... changing to a more meaningful title...

Comment #2

Gábor Hojtsy

he/him

Hungarian

Hungary

CreditAttribution: Gábor Hojtsy commented 22 October 2010 at 07:56

Status:

Active

» Postponed (maintainer needs more info)

You don't need to use l10n_install to install Drupal, its in beta as you have seen. Just clicking the translations tab here will get you the Drupal core translation downloads, which you can import into an existing website. So I don't think that its an issue that there is only one Japanese video for l10n_install. Thanks for testing though!

Now for the actual error, can you look at your "Administer > Reports > Recent log entries" list and look for relevant errors which happen at the end of install. The white screen should be accompanied by error messages there hopefully. Thanks!

Comment #3

bbenone CreditAttribution: bbenone commented 22 October 2010 at 16:29

Status:

Postponed (maintainer needs more info)

» Active

Unfortunately, I don't see anything in watchdog. Only a success message: "The Spanish language (es) has been created."

I turned up PHP error reporting (E_ALL) and went through the process again, but don't see anything reported on the white screen. I also checked my memory limit, and it's currently 96M (which I think it the max my webhost will allow, but should be more than sufficient, no?). It happens relatively quickly, so I don't think it's a PHP timeout either.

I should clarify that attempting to reimport here: /admin/build/translate/import/package doesn't generate a whitescreen, or any watchdog/error/success messages either. It just quietly directs me back to the Overview tab. It does so very quickly too.

I feel like I must be missing a step or something? Did I need to manually download any translations? install any modules? ...?

Any other ideas?

Lastly, Regarding docs...

If you click the Translations tab it says right at the top, very first sentence: "Install Drupal localized with Localized Drupal." Which seems to indicate that this is now the official way to go about it (instead of, for example, extracting http://drupal.org/project/es into your webroot and selecting spanish during normal install). It seems that drupal.org is pushing people pretty strongly toward this install profile... beta or not.

But.. I'm a bit of a stickler for documentation, so that's just me being grumpy... if I ever get this working I'll quit complaining and instead type up a guide that might help...

Comment #4

bbenone CreditAttribution: bbenone commented 25 October 2010 at 01:08

With a little more digging through error logs, I've found that the issue seems to be w/ MySQL. I found a bunch of "MySQL server has gone away" messages in my php errorlog file.

I'm guessing that I'm hitting a time out or that there is some mysql mem limit that is being reached. My webhost does not give me access to modify the my.ini file, or customize any mysql configurations. Is there any other path forward here?

Here is the relevant error message:

[22-Oct-2010 10:03:26] PHP Warning:  MySQL server has gone away
query: INSERT INTO watchdog
    (uid, type, message, variables, severity, link, location, referer, hostname, timestamp)
    VALUES
    (1, &#039;php&#039;, &#039;%message in %file on line %line.&#039;, &#039;a:4:{s:6:\&quot;%error\&quot;;s:12:\&quot;user warning\&quot;;s:8:\&quot;%message\&quot;;s:526:\&quot;MySQL server has gone away\nquery: UPDATE cache SET data = &amp;#039;a:3:{s:4:\\&amp;quot;name\\&amp;quot;;s:19:\\&amp;quot;localize.drupal.org\\&amp;quot;;s:10:\\&amp;quot;server_url\\&amp;quot;;s:42:\\&amp;quot;http://localize.drupal.org/l10n_server.xml\\&amp;quot;;s:10:\\&amp;quot;update_url\\&amp;quot;;s:86:\\&amp;quot;http://ftp.drupal.org/files/translations/%core/%project/%project-%release.%language.po\\&amp;quot;;}&amp;#039;, created = 1287759806, expire = 0, headers = &amp;#039;&amp;#039;, serialized = 1 WHERE cid = &amp;#039;l10n_update_server:http://localize.drupal.org/l10n_server.xml&amp;#039;\&quot;;s:5:\&quot;%file\&quot;;s:45:\&quot;/home/mueblesc/public_html/inclu in /home/mueblesc/public_html/includes/database.mysqli.inc on line 128

Comment #5

Gábor Hojtsy

he/him

Hungarian

Hungary

CreditAttribution: Gábor Hojtsy commented 25 October 2010 at 08:49

Well, this error seems to be happening when a cache entry is refreshed, which is neither big nor should cause a timeout (which is not happening as you've explained). I don't know why would MySQL drop your connection in this case, I don't think the code does anything to cause that...

Comment #6

bbenone CreditAttribution: bbenone commented 25 October 2010 at 14:45

Right, well, in my experience many times it's the query immediately before the first logged "MySQL has gone away" failure that caused the timeout/problem. I haven't had a chance to dig through the code on this to see what that is.

My configuration is fairly standard. Brand new hosting account (w/ Siteground.com), nothing else installed on the account and nothing else downloaded other than this install profile. In my opinion, Siteground gives somewhat low resource limits which is what I'm guessing the problem is here.

For now, I've proceeded the "old" way. I'll come back to this install profile once I get the current site deployed and see if I can figure anything out.