Michael

I confirm the issue the status is not appended to the new_user_approve_filter querystring parameter.

Thanks for the quick reply ??

Hi Lawrence, Thank you for the quick reply.
I’m very familiar with Clef, I have been using it for quite sometimes.

My concern is there is no real way to fully logging out from a single WP without using the clef app. While it’s perfect in most use cases where the workstation is not shared, I find it dangerous on shared ones.

I was looking for a workaround the SSO, to make sure users are fully log out when they hit the logout link on wp.

I guess either I remind the user to logout on their phone if they switch workstations or I use a regular OTP for my project.

Same issue here and last update was 12 month ago.

Disabling the plugin the way sudeys mentionned it works. However, it’s a bit of pain when you need to do it on multiple websites…

Hi,

I’m also getting the same type of error when the mysqldump are occurring. So far I have experienced it on several websites and servers on cloudways, all involving wordfence tables. It’s looks like this issue has been around for a while but was never really solved.

The only solution so far was to reinstall wordfence from scratch after making sure to drop the data on the uninstall.

Of course I’m not running an outdated version of mysql…

Any idea how to prevent it?

Thanks

Michael

a big thank you ??

I agree the plugin works fine ??
I always enable the DEBUG on the dev site when testing a new plugin, this prevents surprises. So the less notices the better.
Thanks for the super quick reply !!

You can override the posts and posts-single template in templates/profile.
The post_type is customizable.

Or you can create your own tabs and load whatever you need there.

Michael

Thanks Sam for the feedback!

Hi Sam,

“we are no longer supporting new keys”, how does it affect the plugin?

thanks

Michael

It has been down for a couple of days, I wondered if it was already the end of bruteprotect as a standalone plugin…

Hi Daniel, you need to be sure that jquery.blockui.js is enqueued in the wishlist page.

I have the tendency to unload woocommerce script on non shop pages in order to reduce their payload. In this case, the wishlist page is not a shop page but still require the jquery.blockui.js plugin in order to trigger block() and unblock() functions. If not enqueued, you will get these javascript errors and won’t be able to delete the items in the wishlist.

Hope it helps.

It looks like this issue only affects registered users and rules.
It doesn’t seem to affect the product specific overrides.

Any idea how we can at least patch it for now?

Just found out that the blockUI jquery plugin wasn’t enqueued on the wishlist page generating errors on the block() and unblock() calls.
So no need to bother ??