{"id":27123,"date":"2025-07-24T12:54:49","date_gmt":"2025-07-24T07:24:49","guid":{"rendered":"https:\/\/www.webwingz.com\/?p=27123"},"modified":"2025-07-24T12:54:49","modified_gmt":"2025-07-24T07:24:49","slug":"php-wall-failed-to-open-stream","status":"publish","type":"post","link":"https:\/\/www.webwingz.com\/blog\/php-wall-failed-to-open-stream\/","title":{"rendered":"Cron Job Fails? Avoid PHP Include Path Pitfalls in CLI Scripts"},"content":{"rendered":"\n

My Intern Hit a PHP Wall \u2014 Here’s How We Fixed It Together<\/strong><\/h2>\n\n\n\n

It started with a Slack message from our intern:<\/p>\n\n\n\n

\u201cI think I broke the script. It worked yesterday, but now it\u2019s throwing fatal errors!\u201d<\/p>\n\n\n\n

I smiled. These are the moments I look forward to \u2014 not because things are broken, but because they\u2019re teachable.<\/p>\n\n\n\n

The script in question was a PHP cron job. Simple task: send invoice emails automatically. But when our intern tried to run it from the command line, he was greeted with a screen full of errors like:<\/p>\n\n\n\n

PHP Warning: include(..\/..\/model\/InvoiceEmail_model.php): Failed to open stream…<\/p>\n\n\n\n

PHP Fatal error: Uncaught Error: Class “Base_Controller” not found…<\/p>\n\n\n\n

It\u2019s a common issue in PHP projects \u2014 especially with cron jobs or command-line scripts.
So I sat down with our intern and we solved it together, step by step.<\/p>\n\n\n\n

Here\u2019s what we learned \u2014 and how you can fix this issue for good.<\/p>\n\n\n\n

The Real Problem: Relative Paths & CLI<\/strong><\/h2>\n\n\n\n

PHP was trying to include files like this:<\/p>\n\n\n\n

include('..\/..\/config\/config.php');\ninclude('..\/..\/model\/InvoiceEmail_model.php');\ninclude('..\/..\/libraries\/autoload.php');<\/code><\/pre>\n\n\n\n
These worked fine when run via a web request. But in the CLI environment \u2014 especially within a chroot \u2014 PHP didn’t know where to find these paths.<\/p>\n\n\n\n
Why?<\/p>\n\n\n\n
Because relative paths are resolved from the current working directory<\/strong>, not from the file that contains the include().<\/p>\n\n\n\n
So when our intern ran:<\/p>\n\n\n\n
php api\/controller\/cron\/invoices.php<\/code><\/pre>\n\n\n\n
PHP looked for ..\/..\/model\/InvoiceEmail_model.php relative to the terminal’s current directory<\/strong>, not relative to invoices.php.<\/p>\n\n\n\n
The Solution: Meet <\/strong>__DIR__<\/strong><\/h2>\n\n\n\n
I introduced our intern to a PHP superpower: the __DIR__ constant.
It always points to the directory of the current file \u2014 no matter how or where the file is executed.<\/p>\n\n\n\n
We changed:<\/p>\n\n\n\n
include('..\/..\/model\/InvoiceEmail_model.php');<\/code><\/pre>\n\n\n\n
To:<\/p>\n\n\n\n
include(__DIR__ . '\/..\/..\/model\/InvoiceEmail_model.php');<\/code><\/pre>\n\n\n\n
Now the path is always correct, whether you run the script from your root directory, a cron job, or a chrooted environment.<\/p>\n\n\n\n
Problem solved instantly.<\/p>\n\n\n\n
How We Refactored the Codebase<\/strong><\/h2>\n\n\n\n
To make this bulletproof, we updated all relevant files.<\/p>\n\n\n\n
Step 1: Base Path (Optional)<\/strong><\/h3>\n\n\n\n
We could\u2019ve added a constant like:<\/p>\n\n\n\n
define('APPROOT', dirname(__DIR__, 2));<\/code><\/pre>\n\n\n\n
Then use:<\/p>\n\n\n\n
include(APPROOT . '\/model\/InvoiceEmail_model.php');<\/code><\/pre>\n\n\n\n
But for simplicity, we just stuck to __DIR__.<\/p>\n\n\n\n
Step 2: Updated All Includes<\/strong><\/h3>\n\n\n\n
We walked through:<\/p>\n\n\n\n