derekakelly

How would that work if the customer’s role isn’t changed until after they place an order and start their subscription?

Thanks for your prompt support!

I look forward to trying the new version.

Yes, that is correct.

Their reply:

Bora (Cloudflare)
Dec 24, 7:03 AM PST
Hi Derek,
First of all please accept our apologies for the delay in responding to you. We are experiencing an unprecedented demand for our Free service which is causing delays for our Free customers.
We have plans to update our plugin but for now, there’s no ETA on when this will happen. I do apologize for the inconvenience.
I will recommend that to remove the Cloudflare WordPress plugin if you wish to upgrade PHP.
There’s no need to use Cloudflare WordPress Plugin for Cloudflare features to work.
Please let me know if you have any questions regarding this ticket.
Kind regards
Bora | Cloudflare
Support Engineer
Join the Cloudflare Community

• This reply was modified 5 years, 11 months ago by derekakelly.

I am also getting this fatal error. I also have not upgraded to WP5 yet.

I have tested this with php 7.0, 7.1, 7.2 & 7.3

The first thing I noticed is that it breaks my list of plugins when using 7.1+, so i reverted back to 7.0

I have started a thread on their github in hopes of getting their attention.

https://github.com/cloudflare/Cloudflare-WordPress/issues/228

I am also seeing these warnings. When can we expect this to be fixed?

It was loaded through a shortcode from my theme.

Ohh the irony that you use mailchimp and not mailpoet for your list.

I am also anxiously awaiting the updated version of this plugin. I appreciate all of your hard work!

@wfalaa Sorry for not getting back to you sooner, but I’ve got a lot on my plate. ANYWAYS!

I contacted my help desk asking them to update that setting and I got the following reply.

Hello Derek,

Thank you for contacting our Help Desk.

max_long_data_size was removed in MySQL 5.6 and replaced by max_allowed_packet, as you are probably aware, your server is currently running MySQL 5.6.

Thus, I have increased the value of max_allowed_packet from 16М to 64М.

I however am now getting this error.

Error finishing writing value for wfsd_engine (MySQLi error: [1118] The size of BLOB/TEXT data inserted in one transaction is greater than 10% of redo log size. Increase the redo log size using innodb_log_file_size.)

So i assume i should do as the error states and have them increase innodb_log_file_size?

• This reply was modified 7 years, 9 months ago by derekakelly.

I had them check the configuration of these variables in the MySQL configuration file on the server. The value of max_allowed_packet is 16M.

As for max_long_data_size, there is no value specified for it.

However, if you provide us with the exact values, we will gladly apply the changes on the server.

I too am getting this error, I have sent you an email as well.

@bcworkz

Thanks for your reply. I relayed your message to my hosting provider and this was their response.

In your post, you mention that you run another website from the same account that does not generate said issue. This clearly indicates that the problem is not with the server setup. It could be a conflict between the website’s settings and the server, but without being able to replicate the issue, it is hard to confirm. If you have noticed any particular pattern when the error occurs, let us know.

I’ve re-enabled debug logging on my other website to re-confirm that my other website is not experiencing the same issue. I’ll post again next week.

Thanks and Happy Holidays!
-Derek

With this particular site, it’s an ecommerce site and people sign up as part of the checkout process. I use the woocommerce mailpoet addon. Because of this, we don’t force users to confirm their email.

This has not occurred again since I last posted here. I will report back if I find anymore errors.

Thanks,
Derek