search

umbraco / Umbraco.Forms.Issues

Public issue tracker for Umbraco Forms
30 stars 0 forks source link

Global Settings and more defined Accept entry process #617

Closed thenexus00 closed 2 years ago

thenexus00 commented 3 years ago
  1. Global Settings.

I think under Forms there should be more global settings. Anything with the main email configuration currently in the config should be brought here so people with less experience can easily manage a default global email, change and edit the email server configuration to begin with and have an area developers can add in expansion easily but also for the forms themselves.

One new feature which could sit in this area is Anti Spam controls not captcha. So right now many of the recaptcha's are bypassable and this bot human simulation spam where someone is solving a captcha for spam bots to spam and not something legit they think they are using (e.g there are mobile apps that popup a recaptcha but its actually for spam/bot use, not the app) so spam still gets through. I would like to see if you have an IP or email condition that coms through you can have an interface feature and process tool to not accept the emails if they contain .ru in the email or IP blocking.

  1. With the above and I acknowledge you can tap into the form process already I do not think it's a true step before the form is process element you can tap into with custom code. One of the next big steps to Umbraco forms I would like to see and maybe work on is having payment abilities introduced. In part a workflow to handle what happens after submission but having a proper flow process step on submission that can be more easily tapped into and managed at it's core would be great and payments is a great feature to have. 3rd Parties could create additional field types but some may be able to be integrated. This and a proper settings area where you can add in the settings for the payment (Key credentials etc) as noted in 1 can be added, code to step into the submission process to handle payment and return errors.

I ask for these to be looked at and considered because I have seen the code and examples of payments and the processes and find it all very clunky because of the current setup of forms. A lot of new solutions just skip forms and spend time and cost with custom solutions when I think it is only a stones throw away for Forms to be able to just have extensions as well as down the line built in, maybe a deal with Stripe and Umbraco as a native option and so on.

I think there is some basic stuff from Umbraco Forms to do that can open this all up a bit more to give more room for it to grow more.

umbrabot commented 2 years ago

Hiya @thenexus00,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.

For example:

@umbrabot still relevant This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face: