You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PHP Notices are triggered during plugin initialization. This issue should focus on fixing notice coming from setting Jetpack Config.
Describe the bug
Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the <code>woocommerce</code> 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 <code>init</code> action or later. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in .../wp-includes/functions.php on line 6114
To Reproduce
WP 6.7.0.
Other language the EN
wp-config.php -> define('WP_DEBUG',true);define('WP_DEBUG_DISPLAY',true);@ini_set('display_errors',0);define('SCRIPT_DEBUG',true);
Actual behavior
Open any page
Desktop (please complete the following information):
Internal investigation results by @mordeth (paJDYF-fWD):
The first instance occurs during the initialization of the Jetpack WooPayments configuration, specifically the custom content property, which includes localized strings. This needs to be hooked into plugins_loaded with priority 1 because Jetpack-config initializes modules on plugins_loaded with priority 2.
The text was updated successfully, but these errors were encountered:
This issue is the second part of #9727
PHP Notices are triggered during plugin initialization. This issue should focus on fixing notice coming from setting Jetpack Config.
Describe the bug
To Reproduce
wp-config.php -> define('WP_DEBUG',true);define('WP_DEBUG_DISPLAY',true);@ini_set('display_errors',0);define('SCRIPT_DEBUG',true);
Actual behavior
Open any page
Desktop (please complete the following information):
Additional context
debug.log
Internal investigation results by @mordeth (paJDYF-fWD):
The text was updated successfully, but these errors were encountered: