Link Manager 3.0 Support Thread

[jabbawest]

Sorry, forgot to add this error to the first issue.
Warning: file(http://mysticmountainnaturals.com/demotest) [function.file]: failed to open stream: no suitable wrapper could be found in D:\Hosting\*******\html\admin************\links.php on line 615

[clydejones]

This is a fresh install of your latest version.
Couple of issues.
1. The following error when using Check Links:

Warning: file() [function.file]: URL file-access is disabled in the server configuration in D:\Hosting\*******\html\admin**********\links.php on line 615

Should I just create a file named funtion.file and put it in my /admin directory? OR could this be something that needs to be adressed with .htaccess?

2. The following SQL complaints.
ERROR: Cannot insert configuration_key "IH_VERSION" because it already exists
Error ERROR: Cannot insert configuration_key "IH_VERSION" because it already exists
Warning Note: 1 statements ignored. See "upgrade_exceptions" table for additional details

Would IH_VERSION refer to Image Handler?

Other than that, the module seems to be working just fine.
Nice work and I appreciated the order steps mod too.

Sorry, forgot to add this error to the first issue.
Warning: file(http://mysticmountainnaturals.com/demotest) [function.file]: failed to open stream: no suitable wrapper could be found in D:\Hosting\*******\html\admin************\links.php on line 615

ERROR: Cannot insert configuration_key "IH_VERSION" because it already exists
This can safely be ignored (It just means that that particular table row already exists)

Warning: file() [function.file]: URL file-access is disabled in the server configuration

As the error message states - this is a server issue. You will need to contact your hosting provider to correct this issue.

[jabbawest]

As the error message states - this is a server issue. You will need to contact your hosting provider to correct this issue.

Well, a little searching found that this needs to be allowed in the php.ini file by adding the following.
allow_url_fopen = On;
allow_url_include = On;

More research suggests that doing this would allow a huge opening for DoS attacks and scripting injections both of which I'm quite familiar with from running php-nuke sites. Back then I was able to install a security module that would automatically ban anyone trying hack into my sites.

Any opinions about this, or maybe it should be a new topic in the security forum?

Thanks