Does Form Builder only work with php?

Hi, I have built a form using your extension and am wondering if I can submit the form to my server's standard CGI form processor, FormMail.pl? In the description of the extension when I purchased the product, I didn't see any mention of PHP being required. I thought I would ask, rather than take the time to test it myself since I have already spent more time using the extension than it would have taken to hand-code it myself.

Also, I am having a problem where the form fits easly within the #content div of a CSS Sculptor page but all the fields are being pushed down to sit at the bottom of the form. It is as though there are three <p> tags within the form itself before the fields start. I know that someone in this forum had a similar issue but since my form easily sits within the div, I don't think this is the same issue. The page is 960px wide and it is a 3-column template; each side column is fixed at 179px wide. That leaves about 510px for the center column and my form is 490px but still has the unsightly void above the first field.

TIA,
John Cavanagh

it really depends on your FormMail.pl script. does it have any requirements? Does it require any of the form elements have a specific name?


To troubleshot the display issue, I will need to see the page in a browser, it is impossible to say what is wrong with out seeing the problem in context.

Yes the formmail script has 3 hidden fields, recipient; subject; redirect. The email field must be named email. It is the very standard formmail that almost every server I have ever been on uses.

Also, I had bought validation toolkit and was told this product supersedes that extension so I upgraded, but I am absolutely unable to use the extension to validate any form that was formerly able to be validated by Toolkit. It doesn't even see the form on the page. What's up with that?

Sorry I can't give you a URL for the CSS issue; I needed to actually get the form working so I just hand-coded it so I could keep the client happy. I like the concept of this extension but it feels more like beta-ware than a shipping product, particularly its inability to see hand-created forms on any pages that weren't made by form-builder itself.

You cant control the names of the form elements that CSS Form builder will create, so it will not create the forms using the correct names.


After the form is created you can rename the elements to work with your pearl script.


as for the validation, did you uninstall validation toolkit before installing css form builder?

are you using client or server side validation?

can you send a sample of one of the pages you cannot apply validation to?

A screen shot demonstrating the problem would be helpful as well.

Originally Said By: Jason Byrnes

  You cant control the names of the form elements that CSS Form builder will create, so it will not create the forms using the correct names.


After the form is created you can rename the elements to work with your pearl script.


as for the validation, did you uninstall validation toolkit before installing css form builder?

are you using client or server side validation?

can you send a sample of one of the pages you cannot apply validation to?

A screen shot demonstrating the problem would be helpful as well.  

========================================================
So the file does not need a PHP extension for the validation to work?

Yes I uninstalled validation toolkit, which of course always recognized every form and form element on a page no matter how it was named.

I am using client-side validation.

I will send a sample form that will not validate in a few days.

I had an older working form (not built with CSSFormBuilder) that the validator couldn't see. The form had an 'id=' property, but not a 'name=' property.

I had to add the 'name' property before FB validation could 'see' it - (i.e. name="form1" id="form1")

Originally Said By: neilo

  I had an older working form (not built with CSSFormBuilder) that the validator couldn't see. The form had an 'id=' property, but not a 'name=' property.

I had to add the 'name' property before FB validation could 'see' it - (i.e. name="form1" id="form1")  

Good suggestion...I'll check to be sure the form in question has a name; I know it has an ID.