Hi Nebu, That makes sense, however is there a way for WP Checkup to detect which of the two methods has been used so we have some consistency? It's a little misleading for Defender Pro to say it's disabled XML-RPC while your own tool WP Checkup says otherwise. Best Regards, Austin

Here are the relevant screenshots. Support has been enabled for the site. [image pos="0"] [attachment=1404742,131358]

Hi Adam, Thanks for your quick response! I checked out a couple of my other sites and find the statistics to be off as well. I'm unable to identify an obvious rhyme or reason for the numbers that are presented, but when I do the calculations manually the percentages and sometimes the direction (positive/negative) are inaccurate. See attached images.

Here are the two images for comparison. Each was taken from the PDF sent May 1st and then June 1st. [image pos="0"][attachment=1403654,131241]

Hi Tho Bui, I added your custom snippet to my child theme's functions.php file and confirm that it's working beautifully! I can now change the SmartCrawl settings in the Extra theme layout and the SEO homepage title shows up exactly as I expect. Thanks so much for your work on this, much appreciated! Best Regards, Austin

Hi Patrick, Thanks for your quick response, I've sent the admin login credentials to you via the contact form and look forward to your reply in due time. Best Regards, Austin

Thanks for pointing me in that direction. I tried adding the code to my child theme's functions page but got the following fatal PHP error: Fatal error: Uncaught Error: Call to undefined method Smartcrawl_OnPage::get_resolver() in /var/web/site/public_html/wp-content/themes/Extra-child/functions.php:87 Stack trace: #0 /var/web/site/public_html/wp-includes/class-wp-hook.php(286): {closure}('Home') #1 /var/web/site/public_html/wp-includes/plugin.php(208): WP_Hook->apply_filters('Home', Array) #2 /var/web/site/public_html/wp-includes/general-template.php(1040): apply_filters('pre_get_documen...', '') #3 /var/web/site/public_html/wp-includes/general-template.php(1157): wp_get_document_title() #4 /var/web/site/public_html/wp-includes/class-wp-hook.php(286): _wp_render_title_tag('') #5 /var/web/site/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array) #6 /var/web/site/public_html/wp-includes/plugin.php(465): WP_Hook->do_action(Array) #7 /var/web/site/public_html/wp-includes/general-template.php(2746): do_action('wp_head') #8 /var/web/site/public_html/wp-content/themes/Extra/header.php(33): wp_head() #9 /var/web/site/public_html/wp-inc in /var/web/site/public_html/wp-content/themes/Extra-child/functions.php on line 87 Does SmartCrawl still use the get_resolver() method? The site is hosted on WPMU Dev's servers, so if you need FTP access let me know.

Hi Adam, No worries, glad to hear a fix for the S3 libraries conflict is already in the works. In this case I was able to find a work-around, so we can close this ticket out at your convenience. Thanks again for your help! Best Regards, Austin

It happened again so I turned WP_Debug on for a second and the Contact page (and any time I try to edit a post or page in the Dashboard) spits out this error: Fatal error: Uncaught TypeError: Argument 3 passed to GuzzleHttp\Client::request() must be of the type array, string given, called in /home/100937.cloudwaysapps.com/khtjubuqva/public_html/wp-content/plugins/snapshot/lib/Snapshot/Model/Destination/aws/vendor/guzzlehttp/guzzle/src/Client.php on line 89 and defined in /home/100937.cloudwaysapps.com/khtjubuqva/public_html/wp-content/plugins/snapshot/lib/Snapshot/Model/Destination/aws/vendor/guzzlehttp/guzzle/src/Client.php:128 Stack trace: #0 /home/100937.cloudwaysapps.com/khtjubuqva/public_html/wp-content/plugins/snapshot/lib/Snapshot/Model/Destination/aws/vendor/guzzlehttp/guzzle/src/Client.php(89): GuzzleHttp\Client->request('createRequest', 'GET', 'https://api.con...') #1 /home/100937.cloudwaysapps.com/khtjubuqva/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/constantcontact/constantcontact/src/Ctct/Services/BaseService.php(69): GuzzleHttp\Client->__call('createRequest', Array) #2 /home/100937.cloudwaysapps.com/khtjubuqva/public_html/wp-conte in /home/100937.cloudwaysapps.com/khtjubuqva/public_html/wp-content/plugins/snapshot/lib/Snapshot/Model/Destination/aws/vendor/guzzlehttp/guzzle/src/Client.php on line 128 It seems the Constant Contact plugin is conflicting with Snapshot Pro. If I disable either Constant Contact or Snapshot Pro suddenly everything starts working again. I'm going to try integrating Constant Contact using the CF7 plugin instead of the official Constant Contact plugin. Addendum: Integration to Constant Contact through CF7 was successful so I'm just going to delete the Constant Contact plugin that was causing the issue. Please feel free to pass the above error along to developers in case they want to fix the conflict or find a way to gracefully handle the error.

Hi Adam, Thanks for your reply. I had previously excluded the Contacts page from being cached by Breeze and Hummingbird, but for the sake of testing I've disabled both. I also additionally disabled Varnish at the server level. I increased the WP_MEMORY to the recommended 265MB. An interesting point I noticed is that the improper page loading only happens after Snapshot runs a managed backup. If the page is broken after a backup and I disable Snapshot Pro and then re-enable Snapshot Pro the page looks fine until the next managed backup, then it breaks again. This behavior lends credence to your theory about the memory limit. I'll continue monitoring given these recent changes and will update accordingly. Best Regards, Austin