Miscellaneous Settings
These various site-wide settings allow you to further control and customise the way your website functions, both in the admin and on the front-end.
Access CMS controls for things like admin interface behaviours, reCAPTCHA threshold, CSS and Javascript asset control, upload folders, and GDPR settings.
Admin Panel Settings
reCAPTCHA Settings
See the external resources section for more information on reCAPTCHA V3.
This setting allows you to choose either reCAPTCHA v2 or reCAPTCHA v3 to be used on all system forms, which include:
- login form
- restore password request form
- reset password form (on ’reset-password’ system page)
- Update account form
The selected reCAPTCHA version will affect both the way the form's HTML is generated from the Component Manager and how the reCAPTCHA validation for the submit action functions.
Be sure to update the form code for all these form locations you have in use if adjusting this setting.
Enter the site key generated after registering your v2 reCAPTCHA domain with Google.
Enter the secret key generated after registering your v2 reCAPTCHA domain with Google.
Enter the site key generated after registering your v3 reCAPTCHA domain with Google.
Enter the secret key generated after registering your v3 reCAPTCHA domain with Google.
Set Up Custom reCAPTCHA Key
WebinOne allows you to add a custom Google reCAPTCHA key for any of your sites and this provides additional statistics and settings for your reCAPTCHA at an individual site level. This can be helpful for gaining better insights into the spam threats occurring on an individual site so you can make more informed decisions on combatting such spam.
Adding a custom reCAPTCHA key can also resolve issues where your site uses an unsupported domain extension for the default reCAPTCHA key provided by WebinOne.
This guide will help you configure your own Google reCAPTCHA key on your WebinOne site so that it works with all your site forms.
Requirements
In order to configure the integration you, or your client, will need to have:
- A website instance on WebinOne
- A Google Account
- A Google reCAPTCHA Site Key and Secret Key
Creating Your Google reCAPTCHA Keys
To create your Google reCAPTCHA keys visit https://www.google.com/reCAPTCHA
Click on “v3 Admin Console” at the top of the page.
(You will need to login into your google account to register Google reCAPTCHA. If you don’t have an account you will need to create one. Just follow the onscreen steps.)
Register a new site for Google reCAPTCHA
If you have no other reCAPTCHA registrations in your account, you’ll immediately see the set-up screen for a new registration.
If you already have other registrations, click the plus icon towards the top right of the page to start a new registration.
Under “Label” enter a description (which is for your reference only).
Select reCAPTCHA v3 or v2 from the reCAPTCHA type option.
- The reCAPTCHA v3 verifies the requests with a spam threshold score.
- The reCAPTCHA v2 validates the requests with a challenge and offers three methods to process the validation. (If selecting reCAPTCHA V2 select “I’m not a robot” Checkbox.)
Enter your site’s domain name(s).
Enter domain name only, ie: “mydomain.com”, all subdomains are automatically included.
Add any additional owners if required, accept the terms and submit the registration.
Get your Google reCAPTCHA Site Key and Secret Key
From the confirmation screen, copy your Site Key and Secret Key somewhere you’ll have access to them in the next step, or leave the Google reCAPTCHA tab open so you can refer back to it below.
Set up reCAPTCHA in WebinOne
Go to your WebinOne website admin (corresponding to the domain you registered the reCAPTCHA keys for), then ‘Settings’ > ‘Misc’ and down to the “reCAPTCHA Settings” and add the relevant keys from the previous step.
You don’t need both versions v2 and v3, only the version you are using on your site.
Update Form Code
Sites generated from version 6.6 or higher should not require any changes to existing forms as newly created forms will now use the Liquid tag {{this.recaptcha_sitekey}}
or {{request.system_recaptcha_sitekey}}
to populate the appropriate key.
Older sites, or sites duplicated from older trial sites, will likely require all forms to be updated with the new reCAPTCHA code.
This includes both forms you’ve created and system forms (such as; request reset password forms, reset password forms, login/out forms, etc.)
Updating the form code can be done either by resetting the form layout, inserting just the reCAPTCHA form field in the form builder layout, or replacing the default, hard-coded reCAPTCHA key with one of the Liquid tags above.
For example, for v2 reCAPTCHA:
<div class="g-recaptcha" data-sitekey="{{this.recaptcha_sitekey}}"></div>
For reCAPTCHA v3:
<script>
'use strict';grecaptcha.ready(function(){function e(a){grecaptcha.execute("{{this.recaptcha_sitekey}}",{action:'general_form_{{this.Alias | replace: "-","_"}}'}).then(function(b){document.querySelector(".g-recaptcha-response-v3-{{this.Alias}}").value=b;a&&a()})}window.customFormSubmit=new Event("customFormSubmit");let a=document.querySelector(".g-recaptcha-response-v3-{{this.Alias}}").closest("form");if(null!=a){let d=!0,b=0,c=document.getElementById("paymentFields_"+a.getAttribute("name"));a.onsubmit = function(f){f.preventDefault(); if (!a.classList.contains("form-validation-error")){if(d)return b++,d=!1,a.CMS_CustomSubmit=new Event("CMS_CustomSubmit",{cancelable:!0}),e(function(){c?"true"===c.dataset.paymentEnabled?(a.dispatchEvent(window.customFormSubmit),b=0,d=!0):a.dispatchEvent(window.customFormSubmit):(a.CMS_CustomSubmit.data={form:a},a.dispatchEvent(a.CMS_CustomSubmit))}),!1;0<b&&b++;if(1<b)return alert("Form submission is in progress."),!1}};c||a.addEventListener("CMS_CustomSubmit",function(c){ c.defaultPrevented ? (b = 0, d = !0) : a.submit()})}else e()});
</script>
<input type="hidden" class="g-recaptcha-response-v3-{{this.Alias}}" name="g-recaptcha-response-v3">
If you are updating the site's reCAPTCHA implementaion from v2 to v3, see this article for further instructions.
CMS Assets Management
When certain CMS features are initiated on a page load, additional assets may be required to allow proper functionality and/or display and these will be automatically injected into the page. However, for custom solutions, you may want to override these assets with your own and so the ability is provided here to disable them on a global level.
NOTE: These assets can also be controlled on a per template basis for more fine-grain control.
CRM Settings
Turning off the verification flow could result in fake account sign-ups and/or account abuse. Be sure to assess if this reduction in security is suitable for your secure zone implementation.