Skip to content

Upload strings and more security? #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
steelzeh opened this issue Mar 24, 2017 · 3 comments
Open

Upload strings and more security? #16

steelzeh opened this issue Mar 24, 2017 · 3 comments

Comments

@steelzeh
Copy link

steelzeh commented Mar 24, 2017

Could we get the option to upload .strings og .xliff files? .strings would be fine for at start.
It's a bit hard to hand some api key to your translator and ask him to translate through that.
Would also be nice to have an option to download the translated file.

Also if you have the api key you can fuck up the whole translation. Would be nice to be able to secure it with some password.

It takes 10 seconds on charles to find the api key, when the framework does the /languages call.
After that it's possible to change the translation without any other security.

@Felizolinha
Copy link

The security thing is a really big problem for production. The website definitely needs to ask for a login before changing anything for this to be viable in production :/

@willpowell8
Copy link
Owner

I agree. I have been updating this and will be adding this to next release.

@willpowell8
Copy link
Owner

I have added more security to localizationkit 2.0 UI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants