Thank you for taking the time to showcase my package on your channel, It's always exciting to see my work being recognized in the community, It means a lot to me I really appreciate the support. ❤❤
I do use your package and it is amazing. what I was not able to do, is to load the en.json file that it is in the root of the lang folder. I’m missing something or this feature is not available.
This is actually very useful when you are inviting external users to translate your website for you. Then those external users don't have to learn Laravel or edit source files directly. Even Facebook use similar techniques to this. That's how they manage to translate their websites to many languages.
Thanks again for a great video, you are for sure the BEST source of knowledge in the Laravel ecosystem. Taylor must add "Laravel Daily" in the official Laravel docs!
Awesome package indeed! I opened an discussion to add support for pt_BR as it seems to be missing and wont work with my code. Thank you Povilas for the showcase and Mohamed Ashraf for creating it.
hello , nice job , i have an issue with this package Target class [Outhebox\LaravelTranslations\Http\Controllers\Outhebox\LaravelTranslations\Http\Controllers\TranslationController] does not exist. the controller path duplicate when i add this to my project could you please give any advise
You can override the behavior of exceptions, probably read this section of docs: laravel.com/docs/9.x/errors#the-exception-handler But it depends on WHAT type of error you want to catch.
hi i opened the link to the usefull packages and its amazing i want to ask do you have a course with demos that goes through all those usefull packages ?
My courses are mostly about specific topics, not just listing the packages :) More useful packages I often demo on this RU-vid channel, not sure if it would be worth a separate course.
Unfortunately, I do not find the package so great. Purely database-based would be rather nicer. Let's assume the project is in a github repository and deployed to a server. Then you get, if someone changes the translation directly in the files on the server, a conflict of the versions locally or if a dev deploys his changes
Thank you for your feedback. The database is actually an important component of the package, as it is used for several key features such as tracking changes and enabling rollbacks (revisions). This revision feature is currently in development and will be released in a future update. Additionally, the database is used to store phrases and their attributes for validation, which helps to ensure that the package functions smoothly in a production environment. There are also several ways to avoid conflicts while using the package, such as not needing to track the translation files once the package has been installed and all translations have been imported. Thank you for your understanding.
If this package was purely database reliant it would slow the website down quite a lot for no reason and introduce a lot more memory requirement! The fact that you can publish the changes at will to the config files means the app will not run slower than if it was all in a database. The issue of overwriting changes made locally to the files you mention can simply be fixed by the package scanning for changes or keeping track of when the package updated the file Vs when the file was last edited and rescanning if they differ. Not a massive issue really... (I should note I have no affiliation to this developer nor have I used the package)
Thank you for your feedback. I understand your concern about the database being duplicate data storage. However, the database is actually required for several important features in the package, including the ability to track changes and roll back to previous versions (revisions). This feature is currently in development and will be released in a future update. In the meantime, the database serves a crucial role in the functioning of the package, such as storing the phrases and their attributes for validation. Thank you for your understanding.
This is actually very useful when you are inviting external users to translate your website for you. Then those external users don't have to learn Laravel or edit source files directly. Even Facebook use similar techniques to this. That's how they manage to translate their websites to many languages.
I disagree, for the functionality and convenience this package offers the database is required. I was thinking this would slow down the application a lot until it was mentioned that you need to publish any changes which write them to the original files meaning there would be no noticeable difference in speed of the application. I don't believe this would be as quick or easy to build without the database...
