Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration with WP Debug Bar #29

Closed
ejntaylor opened this issue Dec 10, 2014 · 5 comments
Closed

Integration with WP Debug Bar #29

ejntaylor opened this issue Dec 10, 2014 · 5 comments

Comments

@ejntaylor
Copy link

Currently the warning is shown:

WARNING: wp-includes/update.php:457 - An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.)
require_once('wp-admin/admin.php'), do_action('load-themes.php'), call_user_func_array, wp_update_themes, trigger_error

Would be ideal to have this integrated so this doesn't show. As currently if there are other warnings, they could go unnoticed because the Debug will always be lit up as red. Will look into integration. Perhaps as an extension.

Screenshot: https://www.dropbox.com/s/zwg5wowc1ui9ap7/Screenshot%202014-12-10%2013.18.07.png?dl=0

@norcross
Copy link
Owner

that's odd only because it should not even try to make the attempt in the first place. will need to test further to find the specific point where it's doing that.

@norcross
Copy link
Owner

I think #30 fixed this issue, can you confirm?

@norcross
Copy link
Owner

I noticed this came up again on my end, albeit a different line ( 295 on wp-includes/update.php) so it looks like the update request is still getting passed.

@johnbillion any ideas on where to address this? was thinking maybe http_request_args filter was the place but wanted your thoughts.

@norcross
Copy link
Owner

here are some screenshots on my end:

http://cl.ly/image/292x0Z1q1o1b/Image%202015-01-23%20at%209.27.49%20AM.png
http://cl.ly/image/0L0A1Y160J28/Image%202015-01-23%20at%209.27.55%20AM.png

so it looks like various parts of the update logic is being fired at different times.

@norcross
Copy link
Owner

norcross commented Apr 2, 2015

I think we finally solved this.

@norcross norcross closed this as completed Apr 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants