wpcork

Hi Mário,

Thanks for your response and the complexity is caused by the user wanting to alternate between two different email addresses, where each address gets every second email.

It looks like I’m going to need to install Flamingo, which will give me access to an auto-incrementing submission ID. I can use that along with the “wpcf7_before_send_mail” hook to check if the ID is even or odd. Then the even numbers can be sent to one email and the odd numbers can be sent to the other email.

It would look something like this…

add_action( 'wpcf7_before_send_mail', 'wpcf7_change_recipient' );
function wpcf7_change_recipient($contact_form){
	$submission = WPCF7_Submission::get_instance();

	$recipient = "email_1_@emailaddress.com" //set email address

	if ($mail[_serial_number] % 2 == 0) {
	$recipient = "email_2_@emailaddress.com"  //change email address if ID is even
	}

	if($recipient) {
		$mail = $contact_form->prop( 'mail' );
		$mail['recipient'] = $recipient;
		$contact_form->set_properties(array('mail'=>$mail));
	}
}

If there’s a better way to do this, please let me know.

Hi Rogier,

I’ve updated to the latest version of your plugin (1.5.7) but I’m still seeing the error.

It looks like it’s recording visitors and page views, but is there something I can do about the error?

Thanks again,
Donal

• This reply was modified 2 years, 6 months ago by wpcork.

Hi Rogier,

Here are the errors that were displayed in the admin area. I’ve left the WP Debug enabled so that you can see the errors on the front end when you visit the site.

WordPress database error: [Specified key was too long; max key length is 1000 bytes]
CREATE TABLE wpwa_burst_statistics ( ID int NOT NULL AUTO_INCREMENT , page_url varchar(255) NOT NULL, time int NOT NULL, uid varchar(255) NOT NULL, time_on_page int, entire_page_url varchar(255) NOT NULL, page_id int NOT NULL, referrer varchar(255), browser varchar(255), browser_version varchar(255), platform varchar(255), device varchar(255), device_resolution varchar(255), session_id int, first_time_visit tinyint, bounce tinyint DEFAULT 1, PRIMARY KEY (ID), INDEX time_index (time), INDEX bounce_index (bounce), INDEX page_url_index (page_url), INDEX session_id_index (session_id), INDEX time_page_url_index (time, page_url) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci

WordPress database error: [Specified key was too long; max key length is 1000 bytes]
CREATE TABLE wpwa_burst_summary ( ID int NOT NULL AUTO_INCREMENT , date DATE NOT NULL, page_url varchar(255) NOT NULL, sessions int NOT NULL, visitors int NOT NULL, first_time_visitors int NOT NULL, pageviews int NOT NULL, bounces int NOT NULL, avg_time_on_page int NOT NULL, completed tinyint NOT NULL, UNIQUE KEY unique_date_page_url (date, page_url), INDEX page_url_date_index (page_url, date), INDEX date_index (date), PRIMARY KEY (ID) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci

Hi vupdraft,

I can see the Dropbox account owners name there. It doesn’t give me the associated email address, but it’s great that I now have a person to contact about the Dropbox account.

Thanks for your help, it’s greatly appreciated,
Donal

• This reply was modified 2 years, 11 months ago by wpcork. Reason: Marking as resolved

Hi,

I’ve found that it seemsto be Cartflows that is causing the issue, as I’ve tried updating each plugin individually and it only fails when I go above version 1.5.10 of Cartflows.

I’ve reached out the developers and we’re going to try to clarify definatively if this is a Cartflows issue or not.

That rules out the WC Stripe Gateway, so I’m going to close this topic now.

Thanks again for your help in getting this far.

Best Regards,
Donal

Hi Maykato,

I’ve rules out 1 of the three possible causes (WooCommerce 5.6.0) and I’ll be checking the other two next week, so if you don’t mind I’d like to keep this open for another few days.

-Donal

Hi Abwaita,

It could still be a problem with WooCommerce as the way I stopped the issue was…

1. I rolled back WooCommerce from 5.6.0 to 5.5.2
2. I rolled back WC Stripe Gateway from 5.4.0 to 4.4.0
3. I rolled back Cartflows plugin from 1.7.0 to 1.5.10

These were the versions that were in place a week before the failed payments issue started to appear, so it could be either of these plugins, or a combination of each.

Testing will take a while as I’ll need to change each plugin individually and I’ll post an update here if I find which plugin is causing the issue.

• This reply was modified 5 years, 1 month ago by wpcork.

Hi,

Thanks for the info, and I can reach out to Divi developers about their error.

What about the WooCommerce error…

2021-08-17T16:05:51+00:00 CRITICAL Uncaught Error: Class 'WC_Structured_Data' not found in /home/airmedica/public_html/wp-content/plugins/woocommerce/includes/class-woocommerce.php:616
Stack trace:
#0 /home/airmedica/public_html/wp-includes/class-wp-hook.php(292): WooCommerce->init('')
#1 /home/airmedica/public_html/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)
#2 /home/airmedica/public_html/wp-includes/plugin.php(484): WP_Hook->do_action(Array)
#3 /home/airmedica/public_html/wp-settings.php(560): do_action('init')
#4 /home/airmedica/public_html/wp-config.php(102): require_once('/home/airmedica...')
#5 /home/airmedica/public_html/wp-load.php(37): require_once('/home/airmedica...')
#6 /home/airmedica/public_html/wp-blog-header.php(13): require_once('/home/airmedica...')
#7 /home/airmedica/public_html/index.php(17): require('/home/airmedica...')
#8 {main}
  thrown in /home/airmedica/public_html/wp-content/plugins/woocommerce/includes/class-woocommerce.php on line 616

• This reply was modified 5 years, 1 month ago by wpcork.
• This reply was modified 5 years, 1 month ago by wpcork.