Hello,
So ive got a child theme with the beta theme and everything works perfectly fine when I click the preview button to see the preview of the theme. but when i click activate the translation files are not being used for the text, it is using the default translations. It is strange how it works on the preview but when i click activate child theme it goes back to the default translation. is this a bug? or have i not updated another relevant file somewhere for it to read translations in the child theme folder.

Kind Regards

@samsosclass
In same way as it is done in default theme you should try to do it in child theme.
Keep in mind that i.e. in beta, if you have function to print text like this:
__('Some text', 'beta');
_e('Some text', 'beta');

This should probably be changed into:
__('Some text', 'beta_child');
_e('Some text', 'beta_child');

As if you look here:
https://osclasspoint.com/blog/osclass-create-child-theme-b21

themename is being changed to themename_child (folder)

Next step should be to copy languages folder into child theme. Then you open .po file and in Catalog > Properties > Source paths, you ensure it's set to languages\en_US\  (or your locale ... cs_CZ, de_DE, fr_FR, ...).
Save .po file and click on Catalog > Update from source code, this will get all strings used in child themes. It should be much less than you had in original theme, as you do not copy every file from original theme.

Once done, upload new language files (.po & .mo) into child theme.

It should work now if it is done properly in core, but I think it has never been explored completely, there was never any good tutorial better than is at osclasspoint.com, you may let us know about results

Hello Im trying everything when it comes to putting the .po and .mo files in the language files but it just doesnt seem to be working when i activate the child theme

Try to identify from which file translations are taken.

I did that, i renamed every single file in core and in all themes and the original was still showing i have no idea what seems to be overiding it or using from

I have completely changed the PO and MO files in the child theme but it doesnt want to read it from there

Is there a video tutorial on this or a clear step by step for child theme translations ? because its just the translations that seem to be the problem.

@samsosclass
There is no tutorial or docs regarding child themes

What else can  try to get this working then?

Kind Regards

Because the text that i need to change in beta doesnt come from the functions, it comes from the translation files so im having to do a translation in order to change default text on the website such as the opening text above the search on the home page of beta. There doesnt seem to be another way of changing this text anywhere other than translation files. and shild theme doesnt want to listen to translation files.

hello looks like the translation files are still being used from the main beta theme file so how do i get it using the child one?

but then when child theme is activated it doesnt use either one of them by the looks of it

When I will have time, will take a look on it. There could be also problem in core.

Hello, thank you, because i cant update my beta theme which i paid for because of this at the moment.

@samsosclass
Ok I've done a lot of testing, and outcome is:
- let's consider we have sigma theme and sigma_child theme
- to make translations working properly, languages folder must be created in sigma_child
- if languages folder does not exists, osclass takes oc-content/languages folder
- to ensure osclass takes translations from child languages file, functions in php files must use domain 'sigma_child', not 'sigma'
- this means it is not possible to properly use child themes with translations (you would need to create all files and change translation domain)

This is completely missing in osclass now, to consider parent theme for child as well.
I've done some development and this will be fixed in 4.2.0 version, and will work in this way:
- first, it will load parent theme translations and apply it on everything with domain 'sigma', even it is used in child theme as well
- next, it will load child theme translations and apply it on everything with domain 'sigma_child'

This will basically merge different translation files and allow to use full potential of child themes.

I've done demo and created child for home page on sigma there
https://dev7.abprofitrade.eu/

<?php _e('All locations', 'sigma'); ?>  ---> loads translation from oc-content/themes/sigma/languages
<?php _e('All categories', 'sigma_child'); ?>  ---> loads translation from oc-content/themes/sigma_child/languages

Both used in same file main.php