I can use Form Pro for my forms that don’t require a date box, I’ve built one and tested it, and the emails are being received, but when the user (me in this case) clicks send, there is no message to say the form has been successfully sent. I’ve looked at the docs and tried the one your stacks page, and there doesn’t appear to be a confirmation message there either.
Is something going wrong or are there meant to be no confirmation messages?
EDIT: OK, worked it out. After you click to send the page jumps back to the top of the form, to the very first input box, which is the name. But, the confirmation box appears above this, off the screen. Example from your site attached.
Can you sort it, so the confirmation message is visible without requiring the user to scroll up? Cus most won’t; they’ll assume the form hasn’t worked
And if you fancy adding in a calendar box at the same time, that’d be cool
Seriously though. It’s a really nice form stack, so simple to setup. I’ve used quite a few over the years, and most really over complicate things. By default they seem to all do things that make you think “why would anyone want to set a form up like that?” You then have to dig into them to set them up as 99% of users want them (I’m assuming the 99% bit).
Forms Pro is nice, and quick, and does what you need. C’ept for me, the calendar bit
I’ve been using FormSnap (Form loom in Stacks form) for years. Its really robust, and the big advantage it has over many others is the option for MySQL input. For more complicated forms, like meeting registrations, its a real godsend.
There are a few differences between formloom and formsnap. The main one for me is that you can save form data to a Google sheet with formloom. I’m working on one now that does this and that has the results immediately show up in a grid iron table. It’s here: Game settings in Versus - the most flexible iOS scorekeeping app
The form itself appears within a foundry side bar which I think works well.
There are some issues with grid iron that I am currently speaking with support about but when those are resolved I think this will work nicely.