peterjabu

Hi Han

Thanks for the message. Are you referring to the pro or free version? I checked the code for free and seems to be good although in pro there were some issues around thi – fixed

It will be on the next update

If you can just confirm the full path to the file so I can make sure

Thanks
Pete

Hi @xamad

This is solved now, WordPress is now serving the right files – please update and let me know 😀

Hi @locker17

1. The plugin currently accepts both email addresses and usernames, not ONLY emails.
2. No built-in rate limiting.

I will look at adding this in the near future. In the meantime you could use our developer hooks: https://docs.wpenhanced.com/frontend-reset-password/faq/#what-hooks-are-available

1) Something like this

add_action( 'somfrp_post_request', 'restrict_reset_to_email_only', 40 );
function restrict_reset_to_email_only( $action ) {
    if ( 'somfrp_lost_pass' !== $action ) {
        return;
    }
    
    $user_info = isset( $_POST['somfrp_user_info'] ) ? trim( $_POST['somfrp_user_info'] ) : '';
    
    // Check if it's NOT an email
    if ( ! empty( $user_info ) && ! is_email( $user_info ) ) {
        $_REQUEST['errors'] = array(
            'email_only' => __( 'Please enter a valid email address.', 'frontend-reset-password' )
        );
        // Prevent further processing by removing the default handler temporarily
        remove_action( 'somfrp_post_request', 'somfrp_lost_pass_handler', 50 );
    }
}

2) More complicated then above but we have some hooks

somfrp_post_request, somfrp_lost_pass_action, lostpassword_post

It is hard for me to support custom code but will look at implementing this for you

Sorry I was just trying to get this solved as quick as possible. I will not ask for admin logins again. Let me try debug more locally to try replicate this and get a fix

• This reply was modified 2 months ago by peterjabu.

does your user role allow you to manage posts? I added in security “manage_posts” and it’s blocking you

hey @p42webdev Implemented a fix to use our own REST API rather than WP

Please update to 1.3.1 and let me know, it has the fix