page-builder-framework
page-builder-framework copied to clipboard
mapsteps
Persistent _load_textdomain_just_in_time notice in v2.11.5
In v2.11.5 load_theme_textdomain was moved to the init hook.
We still get this notice in our error_log while debugging.
Backtrace:
Functie _load_textdomain_just_in_time werd <strong>verkeerd</strong> aangeroepen. Vertaling laden voor het <code>page-builder-framework</code> domein werd te vroeg geactiveerd. Dit is meestal een aanwijzing dat er wat code in de plugin of het thema te vroeg tegenkomt. Vertalingen moeten worden geladen bij de <code>init</code> actie of later. Lees <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Foutopsporing in WordPress</a> voor meer informatie. (Dit bericht is toegevoegd in versie 6.7.0.)
/home/customer/www/site/public_html/wp-includes/functions.php -- line 6114
/home/customer/www/site/public_html/wp-includes/functions.php -- line 6054
/home/customer/www/site/public_html/wp-includes/l10n.php -- line 1370
/home/customer/www/site/public_html/wp-includes/l10n.php -- line 1408
/home/customer/www/site/public_html/wp-includes/l10n.php -- line 194
/home/customer/www/site/public_html/wp-includes/l10n.php -- line 306
/home/customer/www/site/public_html/wp-content/themes/page-builder-framework/inc/customizer/settings/settings-general.php -- line 16
/home/customer/www/site/public_html/wp-content/themes/page-builder-framework/inc/customizer/customizer-settings.php -- line 18
/home/customer/www/site/public_html/wp-content/themes/page-builder-framework/inc/init.php -- line 36
/home/customer/www/site/public_html/wp-content/themes/page-builder-framework/functions.php -- line 252
/home/customer/www/site/public_html/wp-settings.php -- line 672
/home/customer/www/site/public_html/wp-config.php -- line 106
/home/customer/www/site/public_html/wp-load.php -- line 50
/home/customer/www/site/public_html/wp-admin/admin.php -- line 34
/home/customer/www/site/public_html/wp-admin/index.php -- line 10
As a test, commenting out some of the customizer settings, solved the problem.
// Load customizer helpers & setup.
require_once WPBF_THEME_DIR . '/inc/customizer/settings/settings-helpers.php';
require_once WPBF_THEME_DIR . '/inc/customizer/settings/settings-setup.php';
// Load customizer settings.
require_once WPBF_THEME_DIR . '/inc/customizer/settings/settings-compatibility.php';
require_once WPBF_THEME_DIR . '/inc/customizer/settings/settings-premium.php';
// require_once WPBF_THEME_DIR . '/inc/customizer/settings/settings-general.php';
// require_once WPBF_THEME_DIR . '/inc/customizer/settings/settings-blog.php';
// require_once WPBF_THEME_DIR . '/inc/customizer/settings/settings-typography.php';
// require_once WPBF_THEME_DIR . '/inc/customizer/settings/settings-header.php';
// require_once WPBF_THEME_DIR . '/inc/customizer/settings/settings-footer.php';
I suspect the culprit is the ->title() and ->label() methods of the various wpbf_customizer_ functions.
Can this be resolved?
We're unable to replicate this issue. Do you have the Premium Add-On installed and/or is this a fresh install?
Cheers, David
