Support for the 2.0 remote server API
Gábor Hojtsy - October 20, 2008 - 22:35
| Project: | Localization client |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | needs work |
Description
There is a new 2.0 server API just committed at http://drupal.org/node/323914 for l10n_server. This patch adds support for that API in l10n_client. Architected and implemented by Jose A Reyero, cleaned and tightened up by myself. Committed to 6.x.
| Attachment | Size |
|---|---|
| new_20_api_client.patch | 6.93 KB |
#1
need 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?
#2
Have 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.
#3
Ok 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?
#4
The 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.
#5
Automatically closed -- issue fixed for two weeks with no activity.
#6
How 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. :( ...
#7
Some users receive an error when adding the translation (to the l10 server).
This patch fixes the problem.
#8
This bug is still present and it is not fixed: (
#9
Let's trim the key on entry/submission to the client form, not when it is used.