New answers tagged

3

I've tried a few different approaches for verifying the user's email. For now, what I am doing is this: When a user first registers, set the user's user_metadata 'email_not_verified' to 1. add_action( 'user_register', 'sc_user_email_not_verified' ); function sc_user_email_not_verified( $user_id ) { update_user_meta( $user_id, 'email_not_verified', 1 ); } ...


2

I had a look into the wp_usermeta table and noticed the default_password_nag meta key. I checked and this was introduced in #9710 about 7 years ago. If the user has an auto generated password then it's value is 1 and she will get a notice displayed on the dashboard screen. When she first registers, default_password_nag is 1 and when she resets the ...


0

There's a lot of reasons this isn't working. The best place to to start is the Widgets API page in the Codex. It outlines a basic class for creating a widget. At a minimum, you need a class with a __construct(), widget(), form(), and update() function. You also need to register your widget correctly. The register_widget() function takes the class of the ...


2

This is not a complete answer, but it's an attempt at giving you some direction. Hopefully with the community here we can come up with a solution for you! Firstly, I've been able to replicate your issue: I took your code and placed it in my theme's functions.php for now. I removed the if( $strict ) test I tried registering an 8 character Hebrew name - it ...


1

So unfortunately without major revisions to both code and database structure this is not possible because WordPress stores the user email in a "UNIQUE" row in the database. Just unsetting the error message will not solve this issue because the user does not get created.



Top 50 recent answers are included