<p>Bubble Under may share information you give us here with
other like-minded people or websites to promote the event.
Please confirm if you are happy for us to do this.</p>
<input type="checkbox" name="field-ZZZZZZZZZZZZZ"
id="field-ZZZZZZZZZZZZZ" value="I am happy for this
event to be publicised outside of and beyond
BubbleUnder.com where possible"/>
<label for="publicize">I am happy for this event to be
publicized outside of and
beyond BubbleUnder.com, where possible</label>
<input type="submit" value="Send Us the Info"/>
We’re almost done, but if you’re looking at the markup above and thinking, “There’s
something wrong with that,” then give yourself a well-deserved pat on the back!
What’s the problem with the previous block of markup? Earlier in the chapter, I
pointed out that each form control needs to have an associated
element islinked to the related form control with a
attribute that matches
the form control’s
attribute. By originating the form on Freedback.com, some
attributes have been created to manage the form handling, and these are
completely different from those we set earlier. There’s no working around this, so
we’ll have to accommodate these values by amending the
attribute for each
control. In the markup below, I’ve highlighted the parts that have changed (again,
the values will be unique to you, not exactly as shown below):
<form enctype="multipart/form-data" method="post"
<input type="hidden" name="acctid"
<input type="hidden" name="formid"
<input type="hidden" name="required_vars"
Forms: Interacting with Your Audience