Generated Form Field Names
Just doing some testing with the new CSS Form Builder and I noticed that when using the eCommerce templates the form fields do not match the existing form field names generated by the eCart Wizard, any reason why ?
Just doing some testing with the new CSS Form Builder and I noticed that when using the eCommerce templates the form fields do not match the existing form field names generated by the eCart Wizard, any reason why ?
We didn't have a regular syntax we used throughout eCart, DataAssist, SecurityAssist, and other products that create forms.
You can highlight and inspect a current form to populate names from an existing form.
Since we had no standard really defined we decided to define one with Form Builder and we will start using the FormBuilder naming convention moving forward when we do updates to include form builder functionality in those tools.
To replace an existing form, highlight that form before entering form builder and those existing form element names will be used for the generated form.
Ray,
I just thought it was strange that it didn't match eCart (or Powerstore for that matter) as anyone trying to use one of the generated forms in an existing site could easily get caught out as the payment processing / session variables would not fire if you didn't change those to match the new field names (and you KNOW that someone at some point is going to get caught out !)
Yes, you are correct we won't get away without criticism for someone working on their checkout form.... or the contact form, or registration form, or anything else...
We decided to take the hit now so that we can standardize moving forward rather than standardizing on inconsistant conventions to match previous forms... since we used to create forms by hand or using a variety of methods to meet the specific application we created them for.
We created the feature to inspect highlighted forms so that users could easily edit existing forms or manipulate form names manually rather than using the formbuilder naming convention, but maybe it will be a headache for us as you point out.
Fair enough Ray, for what it's worth I am happy with what I have seen in the tool so far so I look forward to the standardization process taking place.
Your friends over here at WebAssist! These Dreamweaver extensions will assist you in building unlimited, custom websites.
These out-of-the-box solutions provide you proven, tested applications that can be up and running now. Build a store, a gallery, or a web-based email solution.