I’m using the Soledad theme with WordPress 6.8 and I’ve encountered the following notice on frontend pages when WP_DEBUG is enabled:
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the soledad 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.)
After inspecting the theme files, I noticed that while load_theme_textdomain() in functions.php is correctly hooked into init, some template files (e.g., archive.php) contain direct calls to __() and _e() outside of any WordPress hooks. Since WordPress 6.7, this triggers the _load_textdomain_just_in_time() warning if the domain hasn't been registered yet.
Would it be possible to wrap those template-level translations in a way that ensures the theme's textdomain is already loaded (e.g. using after_setup_theme or init)? This would help avoid confusion and maintain compatibility with the latest WP standards.
Thanks in advance, and keep up the great work on Soledad!
We’ve fixed this issue in the latest version of the Soledad theme. Please update the Soledad theme and all related plugins to the latest version, then check again.
This is a new issue related to text translation in the latest WordPress update. We're currently working on an update and will release a fix as soon as possible. In the meantime, you can hide this text by turning off WP_DEBUG mode. Please follow the instructions in the documentation at this link: https://codex.wordpress.org/Debugging_in_WordPress
Hi Penci Team,
I’m using the Soledad theme with WordPress 6.8 and I’ve encountered the following notice on frontend pages when WP_DEBUG is enabled:
After inspecting the theme files, I noticed that while load_theme_textdomain() in functions.php is correctly hooked into init, some template files (e.g., archive.php) contain direct calls to __() and _e() outside of any WordPress hooks. Since WordPress 6.7, this triggers the _load_textdomain_just_in_time() warning if the domain hasn't been registered yet.
Would it be possible to wrap those template-level translations in a way that ensures the theme's textdomain is already loaded (e.g. using after_setup_theme or init)? This would help avoid confusion and maintain compatibility with the latest WP standards.
Thanks in advance, and keep up the great work on Soledad!
Best regards,
Francesco
Hi,
We’ve fixed this issue in the latest version of the Soledad theme. Please update the Soledad theme and all related plugins to the latest version, then check again.
Regards,
PenciDesign.
We already have Soledad Theme Version 8.6.4
What we can do?! Thank you in advance.
Hi,
If your site is running on Soledad 8.6.4, please make sure you’ve also updated all the installed plugins, then check again.
Regards,
PenciDesign.
All Penci and third party plugins are up to date... !!
Any other idea?
I am facing same issue. all plugin and theme is updated and latest.
website = www.newz24india.in
Hi,
This is a new issue related to text translation in the latest WordPress update. We're currently working on an update and will release a fix as soon as possible. In the meantime, you can hide this text by turning off WP_DEBUG mode. Please follow the instructions in the documentation at this link: https://codex.wordpress.org/Debugging_in_WordPress
Regards,
PenciDesign.
this solution is not solve the issue
Hi @adverttree,
If you’re unable to turn off the debug mode, please send me your WordPress admin account details and I’ll help you configure it.
Regards,
PenciDesign.
where i send WordPress admin account details