Hi, @pyoungerv.
Actually, no. Anyone accessing your website should be able to access it using HTTPS.
The issue here is that the form is available over both HTTPS and HTTP. This is a fairly common issue, and the good news is that it is easily fixed.
The long version of what’s going on here: your site’s resources should load over HTTPS (using an SSL certificate). One of those files, which is critical to the operation of WordPress in general, and Give specifically, is the admin-ajax.php file. A security feature of that file is that it is not able to be executed from a different url. https://example.com and https://example.com are technically different URLs. So if a person is visiting in a browser that is on https://example.com and attempting to execute the file at https://example.com the security feature kicks in and prevents anything from happening.
The fix is to route all traffic on your site to HTTPS, and to change all instances of the HTTP version of the URL in the database to the HTTPS version. Another “gotcha” that sometimes results in frustration is that the www and non-www versions all need to be standardized, and the files should be delivered over the same version (https://www.example.com or https://example.com) that all traffic is forced over.
We have a detailed tutorial that covers these items really well. The article will walk you through the following things that are relevant to this issue:
1. the “update your Site URL” section
2. the “Force HTTPS Throughout your Site” section
3. the “Resolve insecure elements your Pages” section.
That article is here: https://givewp.com/documentation/resources/how-to-use-ssl-and-https-for-your-wordpress-website/
Let me know if you need further assistance. Thanks for using Give! Have a great day.
