Ionize - Free & Open Source creative CMS

[eluser]BrianDHall[/eluser]
[quote author="Too Pixel" date="1258422911"]That's where you should consider just update the Codeigniter.php file instead of trying to hack Ionize. it's just 5 lines to change, not a big deal, just not forget do it after an update of CI's core.

I really hope one day they will make possible to hack the core like we can hack the other libs...[/quote]

OK, jeesh, how about a 1 liner?

Don't know if the function is used elsewhere, but here is the fetch_controller_path() with the return value changed and 1 additional line - of course renamed to what CI expects:

Code:

public function fetch_directory()
    {
        // Fix for CodeIgniter's hard-coded routing path
        $dots = preg_replace('/\w+(\/)/', '..\1', APPPATH) . '../';
        
        if($this->module_path)
        {
            $path = $this->config->item('module_path') . $this->module_path . '/';
        }
        else
        {
            $path = APPPATH;
        }

        return $dots . $path . 'controllers/' . ($this->directory ? $this->directory . '/' : '');
    }

Can't be any more simple a solution than that to avoiding a core hack.

I'm big on no core hacks because if it is going to use CI I want it to work on the same base all my other applications run on. One common codebase to maintain, so when I have to hack, fix, or extend something in the core I don't have to worry about other applications and their changes - just mine.