Jesse Pollak

Thanks for that report @engagecommerce! Do you think there’s any chance I could have admin access to your site (or one like it that has the same issue)?

If not, would you mind letting me what host you use and anything special that you may have configured? I’m trying to reproduce this issue so I can fix it.

One more thing: off the top of my head, it looks like the switch from *displaying errors* to *logging error* may have caused Clef to start working. This makes me think that errors were being displayed somewhere, which was causing the body to not be parsed — do you think this could be possible? Could you try leaving display_errors on, and also having log errors on?

Thanks!

cc @jeremycaris – would love any help you can offer as well!

Hi, just wanted to follow up here —?any chance y’all can help us out with this information?

Thanks!

Hey y’all, thanks for posting here! This is actually a bug we are trying to track down so any help you can provide will be very much appreciated.

The most useful thing for me would actually be to get admin access to one of your sites —?if you can add me at [email protected], I can take a look.

If you can’t do that, the next best thing you would be to install Query Monitor and do a few things:

1. Visit the Clef settings page and walk through the tutorial.
2. When you see the error message, copy down the contents of the ajax message that happened directly before. Having access to the request headers and body would help me determine what exactly is going on here.

If you’d prefer, you can also achieve the above steps by using the Javascript Console to inspect the requests that are being sent.

Thank you so much for your help! If you’d prefer to work through this in private, you can also email us at [email protected] and we can get this solved.

Cheers,
Jesse

Hey David, just to confirm —?everything is working totally fine now? Can you verify whether adjusting a setting is saved?

Thanks!
Jesse

Hi David! Thank you for the bug report —?we thought we fixed this issue in the latest release.

Would you mind answering a few questions so we can try and track down what’s going on here?

* Is this your first time installing Clef on the site?
* Do you see any error messages during configuration or does everything _look_ ok?
* Do you have Clef setup on other sites and does it work OK there?

Also, if you’d send us a note at [email protected], we’d love to help hands on.

Jesse

This is fixed in 2.4.1 (about to be released!)

Accepted! It should be out in the next week.

Hey Giovani —?this is part of the core Clef product, so it’s not translated in the plugin. If you’d like to help us translate, you can go here: transifex.com/clef/clef!

Thanks!

Hi Elizabeth — it can be either! Depending on the settings you choose, you can make it so your users either have to use Clef or they can choose to enable it on their accounts.

Thanks for the heads up on the video — we’ll get that fixed ASAP.

Anything else I can help with?

Jesse

Hi sokolum, what you’re seeing here is actually the fact that users signing up with Clef already have a verified email, so they don’t need to confirm it again. Let me know if you have any questions about that.

Hi drmagoo! You can read about why this happens here. All the attacks are being blocked, it’s just that your other software is also reporting it.

Thanks!
Jesse

Hi, thanks for the feature request — we’re looking into this option!

We discussed this through our support channel and right now Simple Membership isn’t compatible with Clef.

I’m not sure —?have you given it a try and run into issues?

Can you try this guide to fix the issue?

Thanks!