? Success

User tests: Successful: Unsuccessful:

avatar infograf768
infograf768
23 Jan 2017

See discussion here:
#13659
and here
#13666

This patch adds to the translation the type itself as it is used in the field.

We now should get a dropdown like this when choosing a field type:
screen shot 2017-01-23 at 16 55 40

In French we will get stuff like this ( did not change all ini yet)
screen shot 2017-01-23 at 17 10 58

avatar infograf768 infograf768 - open - 23 Jan 2017
avatar infograf768
infograf768 - comment - 23 Jan 2017
avatar rdeutz rdeutz - change - 24 Jan 2017
Milestone Added:
avatar infograf768 infograf768 - change - 24 Jan 2017
Status New Pending
avatar infograf768 infograf768 - change - 24 Jan 2017
Category com_fields Language & Strings Plugins
avatar infograf768
infograf768 - comment - 24 Jan 2017

@mbabker

Looks like we have issues again with test not displaying here.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/13710.

avatar marrouchi
marrouchi - comment - 24 Jan 2017

I have tested this item successfully

(I did have issues while confirming the test on issues.joomla.org)

avatar AlexRed
AlexRed - comment - 24 Jan 2017

I have tested this item successfully

avatar infograf768 infograf768 - change - 24 Jan 2017
Status Pending Ready to Commit
avatar infograf768
infograf768 - comment - 24 Jan 2017

rtc. thanks for testing


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/13710.

avatar laoneo
laoneo - comment - 24 Jan 2017

Just for the record, I don't think this is a good idea. Showing technical details to the end user is for me wrong. And what happens when a field has a strange name which makes sense for developers but not end users?

avatar mbabker mbabker - alter_testresult - 24 Jan 2017 - AlexRed: Tested successfully
avatar mbabker mbabker - alter_testresult - 24 Jan 2017 - marrouchi: Tested successfully
avatar infograf768
infograf768 - comment - 24 Jan 2017

And what happens when a field has a strange name which makes sense for developers but not end users?

If a field has a strange name, it will be shown between parenthesis and in the Type list.
The developper using a "strange name" may want, to be understood correctly, create a string value which has a meaning for the end user.

PLG_FIELDS_IDIOTICNAME_LABEL= "Totally idiotic name (%s)"
=> Totally idiotic name (idioticname)
or
PLG_FIELDS_POCAHONTAS_LABEL= "Disney Tribe (%s)"
=> Disney Tribe (pocahontas)

avatar Bakual
Bakual - comment - 24 Jan 2017

ust for the record, I don't think this is a good idea. Showing technical details to the end user is for me wrong. And what happens when a field has a strange name which makes sense for developers but not end users?

On the other hand, this encourages developers to NOT use strange names. ?

avatar infograf768
infograf768 - comment - 25 Jan 2017

@rdeutz
Please merge. Thanks

avatar rdeutz rdeutz - change - 25 Jan 2017
Status Ready to Commit Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2017-01-25 07:34:02
Closed_By rdeutz
avatar rdeutz rdeutz - close - 25 Jan 2017
avatar rdeutz rdeutz - merge - 25 Jan 2017
avatar joomla-cms-bot joomla-cms-bot - change - 25 Jan 2017
Category com_fields Language & Strings Plugins Administration com_fields Language & Strings

Add a Comment

Login with GitHub to post a comment