techsurgeons

Why are you marking this as RESOLVED when it hasn’t been?

RESOLVED means the problem is fixed. You haven’t fixed this yet.

It’s been months.

-TS

Sure, will do, right after you release 2.6.2 so everyone else gets the fixed version.

2.6.2 worked for my client suffering this issue. Thanks!

-J

That would be great, thanks.

-TS

Thanks. Review updated to reflect the successful fix.

Of course we’re still having the issues, your free plugin isn’t fully compatible with PHP >=7.1.

This is an issue you’ve known about for months, and has been acknowledged in a previous support message.

I don’t have time for deflection attempts. I’ll just recommend my client find a different plugin and remove yours.

Oops, I didn’t scroll far enough back in the support history.

This is a duplicate report to: https://www.ads-software.com/support/topic/php-7-1-non-numeric-error/

Thanks Marcin (@mrsztuczkens),

It works great here, both on 5.6.x & 7.0.x.
-TS

It breaks on 7.0.x as well.

-TS

Yes, thanks. One of my team added a comment there.

-TS

Cool, thanks. I’ll relay that on.

-J

Perfect, thanks!

Thanks for the response.

HyperDB is different enough in that it mostly solves scaling problems, not availability ones. It would still be vulnerable to replication issues.

There are no duplicated tables, the error I mention is referring to the -attempted- creation of the permanent column on the wfBlocks table when it already exists.

How do you know you never saw these error messages? What DB clustering scheme did they use? And again, of all the plugins our clients run on their sites, only Wordfence has these issues.

Thanks!

s33ca: Is the payment actually going through?

We had a problem where the transaction was hanging. To fix it we went into the WP Stripe settings and clicked save.

I’m guessing the new version added some settings dependencies.

-J

P.S. Thanks Noel for a great plugin

We had this problem too. Here’s what fixed it for us.

Go into the WP Stripe settings and click save.

-J