Hello @3ickleonerd ,
Glad you reached out, happy to help.
The answer to your translation question is on the thread you originally commented on here:
https://ww.wp.xz.cn/support/topic/loco-translate-cannot-translate-some-fields-of-givewp/
The Notice entry that is in your log files is part of a recent core update. The way translations are loaded in WordPress have been changed to align with best practices for internationalization. This shift affects how and when translation strings should be triggered, aiming to prevent potential issues that arise from loading translations too early.
That said, as the plugin ecosystem adjusts, you may encounter warning notices, with GiveWP and other plugins. Here is an example:
_load_textdomain_just_in_time was called incorrectly. Translation loading for the <PLUGIN> domain was triggered 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 /srv/htdocs/wp-includes/functions.php on line xxxx.
Our team has revised this code in the core GiveWP plugin, and will be doing the same in our add-on plugins as well.
What You Can Do to Minimize Impact
For production sites, to avoid seeing these notices disrupt frontend functionality, we recommend adding this entry to the debug section of your wp-config.php file (,unless you are actively troubleshooting another urgent issue). This prevents notices from displaying and breaking some functionalities on the frontend screens.
define( 'WP_DEBUG_DISPLAY', false );
If you need assistance with that, your web host should be able to help. Also, there is some official documentation on that: https://codex.ww.wp.xz.cn/WP_DEBUG
Please use caution when updating that file as it controls all aspects of your WordPress website’s access and functionality. This article can assist with what is in the wp-config.php file and how to safely make changes:
https://www.wpbeginner.com/beginners-guide/how-to-edit-wp-config-php-file-in-wordpress/
Also, for troubleshooting or development environments where these notices are filling up your log files, you might want to temporarily suppress these notices with the following snippet in your code snippet plugin, or functions.php or related file:
add_filter( 'doing_it_wrong_trigger_error', '__return_false' );
If you need assistance implementing custom PHP code on your website we have this guide: https://givewp.com/documentation/resources/adding-custom-functions-to-your-wordpress-website/.
Please note that this code snippet is provided as an example of how you can extend GiveWP with code. It’s up to you to implement and customize to your liking. We cannot provide support for custom code on your website, only the code that we create and distribute.
Please use caution when updating that file as it controls all aspects of your WordPress website’s access and functionality. This article can assist with what is in the wp-config.php file and how to safely make changes:
https://www.wpbeginner.com/beginners-guide/how-to-edit-wp-config-php-file-in-wordpress/
Also, for troubleshooting or development environments where these notices are filling up your log files, you might want to temporarily suppress these notices with the following snippet in your code snippet plugin, or functions.php or related file:
add_filter( 'doing_it_wrong_trigger_error', '__return_false' );
If you need assistance implementing custom PHP code on your website we have this guide: https://givewp.com/documentation/resources/adding-custom-functions-to-your-wordpress-website/.
I hope this helps to clarify! 🙂
