Ajax Text Field - Translations

J 1.7 - CB 1.7 - CB ajax field plugin 1.2

At first view, seems that strings are not translatable.
But it's not right, the problem is somewhere else.

Eg.: Placeholder Text

1. Loading the profile page, field is not translated
2. Edit the field but leaving it BLANK and save
3. Now field is translated
4. Reload the page and field is again no more translated

Strange

Confirmed your issue, in 2 locations the wrong parameter is being called and thus the default is always taking place. Have fixed for next release. All instances of the placeholder are passed through CBs language string function. If the string is translated (default string of: Click to edit) it will translate in all cases. If you change this however from within the fields parameters the default is still used during ajax reload. Below is example translations of the the field.

'Click to edit' => 'Click to edit',
'Save' => 'Save',
'Cancel' => 'Cancel',
'Click to edit...' => 'Click to edit...'

The above assumes the defaults are used and unchanged.

Great that you fixed it. When you fix something, is it possible to download the last version of the plugin, in order to not to have for next release of all. In the forge for instance?

Next release (version 1.3) has been released as of today, please upgrade and confirm if your issue is resolved as could not confirm issue with 1.3.

Thanks a lot krileon, works fine for the translations!

The last thing would be to fix the Minimum and Maximum length and the field entry:

• Max limit: if set to eg.255, field is nor stopping the entry at 255, neither giving any warning message but let us go on.
• Validation: if set to eg."Multiple words with spaces" introducing numbers will not display the warning and, when saving, it reloads the previous entry. Now if we want to re-edit, it displays (propose) the previously refused entry that we tried to introduce.

Thanks again for your work

Max limit: if set to eg.255, field is nor stopping the entry at 255, neither giving any warning message but let us go on.

Known issue for maximum input limit to be non-functional. Bug ticket on forge as follows regarding this.

forge.joomlapolis.com/issues/2698

Validation: if set to eg."Multiple words with spaces" introducing numbers will not display the warning and, when saving, it reloads the previous entry. Now if we want to re-edit, it displays (propose) the previously refused entry that we tried to introduce.

Validation still works, but just doesn't display the error. I've added a feature ticket for this as follows.

forge.joomlapolis.com/issues/2751