My hosting provider has just announced that for security reasons they are going to disable the allow_url_fopen function in our PHP installation. I see there are past posts in the forum regarding the fact that disabling allow_url_fopen interferes with the link checkers, but does anyone now if there is any other aspect of the directory that will be effected? Is there anyone out there running WSN Links on a system with allow_url_fopen disabled, who could let me know if their directory runs properly otherwise?
Comments on disabling allow_url_fopen
Member
Usergroup: Customer
Joined: Dec 27, 2003
Total Topics: 9
Total Comments: 18
My hosting provider has just announced that for security reasons they are going to disable the allow_url_fopen function in our PHP installation. I see there are past posts in the forum regarding the fact that disabling allow_url_fopen interferes with the link checkers, but does anyone now if there is any other aspect of the directory that will be effected? Is there anyone out there running WSN Links on a system with allow_url_fopen disabled, who could let me know if their directory runs properly otherwise?
Thanks in advance.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
It affects all spots that try to load a url. That could include link checks, meta description buttons, possibly even html/static generation.
CURL will be supported as of 3.20, and you can replace your geturl() function to make it work in 3.16. It's in filefunctions.php.
Of course, this still requires that your host support CURL if it doesn't support fopen urls.