falkemediawy

I kept the variable in place and only added a default value at the beginning of the function:

	/**
	 * Load stripe site messaging script.
	 *
	 * @return void
	 */
	public static function load_stripe_bnpl_site_messaging() {
		// The messaging element shall not be shown for subscription products.
		// As we are not too deep into subscriptions API, we follow simplistic approach for now.
		$is_subscription           = false;
		$cart_contains_subscription = false; // this line is the new one :)
		$are_subscriptions_enabled = class_exists( 'WC_Subscriptions' ) || class_exists( 'WC_Subscriptions_Core_Plugin' );
		if ( $are_subscriptions_enabled ) {
				global $product;
				$is_subscription            = $product && WC_Subscriptions_Product::is_subscription( $product );
				$cart_contains_subscription = is_cart() && WC_Subscriptions_Cart::cart_contains_subscription();
		}

		if ( ! $is_subscription && ! $cart_contains_subscription ) {
			require_once __DIR__ . '/class-wc-payments-payment-method-messaging-element.php';
			$stripe_site_messaging = new WC_Payments_Payment_Method_Messaging_Element( self::$account, self::$card_gateway );
			echo wp_kses( $stripe_site_messaging->init() ?? '', 'post' );
		}
	}

• This reply was modified 1 year, 4 months ago by falkemediawy.

Apparently time solved it – the next day it worked without issues. Seemed to be an issue on Facebook’s end.

Hi David,
no there is no free version. I can send you the plugin folder but you can’t activate it because of the license. Would the plugin folder and the files be any help to you?

Thanks,
Hannah

Hi @darshanaw, changing the DB structure worked like a charm, thank you! The long emails are now visible in the log, and I don’t notice any significant performance issues.

The DB structure isn’t altered during plugin updates, correct? Or do I need to keep an eye on the right column type in the future? I suppose if I deactivate the plugin and reactivate it, that’s when I’ll need to change the data type again?

Hi,
my question has been answered. Sorry for the inconvenience. This topic can be closed.

I’ve looked a bit through the code and noticed that the instagram-settings-page is limited to the role administrator. Just a heads-up that it’s considered best-practice to make it dependant on capabilities instead, like you already did with the facebook-settings page which is limited to the manage_options capability. Would be a quick fix 🙂