tabacitu on composer
Apply fixes from StyleCI (compare)
dependabot-preview[bot] on composer
[Security] Bump symfony/http-fo… (compare)
tabacitu on fluent-syntax
renamed field wrapperAttributes… Show operation automatically ad… Merge pull request #2610 from L… and 2 more (compare)
Hi, i am trying to use the localization feature of backpack with spatie/laravel-translatable and I observed one behavior I find odd:
1) I create an entity. The language for the translatable fields seems to be fixed (determined by the App locale?). In my case the locale is 'en'.
2) Then, I open the update mask for a different language (e.g. 'de') than the one used during creation.
The update mask's translatable fields are already filled out, but with the translations for the other language ('en') used during the creation of that entity. Thus, from the user interface it looks like these fields are already filled out (although with the wrong translations ('en instead of ones fitting 'de') where in fact the database does not store these translations yet (it only contains 'en). One can of course edit the translations accordingly and save the entity and then the database contains data for both language ('en' and 'de'). However, I think this user experience is odd and not what I would expect.
Is there any way to keep translatable fields empty that do not yet have a translation? I guess that not translation for 'de' is found and then it falls back to the default locale which in my case is 'en'.
IDand I would like to hide it using
hiddenfor table update, but I also want to show it as a
@alucard001 i suggest you use laravel debugbar, it could be helpfull
Thank you very much. I will try that