Cory Hughart

Oops, I see now your instructions for custom post type support. Still, the plugin should probably not prevent custom post type editing even when not explicitly told to support them.

I’ve sorted it out. I have a no-js class in my html element that for some reason is not being removed properly by my theme’s JavaScript. Removing the no-js class fixes the issue.

I’m seeing (or, rather, not seeing) the same thing. Safari (13.0.5 (15608.5.11)) is not loading any images.

No errors or output of any kind in the console. The lazyload.js file is loaded, the images src attribute have all been replaced with the placeholder.svg, and the native-lazyload-js-fallback class is applied.

Just about to update, I’ll report back in a few minutes!

EDIT: Looks good on my end. I just need to fix some of my non-gutensliders now that the styles aren’t leaking. Thanks!

• This reply was modified 5 years ago by Cory Hughart.

I’m having the same issue, here is the PHP error output:

[12-Jul-2019 18:12:11 UTC] PHP Fatal error:  Uncaught Error: Maximum function nesting level of '256' reached, aborting! in /Users/me/example.com/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php:92
Stack trace:
#0 /Users/me/example.com/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php(92): ArrayIterator->__construct(Array)
#1 /Users/me/example.com/htdocs/wp-includes/Requests/Cookie.php(229): Requests_Utility_CaseInsensitiveDictionary->getIterator()
#2 /Users/me/example.com/htdocs/wp-includes/Requests/Cookie.php(84): Requests_Cookie->normalize()
#3 /Users/me/example.com/htdocs/wp-includes/Requests/Cookie.php(423): Requests_Cookie->__construct('pardot', 'f62g94182jrlq23...', Object(Requests_Utility_CaseInsensitiveDictionary), Array, NULL)
#4 /Users/me/example.com/htdocs/wp-includes/Requests/Cookie.php(442): Requests_Cookie::parse('pardot=f62g9418...', 'pardot', NULL)
#5 /Users/me/example.com/htdocs/wp-inclu in /Users/me/example.com/htdocs/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 92

For me clicking on the link to open the Customizer just hangs/times out.

Thanks for this. For anyone else looking to fix this, download the latest release of Select2 here:

https://github.com/select2/select2/releases/tag/4.0.5

Then replace wp-notification-bars/admin/js/select2.full.min.js with the new file you downloaded (dist/js/select2.full.min.js).

Unfortunately, now the select field is way too wide for the sidebar metabox, but at least the JS error isn’t blocking the rest of the JS on the page.

@jtsternberg Than you! I have confirmed that installing CMB2 fixes the issue without having to edit the plugin code. I’ve been peppering this forum with this solution since the announcement that the plugin will no longer be supported.

Easy fix: Install the CMB2 plugin from the repository. This overrides the out-of-date version that is embedded in this plugin and fixes the error.

Easy fix: Install the CMB2 plugin from the repository. This overrides the out-of-date version that is embedded in this plugin and fixes the error.

Easy fix: Install the CMB2 plugin from the repository. This overrides the out-of-date version that is embedded in this plugin and fixes the error.

@webdevmattcrom Your embedded CMB2 includes need to be updated to at least v2.3.0, which includes compatibility fixes for PHP 7.2. Generally, the errors are along the lines of:

Fatal error: Declaration of CMB2_Type_Textarea_Code::render() must be compatible with CMB2_Type_Textarea::render($args = Array) in /Users/coryhughart/Dev/web/onx.com/htdocs/wp-content/plugins/google-maps-builder/vendor/wordimpress/maps-builder-core/includes/libraries/metabox/includes/types/CMB2_Type_Textarea_Code.php on line 13

For those waiting on this fix, I downloaded CMB2 v2.3.0 and dropped the files into the plugin at google-maps-builder/vendor/wordimpress/maps-builder-core/includes/libraries/metabox/. It would probably make sense to include a more recent version, but this was closest to the version embedded into this plugin with the PHP 7.2 fixes.

For anyone who wants to keep the customer details section (to stay consistent with old records, for example), here’s a filter that you can drop into functions.php:

/**
 * WooCommerce new order email customer details
 */
function wc_customer_details( $fields, $sent_to_admin, $order ) {
	if ( empty( $fields ) ) {
		if ( $order->get_billing_email() ) {
			$fields['billing_email'] = array(
				'label' => __( 'Email address', 'woocommerce' ),
				'value' => wptexturize( $order->get_billing_email() ),
			);
		}
		if ( $order->get_billing_phone() ) {
			$fields['billing_phone'] = array(
				'label' => __( 'Phone', 'woocommerce' ),
				'value' => wptexturize( $order->get_billing_phone() ),
			);
		}
	}
	return $fields;
}
add_filter( 'woocommerce_email_customer_details_fields', 'wc_customer_details', 10, 3 );

Thanks for the clarification, I see it now.

For anyone who wants to keep the customer details section (to stay consistent with old records, for example), here’s a filter that you can drop into functions.php:

/**
 * WooCommerce new order email customer details
 */
function wc_customer_details( $fields, $sent_to_admin, $order ) {
	if ( empty( $fields ) ) {
		if ( $order->get_billing_email() ) {
			$fields['billing_email'] = array(
				'label' => __( 'Email address', 'woocommerce' ),
				'value' => wptexturize( $order->get_billing_email() ),
			);
		}
		if ( $order->get_billing_phone() ) {
			$fields['billing_phone'] = array(
				'label' => __( 'Phone', 'woocommerce' ),
				'value' => wptexturize( $order->get_billing_phone() ),
			);
		}
	}
	return $fields;
}
add_filter( 'woocommerce_email_customer_details_fields', 'wc_customer_details', 10, 3 );

I’ve updated to 3.2.1 and also ran the database update, but I’m still no longer seeing the customer details section in new order emails.

I’m having the same problem, but my Google searches have come up empty. I’m not entirely sure if it’s this plugin’s fault, because if I do a “Quick Edit” on a page and update it, the table will also go out-of-whack in a similar manner, even with this plugin deactivated. Is anyone else experiencing this?