[Typo3] sr_feuser register extending form problem

[John Romano]

racco wrote:
> I added new field (thru Ext Kickstarter). But the Labels, Missing etc
> 
> <!--###SUB_INCLUDED_FIELD_tx_feusersnewfields_email_firm###-->
>  <tr>
>   <td class="register_lables">
>    <p align="right">###LABEL_TX_FEUSERSNEWFIELDS_EMAIL_FIRM### 
> ###REQUIRED_TX_FEUSERSNEWFIELDS_EMAIL_FIRM###</p>   </td>
>   <td>
>    <p>###GW2B######EVAL_ERROR_FIELD_tx_feusersnewfields_email_firm######GW2E###</p>
>    <!--###SUB_REQUIRED_FIELD_tx_feusersnewfields_email_firm###-->
>    <p>###GW2B######MISSING_TX_FEUSERSNEWFIELDS_EMAIL_FIRM######GW2E###</p>
>    <!--###SUB_REQUIRED_FIELD_tx_feusersnewfields_email_firm###-->
>    <p><input type="text" name="FE[fe_users][tx_feusersnewfields_email_firm]" 
> size="20" style="width:120"/>
>    </p>
>   </td>
>  </tr>
>  <!--###SUB_INCLUDED_FIELD_tx_feusersnewfields_email_firm###-->
> 
> What is my problem?
> EVAL_ERROR_FIELD_tx_feusersnewfields_email_firm - it was displayed on the 
> frontend just like this. So I looked into the setup and found evalValues 
> { }section. So I added my field there:
> 
> tx_feusersnewfields_email_firm = email,atMost[255]
> 
> Miracously it worked. No more 
> "EVAL_ERROR_FIELD_tx_feusersnewfields_email_firm " on the frontend, all 
> works fine.
> 
> Unfortunately I was wrong.
> 
> When I tried to use other form, which is not using my new field it didn't 
> work. When I clicked Submit on Create screen , it just returned to the page 
> with form (with all values in fields). When erased the line with my new 
> field from the setup, it worked, but now this 
> EVAL_ERROR_FIELD_tx_feusersnewfields_email_firm was on the screen again...

I had to add fields to the sr_feuser extension.   To do so, in addition 
to adding the new field through an extension as you did, also you have 
to make many mods to 
ext/sr_feuser_register/pi1/class.tx_srfeuserregister_pi1.php and 
associated changes to ext_typoscript_setup.txt, pi1/locallang.php and 
pi1/tx_srfeuserregister_pi1_tmpl.tmpl

Specifically you need to write the handlers for the new field... 
including template markers, form field evaluation and finally storage.

Simply adding the new field to the template and the setup does very 
little in attaining the goal you seek.

I hope this helps somewhat.
John Romano