Error 1 with no description

Hi Haydn,

Sorry to hear you are having problems with our plugin.

The error code 1 means that WP generated an error through its HTTP API, and failed to make the HTTP request. I will look into why there is no description, as without it there is not much use to the error log and WP should be generating one.

It would ‘appear’ that WordPress is having problems making HTTP requests, which uses cURL if installed or falls back to other methods if not.

I will have a think about this could be and fix the error description problem, as that would really help in this situation.

Thank you very much for taking the time to let us know about the problems. I will come back to you once I know more.

Hi Peter,

I have used your plugin before and it works great which is why I was surprised to see it not working. It turns out that it is a configuration issue of my server. I did not have cURL installed. I found this out by using the Core Control plugin. I installed cURL by using the command
sudo apt-get install php5-curl as I am using Debian.

I know it is outside of the plugins remit, but I was wondering if you’re expertise may be able to help. I am still getting errors when trying to browse the plugin directory. I also noticed I get errors on the Dashboard where it states:

RSS Error: WP HTTP Error: There are no HTTP transports available which can complete the requested request.

I thought that one I had resolved the issue with cURL that this would no longer be an issue. I have tried searching forums for a solution to this and am yet to find one. I don’t suppose you would be able to shed any light on the issue?

Kind Regards

Haydn

Hi Haydn,

No problem at all, I will always help where I can.

That particular error message “There are no HTTP transports available which can complete the requested request.” occurs when WP cannot detect compatibility with either of the 3 methods for making HTTP calls supported.

cURL: if ( ! function_exists( ‘curl_init’ ) || ! function_exists( ‘curl_exec’ ) ) return false;
Sockets: if ( ! function_exists( ‘fsockopen’ ) ) return false;
Streams: if ( ! function_exists( ‘fopen’ ) ) return false;

You can see the code for the HTTP API in the /wp-includes/class-http.php file. There is more to the checking than I pasted above.

A possibility is that all three methods check that if SSL is enabled for the admin, that openssl is installed. If not they all return false, perhaps this is a possibility as I find it hard to believe none of these options are available/working.

Hi Peter,

Thanks for the quick reply.

I worked out why the RSS feeds hadn’t populated. I was just refreshing the page (after clearing my browsers cache) which didn’t seem to work. To fix this I needed to physically click the configure link next to each affected feed on the dashboard in order for the areas to populate. So this issue is now resolved. Thanks for your help.

Even though this is resolved, the plugin directory still doesn’t work. When I try to browse the plugin directory I get the error:

An unexpected error occurred. Something may be wrong with www.ads-software.com or this server’s configuration. If you continue to have problems, please try the support forums.

Looking at Core Control, it shows under External HTTP access that PHP fsockopen() is not available. I have tried looking up how to enable this and have not found anything that has worked. Do you know how I would achieve this?

Even more strangely, the Twitter widget is now saying there are no tweets to display even though it’s connected to an account and there are tweets to display. I tested changing the account and it worked fine. I removed the app access to the account that wasn’t working on the main twitter site and re-set it up. Unfortunately this did not work. Any ideas?

Kind Regards

Haydn

Hi Haydn,

I think configuring the RSS feeds simply refreshed the feeds cache, so whatever change you last made had fixed it.

It appears that there are still some server configuration errors, but this isn’t really my strong point. I have not run into these sorts of problems before (luckily).

The Twitter widget breaking is frustrating. Just to check it is a specific Twitter account which doesn’t work? This sort of problem is usually down to the Tweets data getting corrupted, caused by character encoding or un-zipping issues, etc. Would you be able to send me a link to the account in question please?

I am out for the evening so probably won’t be able to look into this further until tomorrow morning, sorry.