# Trouble with wp-discourse logins

**URL:** <https://meta.discourse.org/t/trouble-with-wp-discourse-logins/112939>\
**Category:** WordPress\
**Created:** [3월 29, 2019, 3:56오후 UTC](https://meta.discourse.org/t/trouble-with-wp-discourse-logins/112939 "2019-03-29T15:56:45Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![Frank\_Bailey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/frank_bailey/32/83927_2.png) [@Frank\_Bailey](https://meta.discourse.org/u/Frank_Bailey)\
**Post date:** [3월 30, 2019, 7:15오전 UTC](https://meta.discourse.org/t/trouble-with-wp-discourse-logins/112939/22 "2019-03-30T07:15:32Z")

</div>

> [@simon](#):
>
> For the code snippet you posted, it’s important that the  
> `/* some condition */`  
> comment is replaced with a condition. If you are going to bypass email verification for all users, you could leave out the condition and just return `false` from the function. From your description of how users are being registered on your site, it seems that would be safe for your case.

Yeah I just jammed a `return false` in there since our setup provides manual verification.

> [@simon](#):
>
> I’m a little puzzled about what has gone wrong here. If _no_ users were able to login, it would seem that your site’s user IDs have all been changed. Could something like that happen on WP Engine when updating a site from its staging environment?

I checked a few, no IDs were changed. And several of the pre-existing users including my main admin user were able to login fine. I can’t help but think we’re seeing some kind of odd emergent issue caused by… something.

---

_[View the full topic](https://meta.discourse.org/t/trouble-with-wp-discourse-logins/112939)._