fopen: Connection failed! since upgrading to 1.6.6

[lemonaid]

Since upgrading to 1.6.6 and, subsequently,  php 5.(something)  the System Information on my CMSMS  sites tells me that
fopen: Connection failed!

No such warning shows on a phpinfo check.


I've asked the host to check on this and they tell me:

fopen can be used to open system paths, eg fopen("/home/mysite/public_html/textfile.txt"); or it can be used to open web URLs, eg fopen("http://mysite.com.au/textfile.txt"); - the first method is allowed, but for security reasons, the second method is not allowed. Please check your code and make sure you're not using the second method.

Can anyone suggest what might be happening and if it will cause problems with my CMSms sites. 

Thanks

[lemonaid]

This problem specifically happens after upgrading any CMSms powered site to PHP 5.2.10 - which I need to do in order for Calguy's latest module releases to work.

Anybody else have this issue?

[Jeff]

This problem specifically happens after upgrading any CMSms powered site to PHP 5.2.10 - which I need to do in order for Calguy's latest module releases to work.

Anybody else have this issue?

fopen is used in check the main site (cmsmadesimple.org) for update and possibly in some e-comm payment gateways.

It is a issue you need to take up with your hoster, but in the mean time understand that some functionality that requires remote checking may not work.

[lemonaid]

Thanks for your reply, but as I said in the original post it doesn't show when checking the host with a info.php check.

It tells me:

allow_url_fopen    local value ON  master value ON

[Jeff]

That is out side of CMSms what your hoster stated matches the results in the CMSms test. If you really want to know how it is being block when phpinfo() says it is ON as your hoster they are the ones blocking it not us.

As I have stated before --- IT IS AN HOSTING ISSUE.

[lemonaid]

I appreciate you assisting me ajprog and there really is no need to yell.    I'm simply trying to gather enough information to take back to my host.

I understand now that it is the web URLs that are required by CMSms and that is what is causing the error message.