A step in the right direction but not complete. No mention of how UE ties in to the issue at hand.
I can see from the flow chart that CSS Form Builder is in a sense the progenitor to ContactForm Solution Pack which would explain why taking forms built in CFSP and tweaking them in CSSFB would break them.
Of this I was unaware till now.
All this is a bit confusing when the right-up on CSSFB indicates that you can create forms as well as tweaking the ones you've already made in CFSP.
That says to me…
1. Build your form in CFSP.
2. Tweak to your hearts content in CSSFB.
3. Put up your forms. Good to go.
That's clearly not the case. Maybe I missed it somewhere but UE was never mentioned as part of the process necessary to complete this goal.
And yes I did see the following questions in the FAQS…
"Will my CSS Form Builder form send an email or insert to a database?"
"Can I use CSS Form Builder to modify my existing forms?"
And the answers to both were nebulous enough so that I could infer that all the issues raised in those questions had been addressed by my use of CFSP which is the obvious purpose of that product.
This is in no way a complaint about the quality of the product. It is a complaint about it not being clear what steps are necessary to accomplish your goal.
I have no problem with taking the extra steps or the extra time to learn because I know the end result will be worthwhile but I really hate spinning my wheels and I've been doing a lot of that lately.