b0aa111511
The api has been tested and works as intended. Now users do not have to go on the website to get back their token, they just have to register. Torrents show the right stats and username on api request when search is done User model when converted to JSON gives us the apitoken and md5 hash of email (for gravatar) Verification on upload is done by token and username instead of token only Errors are now given in json format in the api Global api response handler for less code redundancy and same response pattern Moved user auth check in cookie_helper to user.go Fixed bug with CSRF prevention in /api Added translation strings |
||
---|---|---|
.. | ||
ca-es.json | ||
de-de.all.json | ||
en-us.all.json | ||
es-es.all.json | ||
fr-fr.all.json | ||
hu-hu.all.json | ||
is-is.all.json | ||
it-it.all.json | ||
ja-jp.all.json | ||
ko-kr.all.json | ||
nb-no.all.json | ||
nl-nl.all.json | ||
pt-br.all.json | ||
pt-pt.all.json | ||
README.md | ||
ro-ro.all.json | ||
ru-ru.all.json | ||
sv-se.all.json | ||
th-th.all.json | ||
zh-cn.all.json | ||
zh-tw.all.json |
After creating a new translation, create a new translation string inside "en-us.all.json", like the following:
...
},
{
"id": "language_(languageCode)_name",
"translation": "(your language name, in English)"
},
...
where languageCode is the newly created ISO code (eg. ja-jp, pt-br).