michaelw90

I found a fix for this:

1. Change PHP to 7.4
2. Quick edit and save on the terms that produces the array_merge warnings.

Removed caching plugins and emptied whatever I could. Permalink refresh as well after PHP switch. Same error appears.

I tested on my local site as well and it uses xDebug which produces a bit more detail. Last lines in the error looks like this here:

The_SEO_Framework\Data\Plugin\Term::get_meta( $term_id = 32 )
array_merge( $arrays = ['doctitle' => '', 'title_no_blog_name' => 0, 'description' => '', 'og_title' => '', 'og_description' => '', 'tw_title' => '', 'tw_description' => '', 'tw_card_type' => '', 'social_image_url' => '', 'social_image_id' => 0, 'canonical' => '', 'noindex' => 0, 'nofollow' => 0, 'noarchive' => 0, 'redirect' => ''], 's:383:"s:374:"s:365:"s:356:"s:347:"a:14:{s:8:"doctitle";s:0:"";s:18:"title_no_blog_name";i:0;s:11:"description";s:0:"";s:8:"og_title";s:0:"";s:14:"og_description";s:0:"";s:8:"tw_title";s:0:"";s:14:"tw_description";s:0:"";s:16:"social_image_url";s:0:"";s:15:"social_image_id";i:0;s:9:"canonical";s:0:"";s:7:"noindex";i:0;s:8:"nofollow";i:0;s:9:"noarchive";i:0;s:8:"redirect";s:0:"";}";";";";";' )

Edit: I checked in admin and there’s definitely differences between the terms in the taxonomy. Not every term produces fatal errors. See screenshot:

• This reply was modified 8 months ago by michaelw90.
• This reply was modified 8 months ago by michaelw90.

Just to make sure I understand you correctly, do you want any users who cancelled the transaction and didn’t verify their identity to have their account deleted

No, I believe the action priorities are mixed up here. No actions should begin (like account creation, etc) before the payment has been confirmed to be made. The verification comes from your plugin and the Stripe API you’re using to make payments. No additional functionality here. Basically, this popup will open on any Norwegian site (and across eu customers for other sites). It’s called “BankID” / “Buypass”. However, if the the customer cancels the process it should function as a validation error. Like typing a wrong email address, etc.

• This reply was modified 2 years ago by michaelw90.

@forsvunnet, I believe you’re using the wrong approach here. Instead of making the newest version dependent on PHP8, I think the better option is to make it compatible? Many Woocommerce sites have more than 20-30 and more plugins active, how can you expect all of them to adhere to your plugins dependency needs? ??

• This reply was modified 3 years, 2 months ago by michaelw90.

Seems weird. We’re using PHP 7.4 and can’t update. This is the message I get: “Det er en ny versjon av Bring Fraktguiden for WooCommerce tilgjengelig, men den virker ikke med din versjon av PHP. Se detaljer for versjon 1.8.6 eller l?r mer om ? oppdatere PHP”.

I second this, you’ve already specified the font-family in the main container, there’s no need to specify deeper.. Or better yet, don’t import it at all, it will fit sites much better, as the plugin will use the theme font branding.

Nevermind, I realized now that you don’t support variable products…

Commented out post__not_in in line 112 in yith-woocommerce-bulk-product-editing -> includes -> class.yith-wcbep-list-table.php as a temporary fix:

$query_args = array(
    'post_type'           => $post_types,
    'post_status'         => 'any',
    'posts_per_page'      => $per_page,
    'ignore_sticky_posts' => true,
    'paged'               => $current_page,
    'orderby'             => $order_by,
    'order'               => !empty( $_REQUEST[ 'order' ] ) ? $_REQUEST[ 'order' ] : 'DESC'
    //'post__not_in'        => $posts_not_in
);

• This reply was modified 7 years, 4 months ago by michaelw90.

Good idea, I’ll make sure to change the selectors.

I managed to stop the modal opening by adding stopImmediatePropagation() to the event! ??

• This reply was modified 7 years, 6 months ago by michaelw90.

I’ve tried event.preventDefault(), but it doesn’t seem to make any difference.

I’m looking at the cmb2.js, could there be anything here that can change the opening of the modal?

handlers.openModal = function() {
	var selection = modal.state().get( 'selection' );
	var attach;

	if ( ! cmb.attach_id ) {
		selection.reset();
	} else {
		attach = wp.media.attachment( cmb.attach_id );
		attach.fetch();
		selection.set( attach ? [ attach ] : [] );
	}

	cmb.trigger( 'cmb_media_modal_open', selection, media );
};

// When a file is selected, run a callback.
modal
	.on( 'select', handlers.selectFile )
	.on( 'open', handlers.openModal );

// Finally, open the modal
modal.open();

Same problem on several of of our sites. Commenting to save thread.

Aha, that makes sense. Thanks Mike ??

Yes, it was the hide shipping option that did it. Kinda weird that it still displayed in Chrome though?

That was it, thank you so much Mike ??