Jesse Pollak

Hm, that’s very strange. Can you send me a link to one of the sites you’re having trouble on? You can also email it to me at [email protected]!

Sorry again!

Jesse

Hey Meagan! Really sorry about the issues. We shipped an update that caused problems for a small percentage of users. The latest version of the plugin (2.2.9.3) fixes the issue – can you try updating to that via FTP and seeing if it resolves the issue. Really sorry again!

Jesse

Thanks for the info Corey! We actually do something similar with our Safer Hosts program, but that’s primarily for large scale hosts. We’ll keep this in mind as we think more about smaller web designers working with clients ??

For sure, REALLY appreciate the feedback — we are going to be making it more obvious and more fun. PS, try walking through the flow the next time you go to log in (there’s a little link at the bottom of the login page) and let me know what you think, if you like ??

Hey Mary, thanks for the response, but this is actually on our end.

Corey — sorry that this was such a negative experience for you. We’re experimenting with how we can get users talking about Clef in a positive way. The prompt you saw was not an ad, just a prompt to ask you to share Clef: really sorry if that wasn’t clear. You will only ever see it once and we’re heeding your feedback internally as we think whether this is a good move for us.

If you have any other questions or concerns, please don’t hesitate to respond her or email me at [email protected].

Thanks!
Jesse
Co-founder @ Clef

Hey Rahul, how does it stop working? Do you see any errors? Feel free to email us at [email protected], we’ll be faster through that channel!

Best,
Jesse

Whoops, fixed the other syntax error! Have you gotten the firewall issue figured out?

Hey Brejen! We just fixed the syntax error in the PHP code at https://docs.getclef.com.

In terms of the error you’re seeing, I’m guessing that it has something to do with your PHP configuration not being prepared for https requests. Take a look at this Stack Overflow answer and let me know if that helps: https://stackoverflow.com/questions/1975461/how-to-get-file-get-contents-work-with-https.

Thanks!
Jesse

Mmm, that makes sense to me. I’ll add that as a note on our product board!

Thanks for the kind words ??

Thanks for the review! A couple thoughts:

* With regards to (2), we actually do block all password based logins. If you’re still seeing alerts or warnings, it’s likely because the plugin that generates those alerts or warnings is blocking the attempt *before* it gets to Clef – not much we can do about that! You can read more about that distinction here.
* In terms of the style of the login window, how can we improve it? Are you seeing this? We think it looks pretty great, but we know things can always improve ??

Thanks again for the kind words!

Hey! Just took a look at this and it looks like it’s a bug on our end. We’re shipping a fix right now and you should be good to go shortly ??

No problem — I’m here to help!

What about something like:

function my_login_redirect( $redirect_to, $request, $user ) {
    //$request = $_SERVER['REQUEST_URI'];
    return wp_get_referer();
}   

add_filter( 'login_redirect', 'my_login_redirect', 10, 3 );

Have you tried using the referrer instead of the REQUEST_URI?

Hey Sascha! What’s the error that you’re seeing? We use the normal login logic so login redirection should work as-is.