Closed (won't fix)
Project:
Localization update
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Mar 2011 at 22:31 UTC
Updated:
22 Dec 2012 at 16:33 UTC
Project user_visits not listed on localize.drupal.org
Comments
Comment #1
pasquallehttp://localize.drupal.org/translate/projects/user_visits
Comment #2
gábor hojtsyComment #3
alexbk66- commentedSorry, I'm new to Drupal, so I'm not really sure where the problem is. I use live-translation module which is configured to use drupaler.ru for Russian translation.
I get at admin/reports/live-translation
So do you think I should log a request at drupaler.ru?
Comment #4
gábor hojtsydrupaler.ru is not an official source for translation, it is not run, neither endorsed by drupal.org. If you intend to use that server, talk to the server admins themselves. We are not affiliated.
Comment #5
alexbk66- commentedWhen I installed live-translation module it was configured to use drupaler.ru for Russian translation. I didn't change any settings.
If you have a better idea, please explain.
Comment #6
gábor hojtsyLook, localize.drupal.org suggests you on its download pages to use l10n_update module, which is the standard method of updating translations from a localization server. Live translation was developed as a one-off tool, its server source code is not available and it is not supported on drupal.org. Not sure who suggested you use that module, if you know of endorsement appearing on drupal.org to do so, please let me know.
Comment #7
alexbk66- commentedThank you Gábor.
When I just started Drupal, I used l10n_update module, it screwed up my site for Russian translation, i.e. (in Russian)
http://drupal.org/node/1024024
http://www.drupal.ru/node/55316
In reply somebody recommended Live translation module which worked for me, and I'm happy there was another alternative!
Yeah, I guess it was a temporary screw up, I should try l10n_update again.
Comment #8
alexbk66- commentedGábor, I installed the module, on admin/build/translate/update it says that both local and remote updates are available for every module!
When I click 'Update Translation' - it says 'Updating translation.' (batch?op=start&id=26), that's all, nothing happens.
Just checked the log, there's an error:
Type access denied
Date Wednesday, 23 March, 2011 - 22:37
User Guest
Location xxxxx.com/batch
Referrer
Message batch
Severity warning
Hostname 66.220.149.244
Note, I'm logged in as user1. Any ideas?
Comment #9
gábor hojtsyI have not seen that issue before. Moving to the right module so it might get more attention by other users.
Comment #10
alexbk66- commentedFound similar issue http://drupal.org/node/292060#comment-1129581
I have max_allowed_packet = 16M, is it possible that even this isn't enough as it tries to update ALL modules?
Is it possible to split updates?
Comment #11
pasqualleComment #12
gábor hojtsyWell, it could be that a module like print causes your batches to fail, are other batches work, like enabling modules with dependencies?
Comment #13
alexbk66- commented1. I don't have print module.
2. Other batches work
3. Found another related core issue #434032: Batch update fails with access denied message
Comment #14
alexbk66- commentedMay be at least it's possible on admin/build/translate/update to add a checkbox next to each module, so I could update translation for just a few modules at a time.
Another option - make configurable limit of updates per cron run, like search module.
If there's no solution at the moment - I will have to go back to live-translation module, I don't have another choice.
Comment #15
gábor hojtsyWell I highly doubt this is about l10n_update running over the MySQL limit. Especially that you have a much higher limit. Are you sure?
Comment #16
alexbk66- commentedI'm not an expert in Drupal, but I'm afraid yes, that's the problem. I can't see any other reason.
According to #434032: Batch update fails with access denied message ACCESS DENIED error is caused by max_allowed_packet limitation. And in my case I get full translation for 75 modules.
And where else can the problem be? I get 'ACCESS DENIED' when I click 'Update translations'. And translations don't get updated.
Comment #17
gábor hojtsyWell, I don't have access to your system, and I've seen sites updating translations which had more than 75 modules. So unless you can provide more details, I'm afraid I'll not be able to help you.
Comment #18
alexbk66- commentedBy 'sites updating translations which had more than 75 modules' do you mean 'UPDATING' or getting FULL translation?
And I have actually around 250 modules, but on the update page there's only 75 listed.
Comment #19
alexbk66- commentedHi Gábor,
I'm afraid you are right, I do have a problem with batch system. When I save 'Taxonomy Menu' settings, the url is 'batch?op=start&id=33', it says "Rebuilding Taxonomy Menu" and that's it. There's no log entries.
So I have to sort out this batch issue first. I know it's irrelevant here, but maybe you could point me somewhere?
[UPDATE]
I found that the theme (Drupal Commons) I'm using is causing the problem. So for batch operations I have to switch to Garland, then switch back to my theme. Great.
Comment #21
sutharsan commentedI assume this response by alexbk66 http://drupal.org/node/434032#comment-4451592 means that this issue can be too.
Comment #22
deanochips commentedI had the same error with drupal 7
adding
innodb_flush_log_at_trx_commit=2
fixed it for me