RSS fetch error

[francistill]

I'm a complete novice. I'm trying to put some RSS feeds into my site and regardless of where I fetch them from (URI) or what skin I'm using, the display contains this error:

Error on line 127 of /home/content/c/o/m/comwebsite/html/serendipity/bundled-libs/Onyx/RSS.php: The specified file could not be opened.

Any ideas?

[francistill]

The file RSS.php appears to be located in the proper folder, btw.

[judebert]

Does it have the correct permissions (0755, most likely)? Can you compare its size to the size of the same file in the original tarball?

[francistill]

It's a godaddy install -- comes with the website hosting plan -- so I've not seen the original code. I've given the file and folder full permissions and tried both charset settings, but no go. Same error. To see the error live: http://francistill.com/serendipity/ LIne 127 in the file, if that's where the error is, appears to deal with cache clearing

[francistill]

downloaded, the filesize is 12.2kb

[garvinhicking]

The problem is NOT the Onyx RSS file! Onyx reports an error that the RSS feed you specified could not be opened!

So either you entered a wrong URL without http://..., or the Server is down, OR your provider is blocking outgoing requests from your server via firewall...

Regards,
Garvin

[francistill]

Well, the server isn't down, the URLs were properly configured and the tool is included with the godaddy hosting plan -- so I'd be surprised if they disabled just that function. You're saying the error message is referring to the URL's package when it says "file" -- which is an interpretation I can grasp (although it wasn't my first understanding), but among the many URLs that I tried were several from Google News, which don't seem to have much problem in other fetch situations. Perhaps there's another module I could use for this purpose somewhere?

[garvinhicking]

What URL exactly did you enter?

It is very common that mass-hosting providers disable remote URL functionality.

Best regards,
Garvin

[francistill]

I'm coming to the conclusion that may be what's going on here. I'll ask godaddy if they're blocking. Bummer, if so. Here's one of the feed URLs I tested -- one that's worked in other readers: http://news.google.com/news?ned=nz&topic=h&output=rss

[judebert]

Sorry to reopen this. We've had some trouble in the past with special characters in URLs. Different plugin, I think, but perhaps the same idea applies. Try using:

Code: Select all

http://news.google.com/news?ned=nz&topic=h&output=rss

as the URL instead of the version with ampersands.

If you've got some spare time, anyway.

[francistill]

no, sorry to keep bugging you, but that didn't work. I did get a reply from the GoDaddy help desk but I have no idea what it means, being a PHP novice. Here it is:

We do not block PHP RSS fetching. The only requirement to be able to do so is the ability to get a page from an external website. This can be done using PHP if the destination site runs on port 80 or port 443. You will need to use our proxy server in order to grab data from an external website.

The IP of our proxy server is 64.202.165.130 and the port 3128. If you are using using cURL with PHP will need to include the following lines on each script that utilizes cURL functions.


curl_setopt ($ch, CURLOPT_HTTPPROXYTUNNEL, TRUE);
curl_setopt ($ch, CURLOPT_PROXYTYPE, CURLPROXY_HTTP);
curl_setopt ($ch, CURLOPT_PROXY, http://64.202.165.130:3128);
curl_setopt ($ch, CURLOPT_SSL_VERIFYPEER, FALSE);

So, the question is, am I using cURL with PHP in this module? And if so, where in the module should I set these additions?

[garvinhicking]

Serendipity does not use cURL, we use the PEAR HTTP/Request module.

If you edit your file bundled-libs/HTTP/Request.php you can change this code:

Code: Select all

        $this->_proxy_host = null;
        $this->_proxy_port = null;
        $this->_proxy_user = null;
        $this->_proxy_pass = null;

into this:

Code: Select all

        $this->_proxy_host = '64.202.165.130';
        $this->_proxy_port = '3128';
        $this->_proxy_user = null;
        $this->_proxy_pass = null;

HTH,
Garvin

[francistill]

Sadly, this is an implementation carried out by GoDaddy. I don't have the modules to edit. I guess I have to give up on Serendipity. But since Serendipity is a value add module GoDaddy implements and since GoDaddy is the biggest web host on the horizon, maybe someone among the developers should have a chat with the GoDaddy team to make this module -- and there's not much of an alternative to THIS module for this very critical function on offer -- work. Or else promote a module that will work in a GoDaddy environment.

[francistill]

Sadly, this is an implementation carried out by GoDaddy. I don't have the modules to edit. I guess I have to give up on Serendipity. But since Serendipity is a value add module GoDaddy implements and since GoDaddy is the biggest web host on the horizon, maybe someone among the developers should have a chat with the GoDaddy team to make this module -- and there's not much of an alternative to THIS module for this very critical function on offer -- work. Or else promote a module that will work in a GoDaddy environment.

[garvinhicking]

Hi!

It's not a problem to install your own Serendipity on a Godaddy host!

Sadly we do not have ressource to work with every hoster that implements serendipity, so we can only offer and give full support for usual Serendipity installations made by users.

You, as a godaddy.com customer, could contact their support though and tell them, that this situation is a bit frustrating, to have a HTTP proxy requirement and that they should think about patching the PEAR library like I mentioned?

Best regards,
Garvin