Debugging eForm Report Templates That Render Wrong Data

eForm issues are not always about validation. Sometimes the form submits, but the generated report or email does not show the expected values. The original case here centered on a phone field that did not behave as expected in the report layer.

Example Field

<input type="text" name="phone" eform=":integer:1" />

Where to Look

• does the value reach $_POST correctly?
• does the eForm validation rule fit the actual user input?
• does the report template use the correct placeholder name?

In many cases the data is present, but a validation rule such as :integer:1 is too strict for real phone values that contain spaces, symbols, or formatting characters.

The practical fix is often to relax the validation rule first and only then clean the value in a reporting step.