Invalid Brizy News URL in Dashboard Widget Causing Timeout

Brooke .

• January 07, 2022 19:08
• Edited

The Dashboard widget that it shown within WP-Admin on dashboard.php is trying to get the most recent Brizy news data from the blog. However, it appears blog has been migrated away from WordPress to the Brizy cloud.

Whatever the case is, the current URL returns a 404 and thus adding a 5 second load time (the default timeout) for loading wp-admin/dashboard.php.

 

$ curl -Is https://www.brizy.io/index.php/wp-json/wp/v2/posts?categories=6 | grep "HTTP/2"
HTTP/2 404

 

This call can be found on Line 61 of admin/dashboard-widget.php

 $request = wp_remote_get( 'https://www.brizy.io/index.php/wp-json/wp/v2/posts?categories=6' );

In addition to updating the REST endpoint, I would recommend setting the timeout to less than 5 seconds if possible.

Thanks!

 

0

• 

  Permanently deleted user

  • January 10, 2022 10:25
  • Edited

  Hi Brooke,

  Sorry for the late reply, support is limited on weekends.

  Please check this error: check this error: curl 28, also, please see this article and this one, it will help you to solve the issue.

  Best regards, Nelea.

   

  0
• 

  Brooke .

  • January 10, 2022 16:25

  Hi there,

  I'm actually quite familiar with cURL, that is not the problem in this case. If you visit https://www.brizy.io/index.php/wp-json/wp/v2/posts?categories=6 in your browser you will get a 404 response. Looking at the Brizy codebase I don't see any specific headers being sent to ensure the JSON response comes back into the Dashboard Widget.

  The most likely case here is that the Brizy Blog content has moved and the URL within the WordPress plugin's Dashboard Widget will need to be updated or removed depending on if there is still an API for the relocated blog.

  Happy to provide additional details, but I believe  this is a bug across all instances of the Brizy WordPress installs regardless of hosting or cURL setup. Happy to be shown otherwise, but the 404 coming from brizy.io is not encouraging.

   

  Thanks!

  0
• 

  Natalia Chitoroaga

  • January 12, 2022 15:58

  Hi Brooke,

  Yes, you are absolutely right. It is an issue from our side. Apologizes for confusing you. 

  One of our developers is already working on this problem. Will keep you updated.

   

  Thank you!

  Natalia

  0

Please sign in to leave a comment.