# wp-discourseのログインで問題が発生しています

**URL:** https://meta.discourse.org/t/trouble-with-wp-discourse-logins/112939
**Category:** WordPress
**Created:** [2019 年 3 月 29 日午後 3:56 UTC](https://meta.discourse.org/t/trouble-with-wp-discourse-logins/112939 "2019-03-29T15:56:45Z")
**Posts on this page:** 3
**Page:** 2

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [2019 年 3 月 29 日午後 8:00 UTC](https://meta.discourse.org/t/trouble-with-wp-discourse-logins/112939/21 "2019-03-29T20:00:02Z")

</div>

That’s great it’s working! 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.

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?

---

<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: [2019 年 3 月 30 日午前 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.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [2019 年 4 月 29 日午前 7:15 UTC](https://meta.discourse.org/t/trouble-with-wp-discourse-logins/112939/23 "2019-04-29T07:15:34Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

[Previous page](https://meta.discourse.org/t/trouble-with-wp-discourse-logins/112939.md?page=1)
