Bug: SGO Link Breaks WP Site Health Status Message
-
Good Day,
Typically, our WP Site Health Status message is “Good” as shown here.
However, when we click SGO’s “Dashboard” link and then go back to our WP Dashboard, the WP Site Health Status message breaks as shown here. This condition always forces us to either re-run Site Health or wait for the next Site Health cron to run.
The above does not occur with any other plugin, only yours.
Can you guys look into this and provide a fix?
Thank you!
-
Hello @generosus ,
I checked the reported issue but I am not able to reproduce it at my end. I even fetched a screen cast where you can see my test:
Most probably some of the other plugins in your site are conflicting with the health check. Disable all your plugins one by one, verifying the health check in your site after each disabled plugin, until you identify the problematic one.
Regards,
Plamen.M
Tech Support Team
SiteGround.comHi @plamenm,
Thank you for the quick follow up. Your test (screencast) does not include clicking the “Dashboard” link as described above.
Please click SG’s “Dashboard” link (even if a second time) then go back to Site Health. You’ll see the message breaks when you do. It only happens for that link.
Here’s my screencast: https://www.loom.com/share/5c42731e0661495398317d9ee786f4ea
Environment: All plugins deactivated, WP Cron or Real Cron, PHP 7.4 or 8.1
Please review and advise. Something ain’t right ??
Thank you!
Hello @generosus,
I followed the exact same steps you provided in the video using a fresh WordPress and my own WordPress that has some basic content. In neither application, I am able to recreate the problem as the Health Check always returns the same status. I even tested with additional loops using the different pages of our plugin and going back to the dashboard, however, the result was the same.
Unfortunately, without being able to recreate the issue consistently we cant perform any form of investigation.
Best Regards,
Simeon BoevHi @k3llanved,
I appreciate your efforts. So weird. I will reach out to SG Support (offline) for additional help.
Please leave this topic open until we have a chance to look into this in more detail and agree on what’s happening.
Thank you.
Update:
As promised, SG Support was contacted (offline) about this issue. They were able to duplicate and confirm the reported bug.
In response, Ticket No. 4266794 was generated and a temporary solution was identified. The temporary solution is to disable Memcached (within plugin and Site Tools).
As a result, other issues were also found with your plugin and have been reported in the ticket. SG Optimizer definitely needs to be fixed to solve this.
I will close this topic as “Resolved” for now with the understanding that your developers will fix the plugin.
Thank you!
Thank you for the additional information. I was also able to recreate the reported issue. I filed a report to our plugin developers. I can not provide an ETA of if or when the issue would be addressed.
With this said, my checks showed that the memcached service does not break the health of your site – the content of the site is properly being cached, despite of the warning “No information yet” on the home page. If you go to the health check’s main page,m you can see the “Good” rating there even with Memcached enabled:
/wp-admin/site-health.php
So, it seems that only the home page status is not being fetched properly. You can safely proceed with using Memcached if you decide to do so.`
Regards,
Plamen.M
Tech Support Team
SiteGround.comHi @plamenm,
I’d like to leave this topic open until a final decision has been made. Just making sure this bug (and fix) do not fall into a black hole.
Thank you!
Hello @generosus,
The case was reviewed by the Developers team and I would like to offer some additional information about the issue at hand.
Information for the health check is stored as a transient. Transients are stored into the object_cache when such is being used. ?The cache flush deletes the transients and they can no longer be accessed unless re-generated.
?In order to have the health check information generated and stored as a transient, the WP Heartbeat needs to be enabled and the Site Health screen:?wp-admin/site-health.php must be accessed. Another option for the stats to be re-generated is the cron job:?wp_site_health_scheduled_check to be executed, as you already mentioned in one of your previous replies. Still the check is being run once a week only.So instead of disabling the Memcache service, the above can be summarised as follows:
?1. To get the stats manually, you must:
? Enable Heartbeat for the admin pages.
? Once the cache is flushed, go to the admin Site Health page directly2. To get the stats automatically, you may consider creating a custom code snipped which will run the?wp_site_health_scheduled_check cron event every time the SiteGround Optimizer plugin cache is flushed.
When the cache is flushed we are calling “do_action” request which can be used for this case. The hook used is:?siteground_optimizer_flush_cache.
For the moment no modifications will be made on how the plugin is working, but we thank you for the feedback and will have this in mind for future releases.
Best Regards,
Gergana PetrovaHi Gergana,
Wow, thank you for the detailed analysis and solution options.
In response:
(1) So, I turned on Heartbeat everywhere (Admin, Posts, and Frontend) and Memcached and I’m still having the same issue. That is, when I click on SGO’s Dashboard link, the Site Health Status breaks and I keep getting the “No information yet …” message.
Again, this is not happening with any other plugin links – only yours. So, I can safely conclude that when I’m clicking on SGO’s Dashboard link, I’m clearing our cache as well (or similar). I believe that’s what needs to be fixed. Clicking on the Dashboard link should not clear any type of cache or cause the Site Health Status to break. Please try it.
(2) If you can kindly provide the code snippet mentioned above, I’ll test it to see if the Site Health Status score is generated automatically. I want to make sure the code snippet meets your coding standards. If you prefer that I contact SG Support for this, please let me know.
Thank you!
One more:
(3) Your developers’ advice (above) seems to contradict your plugin’s recommendation, which is to disable Heartbeat in the backend (Admin) — whether Memcached (Object Cache) is Enabled or Disabled.
Perhaps the tooltip for Heartbeat Optimization (WordPress Admin Pages) needs to be updated to reflect your developers’ advice.
Details: https://prnt.sc/Ypi2z-EO0z1I
Thank you!
Hello @generosus,
The code snippet has already been provided in a different thread, which I am linking bellow, for reference to other users:
Help Needed | Creating WP Filter to Purge SG Optimizer Cache
As for the advice provided by our developers, it relates to this particular case and the SiteHealth check status specifically, if one needs to obtain its stats manually while utilising Memcache.
The recommended setting for the Heartbeat in the backend, is indeed to be Disabled, as in our experience – it is not essential as a function for a larger number of WordPress websites.
Thank you for the feedback on the matter.
Best Regards,
Gergana PetrovaHi @gpetrova (et al),
I appreciate the time and effort SG Customer Support put into this.
Unfortunately, your filter did not solve the issue.
I installed the filter using Code Snippets (running in both the backend and frontend), enabled Memcached, enabled Heartbeat (Admin, 60s), cleared SGO Cache (clicked on “Purge SG Cache”), and the Site Health Status for our website did not automatically regenerate itself. Details: https://prnt.sc/-RbmEH84RahQ
Also, after generating the Site Health Status manually, the Site Health Status breaks every time I click on SGO’s Dashboard link (as initially reported). So, the bug with your link “Dashboard” remains.
Not a big issue, but definitely a bug that you guys need to address sooner or later.
Done. We all have better things to do ??
Thank you.
Hello @generosus,
Our developers will consider addressing the issue in future plugin releases.
- The topic ‘Bug: SGO Link Breaks WP Site Health Status Message’ is closed to new replies.