Fix typo in capability check to show edit link for glossaries. See #97.
Glossary: fix fataling test

`create()` only returns the id, not the created object
Rename `should_be_updated_with` to `is_different_from`

After testing with few people reading the code, the latter turned out
to be more understandable, even though it's more low level.
Add link to profile pages to show all contributions the user made for that project/translation set. Fixes #363
Limit recent project. See #340.
Add support for Oriya

See https://make.wordpress.org/polyglots/2014/10/01/requesting-a-new-locale-to-be-included-for-2/
pomo sample app: use safer paths references
Reduce the size of index singular_plural_context. See #349
Fix  guess_uri() for subdirectory installations. See #282
Move retrieving permissions of a user to GP_User. Props joostdevalk. See #365
Don't fatal when hitting a projects page where the parent project has been deleted. See #366
Rename ori to ory

ori is the language code for the macro language, which includes another
language, in addition to ory
Disable public profiles for scalability reasons

Few of the queries run a full-table scan on the huuge translations table,
so we can't deploy this in production in its current form.

Since we want to deploy some later changes, here we just disable the route
and remove the links until performance is better.

See #340.
Add Lingala locale definition

See https://make.wordpress.org/polyglots/2014/11/09/requesting-a-new-locale-for-lingala-language-2/
Change extracted_comment to extracted_comments.
Fixes not exporting translation comments for PO files.

Props yoavf
Fixes #294
Rewrite how we get recent projects/translation sets of a user.
Increases the performance when you are dealing with a lot of translations.
It also stops returning human readable time through the API which should be calculated on display.

See #340
Fix changed variable in GP_User after last changes.

See #340
Fix going to the previous translation with the keyboard.

See #52 and #98
Disregard context if it's any falsy value

Currently when generating the key for an entry we only disregard if
context is NULL. Unfortunately in some recent cases context has been an
empty string and the key calculated included chr(4) in the beginning.

This lead to some wring comparisons and ultimately including the same
oriignal multiple times during import.
Use correct condition

The falsiness equivalent of `is_null` is the negation of the value, not the value
itself.