falkemediawy

We also experience the same issues on version 6.6.5 – we noticed something is wrong when we received a white screen everytime we tried so save something. Log says “Cannot modify header information – headers already sent”

Thank you for the quick fix @adamkheckler !

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 3 months, 2 weeks ago by falkemediawy.

Hi,
I don’t want to post our customer websites publicly. Can we continue to communicate by email?

Thanks,
Hannah

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

Hi David,
German Market informed me that a hook with one parameter that actually expects two is causing the issue. As of the next update, there will no longer be any critical errors as they said.
I mark the topic now as resolved. Thanks for your help.

Hannah

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

Thank you @darshanaw and @dpinson for figuring out a solution so quickly for me! Have a nice day!

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?

Thank you, David! Apart from this issue I’m fine and have been using the plugin for years now with no problems ?? Thank you for your great work! I’m looking forward to your response!

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

Thank you for your quick response! That answers all of my questions ??

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 ??

Hi @jarnovos,
I didn’t receive an email from your colleague.
The infinite refresh occurs without the [falke_facebookteaser] shortcode and blocking our falkeScript.js too.
I have now adjusted the code so that our javascript on the page is not loaded at all. The problem still occurs.

Kind regards

Hi @kimvdijk,

I haven’t received an answer from your colleague yet. Were you able to locate the problem?

Kind regards