Relative path not working in cron PHP script

Question

If a PHP script is run as a cron script, the includes often fail if relative paths are used. For example, if you have

require_once('foo.php');

the file foo.php will be found when run on the command line, but not when run from a cron script.

A typical workaround for this is to first chdir to the working directory, or use absolute paths. I would like to know, however, what is different between cron and shell that causes this behavior. Why does it fail when using relative paths in a cron script?

This is a great resource as well: stackoverflow.com/questions/2857712/… — Ben
– Ben, Commented May 18, 2010 at 14:03
Don't change your PHP files just to make them work from a cron job, instead change the current directory on the cron job line. Check my answer here. — Accountant م
– Accountant م, Commented Apr 9, 2019 at 20:32

TazGPL · Accepted Answer · 2014-04-12 17:30:42Z

112

Change the working directory to the running file path. Just use

chdir(dirname(__FILE__));
include_once '../your_file_name.php'; //we can use relative path after changing directory

in the running file. Then you won't need to change all the relative paths to absolute paths in every page.

edited Apr 12, 2014 at 17:30

TazGPL

3,7442 gold badges41 silver badges60 bronze badges

answered Jul 30, 2011 at 5:56

Withfriendship Hiox

1,3072 gold badges8 silver badges6 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Andy Davies Over a year ago

This was driving me mad. This sorted it out perfectly

You Old Fool Over a year ago

You can also use chdir(__DIR__); which is a bit more concise.

aequalsb Over a year ago

this only works if you can execute chdir() in your environement. include/require dirname( __FILE__ ) is much more reliable.

Accountant م Over a year ago

I don't like to change the PHP code, instead change the directory at the cron tab, check my answer

Sjoerd · Accepted Answer · 2010-01-14 13:58:41Z

14

The working directory of the script may be different when run from a cron. Additionaly, there was some confusion about PHPs require() and include(), which caused confusion about the working directory really being the problem:

include('foo.php') // searches for foo.php in the same directory as the current script
include('./foo.php') // searches for foo.php in the current working directory
include('foo/bar.php') // searches for foo/bar.php, relative to the directory of the current script
include('../bar.php') // searches for bar.php, in the parent directory of the current working directory

answered Jan 14, 2010 at 13:58

Sjoerd

75.9k16 gold badges140 silver badges180 bronze badges

Comments

Sjoerd · Accepted Answer · 2012-08-30 08:35:43Z

7

The only chance I got "require_once" to work with cron and apache at the same time was

require_once(dirname(__FILE__) . '/../setup.php');

edited Aug 30, 2012 at 8:35

Sjoerd

75.9k16 gold badges140 silver badges180 bronze badges

answered Aug 30, 2012 at 8:02

jansch

711 silver badge2 bronze badges

Comments

aequalsb · Accepted Answer · 2015-05-27 21:33:48Z

Because the "current working directory" for cron jobs will be the directory where your crontab file exists -- so any relative paths with be relative to THAT directory.

The simplest way to handle that is with dirname() function and PHP __FILE__ constant. Otherwise, you will need to edit the file with new absolute paths whenever you move the file to a different directory or a server with a different file structure.

dirname( __FILE__ )

__FILE__ is a constant defined by PHP as the full path to the file from which it is called. Even if the file is included, __FILE__ will ALWAYS refer to the full path of the file itself -- not the file doing the including.

So dirname( __FILE__ ) returns the full directory path to the directory containing the file -- no matter where it is included from and basename( __FILE__ ) returns the file name itself.

example: Let's pretend "/home/user/public_html/index.php" includes "/home/user/public_html/your_directory/your_php_file.php".

If you call dirname( __FILE__ ) in "your_php_file.php" you would get "/home/user/public_html/your_directory" returned even though the active script is in "/home/user/public_html" (note the absence of the trailing slash).

If you need the directory of the INCLUDING file use: dirname( $_SERVER['PHP_SELF'] ) which will return "/home/user/public_html" and is the same as calling dirname( __FILE__ ) in the "index.php" file since the relative paths are the same.

example usages:

@include dirname( __FILE__ ) . '/your_include_directory/your_include_file.php';

@require dirname( __FILE__ ) . '/../your_include_directory/your_include_file.php';

John Parker · Accepted Answer · 2009-12-28 13:13:51Z

3

Another possibility is that the CLI version is using a different php.ini file. (By default, it'll use php-cli.ini and fallback to the standard php.ini)

Also, if you're using .htaccess files to set your library path, etc. this obviously won't work via the cli.

answered Dec 28, 2009 at 13:13

John Parker

54.5k11 gold badges133 silver badges131 bronze badges

Comments

You Old Fool · Accepted Answer · 2015-02-01 19:03:46Z

3

In addition to the accepted answer above, you can also use:

chdir(__DIR__);

answered Feb 1, 2015 at 19:03

You Old Fool

23.2k14 gold badges92 silver badges119 bronze badges

3 Comments

aequalsb Over a year ago

only if you are allowed to execute chdir() in the environment you're in

You Old Fool Over a year ago

is that common? I've never worked in any environment where that function wasn't allowed.

aequalsb Over a year ago

i have experienced it related to PHP safe_mode. php.net/manual/en/features.safe-mode.functions.php, but this has been deprecated php.net/manual/en/features.safe-mode.php. -- that's deprecated not removed... meaning, it could still be encountered.

Jan Hančič · Accepted Answer · 2009-12-28 13:06:33Z

2

When executed trough a cron job your PHP script probably runs in different context than if you start it manually from the shell. So your relative paths are not pointing to the right path.

answered Dec 28, 2009 at 13:06

Jan Hančič

54k17 gold badges99 silver badges101 bronze badges

2 Comments

mauris Over a year ago

that's right. In fact, the script's working directory is the working directory of the shell. Should use absolute pathnames.

aequalsb Over a year ago

absolute path names are a nightmare to manage as you move files around... just use dirname( __FILE__ )

Jordan Rumpelstiltskin Nemrow · Accepted Answer · 2013-01-28 00:19:18Z

0

The DIR works although it will not work on my localhost as it has a different path than my live site server. I used this to fix it.

    if(__DIR__ != '/home/absolute/path/to/current/directory'){ // path for your live server
        require_once '/relative/path/to/file';
    }else{
        require_once '/absolute/path/to/file';
    }

answered Jan 28, 2013 at 0:19

Jordan Rumpelstiltskin Nemrow

3824 silver badges5 bronze badges

1 Comment

aequalsb Over a year ago

still using a conditional statement that can be replaced by dirname( __FILE__ )

Collectives™ on Stack Overflow

Relative path not working in cron PHP script

8 Answers 8

4 Comments

Comments

Comments

Comments

Comments

3 Comments

2 Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

8 Answers 8

4 Comments

Comments

Comments

Comments

Comments

3 Comments

2 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related