Bug with [reset_link] link in reset email

Também estou com problemas para a recupera??o da password, o shortcode [wpmem_pwreset] na página de recupera??o da password n?o funciona, aparece como texto.

This is the last open bug from the 3.4.9.6 release, but I can’t seem to reproduce it. Are you sending HTML email or plain text?

@monicaoliveira8 To address your specific question, there is no such shortcode as [wpmem_pwreset]. An unknown shortcode will display as unparsed (plain text of the shortcode) because the plugin doesn’t have such a shortcode. For password reset, there is [wpmem_form password] and [wpmem_profile]. Those are the only two valid shortcodes for displaying the password reset.

• This reply was modified 1 month ago by Chad Butler.

The problem was that the query string was escaped improperly, which resulted in using an invalid entity in the URL’s query string. Fixed in version 3.4.9.7 which is now available.

I used to operate with plain text email settings, but changed to HTML email settings, which solved the problem I commented on at the top of the page.
( 3.4.9.7. did not place the problem in plain text).
I am very appreciative of your response, and I will be sure to keep you posted on how things are going.

However, I am experiencing another problem.
When I click on the reset link, go to the reset screen, enter a new password and reset, a login screen appears below the password success message, and on that login screen I get an email address (the same phenomenon occurs with user names)
and then enter a new password and press submit, I go to the password reset screen again, where I again enter a new password and press the update password button, this time I get a password update success message and the login screen does not appear. If I enter the new password on another password restriction page, this time I can enter the restriction page without any problems. (This is also happening in 3.4.9.5).
I have also tried the password reset fixed page with and without restrictions and the same situation occurs.

This is also happening in version 3.4.9.7.