We’ve made translation module which enabled in context editing as well as editing translations in a list view. I haven’t been able to publish it as a proper module since it contains a few kinks such as:
·Copying the cached templates but with rewritten versions of _t calls (with input capabilities to enable in site editing) to a new directory
·Selecting said directory when admin user is performing in site translations editing
·Requiring a _ss_environment.php file to do above mentioned switch
Previously we saved any changes directly into the lang files. This was a horrible mistake since it means that any changes made live would be overwritten on a new deploy, or it would require keeping the live lang files while deploying and putting them back when you’re done.
The approach we’re doing now is to store any changes in the database and then add the ability to import, export to and from the database.
Also we’re hooking into controller onBeforeInit to overwrite the lang values with any changes from the database enabling translations edited live to be shown instantly.
Is there any noticeable performance impact from using yml instead of the php lang files? We’re having performance issues as it is and would like to avoid more of them J