Grrrr - completely hijacked thread!!
Anyway… @matto98 Let’s deal with your problem as it is the reason for this thread existing. The error is almost certainly due to some form of malformed path…so let’s identify what that path is, so we can locate the cause.
The error is occurring in the clean _path function. We want to know what the path is that suiteCRM is trying to clean, and then go and look at that path and sort out the problem.
In order to do this, we are going to edit some code. (REMEMBER TO CHANGE IT BACK AFTER YOU HAVE FINISHED!!!)
File that we are going to edit is:
C:\xampp\htdocs\CRM\include\utils\file_utils.php
and the function is clean_path. It will look something like this:
53 function clean_path($path)
54 {
55 // clean directory/file path with a functional equivalent
56 $appendpath = '';
57 if (is_windows() && strlen($path) >= 2 && $path[0].$path[1] == "\\\\") {
58 $path = substr($path, 2);
59 $appendpath = "\\\\";
60 }
61 $path = str_replace("\\", "/", $path);
62 $path = str_replace("//", "/", $path);
63 $path = str_replace("/./", "/", $path);
64 return($appendpath.$path);
65 }
The numbers on the left are my line numbers from a recent 7.10.x version, so should be pretty similar to yours. If they’re slightly different, then don’t worry.
Remember to make a backup copy of this file before you edit it, if this sort of thing is new to you.
You want to add the line:
LoggerManager::getLogger()->error('The path is: '. $path." :path[0] is: ‘.$path[0].’ :path[1] is: '.$path1);
between line 55 and 56.
You will then be able to inspect the suiteCRM logs, and the last ‘The path is:’ message before your Fatal error will be the one that lists your malformed path.
Additional resources for you:
- SuiteCRM logging:
https://docs.suitecrm.com/developer/logging/ - In order to change the logging level you need to change Admin->System Settings->Log level to at least the error level for this debug message to be shown.
Once you have identified and corrected the malformed path/filename, remember to remove/comment out the line, and change your logger level back to whatever you have chosen for your system.
If this identifies the problem for you, then please post back what the malformed path looked like so that others can learn from your experience. Good luck 