You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 5, 2018. It is now read-only.
I was trying the export/import functionality of the plugin but the import kept failing. After some digging I found out that it had to do with invalid data in the (generated) csv file. This was caused by some entries in the translation list retrieved from plugin files, like this:
So obviously the generated entries aren't exactly translations, so I don't understand why they are added to the translation list. As it says in this translate plugin documentation, only Craft::t(), Craft.t() and ""|t() should be read and manageable through the translate plugin.
Could someone look into this please?
Thx in advance,
Just a thought, but isn't it 'safer' to just use the language files provided (if provided off course) by the plugin itself instead of scanning the plugin files for translations? In this example both amnav & amforms have specific translations files, so why don't make use of those?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I was trying the export/import functionality of the plugin but the import kept failing. After some digging I found out that it had to do with invalid data in the (generated) csv file. This was caused by some entries in the translation list retrieved from plugin files, like this:
AmNav.js (line:279 / plugin:amnav)
var $elementContainer = this.$container.find('.amnav__node[data-id="'+parentId+'"]').closest('li'),
color.html (line:15 / plugin:amforms)
{%- includejs 'new Craft.ColorPicker("'~(id|namespaceInputId)~'");' %}
So obviously the generated entries aren't exactly translations, so I don't understand why they are added to the translation list. As it says in this translate plugin documentation, only Craft::t(), Craft.t() and ""|t() should be read and manageable through the translate plugin.
Could someone look into this please?
Thx in advance,
Just a thought, but isn't it 'safer' to just use the language files provided (if provided off course) by the plugin itself instead of scanning the plugin files for translations? In this example both amnav & amforms have specific translations files, so why don't make use of those?
The text was updated successfully, but these errors were encountered: