- This topic has 12 replies, 3 voices, and was last updated 2 years, 11 months ago by
.
- Posts
The specific problem seems to be all the external requests so your website, https://premium.status301.com/.
Thank you. After some research we realized that Google News don’t really do much with the news meta keywords anymore: https://searchengineland.com/google-drops-support-meta-news-keywords-tag-292493
One question: could you go to Settings > Google News > License tab, then select “Check license” and hit Save, then let me know if you get an error message that says “An error occurred, please try again.”? I wonder if there is some kind of problem reaching the update server from your site…
About the plugin updates: there is one coming soon that does include some updates to the plugin self-updater routines but I’m not aware of a fix for any admin slowdown. Nor did we get any other reports about this, so that is why I wonder if there is something else going wrong.
Still, I can send you the development version if you are willing to test it. It would help us figure out if there is something that needs to be done before release 🙂
Please let me know!
Yes, meta keywords is largely ignored at this point. We kept it because it is still demanded by users…
We’re considering other features, which you can vote for here if you wish 🙂
Dear Rolf, thank you so much for your kind follow-up. Our original license expired almost exactly year ago (with no updates we didn’t see the point in updating it). When we encountered the problem with a slowdown we updated the license. And then yes, we did hit “Check license” and click “Save” and there was no error message at that stage (the old message about the expired license disappeared). We deactivated the plugin, which speeded up our site, and then activated the plugin, which slowed down our site.
We try to keep our number of plugins to a minimum so we decided to stop using Google News Advanced for now.
Indeed the distance should not be a problem.
The weird thing is that this call to our server (checking for updates) should only happen during the wp_version_check cron job for privileged users. And so it should not be able to slow down your normal admin responses at all, just like any other plugin or core update verification or auto-updates.
The DOING_CRON constant needs to be set to true for the update check to happen during normal admin browsing… IS anything other than WordPress core defining the DOING_CRON constant? Do you have some plugin running that interferes with WP_Cron maybe?
And even then, the license is only checked (the EDD_SL_License->check() in your log) once per week, and the response is then stored as transient data. Do you have a plugin that deletes transient data that has not expired yet?
So in short, two mysteries here that I cannot imagine happening on a normal WordPress installation:
1. Why would the update check happen during normal admin browsing? It should only run when DOING_CRON is true.
2. Why would the license check run more often than once a week? It should store the license status as a transient in the database.I’ll be searching further…
- You must be logged in to reply to this topic.