Adding a test for Translatable

[chandon]

Adding a test to check the capacity to add a new language/value for an
existing translatable entity.
At the time of this commit, there is an issue as the test fails (all new
language/values are added to "en" language)

[chandon]

Of course the Travis test fails, the test is here to proove that there is a failure with Translatable...

[DerekRoth]

This test shows that there is a really huge bug in this behavior. In fact, it is unusable for adding new translations, as soon as the "en" translation exists. The fact that writing and reading translations use the same method for getting a Translation object seems to be a problem : getting the default language Translation for reading is fine, but not for writing.

[festlv]

I can confirm that this problem affects newbies- if the default translation exists, it is always returned when calling translate('otherlocale'). That is not obvious at all looking at the example in documentation.

[ZeeCoder]

I have this exact same issue.

[DerekRoth]

I ended up using my own fork in composer to fix that issue since i don't have time to work on a much better fix...

[ZeeCoder]

How did you fix the issue exactly?

[DerekRoth]

I use this patch : DerekRoth@b292f57
and then when i need to get a translation object in order to write to it, i use this:
$myEntity->translate('fr', false);
If i just want to read from it and fallback to the 'en' translation if the one i am looking for does not exist (current behavior) i just use :
$myEntity->translate('fr');

[TomasVotruba]

@chandon Could you add a code, that would make this test work, to this commit? I think it's necessary to keep test working, so it's ok to have a fix and test in one commit.

E.g. inspire by @DerekRoth solution.