Closed (fixed)
Project:
Localization client
Version:
6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Oct 2008 at 22:35 UTC
Updated:
4 May 2010 at 13:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
akis p commentedneed some clarification,
On local machine we have enabled the,
admin/settings/language/configure/l10n_client
Enable sharing translations with server
and in
Address of localization server to use:
we have the remote server
http://www.demo.somesite.net/
Do we miss something? or isn't yet working?
Comment #2
gábor hojtsyHave you set up a user key for the user you are trying to use to share. Since this works via server-server communication, we need a way to authenticate the client, so that people cannot submit strings in your name. Therefore you need to go into your user settings and set up your user key on the client site. Instructions there will help you do it right.
I agree this could be better documented.
Comment #3
akis p commentedOk so here is how it works.
Version 6.x-1.6 and after
After enabling the module and setting up the permissions for the user roles.
Navigate to
admin/settings/language/configure/l10n_client
check the
Enable sharing translations with server
Enter the web link of your team server under
Address of localization server to use:
http://www.example.com
Click
Save configuration
Go to your account and click
Edit
Find
Your Loalization Server API key:
and enter the key that you would get by clicking on the link after the ,
This is a unique key that will allow you to send translations to the remote server. To get your API key go to
You have to be logged in in at this time on the localization server in order to get the Api key.
And also you must have the permission on the remote server to submit remote translations.
Easy?
Comment #4
gábor hojtsyThe startup setup of this new interface is a bit longer then the previous one, but from there, you don't need to be logged in on the l10n_server at all to contribute. Previously your contributions would just be dropped if you were not logged in, now you don't need to be logged in, since your secret API key authenticates you.
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #6
pvasili commentedHow to keep the access via group using this method?
Will be add transfers any users who have the key? :(
How do I restrict access to external users?
Now the client writes to the log file:
Translation rejected by remote server. Reason: Wrong parameters or signature.
server:
Submitted translation with wrong parameters or signature. :( ...
Comment #7
pvasili commentedSome users receive an error when adding the translation (to the l10 server).
This patch fixes the problem.
Comment #8
pvasili commentedThis bug is still present and it is not fixed: (
Comment #9
gábor hojtsyLet's trim the key on entry/submission to the client form, not when it is used.
Comment #10
andypostThis is a useful change, users could enter a key with copy/paste from browser so key have ending space.
Let's trim it on hook_user('submit')
Suppose no need to check permissions - check presence of value is enough
Comment #11
gábor hojtsyThe issue at #748664: API key not saved also contains this functionality for D7, so no need to port this one up. Let's close this issue and open new ones from now, if this needs more fixups.
Comment #12
gábor hojtsyBTW committed this one to D6 already before the previous comment :)