I populate some read only text fields in my form from a SQL lookup but they do not show in the email notification even though I have selected them from the fields droplist when configuring the email.

Any ideas?

Do you have conditionals assigned to them? You need to have them be hidden inputs or hide them with css. The form builder only submits main form fields that are showing. Using the external css allows you to bypass this because the form builder doesn't know you have them hidden.

No conditionals and they are visible. They are populated by assigning values, in fact it is the continuation of the project that you recently tested for me on your server. The only difference between the fields that are shown in my email and the ones that aren't is the fact they are marked Read Only in the properties.

Do they get passed if their not read only?

Before re-exporting a new test project I noticed a glaring difference in the text field id property (in the form.html).

Read Only text fields have a "disabled id" property whereas standard text fields have an "id" property.

So rather than go through the effort of manually editing all the php values after a fresh export, I merely changed the "disabled id" property of one text field and re-uploaded just the form.html file.

Sure enough it now sent the value in an email but it also could now be manually edited which I don't want.

So why did CoffeeCup arbitrarily decide for me that I cant have "read only" field values sent in my email? Stuff like that frustrates the heck out me when choices are taken away because someone thought it made sense.

Any ideas of a workaround?

I need to display prior purchase values to a customer without allowing him to edit them and I also need those values in the email.

Is there something I can change in one of the many php or some other file files to not disallow these fields from being emailed

Are you using an iframe to display the form? If so are you using it as is or did you remove the script wrapping it?

It is the same form that you tested for me only the text fields are now filled with data from MySQL and the URL parameter is used to drive the MYSDQL Select statement.

http://ericrohloff.com/coffeecup/ccforum/maurice-dykes/testproject/TestURL.php?lic=1234

The iframe is different from your test as shown below.

<div align="center">
<iframe width="650" height="712" style="border:none; background:transparent; overflow:hidden;" id="fb_iframe"
src="MyWFB/MyWFB.html?abc=<?php echo $email ?>&def=<?php echo $name; ?>&ghi=<?php echo $seats; ?"></iframe>
</div>

The form works just fine - all values get populated except the fields with properties of Read Only will not email their values.

Are you setting the fields read only manually? Is so try setting them with JQuery.

I'm setting Read Only using the WFB IDE.

Hmmnn I have no idea what JQuery is although I have heard its name tossed around a lot here.

Is there a hit the ground running type of tutorial I can refer to?

How would this be used to set a field Read Only?

Ah, so reading up on JQuery I found a post on Stack Overflow where a person stated that setting a form field to disabled=true converts the value to Null when submitting a form. I'm getting the impression that disabled and readonly are two different things and WFB uses the disabled tag.