21–30 of 40 posts
Earlier quoted context omitted.
Curious to hear if you generally prefer to manage client's forms and billing through your own account or have them create their own and share credentials with you?
I think there are 2 situations: - 1 client is not technical at all - so you manage on your acc - client is ok with having their own acc, then it is much better option
Earlier quoted context omitted.
Oh then I misunderstood. Sending to in-the-loop third parties is a must. I’ve set up 1 form that goes to me directly and hundreds which go to others.
Curious to hear if you generally prefer to manage client's forms and billing through your own account or have them create their own and share credentials with you?
I would _especially_ like that the developer account gets like 3 free forms as long as clients are paying.
Earlier quoted context omitted.
Oh then I misunderstood. Sending to in-the-loop third parties is a must. I’ve set up 1 form that goes to me directly and hundreds which go to others.
Maybe just sending the confirmation without the actual message. World is transforming and sending to people who filled out the form may open the gates to spammers. What do you think?
I personally believe that sending a confirmation to the person filling out the form is a requirement, in some cases, and not having it would be a mistake.
Forms are tough! Glad ya'll are working on it.
Earlier quoted context omitted.
I think there are 2 situations: - 1 client is not technical at all - so you manage on your acc - client is ok with having their own acc, then it is much better option
That makes sense. Are you currently using something more involved, e.g. Form Spree?
Nice. I always like to see email being leveraged.
Earlier quoted context omitted.
Maybe just sending the confirmation without the actual message. World is transforming and sending to people who filled out the form may open the gates to spammers. What do you think?
I think looking at how Gravity Forms (and similar) handles this within the WP ecosystem is a helpful starting point. A lot of expectations around what a form service does and doesn't do are set by those plugins – for better or worse. I personally believe that sending a confirmation to the person filling out the form is a requirement, in some cases, and not having it would be a mistake. Forms are tough! Glad ya'll are…
I like this! I feel like I've written a half-version of this a dozen times, it's nice to see a version which is fully fleshed out. One feature request: you could likely fully remove the need for an NPM package by accepting POST requests from forms, and staple the API key in with either the URL or an —is that in the roadmap?
Is this FOSS?