Codeigniter Command line error - PHP Fatal error: Class 'CI_Controller' not found

Question

After following the user guide instructions found here: http://ellislab.com/codeigniter/user-guide/general/cli.html I'm unable to run the test script via command line.

My controller located at /var/www/mysite/application/controllers/

class Tools extends CI_Controller
{    
    public function message($to = 'World')
    {
        echo "Hello {$to}!".PHP_EOL;
    }
}

In my browser, I can access

http://mysite/tools/message/ben

And the function correctly outputs "Hello ben"

From terminal I should be able to run:

$ php index.php tools message "Ben"

My terminal should print: "Hello Ben"

However I get the following error:

PHP Fatal error: Class 'CI_Controller' not found in /var/www/mysite/system/core/CodeIgniter.php on line 233

My server is pretty standard; ubuntu LAMP. Codeigniter is pretty standard too and I have no problem running non CI scripts via command line

My PHP binary is only located in /usr/bin/php <-- This post suggests an issue running CI directly from usr/bin/php, however I'm not operating a shared PHP service, and I don't see why this would make a difference to how PHP executes a CI script.

I take it you are running the script from /var/www/mysite/ ? — devrooms
– devrooms, Commented Mar 4, 2013 at 19:15
Yes, otherwise I would immediately get a "Could not open input file" error. — Mijahn
– Mijahn, Commented Mar 5, 2013 at 10:07
I received this unhelpful error when there was a problem with connecting a postgres database with a docker container. I was unable to create a connection in PgAdmin. Upon reviewing the status of postgres in Docker, it was constantly spinning and never resolved (but Mongo did). — mickmackusa
– mickmackusa ♦, Commented Apr 1 at 2:34

Mijahn · Accepted Answer · 2013-03-28 18:52:03Z

13

Solved! (partly) the issue was CodeIgniters error logging.

In application/config/config.php, I modified the following config property:

$config['log_threshold'] = 0;

This disables logging, and allows $ php index.php to execute.

If anyone can explain why CI only shows this error on CLI PHP - might help anyone else who has this issue and needs it resolved with error logging on.

answered Mar 28, 2013 at 18:52

Mijahn

4311 gold badge4 silver badges12 bronze badges

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

Comments

James John McGuire 'Jahmic' · Accepted Answer · 2023-09-21 07:13:12Z

11

This error is often due to not being able to connect to the database. Yes, indeed, judging by the error message, they have nothing to do with each other. Nevertheless, this seems to be first visible error that comes up, when the framework is unable to connect to the database.

So, to solve the error "Class 'CI_Controller' not found", as a starting point, review your database settings (Application -> Config -> database.php), such as *hostname*, *username*, *password* and *database* and see if they are correct and if you can connect manually.

edited Sep 21, 2023 at 7:13

James John McGuire 'Jahmic'

12.8k11 gold badges78 silver badges84 bronze badges

answered Jun 25, 2015 at 13:32

sanjeev goel

1011 silver badge2 bronze badges

4 Comments

arghtype Over a year ago

I understand, that you haven't had enough reputation to post comments yet, but this answer really looks like one. Try adding more details into it.

hi0001234d Over a year ago

@sanjeev goel You are pointing us at right direction, but it takes me one hour to understand and figure out that whole thing. In my case problem is due to db driver of CI, since DB on local server was deleted by team developer so CI is giving this error. But obviously error from CI is not understandable.

Refnaldi Hakim Over a year ago

right.. see you configuration database. database name, username and password must match.

Junior_swashluv Over a year ago

Hi, this is true, please check you have the right database, the right username and password and if all this is correct then you can try to export your database, drop the existing one and create another one then import your db back, remember to change the name in database.php if you changed it in database

dxhans5 · Accepted Answer · 2013-10-16 00:10:50Z

3

To Mijahn:

I had this same problem, and after about two hours of tracing through code to figure out the problem, it seems that there is some sort of conflict with loading the CI_Controller when utilizing the native PHP load_class function.

I worked around this issue by making the following changes to the Common.php file (hack, I know).

//$_log =& load_class('Log');
require_once('system/libraries/Log.php');
$_log = new CI_Log();

My logs then where created exactly like I wanted. Hope this hack helps.

answered Oct 16, 2013 at 0:10

dxhans5

1271 silver badge12 bronze badges

1 Comment

sp00n Over a year ago

For me it wasn't the Log class myking problems but the exception handler in Common.php So I had to change the loading of the Exceptions class accordingly:

// $_error =& load_class('Exceptions', 'core');     require_once('system/core/Exceptions.php');     $_error = new CI_Exceptions('core');

Motomotes · Accepted Answer · 2013-03-04 21:10:45Z

0

This site says to run codeigniter from the command line, one must set the $_SERVER['PATH_INFO'] variable.

$_SERVER['PATH_INFO'] is usually supplied by php when a web request is made. However, since we are calling this script from the command line, we need to emulate this small part of the environment as a web request.

answered Mar 4, 2013 at 21:10

Motomotes

4,2471 gold badge28 silver badges25 bronze badges

1 Comment

Mijahn Over a year ago

Thanks, in the link its using a PHP doc outside the CI application folder, and loads CI by including index.php. I need to run commands on a CI controller within my application. I did change my $config['uri_protocol'] = "PATH_INFO", but still have the same issue.

Community · Accepted Answer · 2017-05-23 12:34:47Z

0

The answer provided in this Stack Overflow post worked for me.

Within system/core/CodeIgniter.php, on around line 75, change:

set_error_handler('_exception_handler');

to...

set_exception_handler('_exception_handler');

Other users have reported that this gave them a better backtrace with which to debug the underlying issue, but for me, this actually removed the problem altogether.

edited May 23, 2017 at 12:34

CommunityBot

11 silver badge

answered Dec 12, 2016 at 10:44

sevenpointsix

4046 silver badges4 bronze badges

Comments

Alex freire · Accepted Answer · 2024-11-16 07:09:09Z

-1

1 - Check disk space. Most of the time is caused for lower disk space. Clean up logs and free space.

2 - Restart the Mysql server (after cleaning space)

2 - downgrade your php version to 7.4

answered Nov 16, 2024 at 7:09

Alex freire

11 bronze badge

3 Comments

Community Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

Nico Haase Over a year ago

After all, the third point makes your answer pretty useless. No current application should use PHP 7.4 anymore

mickmackusa Apr 1 at 2:37

There will certainly be developers in the world who are stuck in PHP7.4 because their application is stuck in CI3.1.11 (at most). If you have one or more dependencies which are not compatible with more modern versions, you have to suffer outdated versions of the language and/or the framework. The CI3.1.11 & PHP7.4 ceiling is probably the point when most people move to Laravel.

Collectives™ on Stack Overflow

Codeigniter Command line error - PHP Fatal error: Class 'CI_Controller' not found

6 Answers 6

Comments

4 Comments

1 Comment

1 Comment

Comments

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

Comments

4 Comments

1 Comment

1 Comment

Comments

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related