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.
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).
Being on a vacation, I can't check the option to choose a time zone format in a views block. However, here is another idea: Add the field to a layout.
Backdrop allows individual fields to...
Posted3 hours 3 min ago by Olaf Grabienski (Olafski) on:
With the help of the Backdrop office hours crew, I was able to figure out a solution that works for me.
I just added an explicit format setting to the long-text field before saving it,...
Yes, I mean something similar to Seven/Bartik/etc , but in another location. And yes, I've tried it, and it's not found. So I figured that there may have been a hook to load it or load it's...
Unfortunately the word" theme" is used in different ways. By "theme" do you mean the equivalent of Basis, Bartik, etc? (appearance themes). BTW, hook_theme has nothing to do with those...
Posted1 day 13 hours ago by Alejandro Cremaschi (argiepiano) on:
Comments
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.
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.
Ok, so basically I came up with this:
Works for profile fields, should be adaptable for other parts of the site.
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.
I think for the time being I'll just use hook_mail_alter and swap contents depending on language...
@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).
@mazze are you interested in testing https://github.com/backdrop/backdrop-issues/issues/704? I'll add notes on how to test soon.