Change and editing langauge for model translation not working

[jannikholsten]

Change and editing langauge for model translation not working

[daftspunk]

Hi @jannikholsten

Where does this happen, is it using a plugin?

[jannikholsten]

Hi @daftspunk

It happens in our own developed plugin (in my company).
For example, in the screenshots above for the "Datenschutz Hinweistext" field, I'm using folling code, to make it translatable:

public $implement = ['System.Behaviors.SettingsModel', '@' . \RainLab\Translate\Behaviors\TranslatableModel::class];

// map_hint_text for "Datenschutz Hinweistext"
public $translatable = ['linktext', 'map_hint_text', 'map_hint_btn_text', 'map_hint_cookie_text'];

It has worked before too.

[daftspunk]

Ok, could you confirm what October CMS version and what version of RainLab.Translate that you are using?

[jannikholsten]

Sure, I use October CMS 3.6.11 and RainLab.Translate 2.2.8

But I also just figured out, that probably I do something wrong, because with the JanVince.SmallContactForm plugin for example, everything works as expected.

[jannikholsten]

I still have the same problem.
Now I figured out, that I probably have to use the model name "Settings", then it works. My settings model called "GlobalSettings" and does not work. I need multiple settings models in my project, so I cannot rename it so "Settings" because I allreay use it for something else.

Does not work because name is "GlobalSettings":

class GlobalSettings extends Model
{
    use Validation;

    public $implement = [
        'System.Behaviors.SettingsModel',
        '@' . \RainLab\Translate\Behaviors\TranslatableModel::class];

Would work because model named "Settings":

class Settings extends Model
{
    use Validation;

    public $implement = [
        'System.Behaviors.SettingsModel',
        '@' . \RainLab\Translate\Behaviors\TranslatableModel::class];

But I need to work with "GlobalSettings", as I said before, it has already worked before with the exact same implementation.

[daftspunk]

Interesting...

Try updating to the latest spec for the Settings model, see if it helps: https://docs.octobercms.com/3.x/extend/settings/model-settings.html#model-class-definition

class GlobalSettings extends \System\Models\SettingModel
{
    public $settingsCode = 'acme_demo_settings';

    public $settingsFields = 'fields.yaml';
}