There is a PHP Notice:
Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the simple-custom-post-order domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6114.
Do you think you will fix this issue soon?
]]>There is a PHP Notice:
Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the event-manager domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6114.
Do you think you will fix this issue soon?
]]>Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-paginate domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /(redacted)/wp-includes/functions.php on line 6114
I tried using some language strings that are already present in WordPress core, but even without specifying a text domain (or when using the default), these strings are still being imported into Poedit.
Is this the correct behavior, or should I always specify a text domain for core strings in my plugin? Thanks!
]]>I wanted to let you know that I noticed an incorrect compilation of the text domain in the plugin files for some strings.
The text domain loaded by class-woocommerce-gift-cards-lite-i18n.php is woo-gift-cards-lite, but in some files the strings use the giftware text domain instead.
I noticed this because I translated some strings with the Loco Translate plugin and I didn’t see the text in the corresponding language on front-end.
At the moment I can tell you that I have identified the second giftware text domain in the class-woocommerce-gift-cards-lite-public.php file, lines 2254-2336.
I don’t know if it is used in other files too.
Temporarily, I’ve manually updated the text-domain of those strings that interest me directly in the php file.
Could you standardize the text domain – or register both – in the next plugin release? In this way the implemented translations will work effectively, and there is no risk of losing them in case of updating your plugin.
Thanks a lot, and good job again 
The “Transparent Header” string in this file does not have the text domain:
https://themes.trac.www.ads-software.com/browser/kadence/1.1.43/inc/meta/react/src/layout.js#L212
The string “sidebar” to this line also has no text domain:
https://themes.trac.www.ads-software.com/browser/kadence/1.1.43/inc/meta/react/src/layout.js#L269
Thanks.
]]>]]>
first I’d like to thank you for contributing to the WordPress eco-system.
I have a request to solve some issues I encountered using the plugin and the Italian translation:
https://translate.www.ads-software.com/projects/wp-plugins/gpt-3-ai-content-generator/dev/it/default/
The plugin is available with this plugin slot (also at the Glotpress installation that I linked before). The text domain is “wpopenai” though. Downloading the .po file from the above link and saving it as “wpopenai.po” creates the .mo-file for the PHP and two .json files for the JavaScript part, after executing:wp i18n make-mo and wp i18n make-json
So far so good.
Now my problem. The dashboard seems still not translated. I can confirm (checking with Query monitor) that the .mo-translation file has been loaded. The translation is at 100%. Do you have any idea why that page remains untranslated?
I have also a suggestion. The text domain needs to be added to the plugin header. I would also suggest changing the text domain to “gpt-3-ai-content-generator” since there is a gap between the plugin’s slug and the text domain.
Regarding this read on here, please:
https://developer.www.ads-software.com/plugins/internationalization/how-to-internationalize-your-plugin/
Cheers!
In order not to affect the parent theme, in the created file, I must reference the text-domain of my child theme, but by default it is the same as the parent theme.
How can I assign a text-domain to the child theme?
I searched for information and found the official WordPress documentation on child themes, but I don’t know how to interpret it, it is very technical language.
What are the steps to follow considering that I am not an expert girl on the subject?
Can you tell me the steps to follow without using any plugin?
Thank you
Most themes and plugins use function load_theme_textdomain() or load_plugin_textdomain().
And often with a path to a custom translation folder: load_theme_textdomain( 'my-theme', get_template_directory() . '/languages' );
In Theme Handbook and Plugin Handbook I read this:
As of version 4.6 WordPress automatically checks the language directory in wp-content for translations from translate.www.ads-software.com. This means that plugins that are translated via translate.www.ads-software.com do not require load_plugin_textdomain() anymore.
If you don’t want to add a load_plugin_textdomain() call to your plugin you should set the Requires at least: field in your readme.txt to 4.6.
Who can explain me why themes such as TwentyTwenty load a text domain, but without a path: load_theme_textdomain( 'twentytwenty' );
It’s my understanding that this function is nowadays only useful in case of loading your own custom translation? This means including a path to a custom translation folder.
Guido
]]>