Posted by akarso on Thu, Oct 18, 2018 - 6:48am

Is the best way at the moment to download and port drupal 7 modules? Namely variables and internalization.

Comments

Sat, Oct 20, 2018 - 11:36am by herb

Because of the changes of variables in the database to being stored in the configuration, the i18n and variable module approach won't work easily. There is work in progress to set up an alternative (easier to implement though): https://github.com/backdrop/backdrop-issues/issues/704. Hopefully we can get it implemented not too long.

Tue, Oct 23, 2018 - 5:18am by akarso

Well, site without language versions is pretty much useless in Europe, so I have to come up with some band aid solution...

Do You think that detecting language and using separate copy of the config files would make sense?

I need to localize whole registration form, too - with twenty or more fields. Made using 'profile' module.

Wed, Oct 24, 2018 - 3:42am by akarso

Ok, so basically I came up with this:

global $language;

$lang_name = $language->langcode;
    
// translation
    
if($lang_name == 'en'){
    $form['profile_uczestnik']['field_faktura']['und']['#title'] = t(config_get('translation.pl', $form['profile_uczestnik']['field_faktura']['und']['#title'])); 
}

Works for profile fields, should be adaptable for other parts of the site.

mazze's picture

Fri, Nov 02, 2018 - 6:59am by mazze

Mmmh, this is really a weak point in BD at the moment, and it might take some time so solve... also interested in helping/reporting/reviewing.

 

 

Fri, Nov 02, 2018 - 8:34am by akarso

I think for the time being I'll just use hook_mail_alter and swap contents depending on language...

Mon, Dec 03, 2018 - 7:03pm by herb

@akarso how is the hook_mail_alter working out?

I've tested out the approach outlined in https://github.com/backdrop/backdrop-issues/issues/704 and created a pull request (patch) https://github.com/backdrop/backdrop/pull/2397 with an experiment to make the registration emails translatables. It's a harder case than some configuration since locale needs the text to be visible on the screen. So I took the approach of adding sections below the form fields which will show the translation if the interface is set to the other language.

If you're comfortable testing you can go to the sandbox and try things out and provide feedback in github (or here).