Hi, I see there is no form stack for Source included. From a post a few years earlier, Doobox is recommended, but this has very few possibilities. I would need e. g. a list of options for the subject etc. Which forms would you recommend which include a honeypot (as I can not use recaptcha due to some GDPR things in Germany)?
Thank you
Hallo Jan,
Formsnap verwende ich sehr gerne, auch in Source Projekten. Viele Möglichkeiten, auch gestalterisch, und hat auch die honeypot Option.
Eventuell ist es ja zu viel fĂŒr deine Belange, aber ich bin sehr zufrieden damit.
GrĂŒĂe,
Tom
Danke :-)
Hi Jan, there is also Super Forms 2 from 1 Little Designer. Has Honeypot and also Rechaptcha and own safety definitions. Maybe worth a look. I donât have Formsnap so I canât compare them
Get yourself an install of Machforms setup. Seriously, once youâve got used to it youâll wonder why you ever bothered with regular RW forms.
You can setup once instance of Machforms, and create forms to embed in all your client websites. You donât need to setup a new instance for each client.
As @TemplateRepo writes. MachForms is both powerful and flexible. Plus, in these uncertain times, you can use it with whatever web design tool you choose to use.
Thanks. I always wanted to try that. But I would need to install that on the customers premise, so right now for this project I need a more comfortable stacks solution which can be deployed using the normal publishing method.
Not sure what you mean by âBut I would need to install that on the customers premiseâ but you do not need to install Machforms on the clients server. You can install it on your own, create forms for your clients, then embed those forms into the clients sites, running on their servers, if needed. It works, I do this.
When a user completes the form, the data is stored in a database on your server (where MF is installed) and a copy of it sent to the client. You can also send a copy of the submitted form to the user too.
It can even be setup so that the client can click âreplyâ and the reply is sent to the user, not the email from which it originated (which will need to be an email account hosted on the same server as the install of MF.
Seriously, this works, I do it for all my clients. Itâs flawless. And no more âfailed to sendâ messages sent from sites using php Mail.
If a user says they completed a form and sent it, but the client didnât get it, you can simply check the database. If itâs there, forward it to the client. Or, even better, you can set up the client as a user with MF, only giving them access to their form and submissions.
Using the old style of PHP Mail forms, or even forms that use SMTP, is dead. It was never particluarly reliable. MF, set up as Iâve describeds above, is 98% successful. With online forms, you really canât get better (without paying a monthly sub!).
MachForms offers a monthly subscription for $15 or a one-time fee of $99. But why would anyone choose MachForms when you can choose a versatile solution like FormSnap 4 for a one-time purchase of $50? If you need all the available stacks, thereâs a bundle for $79, also a one-time purchase. Both options allow unlimited use across multiple websites, helping you avoid the trend of ongoing monthly subscription fees. Another option is One Little Designerâs SuperForm, available for a one-time price of $30, which also allows use on unlimited sites.
Iâve used both FormSnap 3 and 4, along with SuperForm 2, extensively, and they have always worked flawlessly. I donât understand why some believe form submissions fail, because they donâtâat least not if everything is set up properly.
While FormSnap 4 certainly offers a budget-friendly, one-time purchase is a great product, MachForms may appeal to those who prioritize extensive database integration without the hassle. With MachForms, all thatâs required is the initial setup of a MySQL database. After that, MachForms handles the rest, seamlessly.
For instance, when a client needs to modify fields on an existing form or wishes to create a completely new form, they can manage this independently, without needing further technical support. This autonomy extends to the database adjustments MachForms automatically performs in the background, ensuring data integrity and system functionality with minimal intervention.
One of my clients, for example, manages multiple forms, one of which holds over 100,000 records. Over the years, theyâve frequently updated fields and have routinely developed unique forms for specific marketing initiatives. These forms are embedded directly into their blog posts and newsletters, enhancing their marketing efforts with ease. Once a campaign concludes, they can disable or completely remove the form straightforwardly. This level of flexibility and user control is a significant advantage for many businesses, especially those with dynamic and evolving data collection needs.
Thanks for all the replies. For now, I will be using a stack solution. My customers have more or less a standard contact form and not much of e-mail volumes. I also do not want to run a database on the server for these, even though MachForms will take care of the more technical issues.
â Which also means I will switch to MachForms if a client needs more than a standard form, especially for different customer groups, marketing purposes and more.
Formsnap 4 is very good - Iâm currently replacing all my Formloom forms with it. Definitely has honeypot.
Machform is excellent but only really necessary if you want to:
Hi, lots of great solutions here. I love seeing how different developers think and solve some of these fundamental problems.
Anyways, I still actively develop and support what I believe is the most versatile forms stack for most users, FormsPlus. As I continue to work on FormsPlus, Iâm always happy to hear what challenges users face and how I can take FormsPlus to the next level.
Cheers
Greg