Form Builder 2

Has anyone been able to create a form with Form Builder 2?

I tried using a simple contact form and the errors that are generated are impressive.

Does anyone know if the built in templates should just be avoided?

I'm having the exact opposite problem to you. I'm trying to create my own form and experiencing bug, after bug. This software is not good and needs to be fixed before being released.

Coding a form manually I can do in a matter of minutes, using Form Builder I've yet to get a single form working properly.

Originally Said By: Ian H

  I'm having the exact opposite problem to you. I'm trying to create my own form and experiencing bug, after bug. This software is not good and needs to be fixed before being released.

Coding a form manually I can do in a matter of minutes, using Form Builder I've yet to get a single form working properly.  

Ian,

Could you describe some of the specifics. I will be happy to help over the weekend until the WebAssist staff gets back in on Monday.

Regards,

Brian

For the record, I think this extension release is a massive improvement on the previous version. I am genuinely pleased that I am now able to recommend it as a (very) useful tool, having been a disgruntled harrumpher ever since the first version was released.

However, without detracting from the new extension's functionality and usefulness, I did find it a real pile of jobbies to install.

Bearing in mind that most of the problems I experience and document here turn out to be because I've done something stupid, here is my installation scenario:

I knew to uninstall the previous version of CSSFB. However, it didn't occur to me at the time to uninstall HTML Editor or Universal Email, perhaps I should have known that, but it would be helpful if that were mentioned somewhere - say right at the beginning of the guide. You only get that info once you have installed the extension, along with the message that you need to uninstall them and also uninstall CSSFB2 again.

Having done that, and having (out of habit) deleted the cache file, I tested DW CS5 to make sure it was 'clean'. It threw multiple errors, citing problems with many (oh so many) config folder WA javascript files. I couldn't fire up a new blank page in DW, as every time I clicked the 'file' menu item I had 15-20 pop up error message, each of which needed an 'OK' acknowledgement. Same with closing down DW, with particular emphasis on damaged eCart js files.

I uninstalled eCart. Back in DW, again multiple errors. Closed DW, this time multiple errors message saying (mostly) that all the Site Sculptor js files are damaged or inaccessible (or something).

Uninstalled Site Sculptor. Now I can get in to Dreamwevear, and was able to install CSSFB2.

I was able to complete the CSSFB2 process (simple one) - but DW did crash twice while I was doing it (though possibly not to do with CSSFB2, a coincidence worth mentioning, as my DW has not crashed for months).


BUT, install problems aside, this looks to be a really good tool, with everything that has been asked for here.

---------------------------

Ian,

Have had no problem apart from the install, but have only done a simple contact form (compact) Here. All seems to be fine from this end.

Neilo, thanks for pointing this out, we have added a note in the download center to alert people that Universal Email, Digital File Pro, HTMLEditor and validation toolkit will need to be uninstalled before installing CSS Form Builder 2.



Ian and jm271908,

Can you please provide some specifics on the problems that you are encountering so that we can look into them to identify the case.

Screen shots of the errors messages or links to pages demonstrating any issues will be helpful.

Jason,

I've reverted back to using Form Builder 1 for the time being. The main errors I was experiencing with Form Builder 2 were things like it wasn't applying the CSS updates in the actual file e.g. I changed a form width from say 700px to 500px, in the Wizard it would show 500px, in the actual CSS file though it would remain at 700px. If I edited the CSS file by hand and then needed to change something else in the form it would then overwrite my CSS file and revert the form back to 700px again.

I just ran a test and was not able to reproduce this.


I have found with Dreamweaver that if you use the File Inspector along the top to open a linked file like the CSS, that file wont get updated unless you close Dreamweaver.

It doesn't seam to have this issue if you open the file directly from the file panel.

one way you can prevent Form builder from overwriting changes is to create a second css file and add the link to it after the link to the form builder css. use this second file to over ride form builder css settings.

Jason,

You mention using a 2nd CSS file to get round the issue of Form Builder overwriting my CSS, but wouldn't that mean I'd have to create CSS rules that were given the same name as Form Builder in order for the page to pick up the styles? That's time consuming (Having to go through each style, find the the ones that were relevant to my form, because not all of them are) and then write my own rules for them.

I'm not trying to argue for arguments sake here. I believe the product would be a million times better if it didn't simply create a new version of the form each time you made a change, overwriting everything. I'm hoping this factor will be considered for future releases, it would make the extension so much better.

You are already going through the css to make changes.

All I'm suggesting is that rather than make the change directly in the file that will be overwritten, take the extra step of copying that css rule to another css file and make the change there.

This does not seam like a lot of extra work to me, but perhaps e are talking about differant things?

Yeah I see what you're saying now. That's something I will consider doing in the future. Thanks for your help/advice.