Error Message after sending E-Mail through contact form (3.6)

[buzzdee]

Hi,

after sending an e-Mail through the contact form, this error message shows up:

Warning: curl_setopt(): CURLOPT_FOLLOWLOCATION cannot be activated when an open_basedir is set in /var/www/web97/html/buzzpics/lib/G/functions.php on line 1329

Screenshot:

Is it because my hoster did not set open_basedir = off ?

 

[evilmoe2]

No hoster in this world will set open_basedir = off .
I saw the error too in my server logs but I did not find a solution for it yet.

 

[Rodolfo]

Chevereto needs PHP 5.4 with standard libraries and settings. The error described is at PHP level, not script level and is happening because you have safe_mode=on and no one running 5.4.0+ should have that thing enabled (unless of course all the dir restrictions are tweaked).

In other words, you have safe_mode=on and since 5.4.0 that is obsolete because things like this happens. http://php.net/manual/en/features.safe-mode.php

 

[evilmoe2]

Safe mode is off on my server.

[Wed Apr 01 22:45:34 2015] [warn] [client 199.xxxxxxx] mod_fcgid: stderr: PHP Warning: curl_setopt(): CURLOPT_FOLLOWLOCATION cannot be activated when an open_basedir is set in /var/www/virtual/your-pictionary.com/htdocs/lib/G/functions.php on line 1389

EDIT: Its strange, I dont know why curl dependens on open_basedir. They are totaly different things.

 

[Rodolfo]

Maybe your curl is outdated

 

[evilmoe2]

root@xxxx:~# curl --version
curl 7.26.0 (x86_64-pc-linux-gnu) libcurl/7.26.0 OpenSSL/1.0.1e zlib/1.2.7 libidn/1.25 libssh2/1.4.2 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap pop3 pop3s rtmp rtsp scp sftp smtp smtps telnet tftp
Features: Debug GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP

Current is 7.41. I am using the offical from the deb respo.

I have disabled warning on my server to avoid this error to users, system is still working fine even with this warning.

 

[Rodolfo]

This line of code:

curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);

Was added in version 3.5.0 so if you didn't have previous issues in 3.5.X series then something changed in your server.

 

[evilmoe2]

I am not sure. I just noticed this warning few days ago. However, its just a warning and everything is working fine.