We moved to new unified forum!

Please post all new support queries in our New Forum.

T3 Community Discussion & Support

Let's build the best free Joomla template framework, together!
  1. Alvaro
  2. Sherlock Holmes
  3. General Discussion
  4. Friday, 11 December 2015
  5.  Subscribe via email
To create extra fields untranslatable I've always done the following:
create my file, template_name/etc/extrafields/extrafieldfile.xml

This Oportunity needed in 2 languages. so wrote strings of translation, but translate them into en-GB.tpl_template_name.ini. the translation is not working.

But the translation if it works when I created the file, template_name/etc/FORM/com_content.artcle.xml. even though it has only the following code:

<?xml version="1.0" encoding="utf-8"?>
<form>
</form>


The question is; this is my error? T3 error ?; or this necessarily work well?
Comment
There are no comments made yet.
Accepted Answer Pending Moderation
0
Votes
Undo
Hi,

Which extra fields are used for? for articles, menu items or modules. As for each content type, the extra fields adding process is a little bit different.

Regards.
Comment
There are no comments made yet.
  1. more than a month ago
  2. General Discussion
  3. # 1
Accepted Answer Pending Moderation
0
Votes
Undo
Extra fields are for com_content

The extra fields if they work, which is not working is translation.
example:
In myextrafields.xml
label = "EXTRA_AUTHOR_NAME_LABEL"

In en-GB.tpl_template_name.ini
 EXTRA_AUTHOR_NAME_LABEL = "Extra Name"


In my admin I still see EXTRA_AUTHOR_NAME_LABEL
But when I think the com_content.article.xml file in the etc/FORM folder, there if the translation works

But I do not need the file com_content.article.xml

So the question is: This works well? T3 error?
Comment
There are no comments made yet.
  1. more than a month ago
  2. General Discussion
  3. # 2
Accepted Answer Pending Moderation
0
Votes
Undo
Please add the language string to the file: In en-GB.tpl_template_name.sys.ini in folder: language\en-GB
The file includes languages on back-end, the file you added is for front-end.

Regards.
Comment
There are no comments made yet.
  1. more than a month ago
  2. General Discussion
  3. # 3
Accepted Answer Pending Moderation
0
Votes
Undo
Of course that's logical.

My questions are not because they can not solve; but because in some cases it works, and not in others.

Examples:

CASE 1

I think an extra field: /etc/form/com_componentname.view (view = article, product, category, item, etc.).
And translation in: /language/en-GB/en-GB.tpl_template_name.ini. The translation works perfect.

CASE 2
I think an extra field: /etc/extrafields/extrafieldgroup.xml
And translation in: /language/en-GB/en-GB.tpl_template_name.ini. The translation is not working.

For case 2, the solutions would be:
a) the translation in template_name.sys.ini. Which is incorrect and translation would not work in Front-End. And create the same translation in template_name.ini to work in front-end makes no sense.

b) create the file: /etc/form/com_componentname.view.xml. with the following code:
<?xml version="1.0" encoding="utf-8"?>
<form></form>


Note: I've seen those Joomlart make the translation to extra fields in template_name.ini; but always use the /etc/form/com_componentname.view.xml(com_content.article.xml file). I would like to do only with /etc/extrafields/extrafieldgroup.xml tests; And see if there is a solution to that little problem.
Comment
There are no comments made yet.
  1. more than a month ago
  2. General Discussion
  3. # 4
  • Page :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.