Form reference and processes

Mass torts

Forms names usually have the pattern '{product} lawsuit'. 

I'm attempting to transition all mass tort pages to use the same form: 'Generic for Mass Torts'.  Using a feature of the Gravity Form block in the backend editor, we can add the form name so the form becomes reusable, but gets routed to the appropriate queue in Litify. Here is a screenshot of the setting in the editor to show how this can be configured.

Ad landing pages

The following forms are embedded on ad landing pages:

• PPC 2 step form Appeals

• PPC 2 step form TDIU

• PPC 2 step form DIC

If we decide to purchase ads for SSDI, the following form can be used:

• PPC 2 step form SSDI

Forms not working

Check with Chris and/or Justin to see if they changed anything.

Chris: chris.smearing@woodslawyers.com 503-583-8588

Justin: justin.weber@woodslawyers.com 

Lots of spam

• Is Akismet enabled? Make sure it is enabled on the specific form.

• Is reCAPTCHA disabled? Make sure it is not disabled on the specific form.

Akismet and reCAPTCHA are add-ons for Gravity Forms and are usually enabled by default for all forms. However, we've found some cases where we need to disable these on specific forms. Navigate to the settings for the specific form and toggle these on or off depending on the situation.

Please note that these 2 have opposite toggles. Akismet is an enable switch, while reCAPTCHA has a disable.

Troubleshooting

1. Open our site in a private or incognito window to make sure you're seeing the public version of the site. If you're currently logged into WordPress, this prevents the browser from loading the site as if you are writing or editing something.

2. We subscribe to a service called LambdaTest. You can find the login in LastPass. You can use their Real Time testing tool to test our site in a variety of browsers across desktop and mobile. I (Chris) try to test each release in Chrome and Safari on Mac and iOS as these are the most problematic versions historically. If a user reports an issue with a specific operating system in a specific browser, this tool allows you to select the exact versions.

3. Submit a form with test data to see if forms are working at all. If you don't get a confirmation of success, that's an indication that the site is not responding to submissions. This situation is very bad and most likely caused by a configuration error.

4. If the test submission goes through, you should see a confirmation displayed in place of the form. 

   1. Go to the Entries pane of the form you just submitted. Make sure it was not flagged as spam. If it is, it won't be processed and sent to Litify. If it is marked as spam, you can click 'Not Spam' and it will be processed appropriately. See screenshot below.

   2.  Login to Litify and check to see if the submission exists. This tests to make sure the submission flows from our website properly.

5. Is Akismet service working? https://automatticstatus.com/

6. Is reCAPTCHA service working? https://status.cloud.google.com/  https://downdetector.com/status/recaptcha/

7. Check for issues with Cloudflare. Our plan with WP Engine uses Cloudflare to enhance site performance globally. https://www.cloudflarestatus.com/

8. Clear the site cache; see screenshot below.

Form monitoring

Check out https://dashboard.woodslawyers.com/ to see a snapshot of the day's activity. For more information, see the forms dashboard page.

Archiving Gravity Forms

Prerequisites

SSH keys must be configured first.

API keys are required to interact with Gravity Forms on either the staging or production site. Keys are stored in a Secret vault provided by a PowerShell module. Find the file ‘setup-secrets.ps1’ on the network at: F:\Marketing Department\Website\Developer

Run this script and you should have everything you need to be able to run the actual script for archiving form entries.

Details:

• Install the required modules

• Create the default vault storage

• Set the required values for keys used in the archive script

Run the script

Open a Windows Terminal and make sure it is running a recent version of PowerShell. This has been developed with PS 7.5.1. 

Navigate to the root of the WordPress repo. The actual directory depends where you installed Local or where you cloned the repo.