hykw

Thank you, I’ve found the reason, which was the browser cache.

Details:
During the recent update (on my WordPress site, not in the plugin’s logic), the assets/js/wpp.min.js file was updated. The obsolete file that was cached in the browser had pointed to /v1/. Clearing the browser cache has resolved the issue.

Since src/Front/Front.php contains logic that accesses the following outdated URL, wouldn’t it constantly trigger a deprecated warning, even when the widget is simply being called as usual?

‘ajax_url’ => esc_url_raw(rest_url(‘wordpress-popular-posts/v1/popular-posts’)),”

If I’m not misreading, according to https://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/, the maintenance has been taken over by W3 EDGE, the company which provides W3 Total Cache?

Sorry, the information was old.

• This reply was modified 2 years, 5 months ago by hykw.

Hi @hcabrera,
Thank you for your quick fix. I’ve confirmed that the issue has gone in the latest version!

• This reply was modified 7 years, 2 months ago by hykw.
• This reply was modified 7 years, 2 months ago by hykw.

c.f. https://www.ads-software.com/support/topic/broken-sql-since-wp-4-8-2/

c.f. https://www.ads-software.com/support/topic/broken-sql-since-wp-4-8-2/