Jim Hill

Hi Frank, thanks for responding so far, you have us spoiled with your quick response as usual.

* the last update of AO is 3 months old, did you apply the update just recently?
No, it auto-updated a day or two after the latest update came out. The logs say that was on 12/24/2020 when it went from version 2.8.0 to 2.8.1.
* you are using the “critical CSS” integration I suppose? Yes, Boris worked on that for me a month ago.
* on Settings -> Autoptimize -> Critical CSS do you see active path-based & conditional rules? How many of each? No, nothing there, just a whole bunch of jobs in the queue. Some are marked with an “E” but those are mostly when they are hacker’s php files like “/yapgb.php” and stuff like that. A few are left over URL’s from Joomla in the form /component/tags.

I can send you credentials by email if you want to look.

Me too, this is the error. Our site runs behind Sucuri, server is Litespeed.

A notice from plugin Warm-cache: Your configured sitemap url ( https://www.mysite.com/sitemap_index.xml ) is configured, but does not appear to contain an xml opening tag, or a combination of urlset or sitemap, I cannot crawl your pages. Please check your sitemap plugin to fix your currupt sitemap.
Note: this check will be cached for 2 minutes. So if you fix the problem, this notice might still be present for 2 minutes.

Error detail: WP_Error Object ( [errors] => Array ( [http_request_failed] => Array ( [0] => cURL error 60: SSL: no alternative certificate subject name matches target host name 'www.mysite.com' ) ) [error_data] => Array ( ) [additional_data:protected] => Array ( ) )

• This reply was modified 3 years, 8 months ago by Jim Hill.

This gives some guidance on pluggable errors:

https://www.wpbeginner.com/wp-tutorials/how-to-fix-pluggable-php-file-errors-in-wordpress/

@rajricki what was the fix you determine for this on your Litespeed server?

I use Admin Tools with Sucuri, alongside Modsecurity, CXS and Config Server Security on my Litespeed Server. I run only the minimal rules in Admin Tools and only have not had issues.

You guys have provided the absolute best service time after time, especially during the custom engagement you did with us. Thanks for being so prompt in your replies and for a great extension.

Yes, those are from a different source, so my error report is different. I have the same error code but coming only from Autoptimize. I will take it up with Frank on that forum. Thanks.

On my site the warning is from the “Enable jQuery Migrate Helper” plugin. I am also testing the recent changes in WordPress 5.6. Here is a screen shot of the current list from my web site:

Jquery helper screen shot

I can confirm that it is working fine on my web site. First, visit your Debounce console and do an email test there: https://app.debounce.io/single-validation

Second, be sure that you did not set a wrong CORS value in the Debounce API settings.

Once you get the test function working in WordPress, then in Gravity Forms it will validate the email once you press the form submit button. Feel free to visit my site and try it on our main contact form. https://www.ufcinc.com not hyperlinked in this post.

I an help you if you want. Ping me. jimhill10 at g mail dot com

It sure does work with Gravity Forms. Be sure that you have it configured correctly. Enter your API key in the settings, and make sure that you have a valid subscription to the Debounce API. Se the option to integrate it with Gravity Forms. Then, under WordPress admin settings, browse to the Debounce settings, then do a test using the function provided on the very bottom of that page “Validate Email Address.” Enter an email you know is valid (or not valid) and do a test there. This plugin is working just fine on my installation.

Thanks, that error went away. A new error shows now. When in the Reports section of the plugin options, an error shows in the javascript console:

Uncaught SyntaxError: Unexpected token ;
https://<sitename&gt;.com/wp-admin/admin.php?page=elastic-report:539

OK, we will install the update when it comes on Thursday. Thanks.