ragrant0

Yes, I did notice the message was missing on the shop page for guests clicking the AJAX the buy button. I forgot to mention it. Thanks for fixing that!

Will let you know if I come across any other issues.

*** UPDATE – just tried it again, and the AJAX is working fine now. I might have refreshed the shop page too early before the plugin setting had updated. Slow internet!

Hi,

I followed your instructions to prevent guests from buying products. However, it doesn’t work for me. My shop page and products pages use AJAX add-to-cart buttons.

*** Do you think you could update your plugin to work with AJAX add-to-cart buttons in a future release?

But even if that could work, it is still a workaround for me.

I would rather limit purchases for guests too because my checkout requires guests to login or enter details for a new account. I understand that a more convenient purchase experience (i.e. allowing users to start shopping before being forced to create an account or login) increases sales.

Not sure if this can easily be done, but ideally, the plugin would limit guests or logged-in users from adding too many items to the cart. Lets say I sell products A, B, C, D, E, F, G, H. Guests or logged in users can only buy 3 items of a particular category in a lifetime (e.g. items C, F and G).

It would be great if a registered user is logged out and adds items C, F, G. But after the user logs in at checkout, the plugin checks their past orders and detects that they also bought item A. So their cart (current order) would carry them over the lifetime limit of 3 items, and after logging in at checkout, they would see a notice that their current order is not allowed because it would put them over the total purchase limit and that they should remove 1 item from the cart to allow the purchase to proceed.

Thanks. Will do, but I think there are no other errors.

Oh, I just found that I can update the messages myself in the plugin settings (under the ‘Messages’ tab) ??

I think the tabs aren’t obvious enough to new users as they are just a row of small text links.

Perhaps they’d be more noticeable if they were in all-caps and spaced out a bit more. Or, if you could format them into buttons using css, it would be even better.

I would also suggest changing the default heading “Email Verification Options” to “General settings”. I think the word ‘general’ would alert users that there are other settings available from the above tabs, whereas “Email verification options” sounds like those options cover everything the plugin does. That’s probably why I missed the other options available.

Thanks.

From what you say and from my testing, I understand that a page will get cached server-side whenever a visitor views the page while the plugin’s blocking function is disabled. And then anyone visiting through a VPN will still be served the cached pages, regardless of whether they clear their browser cache or not.

So, to prevent that, we just need to purge the server cache once only as soon as we reenable the blocking function.

For what it’s worth, I couldn’t replicate the caching phenomenon in Safari on iPhone

Also, please correct the sentence so that it reads: “Your activation email has been resent.” (not “resend”)

The common wisdom is: If you have a good experience, you tell 10 people; a bad one, you tell 100 (verbally or by a written review)

For all of the 134+ people (as of now) who were satisfied enough to write a five-star review, there are 40,000 people with active installations who seem to be keeping quiet.

So, after reading all the negative reviews and with a pre-installation ondemand site backup created just in case, I decided to give it a shot.

Worked perfectly for me. Glad I risked wasting 20 minutes of my life for a free plugin from an author who seems genuinely willing to offer support and resolve any issues if needed.. also for free.

Ok, thanks a lot!

Thanks, for the info on captcha for Woocommerce, but that was just an FYI.

For captcha to be useful to me, I’d need the “Manual approval” feature to work on Woocommerce’s registration form.

Do you happen to have any information on how to get that working with Woo, such that a new user doesn’t get immediately access on registering and that there is a notification to them in the form that their account is pending?

Thanks

I am guessing the Registration Honeypot isn’t added to Woo’s registration form either.

FYI, the Captcha feature doesn’t appear on Woo’s registration form either.

But I really like your plugin, so I hope it can be integrated with the Woocommerce registration form.

For the moment, I guess I could rely on the default registration form (and use the plugin LoginPress to beautify the form from the ugly WP registration form) and somehow use PHP or some plugin to add the checkbox to agree to T&C’s.

If I take care of those issues, the only remaining issue of concern would be having to rely on the URL /wp-login.php?action=register

I see. thanks!

You wrote “the row containing that IP address will still remain in the login_lockdown table in the database”.
Do you mean that the record remains in the DB but will be no longer displayed in the dashboard?