TYPO3 Core

add this line to the ###FORGOT_FORM### Subpart in your HTML-Template

<input type="hidden" name="tx_felogin_pi1[forgot_hash]" value="###FORGOTHASH###" />

I tried this:

add this line to the ###FORGOT_FORM### Subpart in your HTML-Template

<input type="hidden" name="tx_felogin_pi1[forgot_hash]" value="###FORGOTHASH###" />

...and it still appears to have the same behavior. I have attached the new modified template file.

Oh I see you attached felogin.tmpl.html. This did not work either. The behavior appears to be the same.

I use TYPO3 4.3.2 and it works fine... without any changes in felogin plugin....
A notice: The hidden forgot_hash field is twice at the "template.html " template file!

Thanks for the note about the duplicated hidden field, I need to pay better attention.

I tried the felogin from 4.3.2, same problem. It still uses felogin version 1.3.0. Perhaps my Web hosting does not have all of the required components installed. It must be working fine for everyone else because no one else is complaining. I downgraded my felogin extension version down to 1.0.0 (not recommended, I am not aware of the consequences) and it temporarily solves my problem until I find the real fix.

Can anyone tell me if there are any known security or compatibility issues when running felogin 1.0.0 on Typo3 4.3.1? It seems to be functioning correctly.

I have attached my phpinfo genereated from my Web server. As far as I can see it has all of the required components. I cannot see that it would be a Typo3 configuration problem when a brand new WEC install had the same problem. I guess I am going to have to step through class.tx_felogin_pi1.php again and determine the exact point of failure.

Could someone tell me each step in how the forgot password process normally flows for version 1.3.0? This will help me greatly.

I can confirm this problem. Updated one of our installation from 4.2.x to 4.3.2, FeLogin version is 1.3.0.

Did you found out some solution? I will try to locate the error myself, but some hint where to start / take a look would be very useful.

Sorry it took me so long to respond. No I did not find a solution, and I did not revisit stepping through the script yet. I am hoping someone will be able to explain the correctly working process or tell me where to find it because it will help me find the problem much easier. Unfortunately the felogin 1.3.0 code is not thoroughly commented. The temporary workaround using felogin 1.0.0 is working without any issues so far. I am currently trying to finish up a huge project and I will revisit this later.

Here is the path to the script to get started: typo3/sysext/felogin/pi1/class.tx_felogin_pi1.php

I had the same problem - the forgot password feature did not work.

We have md5 passwords enabled (Ext: kb_md5fepw). I found a bugfix in a forum which worked for me.

/typo3_src-4.3.2/typo3/sysext/felogin/pi1/class.tx_felogin_pi1.php

At line 269 change:

$newPass = $postData['password1'];
to
$newPass = t3lib_extMgm::isLoaded('kb_md5fepw')?md5($postData['password1']):$postData['password1'];

Source:
http://www.typo3-jack.net/typo3-english-lists-netfielders-de/24465-typo3-english-quick-fix-bug-forgot-your-password-ifusing-typo3-v4-3-2-felogin-kb_md5fepw.html

do not use the "kb_md5fepw" with TYPO 3 4.3 !

I have installed:
TYPO3 4.3.2
felogin 1.3
rsaauth 1.0
saltedpasswords 1.0
without "kb_md5fepw" Extension

add this line to localconf.php !?
$TYPO3_CONF_VARS['FE']['loginSecurityLevel'] = 'rsa';

this configuration works fine by me

Here in our installation without kb_md5fepw the localisation and sending of a new password does not work at all.
TYPO3 4.3.3
felogin 1.3.0

Moreover:
sr_feuser_register 2.5.25
...but this has nothing to do about this issue.

[UPDATE] Well I probably should remark that we updatetd from TYPO3 4.3.x to 4.3.3 so I had to use the new template.html.

For other people that have this issue.

1. I had this issue and it was fixed by using the new template under:

typo3/sysext/felogin/template.html

And then redoing the formatting.

Make sure you edit the felogin template and not sr_feuser_register template.

2. Go into the extension manager and then felogin. Make sure you have the hashing field added in the database and update the database if necessary.

This issue does not appear to be an open issue if you do the 2 steps above.