CodeIgniter-Multiple Sub Class Prefix

It´s too late but the right answer for me was to extend the CI_controller or MY_controller class, as you want, into the same file.. (sorry about my english)

application/core/MY_controller.php

<?php

if (!defined('BASEPATH'))
    exit('No direct script access allowed');

class MY_Controller extends CI_Controller {
   ...
   ...
   ...
}

class Admin_Controller extends CI_Controller{
   ...
   do what you need
   ...
}

?>

I saw this answer in another post (can´t remember) and I solved my problem

I have some tricks. I set a new configuration 'loading-cores' on config.php. You can set the config name whatever you want.

$config['loading-cores'] = array(
    "load-my-cores" => TRUE,
    /* core class(es) to be loaded, note: must be a php file type */
    "my-cores" => ["APIResponder", "Anotherclass"]
);

my classes in core folder:

• APIResponder.php
• Anotherclass.php

Then open file ..system/core/CodeIgniter.php, try to find this snippet code:

if (file_exists(APPPATH.'core/'.$CFG->config['subclass_prefix'].'Controller.php')){
        require_once APPPATH.'core/'.$CFG->config['subclass_prefix'].'Controller.php';}

Add lines of codes below to load your core classes, place it right after the snippet code above:

if(isset($CFG->config['loading-cores'])){
    if($CFG->config['loading-cores']['load-my-cores'] && count($CFG->config['loading-cores']['my-cores']) > 0){
        foreach ($$CFG->config['loading-cores']['my-cores'] as $core) {
            if (file_exists(APPPATH."core/{$core}.php")){
                require_once APPPATH."core/{$core}.php";
            }
        }
    }
}

Set "load-my-cores" => FALSE if you don't need the core classes to be loaded.

You can only have one prefix.

What you're trying to do sounds like extending, You wish to extend an existing controller to do other stuff.

Don't forget that a controller is not just an abstract element, it's part of the MVC framework you're using.

the 'base' controller should not be specific(for example, adminController), it should be as general as possible and do 'controller' stuff(load views, load all your models etc.)

Let's say you have a users controller, an admin is a type of user, so it should extend the users model. This prevents you from doubling your code as admins should do at least some of the stuff users are doing. Just an example.

Short answer: not without tweaking the core

Long answer: you can hack your way around by adding a hook in /system/core/CodeIgniter.php, which will load your new controller before any others are loaded. Here's how I've done it:

(note that I use MY_Controller for the admin controllers and MY_Basecontroller for the regular ones):

1. Step one - you add this line to /system/core/CodeIgniter.php, line 241 - see exactly where:

   $EXT->_call_hook('pre_local_controller');
   

   You must do this just before loading the local controller, otherwise it will not work.

2. Step two - add the following code to /application/config/hooks.php:

   $hook['pre_local_controller'][] = array(
                            'class'    => 'Hooks',
                            'function' => 'loadCore',
                            'filename' => 'Hooks.php',
                            'filepath' => 'hooks',
                            'params'   => 'MY_Basecontroller.php'
   );
   

3. Step three - create a file /application/hooks/Hooks.php and put the following code inside:

   class Hooks
   {
       public function loadCore($class)
       {
           require_once(APPPATH . 'core/' . $class);
       }
   }
   

4. Step four - profit

Now your classes can extend from the class MY_Basecontroller which resides in /application/core/MY_Basecontroller.php. Obviously, don't forget it should extend CI_Controller

It's still not exactly 'multiple subclass prefix' - actually it doesn't have anything to do with it, but will do what you asked for.

Tweak to your liking and go wild.

Cheers.