# Trouble with wp-discourse logins **URL:** \ **Category:** WordPress\ **Created:** [March 29, 2019, 3:56pm UTC](https://meta.discourse.org/t/trouble-with-wp-discourse-logins/112939 "2019-03-29T15:56:45Z")\ **Posts on this page:** 1\ **Showing post:** 15
**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:** [March 29, 2019, 7:27pm UTC](https://meta.discourse.org/t/trouble-with-wp-discourse-logins/112939/15 "2019-03-29T19:27:46Z")
> [@simon](#): > > There are some upcoming changes to the [WP Discourse](https://github.com/discourse/wp-discourse) plugin that will allow WordPress admins to mark an email address as valid to handle email verification on a per-user basis. That should be good enough to deal with most cases. Hi, I’m the “WordPress guy” on this project. I figured it’d be worthwhile to jump in here and ask whether the upcoming changes could be manually added to the current version of the WP-Discourse plugin so we can get rid of this problem? On the WordPress side the registration process has not changed in any way since November 2017. We use the EONet Manual User Approve plugin, which allows users to register but not login, and on manual approval by an admin, the user is then made active and issued a password they can either continue to use, or change on first login. (I would also like to point out that the normal WordPress user system is still in use, the only change made by the EONet plugin is for the initial activation. All users that register are 100% normal WordPress users.) I have hooked into the approval process so that a user is only created in Discourse once their account is approved, so email verification should not be an issue. If there’s a way to specify that require\_activation not be turned on then that sounds like the way to solve this. --- _[View the full topic](https://meta.discourse.org/t/trouble-with-wp-discourse-logins/112939)._