Hi, and thank you for answering so quick.

Originally Posted by
cPanelTristan
Hello,
We are going to need to see the section of code that is calling this error if that is available. Also, no part of the error message other than the username has been modified, right? Meaning the end port where it has "(0) in [...]" is exactly how the error appears? We need the full error message or messages if possible with only the username changed to minimize possible issues with modifying the error message making it difficult to troubleshoot effectively.
I have only edited the username. The error-message actually says the path is (0).

Originally Posted by
cPanelTristan
Next, what are the permissions settings on the file being included?
All of the files are owned by username:username, and has permissions set to -rw-r--r--.

Originally Posted by
cPanelTristan
Finally, have you tried copying the custom script to another account to see if it has the same issue such as a test account? Just to ensure the user hasn't modified some setting on their account that might be causing it? People can actually setup individual php.ini files and change settings under CGI, although it isn't as straightforward to do so (as it is under suPHP anyway). I cannot discount the possibility that the user setup their own php.ini to work under CGI and didn't change some setting that is causing this to happen.
Thanks.
I've checked the settings for the user, and I can't see any changes. And if the user made a change to it's own php.ini, the file would be created inside the home directory somewhere? Because there is no php.ini..
The code
PHP Code:
define ('dir_root', '/home/username/public_html');
require 'include/somefile.php';
require_once 'include/someotherfile.php';
Seems like normal require/include-code to me...
The problem might be in the customers code (can you define basedir-options directly in php?), but I want to figure this out fast, and hopefully rule out any error on our side